Found 662 posts.
Search results Show results as topic list.
Solaris and Karma » Command Line Rendering
- mark
- 2597 posts
- Offline
husk's verbosity relies on the ability to communicate to the render delegate via. the render stats. If the delegate doesn't provide render stats, progress can't be reported.
Solaris and Karma » Deep Exr rendering in Solaris?
- mark
- 2597 posts
- Offline
It depends on the render delegate. Karma currently does not render deep images, but it's in the long term plans.
Solaris and Karma » How are people rendering in Solaris with no AOV support.
- mark
- 2597 posts
- Offline
There are some common LPE features that many renderers support. Then again, every renderer has its own flavor of LPE. USD allows AOVs to be specified by an LPE, but I think the expression you enter can be customized for a particular delegate.
Solaris and Karma » How are people rendering in Solaris with no AOV support.
- mark
- 2597 posts
- Offline
Karma will render AOVs from the USD file. The AOV definitions are just passed through to the render delegate.
`husk -p1 -o test.exr test.usd`
generates a bunch of different AOVs for me. Some of the AOVs are Karma specific, but `diffuse` and `indirectDiffuse` are defined by LPE, so should be valid in any delegate which supports LPE.
`husk -p1 -o test.exr test.usd`
generates a bunch of different AOVs for me. Some of the AOVs are Karma specific, but `diffuse` and `indirectDiffuse` are defined by LPE, so should be valid in any delegate which supports LPE.
Technical Discussion » Multi-part exr?
- mark
- 2597 posts
- Offline
In October 2019, there was an experimental OpenEXR driver added to H18.0. You can enable this by setting HOUDINI_OIIO_EXR=1.
https://www.sidefx.com/changelog/Main/?journal=18.0&categories=5&body=openexr&version=&build_0=&build_1=&show_versions=on&show_compatibility=on&items_per_page= [www.sidefx.com]
When Houdini reads a multi-part image, the new driver will be used automatically. But for writing, you'll have to set the environment variable.
Please send feedback on how this works for you.
https://www.sidefx.com/changelog/Main/?journal=18.0&categories=5&body=openexr&version=&build_0=&build_1=&show_versions=on&show_compatibility=on&items_per_page= [www.sidefx.com]
When Houdini reads a multi-part image, the new driver will be used automatically. But for writing, you'll have to set the environment variable.
Please send feedback on how this works for you.
Solaris and Karma » Q: Syntax for setting properties in karma/husk command line
- mark
- 2597 posts
- Offline
I don't think there's a way to specify arbitrary properties on the command line. Right now, the only way is to sick a RenderProperties.json file in the search path… Not the most convenient.
And yeah, there should likely be a command line option to disable both motion blur and DOF (which are both on by default). It's really nasty when importing a camera that has fstop set to 5.4 (the USD default is 0 - which is no DOF).
And yeah, there should likely be a command line option to disable both motion blur and DOF (which are both on by default). It's really nasty when importing a camera that has fstop set to 5.4 (the USD default is 0 - which is no DOF).
Technical Discussion » Houdini 18 Karma Custom Fisheye Lens Shader Revisited
- mark
- 2597 posts
- Offline
Solaris and Karma » ggx bsdf function
- mark
- 2597 posts
- Offline
Solaris and Karma » ggx bsdf function
- mark
- 2597 posts
- Offline
The C++ version of the GGX shader should be about the same performance as the cvex_bsdf(). Due to its architecture, Karma can be significantly more efficient when using C++ BSDFs instead of CVEX BSDFs. However, Karma does still support CVEX BSDFs.
I believe that Mantra should still be using the CVEX versions for BSDF evaluation, since mantra's architecture sees performance benefits from keeping everything in VEX.
I believe that Mantra should still be using the CVEX versions for BSDF evaluation, since mantra's architecture sees performance benefits from keeping everything in VEX.
Technical Discussion » Normal map Issue with Karma
- mark
- 2597 posts
- Offline
Houdini Lounge » Karma motion blur
- mark
- 2597 posts
- Offline
There is a known issue with transforms on instances (compared with references) in USD/Solaris/Karma right now, not sure if crag is a different case though. I'll take a look into this tomorrow. This also might be related to an existing bug (99069).
Houdini Lounge » Karma motion blur
- mark
- 2597 posts
- Offline
Was the discrepancy using packed fragmanets with RBD? Packed fragments support angular velocity which is currently not supported in Solaris/Karma.
I think the xform interpolation will likely be left to the client. USD/Hydra really just provide the raw data. Though, I could see USD/Hydra providing utility functions in the future that provide consistent interpolation across delegates, I don't think this is in yet.
I think the xform interpolation will likely be left to the client. USD/Hydra really just provide the raw data. Though, I could see USD/Hydra providing utility functions in the future that provide consistent interpolation across delegates, I don't think this is in yet.
Houdini Lounge » Karma motion blur
- mark
- 2597 posts
- Offline
You're USD file needs to have multiple motion segments. In the viewport, having a cache LOP should enable this for preview rendering.
The alternative is to use velocity motion blur.
There are some known issues with motion blur on nested instances which we hope to address in the new year.
The alternative is to use velocity motion blur.
There are some known issues with motion blur on nested instances which we hope to address in the new year.
Solaris and Karma » Set Resolution and cap max render time
- mark
- 2597 posts
- Offline
At the current time, there's no way to limit the display resolution. That's still on our todo list.
The
From
The
--timelimit
command line option is likely what you're looking for when batch rendering.From
karma --help
--timelimit arg (=-1) Limit rendering time to this number of
seconds
--timelimit-image Time limit applies to images rather than
the whole sequence
--timelimit-nosave-partial If time limit is exceeded, do not save
partial results
Technical Discussion » Optix DSO error when switching to Karma
- mark
- 2597 posts
- Offline
The DSO warnings are a known bug. Typically, the HOUDINI_DSO_ERROR variable is set when debugging, but should probably be left at 0 unless something is going wrong.
We will try to address the issue in a future build of Houdini/Karma.
We will try to address the issue in a future build of Houdini/Karma.
Solaris and Karma » Explicit subdivision refine level
- mark
- 2597 posts
- Offline
This is dependent on the rendering delegate. Each render delegate handles rendering of subdivision surfaces differently.
Karma and RenderMan will use the shading quality/rate to determine how much to refine the surface based on screen space. Other renderers use different metrics.
Karma and RenderMan will use the shading quality/rate to determine how much to refine the surface based on screen space. Other renderers use different metrics.
Technical Discussion » Karma visibility mask
- mark
- 2597 posts
- Offline
Right now, the visibility mask is set using the USD purpose render tags.
https://graphics.pixar.com/usd/docs/api/class_usd_geom_imageable.html#a6071458f7f849cb36a1b467795f2c1aa [graphics.pixar.com]
We realize this is limiting, and will likely expand on this in the future.
https://graphics.pixar.com/usd/docs/api/class_usd_geom_imageable.html#a6071458f7f849cb36a1b467795f2c1aa [graphics.pixar.com]
We realize this is limiting, and will likely expand on this in the future.
Edited by mark - Dec. 6, 2019 13:47:36
Technical Discussion » Karma fatal error when trying to save to disk
- mark
- 2597 posts
- Offline
jsmackThe bug in the switchlightingbsdf should be fixed in the daily build. Please let us know if this persists.
Fur has been rendering fine for me in Karma. There is a bug in the default hairshader though. It's use of the switchlightingbsdf causes a crash. The workaround is to edit the material to remove these ray switches.
Houdini Indie and Apprentice » Couple of Karma questions
- mark
- 2597 posts
- Offline
David PekarekThere are long term plans to improve the Solaris viewport to make it have function similar to the RenderView (with snapshots, etc.)
1 - Apart of mplay support, does anybody know whether there is going to be any sort of more dedicated render window, similar to Render view? I mean it has all sorts of convenience functions, like region render, mouse tracking, ROPs list, Cameras list, progressive render on/off, auto-update switcher, pixel inspector, and others. All this seems to gone away with rendering through viewport. Is Image view (Space+5) supposed to become that? Right now it doesn't offer any additional functionality compared to viewport.
David PekarekA lot of the camera settings are defined by the USD camera: https://graphics.pixar.com/usd/docs/api/class_usd_geom_camera.html [graphics.pixar.com] Each renderer can add their own “custom” controls. It's quite possible in the future, renderers will provide their own HDAs to provide a “nicer” interface to cameras.
2 - This is not exactly a Karma question, but I don't understand the LOPs camera. It's different from SOP Camera, and I find the LOP one very inconvenient to work with right now due to some bizzare controls (or maybe a lack of it). Am I missing something here? Is LOP camera going to be improved significantly? I can still import my camera from SOPs but that seems to be broken right now (when you move the imported cam view it breaks it). On top of this, the resolution is dialed in Karma not on camera which is not great in my opinion. What I am missing are especially these things - a convenient way to set the image aspect ratio and standard image formats, separate zoom control, crop region, rendered resolution, different projections (panoramic, etc.). Of course, a bit more modern take on camera would be very appreciated - physical controls (ISO, exposure, white ballance…) and a nice collection of lens shaders (glows, flares, etc) would be more than welcome.
David Pekarek
3 - How you do ray contributions and ray limits with Karma? I figured all this is supposed to be controlled per object with Render geometry settings LOP, but it doesn't seem to do anything. Broken?
Yes, the Render Geometry Settings LOP is supposed to set these limits. If it's not working properly, please submit a bug with a simple test case.
David PekarekThe display options has a way to turn on render stats (in the Guides tab). Render time should be in the upper left. There's additional verbosity options in the command line renderer.
4 - How can you get verbose? There is a statistics tab but right now it doesn't seem to do anything (on Windows). Also, it'd be great to have switchers for different things to show up in verbose rather than a slider. I mean, I might wanna just see a texture handling info and nothing else for example. Not sure if that's feasible to do but would be great to have.
David Pekarek
6 - Could Render scheduler become a bit more useful? I mean, It alwas pretty much only told you that something is rendering. What about some more functionality, like estimated time remaining for the frame/job? Or maybe a clickable path where the output goes? Or a click to open sequence in mplay?
David PekarekSome of these should be here (image overscan, filters, OCIO support), some are in the works (cryptomatte, render scripts, auto-folder creation, missing/invalid frames, checkpoint resuming etc.). All features will be receiving UI/workflow improvements (it's not exactly easy to find out how to add OCIO LUTs is it?
7 - I presume features like LUTs support, cryptomatte, render scripts, image overscan, image filters, auto-folder creation, render missing/invalid frames, etc. are not there yet, but will be soon?
David PekarekWe will continue to support mantra. We still use the output context for saving USD and starting batch renders from LOPs.
8 - Given how things have changed now, is OUT context become eventually obsolete and removed, alongside with Mantra?
David PekarekThat's a good question
9 - How dependency/chained renders, or generally complex render scenarios, are (will) be implemented into LOPs?
David PekarekIn the long run - but not likely for H18.0.
10 - Is Texture baker gonna be translated into Karma world?
Technical Discussion » Karma beta documentation
- mark
- 2597 posts
- Offline
In today's daily build, you should be able to render to mplay - please let us know if you're still having issues.
The renderview is already a todo item for the future release. I'm not sure if we have an existing RFE for the flipbook issue - so it might be worthwhile to add one.
- Optix happens concurrently, but also when the render is finished. When rendering to disk, the denoiser should only be triggered on final frame.
- For the bounces/limits/motion blur controls, there are “Render Geometry Settings” and “Render Settings” LOPs which control this behaviour. Standard USD inheritance models should work for the geometry settings.
Also note, that for motion blur, you'll likely have to use a cache LOP to make sure Hydra has enough knowledge about adjacent frames.
The renderview is already a todo item for the future release. I'm not sure if we have an existing RFE for the flipbook issue - so it might be worthwhile to add one.
- Optix happens concurrently, but also when the render is finished. When rendering to disk, the denoiser should only be triggered on final frame.
- For the bounces/limits/motion blur controls, there are “Render Geometry Settings” and “Render Settings” LOPs which control this behaviour. Standard USD inheritance models should work for the geometry settings.
Also note, that for motion blur, you'll likely have to use a cache LOP to make sure Hydra has enough knowledge about adjacent frames.
-
- Quick Links