Have a serious bug in a particular scene when using render regions. The sequence causing the crash:
Render the full scene to PV. Stop.
Render to LV, draw a region.
Save and enable the region in Octane Render Settings
Render to PV. Stop.
Refresh render in LV - even with the region still active the whole view is rendering, not the region.
Toggle region on/off to get it to work again.
Create a new region
Save and enable new region in Octane Render Settings
Render to PV. Crash.
It only crashes when certain objects were added back into a test scene, which I have sent to you. Note also the issue with render regions in the LV not being respected.
A. OSX 10.11.6
B. Titan X (local), + Titan X, GTX980 (slaves)
C. 12GB
D. Nvidia driver 346.03.15f04
E. OctaneRender Standalone version 3.04.3
F. OctaneRender plugin version 3.04.3-R1
G. Cinema 4D R18.020
Render Region crash
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.
Windows 10 - 64GB RAM - Cinema 4D R20 - RTX 2070 x3
There is not any relation with render region and adding objects. I couldn't yet reproduce the crash issue.
Don't you have any bugreport.zip to post here?
Don't you have any bugreport.zip to post here?
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Did you get the scene I PMd you?
What I meant was that certain objects in the scene were related to the crash, removing a bunch of objects seemed to solve the problem, but troubleshooting further gave conflicting results. And it was specifically to do with render regions stored in the Render Settings. I used Octane convert materials on those objects, which I normally never do.
https://dl.dropboxusercontent.com/u/461 ... Report.zip
What I meant was that certain objects in the scene were related to the crash, removing a bunch of objects seemed to solve the problem, but troubleshooting further gave conflicting results. And it was specifically to do with render regions stored in the Render Settings. I used Octane convert materials on those objects, which I normally never do.
https://dl.dropboxusercontent.com/u/461 ... Report.zip
Windows 10 - 64GB RAM - Cinema 4D R20 - RTX 2070 x3
Yes with your scene. What kind of objects and operations caused crash? It looks like a renderer crash from bugreport.zip. Any other bugreport.zips?
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
I think you also have to have network rendering enabled to cause the crash. I'll get it to crash and send another bugreport. here's bug report 2
https://dl.dropboxusercontent.com/u/461 ... Report.zip
Do also note there's an issue with the render region not being respected in LV after you render to the PV, stop, and refresh the LV. The Region icon is lit blue and region area is visible in red but the entire buffer is calculated not the region.
Bonus bug: There's some sort of display problem with the Network Slave stats, a word is truncated
https://dl.dropboxusercontent.com/u/461 ... Report.zip
Do also note there's an issue with the render region not being respected in LV after you render to the PV, stop, and refresh the LV. The Region icon is lit blue and region area is visible in red but the entire buffer is calculated not the region.
Bonus bug: There's some sort of display problem with the Network Slave stats, a word is truncated
Windows 10 - 64GB RAM - Cinema 4D R20 - RTX 2070 x3
This still happens. When you say renderer crash what does that mean in terms of getting it fixed - is it being addressed?
I also get system-wide crashes that reboot the machine, its like OS9 days...
(render info is working properly now though)
I also get system-wide crashes that reboot the machine, its like OS9 days...
(render info is working properly now though)
Windows 10 - 64GB RAM - Cinema 4D R20 - RTX 2070 x3
Yes i fixed it. But no crashes on me. So your problem seems like not about renderer. More a system problem.sdanaher wrote:This still happens. When you say renderer crash what does that mean in terms of getting it fixed - is it being addressed?
I also get system-wide crashes that reboot the machine, its like OS9 days...
(render info is working properly now though)
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Great.
I'm using an external thunderbolt enclosure for the local card so that might be the cause of the system lockups. Could be driver related.
I'm using an external thunderbolt enclosure for the local card so that might be the cause of the system lockups. Could be driver related.
Windows 10 - 64GB RAM - Cinema 4D R20 - RTX 2070 x3
Hi There,
in my opinion the "mac pro classic users" have to switch to pc. It's hard to say as a 10 years macuser, but to be honest, since nvidia has released the web drivers with (beta)support for Titan-X my Mac system doesen't run perfectly (bevor i was with a quadro 4000 for mac - everything runs perfect but slow). With the Webdrivers, there are some issues in Photoshop (Filter/Camera Raw/zooming etc./openCL problems) and also in the osx finder (sierra) when using the GPU with webdrivers. On my mac Pro (classic 5,1 with Titanx) i'm getting the same problems with render region crashes, if i switch heavy between LV and Final render in Picture viewer. And, at the moment i'm also not able to start the node editor from the material. I have to start it from the LV dropdown menu.
My solution is: DO NOT USE RENDERREGION!
Because on my PC everthing is fine. As Aoktar told, it seems to be a system problem. And after 3 years of the "new
" Mac Pro lifetime without nvidia on board you have to realize that the future of GPU rendering is not on the mac system.
ONLY if Octane is ready for openCL with the speed of CUDA. Otherwise... it makes no sense to develop an osx version and there are no modern Macs that are supporting it. Just the old iMac with a GTX 780Moblie (but this one has problems with the heating, if you use it all the day – results in System restarts if it's getting to hot), really old macbook pro (same problem if it's getting to hot) and Classic MacPros 
with no official supported modern Nvidia GPUs.
A.MacOs 10.12.2 (16C67)
B.NVIDIA GeForce GTX TITAN X 12287 MB
C.64 GB 1333 MHz DDR3
D. WEBDRIVER 10.15.20 (367.15.10.25f01) / CUDA 8.0.57
E. OctaneRender 3.04.5.app
F. C4D 3.04.5-R2
G. Cinema 4D R18.028 (Build RB177006)
in my opinion the "mac pro classic users" have to switch to pc. It's hard to say as a 10 years macuser, but to be honest, since nvidia has released the web drivers with (beta)support for Titan-X my Mac system doesen't run perfectly (bevor i was with a quadro 4000 for mac - everything runs perfect but slow). With the Webdrivers, there are some issues in Photoshop (Filter/Camera Raw/zooming etc./openCL problems) and also in the osx finder (sierra) when using the GPU with webdrivers. On my mac Pro (classic 5,1 with Titanx) i'm getting the same problems with render region crashes, if i switch heavy between LV and Final render in Picture viewer. And, at the moment i'm also not able to start the node editor from the material. I have to start it from the LV dropdown menu.
My solution is: DO NOT USE RENDERREGION!
Because on my PC everthing is fine. As Aoktar told, it seems to be a system problem. And after 3 years of the "new
" Mac Pro lifetime without nvidia on board you have to realize that the future of GPU rendering is not on the mac system. ONLY if Octane is ready for openCL with the speed of CUDA. Otherwise... it makes no sense to develop an osx version and there are no modern Macs that are supporting it. Just the old iMac with a GTX 780Moblie (but this one has problems with the heating, if you use it all the day – results in System restarts if it's getting to hot), really old macbook pro (same problem if it's getting to hot) and Classic MacPros with no official supported modern Nvidia GPUs.A.MacOs 10.12.2 (16C67)
B.NVIDIA GeForce GTX TITAN X 12287 MB
C.64 GB 1333 MHz DDR3
D. WEBDRIVER 10.15.20 (367.15.10.25f01) / CUDA 8.0.57
E. OctaneRender 3.04.5.app
F. C4D 3.04.5-R2
G. Cinema 4D R18.028 (Build RB177006)
MacPro 12 [email protected] Ghz - 48GB 2933Mhz DDR4 - AMD Radeon Pro Vega II Duo 32GB