Found 10 posts.
Search results Show results as topic list.
Technical Discussion » Lops and setting 'outputimage'
- michaelblackbourn
- 10 posts
- Offline
They get echoed into the terminal (in my case I was trying to use the redshift plugin and I hadent set the paths properly beforehand. So husk dumped a bunch of options as suggestions.
Technical Discussion » Lops and setting 'outputimage'
- michaelblackbourn
- 10 posts
- Offline
I'm hoping storm can be made to work.
But if you fire husk from command line all the options are suggested… In red. So I'd expect them to work. Sidefx should remove the -R Gl and glhoudini options if they cannot be used.
But if you fire husk from command line all the options are suggested… In red. So I'd expect them to work. Sidefx should remove the -R Gl and glhoudini options if they cannot be used.
Technical Discussion » Lops and setting 'outputimage'
- michaelblackbourn
- 10 posts
- Offline
Thanks for the info. I've managed to build a .usd that I can render in both redshift and karma targeting different rendersettings lops in the husk commandline. All working well and the rendervar for ‘color’ using C.* and LPE works for both.
So major testing can begin. It's super awesome that this eliminates the ifd job on the farm, and that the usd can be used for all the timesamples.
Not I just need to figure out how to setup all the redshift Z N P and all the other AOV's. And for that I'm off to the Redshift forum. Thanks.
One last thing. I was kind of hoping to also be able to use husk and render GL… but so far thats not working.
So major testing can begin. It's super awesome that this eliminates the ifd job on the farm, and that the usd can be used for all the timesamples.
Not I just need to figure out how to setup all the redshift Z N P and all the other AOV's. And for that I'm off to the Redshift forum. Thanks.
One last thing. I was kind of hoping to also be able to use husk and render GL… but so far thats not working.
Technical Discussion » render cache on multiple hard drive
- michaelblackbourn
- 10 posts
- Offline
Just wire them to a switch and set a key on the frame when you want to start using the other cache
Technical Discussion » Lops and setting 'outputimage'
- michaelblackbourn
- 10 posts
- Offline
Reading out what the karma settings attributes use offer some clues.
Looks like C or C.* Is what I need for the rendervar source. But if I render it throws a karma error saying it's looking for Cf.
Any primers here would be appreciated.
Looks like C or C.* Is what I need for the rendervar source. But if I render it throws a karma error saying it's looking for Cf.
Any primers here would be appreciated.
Technical Discussion » Lops and setting 'outputimage'
- michaelblackbourn
- 10 posts
- Offline
All this USD stuff is new and exciting to us, but we see huge potential. I just need a few tips to keep moving forward.
I'm trying to set all the attributes in a USD for rendering (for redshift, but it doesn't really matter what renderer, I'm just trying to set the default USD parameters without dealing with specific renderer options at this point.)
What is the correct way to set the outputimage attribute without using the Karma specific nodes or the USD rop? I'm not looking to override the outputimage with the usd rop, I'd like to set it properly in the usd composed scene using:
render settings
render product
and rendervars.
I can add it as a path in the renderproduct, but then I'm not sure how to configure the required rendervar node. What do I enter into the source line in the rendervar to pull the generic rgba plane? IS there a list of the generic options here? Like P Z N RGBA….
I'd love a screenshot or a hipfile that shows how to set these GENERIC usd settings without getting into anything karma specific. Just the suggested workflow to set the USD parameters for render paths.
The goal would be to hopefully take the resulting USD and feed it to redshift with a commandline to render on the farm, so it needs to contain everything inside instead of last minute overrides.
Thanks.
I'm trying to set all the attributes in a USD for rendering (for redshift, but it doesn't really matter what renderer, I'm just trying to set the default USD parameters without dealing with specific renderer options at this point.)
What is the correct way to set the outputimage attribute without using the Karma specific nodes or the USD rop? I'm not looking to override the outputimage with the usd rop, I'd like to set it properly in the usd composed scene using:
render settings
render product
and rendervars.
I can add it as a path in the renderproduct, but then I'm not sure how to configure the required rendervar node. What do I enter into the source line in the rendervar to pull the generic rgba plane? IS there a list of the generic options here? Like P Z N RGBA….
I'd love a screenshot or a hipfile that shows how to set these GENERIC usd settings without getting into anything karma specific. Just the suggested workflow to set the USD parameters for render paths.
The goal would be to hopefully take the resulting USD and feed it to redshift with a commandline to render on the farm, so it needs to contain everything inside instead of last minute overrides.
Thanks.
Technical Discussion » Karma beta documentation
- michaelblackbourn
- 10 posts
- Offline
Technical Discussion » Karma beta documentation
- michaelblackbourn
- 10 posts
- Offline
After a visit to the redshift site it looks like they have thier renderview running with Hydra and lops. So I think we're covered there for now. We're only now looking into all of this as we've been in non stop production for a while, so all these goodies are hitting us all at once.
Technical Discussion » Karma beta documentation
- michaelblackbourn
- 10 posts
- Offline
Alex, we're in a very similar situation. We currently use Houdini and redshift for all our lookdev, fx, lighting, and rendering work. I'm the VFX supe for The Embassy.
We have gone to considerable effort over the past few years to add features like shared primitives between discreet asset, internal instancing of primitives within assets, layered overrides using a patchwork of Python and otls… But it's a little inelegant, particularly when educating new artists.
Usd's composition concept is fantastic and I can't wait to move our pipeline over to it. It's the endgame of a pile of ideas we've had for years (it makes sense that pixar has suffered and solved the same issues, but with orders of magnitude higher r+d budget).
To adopt lops we will need a solid renderer (I'm expecting redshift to get there first) and a renderview that is at least as functional as the previous one in Houdini. We're just now getting h18 setup at work and we'll see how redshifts lops integration is.
Also… As mentioned in another thread, currently Karma has no isPhantom (or primary Rays off) Geo render setting. Which is another big hole is how we work in Houdini. Is there a better forum to discuss this and other absolute needs for adoption? Maybe I should take this to a beta location (this is my personal email account, but I'm sure we have access at work)…
We have gone to considerable effort over the past few years to add features like shared primitives between discreet asset, internal instancing of primitives within assets, layered overrides using a patchwork of Python and otls… But it's a little inelegant, particularly when educating new artists.
Usd's composition concept is fantastic and I can't wait to move our pipeline over to it. It's the endgame of a pile of ideas we've had for years (it makes sense that pixar has suffered and solved the same issues, but with orders of magnitude higher r+d budget).
To adopt lops we will need a solid renderer (I'm expecting redshift to get there first) and a renderview that is at least as functional as the previous one in Houdini. We're just now getting h18 setup at work and we'll see how redshifts lops integration is.
Also… As mentioned in another thread, currently Karma has no isPhantom (or primary Rays off) Geo render setting. Which is another big hole is how we work in Houdini. Is there a better forum to discuss this and other absolute needs for adoption? Maybe I should take this to a beta location (this is my personal email account, but I'm sure we have access at work)…
Technical Discussion » How to matte out with karma
- michaelblackbourn
- 10 posts
- Offline
jsmack
Matte is one of the options on the karma geometry properties node.
This works fine for Matte, any ideas on how to replicate the phantom workflow? I couldn't find an equivalent to go along with the isMatte property.
-
- Quick Links