OTOY Forums

Could we update the release post for the addon version with the following info:
- What version of Octane is it built against.
- Minimal version of Blender it should work with, or a version it was tested with.

Thanks

I agree, that's important, even if the information is in the non-addon version release post:

viewtopic.php?f=113&t=81652

any updates on when the blender addon will work with Blender 3.6? I tested this morning and it doesn't apparently work.

I just tried to open a scene with the new addon (27.16.4). Unfortunately nothing is rendered in Preview mode - only the wireframes are visible. Final rendering doesn't show anything either. I exported the scene properly from my non-addon version. Not sure what happened. The default scene works as expected.

Here's a screengrab of the Windows console. Maybe it helps ...

pixelmonk wrote:any updates on when the blender addon will work with Blender 3.6? I tested this morning and it doesn't apparently work.

The new addon version working with 3.6 is now available.

great to see the add on version being worked on!
the Aces tone mapping gives me no response what so ever when toggling in the Octane Camera Imager.
What are the steps I need to take if I want the ACES tone mapper back in play (in an otherwise ACES ready blender 3.6 (for cycles))
thanks!

You can try to install the PixelManager config file which includes ACES as well as many other color spaces (like AgX). You should get some infos about that in Silverwing's video here ... https://www.youtube.com/watch?v=rlLCDOt5iMA

The link to the Github for PixelManager is in the description of the video.

thank you, this is indeed a neat config. thanks for posting it.
my question was more in regards to that the add-on version of octane does not seem to behave the same way as the custom build blender. in the viewer panel, toggling the ACES tone mapper doesn't change the image at all and the viewer does not look properly color managed (like it does with the custom build, please see screenshot). so now i have two questions:

- how can I use the config you posted above with the add-on version
- how can I set up the add-on version so it behaves the same way as the custom build in regards to color

many thanks

edit: just seeing you reported the same issue further up in the thread, so i guess it's not resolved yet
edit2: I'm using OctaneBlender Addon 27.16.4 Beta Release [TEST]

You have to load the "config.ocio" file in the addon settings of Octane (screenshot below). After that you can select the various options in the OCIO sections of the Camera Imager or Preview panel.

thank you very much - took me a few attempts for some reason, but I finally got it to work.
Again, the config you posted above is golden - perfect for Vanilla Blender too as it weeds out all the bazillion color transforms that come with the standard ACES package.
great stuff, thanks again!