When running the Commander in Cinema 4D while the Live Viewer in Octane Render is running, it freezes 100% of the time.
This happens in Cinema 4D S26, I don't remember seeing this in R25 or earlier.
The symptoms are very strange and I don't know if it only happens in my environment.
Video of the problem.
https://youtu.be/d1aIPEftZgI
A. Windows 11 Version 21H2 OS Build 22000.795
B. 2x RTX 3090
C. 128GB RAM
D. NVIDIA Studio Driver 516.93
E. F. OctaneRender Enterprise (OctaneRender-for-C4D-2021.1.5-R4-win)
G. Cinema 4D S26
H. As shown in the video, as I run the Commander when Live Viewer is running, Cinema 4D immediately freezes.
This only occurs when the Commander is used while the Live Viewer is running, and not when the Live Viewer is not running or when the menu is used.
Deleting the settings of Cinema 4D, re-intalling the Octane Render, did not resolve the problem.
C4D 26 freezes when I use commander.
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.
Hi,
it could be related to 516.93 Nvidia driver.
Cannot reproduce it here with previous Nvidia Studio version.
Please, try to perform a clean installation of 512.59 Nvidia Studio driver:
https://www.nvidia.com/download/driverR ... 7604/en-us
To perform a clean installation, please follow these steps:
ciao,
Beppe
it could be related to 516.93 Nvidia driver.
Cannot reproduce it here with previous Nvidia Studio version.
Please, try to perform a clean installation of 512.59 Nvidia Studio driver:
https://www.nvidia.com/download/driverR ... 7604/en-us
To perform a clean installation, please follow these steps:
ciao,
Beppe
-
cumuloworks
- Posts: 4
- Joined: Thu Apr 20, 2017 12:52 pm
Hello Beppe, thank you very much for your response.
Actually I already tried several NVIDIA driver versions(including 512.59), and even the latest version does not resolve the problem.
So my guess is that the problem is not driver version related.
I am starting to wonder if there is no other way than a full OS recovery.
Actually I already tried several NVIDIA driver versions(including 512.59), and even the latest version does not resolve the problem.
So my guess is that the problem is not driver version related.
I am starting to wonder if there is no other way than a full OS recovery.
Sorry, do you mind to try with 472.84 version?
https://www.nvidia.com/download/driverR ... 4239/en-us
We have just found another issue with 5xx driver versions, better to stay with 472.84 for now.
ciao,
Beppe
https://www.nvidia.com/download/driverR ... 4239/en-us
We have just found another issue with 5xx driver versions, better to stay with 472.84 for now.
ciao,
Beppe
-
cumuloworks
- Posts: 4
- Joined: Thu Apr 20, 2017 12:52 pm
Hello Beppe, Thank you for your reply.
I tried 472.84, but it did not solve the problem.
(As I troubleshoot the problem, strangely enough, it turned out it was not related to Commander, but to text input as a whole.)
I then did a clean install of Cinema 4D again, which finally solved the problem.
The root cause is still unknown, but it is now working fine with the latest drivers and plug-ins.
The symptoms are very strange and I am not convinced why it was fixed, but thanks for all your help anyway
I tried 472.84, but it did not solve the problem.
(As I troubleshoot the problem, strangely enough, it turned out it was not related to Commander, but to text input as a whole.)
I then did a clean install of Cinema 4D again, which finally solved the problem.
The root cause is still unknown, but it is now working fine with the latest drivers and plug-ins.
The symptoms are very strange and I am not convinced why it was fixed, but thanks for all your help anyway