I think I found a solution.
The log gave away, that the octane.dll and octane.dat were not found.
So I located them and put them into the folder, the plugin was looking for them, according to the log (...\Runtime\Python\addons\OctaneRender\Windows\octane.dll and ...\Runtime\Python\addons ...

Hi Paul,
thanks for the update of the plugin, but it won't start on my end.
I'm getting the following error msg., even tho I've just updated to the latest nvidia driver (572.83) for Win 10 64bit, the just released new Poser version (13.3.1041) and rebooted.
or2025.PNG
The latest or 2024 version ...

Thanks for the update :D
Is it the same version as in https://render.otoy.com/forum/viewtopic.php?f=45&t=82277&start=20#p433986 ? (as it has the same version number, but it's compiled to a different 2024 version of OR?) The build in that thread was a pre-release, so this has some python code ...

Thanks for the update
Is it the same version as in viewtopic.php?f=45&t=82277&start=20#p433986 ? (as it has the same version number, but it's compiled to a different 2024 version of OR?)

I also noticed, that when you open the device settings and tick or untick the Denoise option, it re-starts the rendering. This didn't happen in previous versions.
But I guess that OR 2023.1.2 related, not the plug in (can't test it on the stand alone, as I don't have it installed, atm.)

I understand. I think this version should resolve the issue. Can you please confirm?

https://render.otoy.com/customerdownloads/plugins/5f/40/cf/0b/OctaneRender_for_Poser_2023_1_2_123_STUDIO.exe

Thanks

Paul
Looking good so far.
Render AOVs -> Render passes are all visible again.
123.png ...

Maybe at one point, the OR devs switched up this system, and I just didn't catch it =D If you rightclick the rendertarget and "Load from Default" does it fix the issue?

Paul
I can't, as it's greyed out for me. Looks like I don't have a default RT file.
Saving a default file is possible.
def.png

Hi Paul,

thanks for having a look.
The other installer for 2023.1.2.122 didn't change anything for me.

I think I noticed this behavior quite a while back already, but forgot about it, as I at one point exported the rendertarget setting I once used (as a *.por file) from an old scene and re-using ...

Silly question maybe ...
In previous versions there was an option, to set the "Render AOVs" to "Render passes" and in there, enable/disable the passes we wanted to get over into in the "Viewport" (or not).
(The long list of render passes, we could choose from)
prev.png
and in the Viewport, using ...

Yay!
Thank you