Hi!
RS 3.6.04- doesn't support OCIO 2.3, Houdini 20.5 has OCIO 2.3 by default, the upcoming version of RS will support OCIO 2.3, in the meantime, you can point to another OCIO config with the $OCIO system variable, you can use the .ocio config that comes with Redshift.
Found 161 posts.
Search results Show results as topic list.
3rd Party » New to Redshift with Houdini – Need Help with OCIO Error
- cdordelly
- 162 posts
- Offline
Solaris and Karma » How to remove a sublayer
- cdordelly
- 162 posts
- Offline
Hi,
You can use the Configure Stage LOP to mute layers:
I haven't used it before but looks like it does what you are looking for.
Cheers!
You can use the Configure Stage LOP to mute layers:
I haven't used it before but looks like it does what you are looking for.
Cheers!
Houdini Lounge » Karma XPU in Vulkan viewport less responsive than opengl
- cdordelly
- 162 posts
- Offline
The responsiveness is even less if you have a multi view, I submitted an RFE about this few weeks ago, you might want to add more info to that ticket:
SideFX Support Ticket: #155456
Bug#139821
Cheers!
SideFX Support Ticket: #155456
Bug#139821
Cheers!
Solaris and Karma » MATERIAL override in LOP/SOLARIS, reading primvar
- cdordelly
- 162 posts
- Offline
Hi!
In Redshift, the string user data works only on instances point attributes, no on point/vertex mesh attributes.
In Redshift, the string user data works only on instances point attributes, no on point/vertex mesh attributes.
Solaris and Karma » H20.5 - Light Instances Overrides
- cdordelly
- 162 posts
- Offline
Solaris and Karma » H20.5 - Light Instances Overrides
- cdordelly
- 162 posts
- Offline
I'm having a bit of trouble lining up the wording of this question with the image you posted
Sorry for my bad explanation and thanks for your other answers.
Let's use the car as an example (don't pay too much attention that it is a car, let's think about it as an asset with multiple lights)
1 - Let's say that I have the car asset with the geometry and the light, as an individual asset like this:
As you can see, just for a reference purpose, one light is red and the other is blue (*cyan)
2 - If I instance the Car asset, it is correctly instanced:
3 - Now here is my question, right now if do any light overrides, they will be applied the same to every instanced light:
Now here is my question, there is a way to "map" which lights will be affected by the override? let's say that I want to affect only one of my two lights from this "asset" (Remember to don't pay too much attention that this is a car on the example hehe)
I hope my question is now better understood 😅 :P
Let me know,
Thanks!
Edited by cdordelly - July 29, 2024 15:37:22
3rd Party » Redshift Material Applied to Different Unconnected Islands
- cdordelly
- 162 posts
- Offline
Hi Greg!
Yes you can do something similar to the approach that you mentioned but (unless you want to use Cryptomatte), you don't need to separate your islands in multiple objects/geometry containers.
Check this example:
You can also check the file below.
Hope that helps, cheers!
Yes you can do something similar to the approach that you mentioned but (unless you want to use Cryptomatte), you don't need to separate your islands in multiple objects/geometry containers.
Check this example:
You can also check the file below.
Hope that helps, cheers!
3rd Party » Problem with color space redshift
- cdordelly
- 162 posts
- Offline
Hi!
Probably you are using the OCIO config file that comes with Houdini 20.5 which is not compatible with Redshift right now because it is OCIO 2.3 and RS works with OCIO 2.1 until RS 3.6.04. You can use the Redshift build-in ocio file or the ocio custom config from Saul Espinosa.
Probably you are using the OCIO config file that comes with Houdini 20.5 which is not compatible with Redshift right now because it is OCIO 2.3 and RS works with OCIO 2.1 until RS 3.6.04. You can use the Redshift build-in ocio file or the ocio custom config from Saul Espinosa.
Solaris and Karma » H20.5 - Light Instances Overrides
- cdordelly
- 162 posts
- Offline
Hi Rob!
Another user told me that it was working correctly in the daily build 20.5.307 and it works indeed:
So something is already fixed from this between the current production and the daily build .
It is curious that the "radius" attribute affects the Rectangle light right? or also that the width/height affects a Disk light:
The only thing is that I can't still see the instanced lights on Houdini VK (already mentioned on this thread [www.sidefx.com]), it is the same on your side?
In the other hand, I have one more question about the light instancing workflow, for cases where I have multiple lights in one instanced asset, there is a way to control or "map" the overrides? let's say that I want to apply the overrides only on the "arealight1"
Thanks again!
Another user told me that it was working correctly in the daily build 20.5.307 and it works indeed:
So something is already fixed from this between the current production and the daily build .
It is curious that the "radius" attribute affects the Rectangle light right? or also that the width/height affects a Disk light:
The only thing is that I can't still see the instanced lights on Houdini VK (already mentioned on this thread [www.sidefx.com]), it is the same on your side?
In the other hand, I have one more question about the light instancing workflow, for cases where I have multiple lights in one instanced asset, there is a way to control or "map" the overrides? let's say that I want to apply the overrides only on the "arealight1"
Thanks again!
Solaris and Karma » H20.5 - Light Instances Overrides
- cdordelly
- 162 posts
- Offline
Hi!
With the new light instancing workflow from H20.5, is it possible to override all the USD attributes from the light? I thought that only the color and the intensity were possible to override but thanks to another user I learned that in theory, other attributes should be possible to override too, like the spread or the exposure, the thing is, if I try to override the "height" or the "width" from a rectangle light, it is not working, maybe I'm missing a custom syntax for those cases? or what can I be missing to do this correctly?
For example, if I change from rectLight to disk, the radius attribute override is not working here either.
Let me know if I'm doing something wrong, thanks!
With the new light instancing workflow from H20.5, is it possible to override all the USD attributes from the light? I thought that only the color and the intensity were possible to override but thanks to another user I learned that in theory, other attributes should be possible to override too, like the spread or the exposure, the thing is, if I try to override the "height" or the "width" from a rectangle light, it is not working, maybe I'm missing a custom syntax for those cases? or what can I be missing to do this correctly?
For example, if I change from rectLight to disk, the radius attribute override is not working here either.
Let me know if I'm doing something wrong, thanks!
Technical Discussion » help needed with volume mat assignment in solaris please
- cdordelly
- 162 posts
- Offline
Hi!
Do you have enabled the "Tint Smoke Color with Cd" but you don't have a Cd volume grid with color information, and also might be a good idea to keep the density grid name as "density".
I uploaded the updated file, hope it helps, cheers!
Do you have enabled the "Tint Smoke Color with Cd" but you don't have a Cd volume grid with color information, and also might be a good idea to keep the density grid name as "density".
I uploaded the updated file, hope it helps, cheers!
Solaris and Karma » H20.5 - Light Instances and Viewport visualization
- cdordelly
- 162 posts
- Offline
Hi!
I was testing the new light instancing workflow from H20.5, I noticed that once I create the light instances I can't see them in the viewport but they appear correctly in Karma, that's expected?
I also attached the test hip that I was using.
Let me know, thanks!
I was testing the new light instancing workflow from H20.5, I noticed that once I create the light instances I can't see them in the viewport but they appear correctly in Karma, that's expected?
I also attached the test hip that I was using.
Let me know, thanks!
Edited by cdordelly - July 23, 2024 13:21:32
Solaris and Karma » Colors arent the same in solaris and on final render
- cdordelly
- 162 posts
- Offline
Hi!
Make sure to set the source and output color space into "ACES CG" on the RenderProduct prim, you can create an edit between the Karma render settings and the USD Render ROP.
Probably this is the cause of the color difference.
Make sure to set the source and output color space into "ACES CG" on the RenderProduct prim, you can create an edit between the Karma render settings and the USD Render ROP.
Probably this is the cause of the color difference.
Solaris and Karma » No UI feedback from Karma 'Render to Disk'
- cdordelly
- 162 posts
- Offline
Hi!
Yes the progress bar doesn't appear for single frame renders, it appears for sequence renders. If you want to keep an eye to your render, you can enable the MPlay monitor on the USD Render ROP:
Yes the progress bar doesn't appear for single frame renders, it appears for sequence renders. If you want to keep an eye to your render, you can enable the MPlay monitor on the USD Render ROP:
3rd Party » Problems instaling Redshift
- cdordelly
- 162 posts
- Offline
Hi!
I can't debug the package due to the forum format but maybe you can give a try with the package that was shared on this thread, it should work correctly:
https://www.sidefx.com/forum/topic/93841/ [www.sidefx.com]
Hope it helps,
I can't debug the package due to the forum format but maybe you can give a try with the package that was shared on this thread, it should work correctly:
https://www.sidefx.com/forum/topic/93841/ [www.sidefx.com]
Hope it helps,
Houdini Lounge » Features on Camera enhancement for composition principles
- cdordelly
- 162 posts
- Offline
I see, I'll investigate what is happening with it in H20 (I'm the creator of the tool), for now, to force the refresh of the guides you can disable and enable the "Enable Guides" parm.
Hope it helps, sorry for the problem with H20 :P
Hope it helps, sorry for the problem with H20 :P
Solaris and Karma » MtlX switch textures node
- cdordelly
- 162 posts
- Offline
If you are doing this for instances, you can also try with the string user data workflow. Store the textures on the instances as a string attribute and load the attribute on the material, in theory this doesn't work currently with the MtlX Image because it doesn't support the variadic input yet, but it still works, there is one thread about this but I can't find it. As a plan b from this workflow, you can use the usd texture instead of the mtlx image.
Solaris and Karma » MtlX switch textures node
- cdordelly
- 162 posts
- Offline
You can stack multiple switches to get access to more than 5 inputs by using the If Greater node, so, if you control switch is bigger than 5, it will switch to the second switch, and so on, you can stack multiple inputs with this.
I recently made a mtlx switch node with 10 and 20 inputs because of this, where I used the same logic:
I hope I'll be able to release it next month or in two months,
Hope that helps, cheers!
I recently made a mtlx switch node with 10 and 20 inputs because of this, where I used the same logic:
I hope I'll be able to release it next month or in two months,
Hope that helps, cheers!
Edited by cdordelly - May 30, 2024 11:30:25
Solaris and Karma » Karma cloud dispersion?
- cdordelly
- 162 posts
- Offline
Hi!
You can get the chromatic aberration effect using the Karma Physical Lens shader:
https://www.sidefx.com/docs/houdini/nodes/vop/kma_physicallens.html [www.sidefx.com]
https://www.youtube.com/watch?v=09GCD4ylfQM [www.youtube.com]
You can get the chromatic aberration effect using the Karma Physical Lens shader:
https://www.sidefx.com/docs/houdini/nodes/vop/kma_physicallens.html [www.sidefx.com]
https://www.youtube.com/watch?v=09GCD4ylfQM [www.youtube.com]
Houdini Lounge » Features on Camera enhancement for composition principles
- cdordelly
- 162 posts
- Offline
-
- Quick Links