OTOY Forums

Hello,

I'm having a problem with the latest version of Blender Octane (2025.2.1 - 30.6.2). To better explain it, I'll use a simple example. First, I'll explain the scenario that's causing this problem.



PC Configuration

Nothing special about the PC:

- AMD 5900X (in eco mode)
- NVIDIA RTX 4070
- 64 GB DDR4
- Blender and the Octane server installed on an SSD. Fairly standard configuration. No issues to report on this front.



Software Requirements

- Latest version of Blender and the Octane server (2025.2.1 - 30.6.2) in its standard version (not just the add-on) and with a default configuration.
- A few plugins for 3D modeling, none for rendering, and just "Node Wrangler for Octane" for nodes.

Overall, the software works correctly.

I should point out that I tested it without the plugins, and it didn't change anything.



The test scene

The test scene is very simple : Starting with an empty scene, I place a plane and a cube (which I put in a collection just to keep it clean - but I don't think that affects the issue). To illuminate the scene, I add a "Texture Environment" in World.

I render, and it works correctly; I have a plane and a cube with a white shader - the default one.



Now, the problem.

On the plane, I create a new shader, and as the screenshot shows, I'm almost able to create a ground texture with displacement.
The problem?

Since I added the "Baking Texture" node, at the slightest change, the Octane server closes and therefore doesn't display any rendering. I should point out that Blender doesn't crash, just the Octane server.

I'm also noticing a certain slowness on the shader panel, which is quite unbearable.

Without this node, things are a little better, but more importantly, the server doesn't crash.

In the console, I don't get any particular messages, no warnings, no errors.

I'm new to Octane, so maybe I'm doing it wrong.

Is this a bug ? A mistake on my part ? Can I create my displacement differently ?

Thanks in advance.

Well, after several tests, I found a way to prevent it from crashing, and to do that, I just have to disable real-time rendering while making changes to the shader.

It seems to have temporarily fixed the issue, but it's still not very practical.

As I've mentioned multiple times, Real-Time rendering isn’t a very “safe” option. It disables some important features and can lead to unexpected bugs in certain situations.
My advice is to keep it turned off while doing serious work.

linograndiotoy wrote: Fri Aug 15, 2025 8:31 am As I've mentioned multiple times, Real-Time rendering isn’t a very “safe” option. It disables some important features and can lead to unexpected bugs in certain situations.
My advice is to keep it turned off while doing serious work.

Thank you for your reply.

But in this case, how can I properly create a shader in Octane without seeing the result, except, of course, re-rendering for each change ?

As mentioned above, it's not practical and wastes time.

Maybe I'm missing something about shader creation and relying a little too much on the Cycles render method.

In any case, thank you for your reply