Found 20 posts.
Search results Show results as topic list.
Technical Discussion » Help : CORRUPT .bgeo.sc FILES
- adlabac
- 20 posts
- Offline
Thanks Fred P for the info. SideFX guys are investigating it so we will see if they come up with something.
Technical Discussion » Help : CORRUPT .bgeo.sc FILES
- adlabac
- 20 posts
- Offline
Sure. Pretty much the same description as the author's original post. We launch sims via Deadline. All our project data are stored on a huge Isilon NAS storage. Render slave's OS is Rocky Linux 8.8. It happens randomly, so we can't reproduce ourselves on purpose. I've sent couple of corrupted files under this RFE https://www.sidefx.com/bugs/#/bug/135536 [www.sidefx.com] but I can deliver more if needed. Due to fact Houdini isn't give any error during simulation, we discover particular corruption after whole simulation is done and cache is used.
We are using several Houdini versions ranging from 19.5.xxx to 20.0.xxx. In the past we used HQUEUE on windows (also storing outputs to ISILON)and never saw this happening. As I've already mentioned setting of HOUDINI_BUFEREDSAVE didn't help us.
Because we switched to Deadline and linux OS in the same time we cannot tell what the right reason could it be.
We are using several Houdini versions ranging from 19.5.xxx to 20.0.xxx. In the past we used HQUEUE on windows (also storing outputs to ISILON)and never saw this happening. As I've already mentioned setting of HOUDINI_BUFEREDSAVE didn't help us.
Because we switched to Deadline and linux OS in the same time we cannot tell what the right reason could it be.
Edited by adlabac - April 23, 2024 15:32:08
Technical Discussion » Help : CORRUPT .bgeo.sc FILES
- adlabac
- 20 posts
- Offline
Guys, have anybody solution for this? It starting to be very very unpleasant situation. Unfortunately BUFFEREDSAVE didn't solve this issue for us.
Technical Discussion » Help : CORRUPT .bgeo.sc FILES
- adlabac
- 20 posts
- Offline
HI, We have exactly same problem. Did you manage to solve this issue by setting BUFFEREDSAVE variable?
Technical Discussion » License partitioning
- adlabac
- 20 posts
- Offline
Technical Discussion » License partitioning
- adlabac
- 20 posts
- Offline
thanks for the response. It's cool it's now controlled via hkey. I have one question thou, I'm unable to publish my modifications and I think it's because I'm not admin user. How to add user to admins via cmd line without GUI?
EDIT: reason I'm asking this is we have headless license server and I didn't find a way how to add user as admin locally on the server. If I tried from my machine using hkey it just gives me an error "Error while adding admin user"
Thank you
EDIT: reason I'm asking this is we have headless license server and I didn't find a way how to add user as admin locally on the server. If I tried from my machine using hkey it just gives me an error "Error while adding admin user"
Thank you
Edited by adlabac - Nov. 20, 2023 10:51:23
Technical Discussion » License partitioning
- adlabac
- 20 posts
- Offline
and one more thing.
Let presume user1 belong to Studio group. User2 took 1 shared license from the "Experimental Users" group. Will user1 get another license from Studio group? Does group definition order matter?
Let presume user1 belong to Studio group. User2 took 1 shared license from the "Experimental Users" group. Will user1 get another license from Studio group? Does group definition order matter?
{ "user_groups": [ { "name": "Studio", "if": "machine_name matches '^[a-zA-Z0-9_.]*.render.com$'" }, { "name": "Experimental Users", "if": "username in ['user1', 'user2', 'user3']" } ], "license_partitions": [ { "if": "(product == 'Houdini Engine' or product == 'Houdini FX') and version >= 17.0", "user_group": "Studio", "quantity": 10 }, { "if": "product == 'Houdini Engine' or product == 'Houdini FX') and version >= 17.0", "user_group": "Experimental Users", "quantity": 1 } ] }
Edited by adlabac - Nov. 16, 2023 06:56:36
Technical Discussion » License partitioning
- adlabac
- 20 posts
- Offline
Hello,
We are interested in setting up license partitioning, but we have some questions that we could not find answers to in the documentation. We would appreciate if someone could clarify the following points for us:
• If we turn on partitioning, we need to restart the license server. What happens with the connected clients? Will they be forcefully disconnected and lose their work?
• Do we need to restart the server after editing the .partition.json file to apply the changes?
• What happens with users who do not belong to any group? Will they be granted or denied a license by default?
• Is there any way to test the syntax validity of the .partition.json file without restarting the server?
• Is there a way to see which rule from the .partition.json file was applied to a user requesting a license in the log?
• What happens to a user who borrowed a license from a group if all the licenses from that group are used? Does a user with a dedicated license have precedence over a user with a borrowed license?
Thank you.
AD
We are interested in setting up license partitioning, but we have some questions that we could not find answers to in the documentation. We would appreciate if someone could clarify the following points for us:
• If we turn on partitioning, we need to restart the license server. What happens with the connected clients? Will they be forcefully disconnected and lose their work?
• Do we need to restart the server after editing the .partition.json file to apply the changes?
• What happens with users who do not belong to any group? Will they be granted or denied a license by default?
• Is there any way to test the syntax validity of the .partition.json file without restarting the server?
• Is there a way to see which rule from the .partition.json file was applied to a user requesting a license in the log?
• What happens to a user who borrowed a license from a group if all the licenses from that group are used? Does a user with a dedicated license have precedence over a user with a borrowed license?
Thank you.
AD
Technical Discussion » hou.fileReferences() and LOPs
- adlabac
- 20 posts
- Offline
Hi,
I would expect that using hou.fileReferences() function will return also Reference and Sublayer LOPs in it's results but it's not.
Is this wanted behavior or it is rather bug?
Thanks
AD
I would expect that using hou.fileReferences() function will return also Reference and Sublayer LOPs in it's results but it's not.
Is this wanted behavior or it is rather bug?
Thanks
AD
Technical Discussion » Packages not found on the farm
- adlabac
- 20 posts
- Offline
mabelzileI've tried both and it is working.
You could try to debug first locally to see if it's related to the shared folder (i.e. move the shared folder to a folder local to your machine).
1. On my local machine set HOUDINI_PACKAGE_DIR to network share(same as farm using)
2. copied shared folder to local disk and then set HOUDINI_PACKAGE_DIR there
What do you mean by this ?It just means that this HOUDINI_PACKAGE_DIR environment variable was set properly before render command was started.we have packages directory on the network share which is defined by HOUDINI_PACKAGE_DIR before render starts
UPDATE:
after carefully comparing all the environments, I found the reason of the missing packages. I always thought that @/otls;& endings in HOUDINI_OTLSCAN_PATH were only needed within houdini.env and not supposed it is working in .bat files.
Now errors disappeared.
Edited by adlabac - May 24, 2023 04:04:19
Technical Discussion » Packages not found on the farm
- adlabac
- 20 posts
- Offline
Hi,
I'm trying to figure out what's going on but I'm out of ideas.
we have packages directory on the network share which is defined by HOUDINI_PACKAGE_DIR before render starts
Problem is we gets errors of missing tools Labs and kinex. Strange thing is that if I've set HOUDINI_PACKAGE_VERBOSE=1 it seems to me packages are properly found and loaded.
Same setup works in workstation well except, network directory is mirrored to local disk
R 7| rrErr: = = = Houdini Package log = = =
R 8| rrErr: Loading: //upptools/workgroups/houdini/vfx/production_core/packages/SideFXLabs19.0.json
R 9| rrErr: WARNING: SideFXLabs19.0 is marked as disabled.
:
R 12| rrErr: Loading: //upptools/workgroups/houdini/vfx/production_core/packages/SideFXLabs19.5.json
R 16| rrErr: Loading: //upptools/workgroups/houdini/sw/Houdini 19.5.368/packages/apex.json
R 18| rrErr: Loading: //upptools/workgroups/houdini/sw/Houdini 19.5.368/packages/kinefx.json
R 20| rrErr: Loading: //upptools/workgroups/houdini/sw/Houdini 19.5.368/packages/package_dirs.json
R 21| rrErr: WARNING: Undefined variable $HOUDINI_DISABLE_SIDEFX_PACKAGES used in expression $HOUDINI_DISABLE_SIDEFX_PACKAGES != '1'
R 23| rrErr:
R 24| rrErr: Processing load once: //upptools/workgroups/houdini/vfx/production_core/packages/SideFXLabs19.5.json
R 26| rrErr: Processing: //upptools/workgroups/houdini/vfx/production_core/packages/SideFXLabs19.5.json
R 30| rrErr: Processing: //upptools/workgroups/houdini/sw/Houdini 19.5.368/packages/apex.json
R 32| rrErr: Processing: //upptools/workgroups/houdini/sw/Houdini 19.5.368/packages/kinefx.json
R 34| rrErr: Processing: //upptools/workgroups/houdini/sw/Houdini 19.5.368/packages/package_dirs.json
R 35| rrErr: WARNING: Package folder to process is invalid: C:/Program Files/Side Effects Software/sidefx_packages
R 37| rrErr: Resolved variables:
R 39| rrErr: SIDEFXLABS : //upptools/workgroups/houdini/vfx/production_core/packages/SideFXLabs19.5
R 40| rrErr: HOUDINI_PATH :
R 41| rrErr: //upptools/workgroups/houdini/sw/Houdini 19.5.368/packages/kinefx
R 42| rrErr: //upptools/workgroups/houdini/vfx/production_core/packages/SideFXLabs19.5
R 44| rrErr: //upptools/workgroups/houdini/htoa/htoa-6.1.3.3_rdb15014_houdini-19.5.368
R 45| rrErr: //upptools/workgroups/houdini/sw/Houdini 19.5.368/houdini
R 46| rrErr: //upptools/workgroups/houdini/vfx/production_core/uppLib
R 47| rrErr: //upptools/workgroups/houdini/vfx/production_core/USERLib
R 54| rrErr:
R 55| rrErr: Loading Info:
R 56| rrErr: Loaded Packages (4):
R 57| rrErr: //upptools/workgroups/houdini/vfx/production_core/packages/SideFXLabs19.5.json
R 58| rrErr: //upptools/workgroups/houdini/sw/Houdini 19.5.368/packages/apex.json
R 60| rrErr: //upptools/workgroups/houdini/sw/Houdini 19.5.368/packages/kinefx.json
R 61| rrErr: //upptools/workgroups/houdini/sw/Houdini 19.5.368/packages/package_dirs.json
R 62| rrErr:
R 63| rrErr: Disabled Packages (1):
R 64| rrErr: //upptools/workgroups/houdini/vfx/production_core/packages/SideFXLabs19.0.json
R 65| rrErr:
R 66| rrErr: = = = = = = = = = = = = = = = =
Later we get(shortened)
R101| rrErr: opalias: 'labs::gaea_tor_processor' is not a known operator.
R102| rrErr: opalias: 'labs::simple_retime' is not a known operator.
R103| rrErr: opalias: 'labs::coord_swizzle_vector::1.0' is not a known operator.
R104| rrErr: opalias: 'labs::dds_file' is not a known operator.
R105| rrErr: opalias: 'labs::normal_color' is not a known operator.
R106| rrErr: opalias: 'labs::normal_combine' is not a known operator.
R107| rrErr: opalias: 'labs::normal_invert' is not a known operator.
.
.
.
.
R265| rrErr: opalias: 'kinefx::adapttoterrain' is not a known operator.
R266| rrErr: opalias: 'kinefx::fbikconfiguretargets' is not a known operator.
R267| rrErr: opalias: 'kinefx::rigdoctor' is not a known operator.
R268| rrErr: opalias: 'kinefx::rigmirrorpose' is not a known operator.
R269| rrErr: opalias: 'kinefx::rigpose' is not a known operator.
R270| rrErr: opalias: 'kinefx::skeleton' is not a known operator.
R271| rrErr: opalias: 'kinefx::parentjoints' is not a known operator.
R272| rrErr: opalias: 'kinefx::orientjoints' is not a known operator.
R273| rrErr: opalias: 'kinefx::configurejoints' is not a known operator.
R274| rrErr: opalias: 'kinefx::jointcapturebiharmonic' is not a known operator.
Any ideas what to do?
Thank you
Ales
I'm trying to figure out what's going on but I'm out of ideas.
we have packages directory on the network share which is defined by HOUDINI_PACKAGE_DIR before render starts
Problem is we gets errors of missing tools Labs and kinex. Strange thing is that if I've set HOUDINI_PACKAGE_VERBOSE=1 it seems to me packages are properly found and loaded.
Same setup works in workstation well except, network directory is mirrored to local disk
R 7| rrErr: = = = Houdini Package log = = =
R 8| rrErr: Loading: //upptools/workgroups/houdini/vfx/production_core/packages/SideFXLabs19.0.json
R 9| rrErr: WARNING: SideFXLabs19.0 is marked as disabled.
:
R 12| rrErr: Loading: //upptools/workgroups/houdini/vfx/production_core/packages/SideFXLabs19.5.json
R 16| rrErr: Loading: //upptools/workgroups/houdini/sw/Houdini 19.5.368/packages/apex.json
R 18| rrErr: Loading: //upptools/workgroups/houdini/sw/Houdini 19.5.368/packages/kinefx.json
R 20| rrErr: Loading: //upptools/workgroups/houdini/sw/Houdini 19.5.368/packages/package_dirs.json
R 21| rrErr: WARNING: Undefined variable $HOUDINI_DISABLE_SIDEFX_PACKAGES used in expression $HOUDINI_DISABLE_SIDEFX_PACKAGES != '1'
R 23| rrErr:
R 24| rrErr: Processing load once: //upptools/workgroups/houdini/vfx/production_core/packages/SideFXLabs19.5.json
R 26| rrErr: Processing: //upptools/workgroups/houdini/vfx/production_core/packages/SideFXLabs19.5.json
R 30| rrErr: Processing: //upptools/workgroups/houdini/sw/Houdini 19.5.368/packages/apex.json
R 32| rrErr: Processing: //upptools/workgroups/houdini/sw/Houdini 19.5.368/packages/kinefx.json
R 34| rrErr: Processing: //upptools/workgroups/houdini/sw/Houdini 19.5.368/packages/package_dirs.json
R 35| rrErr: WARNING: Package folder to process is invalid: C:/Program Files/Side Effects Software/sidefx_packages
R 37| rrErr: Resolved variables:
R 39| rrErr: SIDEFXLABS : //upptools/workgroups/houdini/vfx/production_core/packages/SideFXLabs19.5
R 40| rrErr: HOUDINI_PATH :
R 41| rrErr: //upptools/workgroups/houdini/sw/Houdini 19.5.368/packages/kinefx
R 42| rrErr: //upptools/workgroups/houdini/vfx/production_core/packages/SideFXLabs19.5
R 44| rrErr: //upptools/workgroups/houdini/htoa/htoa-6.1.3.3_rdb15014_houdini-19.5.368
R 45| rrErr: //upptools/workgroups/houdini/sw/Houdini 19.5.368/houdini
R 46| rrErr: //upptools/workgroups/houdini/vfx/production_core/uppLib
R 47| rrErr: //upptools/workgroups/houdini/vfx/production_core/USERLib
R 54| rrErr:
R 55| rrErr: Loading Info:
R 56| rrErr: Loaded Packages (4):
R 57| rrErr: //upptools/workgroups/houdini/vfx/production_core/packages/SideFXLabs19.5.json
R 58| rrErr: //upptools/workgroups/houdini/sw/Houdini 19.5.368/packages/apex.json
R 60| rrErr: //upptools/workgroups/houdini/sw/Houdini 19.5.368/packages/kinefx.json
R 61| rrErr: //upptools/workgroups/houdini/sw/Houdini 19.5.368/packages/package_dirs.json
R 62| rrErr:
R 63| rrErr: Disabled Packages (1):
R 64| rrErr: //upptools/workgroups/houdini/vfx/production_core/packages/SideFXLabs19.0.json
R 65| rrErr:
R 66| rrErr: = = = = = = = = = = = = = = = =
Later we get(shortened)
R101| rrErr: opalias: 'labs::gaea_tor_processor' is not a known operator.
R102| rrErr: opalias: 'labs::simple_retime' is not a known operator.
R103| rrErr: opalias: 'labs::coord_swizzle_vector::1.0' is not a known operator.
R104| rrErr: opalias: 'labs::dds_file' is not a known operator.
R105| rrErr: opalias: 'labs::normal_color' is not a known operator.
R106| rrErr: opalias: 'labs::normal_combine' is not a known operator.
R107| rrErr: opalias: 'labs::normal_invert' is not a known operator.
.
.
.
.
R265| rrErr: opalias: 'kinefx::adapttoterrain' is not a known operator.
R266| rrErr: opalias: 'kinefx::fbikconfiguretargets' is not a known operator.
R267| rrErr: opalias: 'kinefx::rigdoctor' is not a known operator.
R268| rrErr: opalias: 'kinefx::rigmirrorpose' is not a known operator.
R269| rrErr: opalias: 'kinefx::rigpose' is not a known operator.
R270| rrErr: opalias: 'kinefx::skeleton' is not a known operator.
R271| rrErr: opalias: 'kinefx::parentjoints' is not a known operator.
R272| rrErr: opalias: 'kinefx::orientjoints' is not a known operator.
R273| rrErr: opalias: 'kinefx::configurejoints' is not a known operator.
R274| rrErr: opalias: 'kinefx::jointcapturebiharmonic' is not a known operator.
Any ideas what to do?
Thank you
Ales
Edited by adlabac - May 23, 2023 07:16:52
Solaris and Karma » Getting render camera
- adlabac
- 20 posts
- Offline
Thanks to Tim's suggestion of using LopSelectionRule() I've discovered this page https://www.sidefx.com/docs/houdini/solaris/pattern.html#syntax [www.sidefx.com] with lots of examples how to use this powerful technique.
It makes really easy to find default camera, rendersettings or renderproduct even without stage object
It makes really easy to find default camera, rendersettings or renderproduct even without stage object
node = hou.pwd() ls = hou.LopSelectionRule() ls.setPathPattern('%rendercamera') resolved_paths = ls.expandedPaths(node.inputs()[0]) prim_path = resolved_paths[0] print(prim_path) ls.setPathPattern('%rendersettings') resolved_paths = ls.expandedPaths(node.inputs()[0]) prim_path = resolved_paths[0] print(prim_path) ls.setPathPattern('%renderproducts') resolved_paths = ls.expandedPaths(node.inputs()[0]) prim_path = resolved_paths[0] print(prim_path)
Edited by adlabac - Jan. 2, 2023 06:26:32
Solaris and Karma » Getting render camera
- adlabac
- 20 posts
- Offline
Now both versions works, thank you very much!
Is there easy way how to get LOP node from USD stage primitive? Let's say I wanna find LOP which created /Cameras/camera1 ??
Ales
Is there easy way how to get LOP node from USD stage primitive? Let's say I wanna find LOP which created /Cameras/camera1 ??
Ales
Solaris and Karma » Getting render camera
- adlabac
- 20 posts
- Offline
Solaris and Karma » Getting render camera
- adlabac
- 20 posts
- Offline
Thank you Hamilton,
my intention is validate scene before sending to the farm, so solution must be bulletproof.
First code presumes that I know name of rendersettings LOP what I don't. It is also possible that rendersettings won't be present
in actual tree at all and will be referenced from other USD file. In that case neither second code would help. I'm sorry I wasn't clear enough.
I really appreciate your help.
my intention is validate scene before sending to the farm, so solution must be bulletproof.
First code presumes that I know name of rendersettings LOP what I don't. It is also possible that rendersettings won't be present
in actual tree at all and will be referenced from other USD file. In that case neither second code would help. I'm sorry I wasn't clear enough.
I really appreciate your help.
Solaris and Karma » Getting render camera
- adlabac
- 20 posts
- Offline
Hi,
I'm struggling with obtaining active camera in my LOP tree using Python (not Python LOP)
My idea was start traversing from my Usdrender LOP to the Rendersettings LOP where I'll read camera parameter.
Problem happens when rendersetting parameter is using primpath name instead LOP path (eg. /Render/rendersettings vs /stage/rendersettings1).
In that case I don't know how to traverse to rendersettings LOP.
What is the easiest approach of getting render camera?
Thank you
A.
I'm struggling with obtaining active camera in my LOP tree using Python (not Python LOP)
My idea was start traversing from my Usdrender LOP to the Rendersettings LOP where I'll read camera parameter.
Problem happens when rendersetting parameter is using primpath name instead LOP path (eg. /Render/rendersettings vs /stage/rendersettings1).
In that case I don't know how to traverse to rendersettings LOP.
What is the easiest approach of getting render camera?
Thank you
A.
Houdini Lounge » Ocio configuration
- adlabac
- 20 posts
- Offline
blahParsecIt's working for us perfectly although we aren't using Indie version don't know if this makes any difference
Everything above is done, and still nothing. Any idea what to try next?
Technical Discussion » Multi-part exr?
- adlabac
- 20 posts
- Offline
Technical Discussion » Hqueue and missing OTLs
- adlabac
- 20 posts
- Offline
Hi group,
I'm looking for answer to this situation.
You are simulating via Hqueue and your slave will lost network connection for brief moment.
You will get this message to your job log
Obviously you can not interact with job as it is running on background. So I'm wondering it exists some way how to specify default action before job is send or other way how to resume job?
Thank you
A.
I'm looking for answer to this situation.
You are simulating via Hqueue and your slave will lost network connection for brief moment.
You will get this message to your job log
Cannot access the OTL source: //192.168.37.100/houdini/sw/Houdini 16.5.439/houdini/otls/OPlibSop.hda
for operator type: timeblend
“Save & Quit” will save the hip file and quit the session
“Discard & Quit” will quit the session without saving the hip file
“Retry” will attempt again to refresh the OTL definition from the same file location
“Embed” will try to use an alternative definition among already loaded OTLs,
and if no suitable definition is found, it will create a hollow, embedded fallback OTL
which allows you to continue working with the hip file
“Refresh OTLs” will reload OTLs found in the search path
and try to use them for the operator definition
“Load OTL” will present a file chooser to specify an explicit OTL location
where the operator definition can be found
0: “Save & Quit”
1: “Discard & Quit”
2: Retry
3: Embed
4: “Refresh OTLs”
5: “Load OTL”
Obviously you can not interact with job as it is running on background. So I'm wondering it exists some way how to specify default action before job is send or other way how to resume job?
Thank you
A.
Technical Discussion » OCIO Implementation plan
- adlabac
- 20 posts
- Offline
Is used OCIO config saved along with scene?
No. From what I've gathered from most OCIO workflows is that this should be entirely controlled by the OCIO environment variables, and not saved in the scene itself.
The next major version of Houdini has some improvements to the OCIO workflow, including expanded support for OCIO in color display in Houdini, and applying colorspace transforms when loading image files.
That could be little bit problematic. If you set your OCIO file on worker machine and he will use eg. OCIO_transform node for texture input then you have to take care also same OCIO setup on the render farm otherwise it will render wrong result. Even Nuke is saving used OCIO config inside script to render same on color un-managed computers.
I would love to hear how larger facilities are solving this.
Also I've take a look on latest version of Houdini. Source color space in Texture node still has only two options Automatic and Linear. Are you planning to propagate OCIO defined color spaces there?
-
- Quick Links