Version 27.16 Feedback Tweet

[Andreas_Resch]

I'm not sure where best to post feedback/bugs for version 27.16, but why not start a thread here.

So far everything works great. Not sure if I'm imagining it, but the preview seems to be significantly faster. Setting the kernels up isn't hard and once that's done one can easily overwrite the startup.blend file - I like that.

There's one thing though. The "ACES tone mapping" checkbox doesn't seem to work. Neither in the Preview flyout nor in the Camera Imager panel. Not a big issue as I can always load the config file manually (and maybe even use AgX). But just wanted to mention it.

[elsksa]

Hi,

Could you share a .gif or hosted video of the issue?
To provide context to others and be able to confirm.

Here or typically what most do, directly as a reply to the initial thread: https://render.otoy.com/forum/viewtopic.php?f=113&t=81626 as an easier way to track down issues related to a particular version but I don't think it's obligatory.

[Andreas_Resch]

There's no reply button in the Releases section (for me). Access seems to be restricted there.

Checking the ACES tone mapping button doesn't result in any changes (image below). Neither in the preview panel nor in the camera imager panel.

[elsksa]

Fair enough, I believe the access is restricted to licensed users.

Nothing in the Console log?
I'd lean on a minor "bug".

Is it occurring on all Camera Imagers?
Is a OCIO config-file loaded (even if unused)? Preferences or env-var.

[pegot]

Any info on when a Mac version will be available. I’m having horrible issues with many of my plugins not working with current Mac Octane Blender versions while they work perfectly in regular Blender releases.

[tapanojum]

Can't believe the addon is finally here, going to play around with it more later today. So far, loading in my old scenes or even importing characters crashes to desktop instantly.

# Python backtrace
File "C:\Users\User\AppData\Roaming\Blender Foundation\Blender\3.5\scripts\addons\octane\core\octane_node.py", line 106 in _update_to_engine
File "C:\Users\User\AppData\Roaming\Blender Foundation\Blender\3.5\scripts\addons\octane\core\octane_node.py", line 109 in update_to_engine
File "C:\Users\User\AppData\Roaming\Blender Foundation\Blender\3.5\scripts\addons\octane\core\object_cache.py", line 602 in update_object
File "C:\Users\User\AppData\Roaming\Blender Foundation\Blender\3.5\scripts\addons\octane\core\object_cache.py", line 705 in custom_update
File "C:\Users\User\AppData\Roaming\Blender Foundation\Blender\3.5\scripts\addons\octane\core\caches.py", line 114 in update
File "C:\Users\User\AppData\Roaming\Blender Foundation\Blender\3.5\scripts\addons\octane\core\session.py", line 181 in view_update
File "C:\Users\User\AppData\Roaming\Blender Foundation\Blender\3.5\scripts\addons\octane\__init__.py", line 216 in view_update

Edit: Seems like there has been some node changes since I've last used Octane last summer. Guess the image node has changed? Is there a way to convert these somehow? It's going to be a major pain in the ass to manually do this.

Edit 2: Still struggling with Blender's particle hair, which is why I ultimately couldn't use Octane for my current project. I can't get it to render hair curves at all, which is probably just an error on my part.

Create plane, add curves>fur, set to use Octane Hair Radius. Hit render, hair doesn't show and the UI gets this visual artifact until I turn render off.

[Andreas_Resch]

Will the standalone free tier version of 27.16 still be released or is it just the addon from now on?

[linograndiotoy]

Before loading an "old" scene in the addon version, it's important to use the File/Export/OctaneBLender_Addon option.
This will generate a new scene with the "addon" suffix that should be loaded correctly into the addon version.

[Andreas_Resch]

Great to see the new addon version. Looks a lot more complete.

There are two bugs that I can see immediately. They occur when loading scenes or appending objects from scenes from the packaged version.

1) The World output isn't correct and not connected up. See attached image.

2) I have some objects/materials that use grouped mapping nodes. When I append those, Octane goes a bit crazy. The render preview stops and when I restart it, it's all white and flickers occasionally. Also the Shader editor UI has a weird display error after that. Even if I delete the imported problematic object, Octane doesn't seem to recover from that. I will have to reload the scene. If I ungroup the mapping group and the append the object/material, it seems to work. I've created a screencast that you can download here ... http://www.argfx.at/upload/Octane_AddonTest_01.zip

I will try to export the problematic files with the "export addon version" procedure mentioned above. But it would be great if that could be fixed eventually as otherwise you would always have to keep an old packaged version installed just to load and convert old scenes.

[Andreas_Resch]

I've loaded another "old" test scene into the addon version. The scene was exported via "export addon version". I've stripped everything from the file that I thought might cause issues. Yet the scene still flickers in the render preview. I've uploaded both a screencast as well as the scene itself to check out.

Screencast ... http://www.argfx.at/upload/Octane_AddonTest_02.zip
Blender file ... http://www.argfx.at/upload/Octane_CMTest_02_addon.zip

Windows 10, RTX 3060, Blender 3.5