You can check the log in the OctaneGUI.
In the octane gui, go to the top bar and click "windows"
Then select "craete log window"
Then you should see the logs of this error. Could you share them with me?
If you are using interactive mode and unreal viewport rendering, it might be that the first ...

You can check the log in the OctaneGUI.
In the octane gui, go to the top bar and click "windows"
Then select "craete log window"
Then you should see the logs of this error. Could you share them with me?
If you are using interactive mode and unreal viewport rendering, it might be that the first ...

You can check the log in the OctaneGUI.
In the octane gui, go to the top bar and click "windows"
Then select "craete log window"
Then you should see the logs of this error. Could you share them with me?
If you are using interactive mode and unreal viewport rendering, it might be that the first ...

This section is the error report of the log after RTX acceleration:
CUDA error 2 on device 0: out of memory
-> failed to allocate device memory
CUDA error 2 on device 0: out of memory
-> failed to allocate device memory
OptiX error for device 0: [ERROR] "sbt->raygenRecord" is null
OptiX API error ...

Through the later tests, I found that this is caused by the "use RTX acceleration" option. Once this option is turned on, when rendering large and complex scenes, it will often display errors, or even fail to render directly. However, when RTX acceleration is turned off, it is too slow. My scene ...

Do you mean volumetric fog from unreal? This is not supported atm, but we are looking into it.
You could try to use unreal fog, either by creating a fog octane material, or by using the environment fog that is part of the environment node in the rendertarget.

Hello, thank you for your reply. I ...

I'm trying to render a scene with tens of thousands of plants. When I just click render, the renderer can work normally. But when I switch the lens or modify the scene, the renderer quickly gets stuck when I update or modify the lens. Then I click octane GUI, which displays the part occupied by the ...

At present, the octane renderer of the virtual engine does not have any fog support at all, which results in a very poor sense of level of the rendered scene. When can I support the rendering or conversion of the virtual internal fog?