A.Windows 11
B.RTX4090 game rock
C.128GB
D.Various
E.na
F.since 2023.1 upto now still
G.again various. Since c4d 2023 and happening still on 2025
H.here is a list that has caused crashes over the last two years that still are occurring
- Color pickers when you click in colour box (ie make world environment black rather than default white) or colour picking a diffuse colour in the node interface
- renaming by double clicking in hierarchy
- opening octane settings GUI
- Send render to picture viewer ( 1st usually okay unless program has been open for long time, 2nd-3rd send to picture viewer render causes crash)
-sometimes opening render settings or changing tabin render settings
-changing save location of a multipass EXR
-Rare but happens (moving an object from a hierarchy null to the root)
-The most annoying one being opening the node editor/tweaking/or accidental clicks
All these just seem to close cinema 4d sometimes with a c4d bug message dialog box sometimes it just disappears.
These also seem to occur after a period of time of cinema 4d being open. And occurs wheter or not Live viewer is running.(happens faster if live viewer is running)
Cinema 4D Crash Triggers
Moderators: ChrisHekman, aoktar
Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
H. A detailed description of the issue and steps to reproduce it (Include Screenshots or video capture), as well as an example scene if applicable.
I. Copies of the Octane Log window and Console window outputs (full text attached as a file to your post is recommended).
Please note that reports of issues inside existing threads will be ignored/removed, and reports may be closed if the reporter does not respond to subsequent queries in the thread.
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
H. A detailed description of the issue and steps to reproduce it (Include Screenshots or video capture), as well as an example scene if applicable.
I. Copies of the Octane Log window and Console window outputs (full text attached as a file to your post is recommended).
Please note that reports of issues inside existing threads will be ignored/removed, and reports may be closed if the reporter does not respond to subsequent queries in the thread.
-
EMAGICSTUDIOS
- Posts: 11
- Joined: Fri Dec 28, 2018 1:46 pm
Last edited by EMAGICSTUDIOS on Mon Mar 03, 2025 11:58 am, edited 1 time in total.
Not to sound glib, but honestly your experiences are the same as most octane users. We report bugs which are reproducible, but the honest truth is that most octane crashes tend to be utterly random and unexplainable. You can crash it pressing undo, changing a material, copy pasting, dragging a slider, moving a light; There is no action you can do which won't cause octane to vanish into a black hole. More than once we've witnessed octane crashing on a machine with nobody using it whilst not rendering.
But, we still use and love it because its the best choice, despite it's eternal stability issues.
If you find a bug which can reliably be reproduced, post it here with steps to reproduce it and they will often quickly fix it, but the broader one-off random crashes, thats just octane.
But, we still use and love it because its the best choice, despite it's eternal stability issues.
If you find a bug which can reliably be reproduced, post it here with steps to reproduce it and they will often quickly fix it, but the broader one-off random crashes, thats just octane.
-
EMAGICSTUDIOS
- Posts: 11
- Joined: Fri Dec 28, 2018 1:46 pm
I do understand what you are saying but for every hour cinema4d will crash 3-10 times and ive not bothered sharing because i thought it would get better or its something to live with. But its software that is subscription based and ive recently had a project that was fairly big and it slowed me down, because I had to remember the last few steps (2-7mins ler save) .a As a result of this I have got into a horrible habbit of saving before actually seeing if i like a change as im scared it will crash all the time.
Another major reason for flagging is because Windows7, Cinema R20 and Octane 4 used to be more stable for me. (Still quirky but not shocking) Then again 2021 and 2022 builds with windows 7 where okay. Its only got worse since the later versions and windows 11 for me which has been the past two years.
Another major reason for flagging is because Windows7, Cinema R20 and Octane 4 used to be more stable for me. (Still quirky but not shocking) Then again 2021 and 2022 builds with windows 7 where okay. Its only got worse since the later versions and windows 11 for me which has been the past two years.
Hi EMAGICSTUDIOS,
please write to help at otoy dot com asking for Beppe.
I would like to see what type of crashes you are having.
ciao,
Beppe
please write to help at otoy dot com asking for Beppe.
I would like to see what type of crashes you are having.
ciao,
Beppe
-
EMAGICSTUDIOS
- Posts: 11
- Joined: Fri Dec 28, 2018 1:46 pm
Hi Beppe,
Thank you for reaching out. I will record my next few cinema 4d sessions and send over the video files.not sure when ill get chance but it will help give you some idea of whats happening. Thanks again.
Jack
Thank you for reaching out. I will record my next few cinema 4d sessions and send over the video files.not sure when ill get chance but it will help give you some idea of whats happening. Thanks again.
Jack
Sorry, I was meaning"I would like to see some logs of your crashes".
So please, write to help at otoy dot com so we can generate some logs to better understand what is going on in your case.
ciao,
Beppe
So please, write to help at otoy dot com so we can generate some logs to better understand what is going on in your case.
ciao,
Beppe
Did you contact Beppe on support about this?EMAGICSTUDIOS wrote:A.Windows 11
B.RTX4090 game rock
C.128GB
D.Various
E.na
F.since 2023.1 upto now still
G.again various. Since c4d 2023 and happening still on 2025
H.here is a list that has caused crashes over the last two years that still are occurring
- Color pickers when you click in colour box (ie make world environment black rather than default white) or colour picking a diffuse colour in the node interface
- renaming by double clicking in hierarchy
- opening octane settings gui
-sometimes opening render settings or changing tabin render settings
-changing save location of a multipass EXR
-Rare but happens (moving an object from a hierarchy null to the root)
-The most annoying one being opening the node editor.
All these just seem to close cinema 4d sometimes with a c4d bug message dialog box sometimes it just disappears.
These also seem to occur after a period of time of cinema 4d being open. And occurs wheter or not Live viewer is running.(happens faster if live viewer is running)
What I would like to know is:
your Nvidia Driver Version
Your HAGS settings "Hardware Accelerated GPU Scheduling" settings and if you perhaps have set Cinema4D to "Game Mode" in that window.
We saw that the checkbox "Optimisations for Windowed Games" can cause all kinds of instabilities with C4D+Octane.
Your experience definitely is not "normal".
-
EMAGICSTUDIOS
- Posts: 11
- Joined: Fri Dec 28, 2018 1:46 pm
Hey DinoMuhic
Yep just sent reports and few videos
As for NVidia Drivers, there are various combos. Now is the most stable it has been for a while, with everything on the latest version. But still get crashes. Only been since moving to windows 11 that its bad.
Do you mean these settings as pictured? (I've just turned off)
thank you
Yep just sent reports and few videos
As for NVidia Drivers, there are various combos. Now is the most stable it has been for a while, with everything on the latest version. But still get crashes. Only been since moving to windows 11 that its bad.
Do you mean these settings as pictured? (I've just turned off)
thank you
DinoMuhic wrote:Did you contact Beppe on support about this?EMAGICSTUDIOS wrote: A.Windows 11
B.RTX4090 game rock
C.128GB
D.Various
E.na
F.since 2023.1 upto now still
G.again various. Since c4d 2023 and happening still on 2025
H.here is a list that has caused crashes over the last two years that still are occurring
- Color pickers when you click in colour box (ie make world environment black rather than default white) or colour picking a diffuse colour in the node interface
- renaming by double clicking in hierarchy
- opening octane settings gui
-sometimes opening render settings or changing tabin render settings
-changing save location of a multipass EXR
-Rare but happens (moving an object from a hierarchy null to the root)
-The most annoying one being opening the node editor.
All these just seem to close cinema 4d sometimes with a c4d bug message dialog box sometimes it just disappears.
These also seem to occur after a period of time of cinema 4d being open. And occurs whether or not Live viewer is running.(happens faster if live viewer is running)
What I would like to know is:
your Nvidia Driver Version
Your HAGS settings "Hardware Accelerated GPU Scheduling" settings and if you perhaps have set Cinema4D to "Game Mode" in that window.
We saw that the checkbox "Optimisations for Windowed Games" can cause all kinds of instabilities with C4D+Octane.
Your experience definitely is not "normal".
- Attachments
-
- Settings HAGS