I've been trying out some large scenes (Kitbash3D assets – scene file about 500MB) and every time I close the LV window (irrespective of whether the render is paused or not), C4D hangs. I get the spinning beach ball, and I have to force quit C4D.
This behaviour does not occur with smaller, lower-poly scenes. I've included the crash log after the force quit.
macOS 10.15.6, C4D R21, 64GB RAM, RX 5700XT.
Octane X C4D freeze on closing LV window
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.
- Attachments
-
- Crash log.rtf
- (2.43 MiB) Downloaded 183 times
Hi,
it would be better to have a c4doctanelog, instead of the osx log.
What about materials used in the scene?
Have you converted them all to Octane?
Please, open the scene, then go to c4doctane Settings/Other tab, and, at the bottom of the panel, enable all the Log option checkboxes:
Then, load the scene in Live View until crash, and share the c4doctanelog.txt file that you find in c4doctane directory, or in the path specified in Settings/Other panel, thanks.
ciao Beppe
it would be better to have a c4doctanelog, instead of the osx log.
What about materials used in the scene?
Have you converted them all to Octane?
Please, open the scene, then go to c4doctane Settings/Other tab, and, at the bottom of the panel, enable all the Log option checkboxes:
Then, load the scene in Live View until crash, and share the c4doctanelog.txt file that you find in c4doctane directory, or in the path specified in Settings/Other panel, thanks.
ciao Beppe
Yes, all materials are Octane native. It appears to be a memory issue, given the size of the texture maps and amount of geometry. I'll send a log next time it happens (which will be any minute now as it's pretty repeatable).
Okay, this log is due to simply closing the LV window.
Okay, this log is due to simply closing the LV window.
- Attachments
-
- c4doctanelog.txt
- (2.41 MiB) Downloaded 211 times
Hi,
thanks for sharing the log, and sorry for the late answer.
You are having memory issues, but I think that this is already been fixed in PR1.1.
We are internally testing it, so it should be released very soon.
ciao Beppe
thanks for sharing the log, and sorry for the late answer.
You are having memory issues, but I think that this is already been fixed in PR1.1.
We are internally testing it, so it should be released very soon.
ciao Beppe
Awesome! It's not a deal breaker, just annoying. I used Octane X all day yesterday and it was brilliant; crashed a few times but was largely very usable. Any additional stability will be very welcome!
Kudos of Ahmet for his continued hard work (and to everyone else involved!)
Kudos of Ahmet for his continued hard work (and to everyone else involved!)