OctaneRender 2025.1 for Houdini production (2025.1.0.0)

Sub forum for plugin releases

Moderator: juanjgon

rifat
Licensed Customer
Posts: 62
Joined: Sat Nov 28, 2015 9:06 am
Location: Melbourne

dom_otoy wrote: Thu Apr 17, 2025 12:22 am
rifat wrote: Wed Apr 16, 2025 11:45 pm
dom_otoy wrote: Wed Apr 16, 2025 3:21 pm

Okay that's helpful. If the bug happens in standalone, it means it's usually an octane core issue. Will pass it to the developers! In the meantime if you want you could try the beta2 and see if that issue is there as well.
I'v actually tried on all versions and started to question my life, haha, same for beta2 as well.
only after reinstalling this build again I notice the tick box of the devil.
Haha sorry what do you mean with the tickbox of the devil? The GPU one?
https://app.milanote.com/media/p/images ... /image.png
This tick box. if it's off on 5090, things are normal. Or disable the denoising from the imager altogether.
dom_otoy
OctaneRender Team
Posts: 43
Joined: Mon Mar 17, 2025 9:33 pm

rifat wrote: Thu Apr 17, 2025 1:56 am
dom_otoy wrote: Thu Apr 17, 2025 12:22 am
rifat wrote: Wed Apr 16, 2025 11:45 pm

I'v actually tried on all versions and started to question my life, haha, same for beta2 as well.
only after reinstalling this build again I notice the tick box of the devil.
Haha sorry what do you mean with the tickbox of the devil? The GPU one?
https://app.milanote.com/media/p/images ... /image.png
This tick box. if it's off on 5090, things are normal. Or disable the denoising from the imager altogether.
Hey rifat!
Our devs are still trying to get to the root of this issue.
Would you be willing to share the file you encountered these crashes on?
Another thing that would be helpful is to disconnect the power plug on your 4090 and see if it runs on just the 5090 (when you don't have both cards connected).
If that doesn't work trying a clean install of the latest NVIDIA drivers would be a good next try.

Let me know if you'd be up to help us troubleshoot this, so we can make sure other users don't encounter these issues.
rifat
Licensed Customer
Posts: 62
Joined: Sat Nov 28, 2015 9:06 am
Location: Melbourne

dom_otoy wrote: Tue Apr 22, 2025 3:12 pm
rifat wrote: Thu Apr 17, 2025 1:56 am
dom_otoy wrote: Thu Apr 17, 2025 12:22 am

Haha sorry what do you mean with the tickbox of the devil? The GPU one?
https://app.milanote.com/media/p/images ... /image.png
This tick box. if it's off on 5090, things are normal. Or disable the denoising from the imager altogether.
Hey rifat!
Our devs are still trying to get to the root of this issue.
Would you be willing to share the file you encountered these crashes on?
Another thing that would be helpful is to disconnect the power plug on your 4090 and see if it runs on just the 5090 (when you don't have both cards connected).
If that doesn't work trying a clean install of the latest NVIDIA drivers would be a good next try.

Let me know if you'd be up to help us troubleshoot this, so we can make sure other users don't encounter these issues.
TBH I don't know what is wrong anymore, so far I find 572.83 is most stable. latest driver crashes none stop even with denoiser off on 5090.

I've tried only with 4090 and only 5090 before, also tried both plugged and disabled GPUS in octane setting as well.
it;s defo 5090 issue with octane. Dont use latest driver!

Feel free to try this file https://media.milanote.com/p/files/1U7p ... 0test.orbx

One thing I notice when I use octane is rendering windows don't pick up info for the second GPU.
I also tested system with RS and blender don't seem to have problem of shutting down.
dom_otoy
OctaneRender Team
Posts: 43
Joined: Mon Mar 17, 2025 9:33 pm

rifat wrote: Wed Apr 23, 2025 2:19 am
dom_otoy wrote: Tue Apr 22, 2025 3:12 pm
rifat wrote: Thu Apr 17, 2025 1:56 am

https://app.milanote.com/media/p/images ... /image.png
This tick box. if it's off on 5090, things are normal. Or disable the denoising from the imager altogether.
Hey rifat!
Our devs are still trying to get to the root of this issue.
Would you be willing to share the file you encountered these crashes on?
Another thing that would be helpful is to disconnect the power plug on your 4090 and see if it runs on just the 5090 (when you don't have both cards connected).
If that doesn't work trying a clean install of the latest NVIDIA drivers would be a good next try.

Let me know if you'd be up to help us troubleshoot this, so we can make sure other users don't encounter these issues.
TBH I don't know what is wrong anymore, so far I find 572.83 is most stable. latest driver crashes none stop even with denoiser off on 5090.

I've tried only with 4090 and only 5090 before, also tried both plugged and disabled GPUS in octane setting as well.
it;s defo 5090 issue with octane. Dont use latest driver!

Feel free to try this file https://media.milanote.com/p/files/1U7p ... 0test.orbx

One thing I notice when I use octane is rendering windows don't pick up info for the second GPU.
I also tested system with RS and blender don't seem to have problem of shutting down.
Thank you for providing this info!
So with the 572.83 driver, do you still get crashes if denoising is on on both GPUs?
Also did you physically unplug the 4090 and you still got crashes on the 5090 with denoising with that driver?
atcovrett
Licensed Customer
Posts: 10
Joined: Sun Jun 07, 2015 6:46 am

Very excited to try out the new Realistic Lens models - however, I've noticed some serious limitations:

1) IPR UI controls (ie Pick Focus, Disable DOF) don't work with Realistic Lens enabled.

2) With Realistic Lens enabled, you can't zoom/pan the IPR camera. (Which is extremely important for look development). This functionality works when switching to any other camera model.

2) Adjusting the Sensor Width parameter allows for some necessary reframing in the IPR, but options currently feel too limited when adjusting the DOF intensity and camera focus distance.

3) As others have noted, when working with Realistic Lens, the IPR struggles to register and update camera/object repositioning without a full-scene reload. (Annoying!)

I'd also like to request a few additional features:

4) It would be incredible to have independent Pan/Zoom functionality on the IPR canvas. Currently, zoom/pan actually modifies the scene camera, which isn't always helpful as that changes the composition/camera positioning, and resets the IPR sampling. In my opinion, this is currently the most disruptive 'quirk' when coming from other working environments/DCCs.

5) Unless I'm missing something, there's doesn't seem to be an intuitive way to work with LUTS when also working in ACES. Ideally, there'd be a way to apply a LUT transformation after the ACES conversion to sRGB display.
dom_otoy
OctaneRender Team
Posts: 43
Joined: Mon Mar 17, 2025 9:33 pm

atcovrett wrote: Fri Apr 25, 2025 2:51 pm Very excited to try out the new Realistic Lens models - however, I've noticed some serious limitations:

1) IPR UI controls (ie Pick Focus, Disable DOF) don't work with Realistic Lens enabled.

2) With Realistic Lens enabled, you can't zoom/pan the IPR camera. (Which is extremely important for look development). This functionality works when switching to any other camera model.

2) Adjusting the Sensor Width parameter allows for some necessary reframing in the IPR, but options currently feel too limited when adjusting the DOF intensity and camera focus distance.

3) As others have noted, when working with Realistic Lens, the IPR struggles to register and update camera/object repositioning without a full-scene reload. (Annoying!)

I'd also like to request a few additional features:

4) It would be incredible to have independent Pan/Zoom functionality on the IPR canvas. Currently, zoom/pan actually modifies the scene camera, which isn't always helpful as that changes the composition/camera positioning, and resets the IPR sampling. In my opinion, this is currently the most disruptive 'quirk' when coming from other working environments/DCCs.

5) Unless I'm missing something, there's doesn't seem to be an intuitive way to work with LUTS when also working in ACES. Ideally, there'd be a way to apply a LUT transformation after the ACES conversion to sRGB display.
Hey atcovrett
Thank you for submitting your feedback!
- To 1&2 yes those thing should be fixed. Our dev is on vacation for just a few more days, but will have him take a look when he's back! For now as a workaround what I would recommend is working using one of the other lens options with the appropriate focal length and then switching to the realistic lens for final render.

- On the... second 2? :D ... so that is a limitation of how the realistic lens works. We can't just change the focal length on the fly as it simulates a real lens, with real glass elements etc, so in terms of a zoom, all we have for now is changing the sensor width. Now maybe they will add "zoom lenses" at some point, but for now that's not the case. Not sure if that's what you meant. One thing that is currently not working is the fstop parameter on the camera, and hopefully that will be fixed here soon, that will at least give you control over the depth of field.

- 3. Hmm I'm not really having any issues with the realistic lens updating in the viewport as I move around. Can you give me a little more info in what ways you're having issue there? Because there is a separate issue where scene geometry is disappearing in animated scenes in the latest build, which is not related to the realistic lens. Do you have an animated camera and the motion is not tracking in the viewport? Or is the issue more with live panning and moving the camera around? What houdini version and what os are you on? The more info you can provide on this the more likely we can improve the issue!

- 4. Yes that's been something that's been requested a lot. I think that's something we will try to get in, but just not sure when :)

- 5. So if you're working in ACES but want to preview luts the way to do that is with the custom output AOVs. If you dive into the rendertarget it will take you to the output AOV section, with one example AOV setup already. You can plug in an "Apply LUT" node into the layer group and add your lut there.
Screenshot 2025-04-25 105129.png
Sorry for the inconvenience. Hopefully we can get most of these things resolved here soon!
dom_otoy
OctaneRender Team
Posts: 43
Joined: Mon Mar 17, 2025 9:33 pm

rifat wrote: Wed Apr 23, 2025 2:19 am
dom_otoy wrote: Tue Apr 22, 2025 3:12 pm
rifat wrote: Thu Apr 17, 2025 1:56 am

https://app.milanote.com/media/p/images ... /image.png
This tick box. if it's off on 5090, things are normal. Or disable the denoising from the imager altogether.
Hey rifat!
Our devs are still trying to get to the root of this issue.
Would you be willing to share the file you encountered these crashes on?
Another thing that would be helpful is to disconnect the power plug on your 4090 and see if it runs on just the 5090 (when you don't have both cards connected).
If that doesn't work trying a clean install of the latest NVIDIA drivers would be a good next try.

Let me know if you'd be up to help us troubleshoot this, so we can make sure other users don't encounter these issues.
TBH I don't know what is wrong anymore, so far I find 572.83 is most stable. latest driver crashes none stop even with denoiser off on 5090.

I've tried only with 4090 and only 5090 before, also tried both plugged and disabled GPUS in octane setting as well.
it;s defo 5090 issue with octane. Dont use latest driver!

Feel free to try this file https://media.milanote.com/p/files/1U7p ... 0test.orbx

One thing I notice when I use octane is rendering windows don't pick up info for the second GPU.
I also tested system with RS and blender don't seem to have problem of shutting down.
Hey rifat!
Do you have any ofx installed on your machine?
I started running into the same issue after installing the red giant suite but after disabling the ofx path this fixed the crashes...
Can you try putting this in your houdini.env and see if it helps?
HOUDINI_DISABLE_OPENFX_DEFAULT_PATH = 1
rifat
Licensed Customer
Posts: 62
Joined: Sat Nov 28, 2015 9:06 am
Location: Melbourne

dom_otoy wrote: Wed Apr 23, 2025 4:25 pm
rifat wrote: Wed Apr 23, 2025 2:19 am
dom_otoy wrote: Tue Apr 22, 2025 3:12 pm

Hey rifat!
Our devs are still trying to get to the root of this issue.
Would you be willing to share the file you encountered these crashes on?
Another thing that would be helpful is to disconnect the power plug on your 4090 and see if it runs on just the 5090 (when you don't have both cards connected).
If that doesn't work trying a clean install of the latest NVIDIA drivers would be a good next try.

Let me know if you'd be up to help us troubleshoot this, so we can make sure other users don't encounter these issues.
TBH I don't know what is wrong anymore, so far I find 572.83 is most stable. latest driver crashes none stop even with denoiser off on 5090.

I've tried only with 4090 and only 5090 before, also tried both plugged and disabled GPUS in octane setting as well.
it;s defo 5090 issue with octane. Dont use latest driver!

Feel free to try this file https://media.milanote.com/p/files/1U7p ... 0test.orbx

One thing I notice when I use octane is rendering windows don't pick up info for the second GPU.
I also tested system with RS and blender don't seem to have problem of shutting down.
Thank you for providing this info!
So with the 572.83 driver, do you still get crashes if denoising is on on both GPUs?
Also did you physically unplug the 4090 and you still got crashes on the 5090 with denoising with that driver?
Sorry guys it wasn't octane or the driver, I was a faulty cable .....
Is swopped it between 4090 and 5090 , and 5090 started working with octane no crash at all...
however same cable on 4090 works fine ...
i guess 50 cards just needs extra cares ,,
dom_otoy
OctaneRender Team
Posts: 43
Joined: Mon Mar 17, 2025 9:33 pm

rifat wrote: Sat May 03, 2025 12:38 pm
dom_otoy wrote: Wed Apr 23, 2025 4:25 pm
rifat wrote: Wed Apr 23, 2025 2:19 am

TBH I don't know what is wrong anymore, so far I find 572.83 is most stable. latest driver crashes none stop even with denoiser off on 5090.

I've tried only with 4090 and only 5090 before, also tried both plugged and disabled GPUS in octane setting as well.
it;s defo 5090 issue with octane. Dont use latest driver!

Feel free to try this file https://media.milanote.com/p/files/1U7p ... 0test.orbx

One thing I notice when I use octane is rendering windows don't pick up info for the second GPU.
I also tested system with RS and blender don't seem to have problem of shutting down.
Thank you for providing this info!
So with the 572.83 driver, do you still get crashes if denoising is on on both GPUs?
Also did you physically unplug the 4090 and you still got crashes on the 5090 with denoising with that driver?
Sorry guys it wasn't octane or the driver, I was a faulty cable .....
Is swopped it between 4090 and 5090 , and 5090 started working with octane no crash at all...
however same cable on 4090 works fine ...
i guess 50 cards just needs extra cares ,,
No worries!
Glad you figured it out!
Thanks for the update!
rifat
Licensed Customer
Posts: 62
Joined: Sat Nov 28, 2015 9:06 am
Location: Melbourne

Hi quick question.

Does this version work with Lops ?
"PXR_PLUGINPATH_NAME": {
"value": "$OCTVERSION/dso/usd_plugins"
Seems like there isn't a USD_PLUGINS folder.
Post Reply

Return to “Releases”