Sorry for the delayed response.
Strange that I have regenerated workitem when I scroll time frame (related only to the SOP context, maybe that what is slowdown whole process)
Can you please take a look at example hip?
Thanks
Ostap
Found 180 posts.
Search results Show results as topic list.
PDG/TOPs » Scrolling frame range with TOP in SOP context is laggy.
- Ostap
- 209 posts
- Offline
PDG/TOPs » Scrolling frame range with TOP in SOP context is laggy.
- Ostap
- 209 posts
- Offline
Hi,
A simple scene with TOP (including ‘ROP Geometry Output’ node with generated workitem) in SOP context will slow down scrolling frame range. It is not a serious issue but would be nice to know why it is going on and why it is only in SOP context?
(build 17.5.200)
Thanks
Ostap
A simple scene with TOP (including ‘ROP Geometry Output’ node with generated workitem) in SOP context will slow down scrolling frame range. It is not a serious issue but would be nice to know why it is going on and why it is only in SOP context?
(build 17.5.200)
Thanks
Ostap
Edited by Ostap - March 27, 2019 22:40:09
Technical Discussion » Suppress error window
- Ostap
- 209 posts
- Offline
Hi,
When I raise any type of error in callback python script (something similar mentioned in this topic - https://www.sidefx.com/forum/topic/40712/) - I have popup this error window (error running callback).
Is any way to suppress this error window? Like you already did from UI - 'Send future errors to the console"
Best Regards
Ostap
When I raise any type of error in callback python script (something similar mentioned in this topic - https://www.sidefx.com/forum/topic/40712/) - I have popup this error window (error running callback).
Is any way to suppress this error window? Like you already did from UI - 'Send future errors to the console"
Best Regards
Ostap
Technical Discussion » hou.nodeType() not represent all parms.
- Ostap
- 209 posts
- Offline
Hi,
Thanks for response.
I'm not sure that it is a bug.
Looks like they(Sidefx) have some reasons to put there only part of parmTemplate otherwise why they support it from version to version:
Houdini 15 - don't have any additional “onCreate” behavior
Houdini 16 - “onCreate” has $deprecated_ifd_ran with opproperty (which can add properties)
Houdini 16.5 - they remove $deprecated_ifd_ran with opproperty
And question is how to work correctly with ‘mantra’ parmTemplate?
How to add all properties ?
Cheers
Ostap
Thanks for response.
I'm not sure that it is a bug.
Looks like they(Sidefx) have some reasons to put there only part of parmTemplate otherwise why they support it from version to version:
Houdini 15 - don't have any additional “onCreate” behavior
Houdini 16 - “onCreate” has $deprecated_ifd_ran with opproperty (which can add properties)
Houdini 16.5 - they remove $deprecated_ifd_ran with opproperty
And question is how to work correctly with ‘mantra’ parmTemplate?
How to add all properties ?
Cheers
Ostap
Technical Discussion » hou.nodeType() not represent all parms.
- Ostap
- 209 posts
- Offline
Hi all,
I tried to copy all ParmTemplateGroups from “ifd” node to other ROP but it is not work for all properties (build 16.5.268).
In this case you will miss most properties.
I found solution in HScript ‘opproperty’ command which can fill all other properties but looks like it is not the best solution.
Maybe somebody know better solution ?
Cheers
Ostap
I tried to copy all ParmTemplateGroups from “ifd” node to other ROP but it is not work for all properties (build 16.5.268).
current_node=kwargs["node"] rop_t=hou.ropNodeTypeCategory() origin=hou.nodeType(rop_t,"ifd") origin_pt=origin.parmTemplateGroup() current_node.setParmTemplateGroup(origin_pt)
In this case you will miss most properties.
I found solution in HScript ‘opproperty’ command which can fill all other properties but looks like it is not the best solution.
Maybe somebody know better solution ?
Cheers
Ostap
Technical Discussion » OpenCL - global switch to turn off
- Ostap
- 209 posts
- Offline
jlait
To repeat, you do *NOT* need a CPU with a GPU core.
One of the awesome things about OpenCL is that it has a CPU runtime that can run on the CPU without touching the GPU. This gets confusing when you do have a CPU with a GPU core, as you'll have two different OpenCL drivers available for the same chip. But in your case, it should be straightforward. If you are running Houdini 16.0, we include the Intel OpenCL CPU drivers with the install. So when a job that needs OpenCl runs on your servers, it should just fallback to the CPU. If it isn't, there is something else going wrong. (Look for a “Failed to load HFS OpenCL driver” on startup, or similar.)
Ok, Thanks.
Tried, fixed load OpenCL driver - works.
Houdini Lounge » Functional Differences Between Qt4 & 5 versions
- Ostap
- 209 posts
- Offline
SreckoM
Thanks for answer, I figured out it is issue with 378 Nvidia drivers. What drivers you use?
Nvidia driver is 375.26.
Looks like it wasn't driver fall, it was just my playing with virtualGL where I beat couple of libs.
Houdini Lounge » Functional Differences Between Qt4 & 5 versions
- Ostap
- 209 posts
- Offline
vuxSreckoM
I can not start Qt5 build on KDE Neon which has latest Qt libraries…
Can't try linux version this time, but I think there is a problem with environment variable where you should override Qt libraries path to houdini folder.
Try to add this line to /home/user/houdini16.0/houdini.env:LD_LIBRARY_PATH = /path/to/your/houdini/bin/folder
Or google for something like “override environment variables in linux”
Hi,
I had the same problem (only with Qt5 build) but in my case it was issues with OpenGL context,
reinstall graphics card driver helped.
Cheers
Ostap
Edited by Ostap - April 5, 2017 05:35:33
Technical Discussion » OpenCL - global switch to turn off
- Ostap
- 209 posts
- Offline
Thanks for your so fast response.
Unfortunately we don`t have CPU with GPU core, we have Intel Xeon CPU E5-2620 which not support Intel OpenCL CPU drivers.
And looks like only two way: print warning information “Dont send on farm OpenCL” and put it in front of artist monitor or find way how to force turn off OpenCL before send job on farm.
(Of course we can list all scene and find OpenCL check boxes but will be nice to find more elegant way)
Unfortunately we don`t have CPU with GPU core, we have Intel Xeon CPU E5-2620 which not support Intel OpenCL CPU drivers.
And looks like only two way: print warning information “Dont send on farm OpenCL” and put it in front of artist monitor or find way how to force turn off OpenCL before send job on farm.
(Of course we can list all scene and find OpenCL check boxes but will be nice to find more elegant way)
Edited by Ostap - March 31, 2017 11:54:32
Technical Discussion » OpenCL - global switch to turn off
- Ostap
- 209 posts
- Offline
Hi,
Can anyone tell me if there is a ‘global’ switch to off OpenCL on hole scene?
For example I need it for farm where we don`t have video card or CPU with GPU.
Maybe some env. var. for example HOUDINI_OCL_OFF ? But I didn't find something like that.
Cheers,
Ostap
Can anyone tell me if there is a ‘global’ switch to off OpenCL on hole scene?
For example I need it for farm where we don`t have video card or CPU with GPU.
Maybe some env. var. for example HOUDINI_OCL_OFF ? But I didn't find something like that.
Cheers,
Ostap
Technical Discussion » setConditional(type, conditional)
- Ostap
- 209 posts
- Offline
Found:
The parmTemplate() function returns a *COPY* of the parameter's template so modifying it won't do anything.
https://houdinitricks.com/adding-parameters-to-the-interface-via-python/ [houdinitricks.com]
The parmTemplate() function returns a *COPY* of the parameter's template so modifying it won't do anything.
https://houdinitricks.com/adding-parameters-to-the-interface-via-python/ [houdinitricks.com]
Technical Discussion » setConditional(type, conditional)
- Ostap
- 209 posts
- Offline
Hi,
Thanks for your feedback.
This is my code example:
n=hou.node('/obj/').createNode(“geo”, “test_condition”)
n.parm(“ty”).parmTemplate().setConditional(hou.parmCondType.DisableWhen, ‘{ tx == 0 }’)
n.updateParmStates()
n.parm(“ty”).parmTemplate().conditionals()
>>>
{}
But when I use one more temp variable, conditionals() will show correct result.
pt=n.parm(“ty”).parmTemplate()
pt.setConditional(hou.parmCondType.DisableWhen, ‘{ tx == 0 }’)
pt.conditionals()
>>>
{parmCondType.DisableWhen: ‘{ tx == 0 }’}
In both cases I don`t have any feedback to UI.
Maybe is it some bug ? Tested 15.5.717 build
Thanks for your feedback.
This is my code example:
n=hou.node('/obj/').createNode(“geo”, “test_condition”)
n.parm(“ty”).parmTemplate().setConditional(hou.parmCondType.DisableWhen, ‘{ tx == 0 }’)
n.updateParmStates()
n.parm(“ty”).parmTemplate().conditionals()
>>>
{}
But when I use one more temp variable, conditionals() will show correct result.
pt=n.parm(“ty”).parmTemplate()
pt.setConditional(hou.parmCondType.DisableWhen, ‘{ tx == 0 }’)
pt.conditionals()
>>>
{parmCondType.DisableWhen: ‘{ tx == 0 }’}
In both cases I don`t have any feedback to UI.
Maybe is it some bug ? Tested 15.5.717 build
Technical Discussion » setConditional(type, conditional)
- Ostap
- 209 posts
- Offline
Hi,
Need help to fill this python function:
setConditional(type, conditional) from parmTemplate()
Tried to fill by setConditional(hou.parmCondType.DisableWhen, ‘{ range != 0 }’) set without any error but it is not work, and look like something wrong with conditional expression.
I don`t know how to write correct condition.
If I write this ({ range != 0 }) expresiion by hand in field “Desable When” - it works.
Any body knows ?
Best Regards
Ostap
Need help to fill this python function:
setConditional(type, conditional) from parmTemplate()
Tried to fill by setConditional(hou.parmCondType.DisableWhen, ‘{ range != 0 }’) set without any error but it is not work, and look like something wrong with conditional expression.
I don`t know how to write correct condition.
If I write this ({ range != 0 }) expresiion by hand in field “Desable When” - it works.
Any body knows ?
Best Regards
Ostap
Technical Discussion » Custom examples file path
- Ostap
- 209 posts
- Offline
Hi folks,
Im looking to way how to write custom example file into custom directory.
Because I find only one way how to add custom examples file to help by “@examples \n:load_example: ….” it is write file into Houdini folder (HOUDINIPATH) and use path like this: /examples/nodes/sop/copy/MyExample.otl
Or use external help server it is not a way for me.
Is there any way to place my example file to custom directory ?
Will be appreciated for help.
Im looking to way how to write custom example file into custom directory.
Because I find only one way how to add custom examples file to help by “@examples \n:load_example: ….” it is write file into Houdini folder (HOUDINIPATH) and use path like this: /examples/nodes/sop/copy/MyExample.otl
Or use external help server it is not a way for me.
Is there any way to place my example file to custom directory ?
Will be appreciated for help.
Technical Discussion » Export data type in alembic
- Ostap
- 209 posts
- Offline
Technical Discussion » Export data type in alembic
- Ostap
- 209 posts
- Offline
Thanks in advance for your help.
In this case I will be use Attribute Create SOP.
And one more think, when I use “Add Attribute” in VOP - datatype still float32_t
And why in previous build 12.5.316 this works fine ?
In this case I will be use Attribute Create SOP.
And one more think, when I use “Add Attribute” in VOP - datatype still float32_t
And why in previous build 12.5.316 this works fine ?
Technical Discussion » Export data type in alembic
- Ostap
- 209 posts
- Offline
A little bit modify your file.
And we have from AbcEcho:
Object name=/torus_object1
CompoundProperty name=.xform;schema=AbcGeom_Xform_v3
ScalarProperty name=.inherits;interpretation=;datatype=bool_t;arraysize=1;numsamps=1
ScalarProperty name=.ops;interpretation=;datatype=uint8_t;arraysize=1;numsamps=1
ScalarProperty name=.vals;interpretation=;datatype=float64_t;arraysize=16;numsamps=1
Object name=/torus_object1/vopsop1
CompoundProperty name=.geom;schema=AbcGeom_PolyMesh_v1
ScalarProperty name=.selfBnds;interpretation=box;datatype=float64_t;arraysize=6;numsamps=1
ArrayProperty name=P;interpretation=point;datatype=float32_t;arraysize=100;numsamps=1
ArrayProperty name=.faceIndices;interpretation=;datatype=int32_t;arraysize=400;numsamps=1
ArrayProperty name=.faceCounts;interpretation=;datatype=int32_t;arraysize=100;numsamps=1
CompoundProperty name=.arbGeomParams;schema=
ArrayProperty name=vector;interpretation=vector;datatype=float32_t;arraysize=100;numsamps=1
ArrayProperty name=floats;interpretation=;datatype=float32_t;arraysize=300;numsamps=1
ArrayProperty name=testVec;interpretation=;datatype=float32_t;arraysize=300;numsamps=1
ArrayProperty name=varmap;interpretation=;datatype=string;arraysize=2;numsamps=1
Where testVec is set as vector type.
And we have from AbcEcho:
Object name=/torus_object1
CompoundProperty name=.xform;schema=AbcGeom_Xform_v3
ScalarProperty name=.inherits;interpretation=;datatype=bool_t;arraysize=1;numsamps=1
ScalarProperty name=.ops;interpretation=;datatype=uint8_t;arraysize=1;numsamps=1
ScalarProperty name=.vals;interpretation=;datatype=float64_t;arraysize=16;numsamps=1
Object name=/torus_object1/vopsop1
CompoundProperty name=.geom;schema=AbcGeom_PolyMesh_v1
ScalarProperty name=.selfBnds;interpretation=box;datatype=float64_t;arraysize=6;numsamps=1
ArrayProperty name=P;interpretation=point;datatype=float32_t;arraysize=100;numsamps=1
ArrayProperty name=.faceIndices;interpretation=;datatype=int32_t;arraysize=400;numsamps=1
ArrayProperty name=.faceCounts;interpretation=;datatype=int32_t;arraysize=100;numsamps=1
CompoundProperty name=.arbGeomParams;schema=
ArrayProperty name=vector;interpretation=vector;datatype=float32_t;arraysize=100;numsamps=1
ArrayProperty name=floats;interpretation=;datatype=float32_t;arraysize=300;numsamps=1
ArrayProperty name=testVec;interpretation=;datatype=float32_t;arraysize=300;numsamps=1
ArrayProperty name=varmap;interpretation=;datatype=string;arraysize=2;numsamps=1
Where testVec is set as vector type.
Technical Discussion » Export data type in alembic
- Ostap
- 209 posts
- Offline
And one more thinks,
Houdini works fine with this .abc, but in other program datatype still float32_t.
In houdini 12.5.316 all works fine but now in 13 …
Houdini works fine with this .abc, but in other program datatype still float32_t.
In houdini 12.5.316 all works fine but now in 13 …
Technical Discussion » Export data type in alembic
- Ostap
- 209 posts
- Offline
Hi everyone,
Maybe somebody know what it going on when I write vector custom attributes in alembic file ? Because when I read this .abc file in AbcEcho (example program) I see “datatype=float32_t”.
Why not float32_t ?
Anyone could give any advice ?
thanks
Maybe somebody know what it going on when I write vector custom attributes in alembic file ? Because when I read this .abc file in AbcEcho (example program) I see “datatype=float32_t”.
Why not float32_t ?
Anyone could give any advice ?
thanks
Technical Discussion » Strange velocity form
- Ostap
- 209 posts
- Offline
Hi Guys,
I have strange form of the cube (must be spherical) and central shape like “X” created when I raise substeps.
Why?
I have strange form of the cube (must be spherical) and central shape like “X” created when I raise substeps.
Why?
-
- Quick Links