A. Windows 8.1 Professional
B. 7 x TitanX (Pascal)
C. 128GB RAM
D. Nvidia Driver Version 378.49
E. Octane Standalone 3.05.3
F. Octane Plugin 3.05.3
G. Cinema 4D R16.050
Two Issues I have experienced -
First one happened twice, but am unable to replicate just now as I don't have much free time to setup in-depth procedural materials at the moment -
With the 3.05.3 Live Viewer open, dragging and alt+dropping an Octane Material onto an Octane Mix Material to replace it, C4D becomes unresponsive and subsequently crashes.
Feel free to give it a whirl, tried to replicate it just now without assigning any shaders to the original materials - and it didn't crash. I scanned through to see if anyone had mentioned something similar,
but was unable to find anything. It could possibly be unrelated to Octane, but was more curious to see if anyone else had experienced this.
Last one, I am able to replicate every time -
Upon opening C4D R16.050 without having accessed the live viewer (to initiate the Octane Plugin Activation,) if you were to setup your project in render settings and make Octane the choice of renderer,
C4D crashes. If it doesn't crash, go to the Octane passes menu, and check the checkbox to output passes. I was unable to get past this step with my configuration.
This isn't a big deal, as normally I would have Octane already activated before changing the render settings - but a minor inconvenience to anybody who might set up their project first.
Let me know if you need any more info!
C4D Activation Crash + Material Alt+drop 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.
i7 6950x | 7 x Titan XP 3 x GTX980 | 128GB RAM youtube.com/nikkyyhd
Video capture to show what you did and bugreport.zip. it's what i need.
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
-
CPH_Pixels
- Posts: 10
- Joined: Tue Mar 22, 2016 10:36 am
Hey Ahmet
I just tried on Mac OS X 10.12.3 - Same issue here.
I made a screen capture, and a bug report.
Best
André
A. macOS Sierra 10.12.3
B. GTX 980ti eGPU
C. RAM 6 GB
D. Nvidia webDriver 367.15.10.35f01
E. 3.05.3
F. 3.05.3
G. Cinema 4D R18.039
I just tried on Mac OS X 10.12.3 - Same issue here.
I made a screen capture, and a bug report.
Best
André
A. macOS Sierra 10.12.3
B. GTX 980ti eGPU
C. RAM 6 GB
D. Nvidia webDriver 367.15.10.35f01
E. 3.05.3
F. 3.05.3
G. Cinema 4D R18.039
- Attachments
-
- _BugReport.txt
- (179.61 KiB) Downloaded 266 times
-
- Render_Settings_Crash.mov
- (22.37 MiB) Downloaded 2279 times
First one that i cannot reproduce. Maybe a particular and depends to some unexpected factors. Only i can fix that when i produce here.
Second problem was about using Octane functions before activation of Octane. Since i've changed the activation pattern this kind of problems could appear. I've fixed this on my dev builds. Thanks for info.
Second problem was about using Octane functions before activation of Octane. Since i've changed the activation pattern this kind of problems could appear. I've fixed this on my dev builds. Thanks for info.
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