3.03.2 R5
Network rendering
LV
Render region active
Changed the source or an instance in a scene
no change to render, click Refresh...crash
Net rendering crash (another)
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
Can we keep similar posts in same topic? We're looking that. Thx.
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 was asked before to put different ones in a different post. From my POV its crashing for a different reason.
Please, I'm not a beta tester - make it easier to report and track bugs...
Please, I'm not a beta tester - make it easier to report and track bugs...
Windows 10 - 64GB RAM - Cinema 4D R20 - RTX 2070 x3
Sure nobody is beta tester. But all seems(at least 3 post with NETRENDER) related with netrender. And we'll look it.
Seperated threads are just making harder and confusing to track and answer. Also please post bugs in bugreports section with bugreport.zip if you want to help us.
Thanks!
Seperated threads are just making harder and confusing to track and answer. Also please post bugs in bugreports section with bugreport.zip if you want to help us.
Thanks!
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
Correct, we're users: paid for the software. I'm doing 20x more bug reporting with octane than any other sw I use.
Otoy needs to invest more in a simple bug reporting system, rather than expecting users to do a lot of the leg work. You guys need to make it easier for us, not the other way round.
Otoy needs to invest more in a simple bug reporting system, rather than expecting users to do a lot of the leg work. You guys need to make it easier for us, not the other way round.
Windows 10 - 64GB RAM - Cinema 4D R20 - RTX 2070 x3
It's not so easy and don't know better way. Plugin is build in middle of lot of layers. C4D SDK and Octane Renderer SDK. Also Octane is build on Cuda API. And networking is another layer. Sometimes it's impossible for me to catch exact points due this isolated parts.sdanaher wrote:Correct, we're users: paid for the software. I'm doing 20x more bug reporting with octane than any other sw I use.
Otoy needs to invest more in a simple bug reporting system, rather than expecting users to do a lot of the leg work. You guys need to make it easier for us, not the other way round.
At least posting a BUGREPORT.ZIP and scene with latest step will help to understand where to look.
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 just fixed a deadlock in the net render master which seems to occur only on OSX. It happens when a message was being sent at the same time when some new render data arrived and the master cancelled the current update messages. Hopefully this will solve the issue above.
EDIT: After re-reading your opening post, It will probably not fix it. I will try to reproduce the problem.
EDIT: After re-reading your opening post, It will probably not fix it. I will try to reproduce the problem.
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Ok, I tried to reproduce your problem without any luck. I very quickly run into the problem that the network rendering stops and C4D doesn't wants to quit / crashes during shutdown, but I couldn't make it crash just by clicking refresh in live viewer. The net render hang will be fixed with the next Octane release.sdanaher wrote:3.03.2 R5
Network rendering
LV
Render region active
Changed the source or an instance in a scene
no change to render, click Refresh...crash
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
It just happened again. It was when changing the linked object in a cinema instance while LV was active.
Windows 10 - 64GB RAM - Cinema 4D R20 - RTX 2070 x3
I tried again, but had no luck. Maybe wait until 3.03.3 is out and if the problem still occurs, please send me the C4D scene and the last steps you did until it crashed. Thanks.sdanaher wrote:It just happened again. It was when changing the linked object in a cinema instance while LV was active.
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra