Found 12 posts.
Search results Show results as topic list.
Solaris and Karma » re-editing material usd once made into a usd
- vochsel
- 12 posts
- Offline
Solaris and Karma » re-editing material usd once made into a usd
- vochsel
- 12 posts
- Offline
Hi all. Just wondering if there were any updates for this or planned for 18.5? The edit material node also seems to struggle on Shader Nodes created for other render delegates (In particular the HdCycles render delegate). Happy to provide some examples if needed.
Thanks for any insight,
- Ben
Thanks for any insight,
- Ben
Edited by vochsel - 2020年9月2日 13:36:19
Solaris and Karma » Automatic transformation for upAxis and metersPerUnit?
- vochsel
- 12 posts
- Offline
Was there any resolution to this? Some node which applied those transformations with overrides would be helpful.
Cheers
Cheers
Solaris and Karma » USDRender Node: Storm & HoudiniGL
- vochsel
- 12 posts
- Offline
Solaris and Karma » USDRender Node: Storm & HoudiniGL
- vochsel
- 12 posts
- Offline
This partially works for our use case: https://www.sidefx.com/forum/topic/71004/ [www.sidefx.com]
Would be good for Storm support in the future, and consolidating to the usdrender node.
Thanks for the answer above twod. That makes sense. Appreciate the response!
Cheers.
Thanks for the answer above twod. That makes sense. Appreciate the response!
Cheers.
Edited by vochsel - 2020年1月7日 21:31:58
Solaris and Karma » USDRender Node: Storm & HoudiniGL
- vochsel
- 12 posts
- Offline
Hey all,
Any reason we can't render with Storm or the HoudiniGL Hydra Delegates from the usdrender node?
Perhaps I'm missing something?
Cheers.
Any reason we can't render with Storm or the HoudiniGL Hydra Delegates from the usdrender node?
Perhaps I'm missing something?
Cheers.
Edited by vochsel - 2020年1月7日 19:19:31
Solaris and Karma » Customize Stage Manager
- vochsel
- 12 posts
- Offline
Hi all,
Just posting here to see if anyone had any insight.
We'd be interested in customizing the Stage Manager LOP Node. By default it has a file browser.
We store USD files via URI reference using our custom USD ArResolver (https://github.com/UTS-AnimalLogicAcademy/turret [github.com]). It'd be great to populate the stage manager with our assets, perhaps even a thumbnail, and when dragged have it use our uri instead of a file path on disk.
Anyone got any experience or also interested in doing this?
Cheers,
Ben Skinner
Just posting here to see if anyone had any insight.
We'd be interested in customizing the Stage Manager LOP Node. By default it has a file browser.
We store USD files via URI reference using our custom USD ArResolver (https://github.com/UTS-AnimalLogicAcademy/turret [github.com]). It'd be great to populate the stage manager with our assets, perhaps even a thumbnail, and when dragged have it use our uri instead of a file path on disk.
Anyone got any experience or also interested in doing this?
Cheers,
Ben Skinner
PDG/TOPs » Tractor Scheduler Node Refreshed
- vochsel
- 12 posts
- Offline
Awesome, thanks for adding those params!
Cheers for the direction with that error message. I'm going to put that one down to trying new things late on a Friday afternoon at work…
Cheers for the direction with that error message. I'm going to put that one down to trying new things late on a Friday afternoon at work…
PDG/TOPs » Tractor Scheduler Node Refreshed
- vochsel
- 12 posts
- Offline
Hey, thanks so much for this.
We are running some tests and we've come into a need to specify the relay and xmlport ports due to our firewall restrictions. Is there a possibility to expose this in the Scheduler parms? We hardcoded the values in prtractor.py
and it worked.
Another thing that might be useful for new people is setting the default value of $HFS NFS path toand the default value of Shared File Root Path NFS to
Another another thing is we noticed four frames appeared to fail in the PDG node output, but they actually rendered fine. This is possibly a more edge case problem. The log in Tractor was as follows:
Again, thanks so much for this change. Seeing them all under one job is great!
Thanks,
Ben
We are running some tests and we've come into a need to specify the relay and xmlport ports due to our firewall restrictions. Is there a possibility to expose this in the Scheduler parms? We hardcoded the values in prtractor.py
mq_cmd = '"__PDG_PYTHON__" "__PDG_SCRIPTDIR__/pdgmq.py" --xmlport 40002 --relayport 40001 --start'
and it worked.
Another thing that might be useful for new people is setting the default value of $HFS NFS path to
$HFS
$HIP
Another another thing is we noticed four frames appeared to fail in the PDG node output, but they actually rendered fine. This is possibly a more edge case problem. The log in Tractor was as follows:
*** Starting:
/mnt/ala/software/ext_packages/houdini/17.5.278/install/bin/hython /mnt/ala/mav/2019/sandbox/users/benjamin.skinner/houdini/new_tractor/pdgtemp/8465/scripts/rop.py -p /mnt/ala/mav/2019/sandbox/users/benjamin.skinner/houdini/new_tractor/benandrewmattyay.hipnc -n /obj/topnet1/ropmantra1/ropnet1/mantra1 -to /obj/topnet1/ropmantra1 -i ropmantra1_ropfetch1_21_2 -fs 21 -fe 21 -fi 1
Error: Unknown operator on load "stage.def".
Unknown operator on load "stage.parm".
Unknown operator on load "stage.userdata".
Unknown operator on load "stage.datablocks".
Unknown operator on load "stage.net".
Loading .hip file /mnt/ala/mav/2019/sandbox/users/benjamin.skinner/houdini/new_tractor/benandrewmattyay.hipnc.
PDG_RESULT: ropmantra1_ropfetch1_21_2;-1;'__PDG_DIR__/render/benandrewmattyay.ropmantra1.0021.exr';file/image;0
Again, thanks so much for this change. Seeing them all under one job is great!
Thanks,
Ben
Edited by vochsel - 2019年6月6日 21:38:07
PDG/TOPs » ROP Fetch libHoudiniUT.so undefined symbol
- vochsel
- 12 posts
- Offline
Hi all,
In the latest daily builds for Houdini 17.5.208 and 17.5.214, it seems that all ROP Fetches appear to fail. It seems to be an undefined symbol in libHoudiniUT.so.
Just wondering if anyone else was experiencing this?
Dirtying and cooking the node immediately changes them to success and goes green.
It works successfully in 17.5.173.
All done on the local scheduler.
Thanks,
Ben
Full output.
In the latest daily builds for Houdini 17.5.208 and 17.5.214, it seems that all ROP Fetches appear to fail. It seems to be an undefined symbol in libHoudiniUT.so.
Just wondering if anyone else was experiencing this?
Dirtying and cooking the node immediately changes them to success and goes green.
It works successfully in 17.5.173.
All done on the local scheduler.
/home/142738/packages/houdini/17.5.214/install/bin/../dsolib/libHoudiniUT.so: undefined symbol: _ZN3tbb19task_scheduler_init27internal_blocking_terminateEb
Thanks,
Ben
Full output.
Houdini DSO error on '/mnt/ala/software/int_packages/usd_houdini_hdk/0.0.4/houdini-17.5.208+/embree_lib/dso/libOP_gusd.so' libHoudiniAPPS3.so: cannot open shared object file: No such file or directory [SG update_context_variables] Ignoring update context variables, hdefereval not defined, most likely you are running a job in the farm and this automation is not needed. Loading .hip file /mnt/ala/mav/2019/sandbox/users/benjamin.skinner/houdini/auto_lod/auto_lod_main.hipnc. [SG update_context_variables] Ignoring update context variables, hdefereval not defined, most likely you are running a job in the farm and this automation is not needed. [Turret] Turret will not cache resolves to disk TURRET USD Resolver - Created Resolver [Turret] TURRET USD Resolver - using default resolver for file path: /mnt/ala/mav/2019/sandbox/users/benjamin.skinner/houdini/auto_lod/geo/pizzaBox01_LOD7_wip.usd [Turret] TURRET USD Resolver - using default resolver for file path: /mnt/ala/mav/2019/sandbox/users/benjamin.skinner/houdini/auto_lod/geo/pizzaBox01_LOD7_wip.usd [Turret] TURRET USD Resolver - using default resolver for file path: /mnt/ala/mav/2019/sandbox/users/benjamin.skinner/houdini/auto_lod/geo/pizzaBox01_LOD7_wip.usd [Turret] TURRET USD Resolver - using ala usd resolver for file path: tanks119/publish_asset_variant_set_usd?Step=model&Task=model&asset_type=setPiece&version=latest&Asset=pizzaBox01 [Turret] usd resolver received live response: /mnt/ala/mav/2019/jobs/s119/assets/setPiece/pizzaBox01/model/model/caches/usd/v004/pizzaBox01_model_model_usd.v004.usd for query: tanks119/publish_asset_variant_set_usd?Step=model&Task=model&asset_type=setPiece&version=latest&Asset=pizzaBox01 [Turret] TURRET USD Resolver - using default resolver for file path: /mnt/ala/mav/2019/jobs/s119/assets/setPiece/pizzaBox01/model/model/caches/usd/v004/LOD0/pizzaBox01_model_model_LOD0_usd.v004.usd [Turret] TURRET USD Resolver - using default resolver for file path: /mnt/ala/mav/2019/jobs/s119/assets/setPiece/pizzaBox01/model/model/caches/usd/v004/LOD0/pizzaBox01_model_model_LOD0_usd.v004.usd [Turret] TURRET USD Resolver - using default resolver for file path: /home/142738/packages/houdini/17.5.214/install/dsolib/usd_plugins/usdSkel/resources/generatedSchema.usda [Turret] TURRET USD Resolver - using default resolver for file path: /home/142738/packages/houdini/17.5.214/install/dsolib/usd_plugins/usdLux/resources/generatedSchema.usda [Turret] TURRET USD Resolver - using default resolver for file path: /home/142738/packages/houdini/17.5.214/install/dsolib/usd_plugins/usdUI/resources/generatedSchema.usda [Turret] TURRET USD Resolver - using default resolver for file path: /home/142738/packages/houdini/17.5.214/install/dsolib/usd_plugins/usdVol/resources/generatedSchema.usda [Turret] TURRET USD Resolver - using default resolver for file path: /home/142738/packages/houdini/17.5.214/install/houdini/dso/usd_plugins/usdMantra/resources/generatedSchema.usda [Turret] TURRET USD Resolver - using default resolver for file path: /home/142738/packages/houdini/17.5.214/install/houdini/dso/usd_plugins/usdHoudini/resources/generatedSchema.usda [Turret] TURRET USD Resolver - using default resolver for file path: /home/142738/packages/houdini/17.5.214/install/dsolib/usd_plugins/usdShade/resources/generatedSchema.usda [Turret] TURRET USD Resolver - using default resolver for file path: /home/142738/packages/houdini/17.5.214/install/dsolib/usd_plugins/usd/resources/generatedSchema.usda [Turret] TURRET USD Resolver - using default resolver for file path: /home/142738/packages/houdini/17.5.214/install/dsolib/usd_plugins/usdGeom/resources/generatedSchema.usda [Turret] TURRET USD Resolver - using default resolver for file path: /home/142738/packages/houdini/17.5.214/install/dsolib/usd_plugins/usdRi/resources/generatedSchema.usda PDG_RESULT: perform_lod_1_136;-1;'__PDG_DIR__/geo/pizzaBox01_LOD7_wip.usd';;0 /home/142738/packages/houdini/17.5.214/install/bin/hython-bin: symbol lookup error: /home/142738/packages/houdini/17.5.214/install/bin/../dsolib/libHoudiniUT.so: undefined symbol: _ZN3tbb19task_scheduler_init27internal_blocking_terminateEb
PDG/TOPs » Tractor Scheduler floods farm with separate jobs per work item
- vochsel
- 12 posts
- Offline
PDG/TOPs » Tractor Scheduler floods farm with separate jobs per work item
- vochsel
- 12 posts
- Offline
Hi there,
We've begun using PDG/TOP Nets for some tractor scheduling and have run into an issue where submitting work items via the built in tractor scheduler causes our tractor to be flooded with separate jobs when run.
Is there a reason that each PDG work item gets submitted as its own job? It would seem to make more sense to group all work items under the one job as tasks. Perhaps there is PDG concept I'm not familiar with yet. Just wondering if there was anyone else experiencing this.
Thanks,
Ben
We've begun using PDG/TOP Nets for some tractor scheduling and have run into an issue where submitting work items via the built in tractor scheduler causes our tractor to be flooded with separate jobs when run.
Is there a reason that each PDG work item gets submitted as its own job? It would seem to make more sense to group all work items under the one job as tasks. Perhaps there is PDG concept I'm not familiar with yet. Just wondering if there was anyone else experiencing this.
Thanks,
Ben
-
- Quick Links