Unstable large-ish scene

Forums: Unstable large-ish scene
Sub forum for bug reports

Moderator: 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.

Unstable large-ish scene

Postby sunsneezer » Thu Aug 06, 2020 4:48 pm

sunsneezer Thu Aug 06, 2020 4:48 pm
Windows 10 version 1909 (OS Build 18363.959)
2x RTX 2080TI
128 GB Ram
Nvidia Studio Driver v451.48
OCtane Standalone + PLugin version 2020.1.4
Cinema 4D S22.118(RC)

Loading the scene and sending it to Live Viewer will sometimes hang Cinema 4D.
Sending the scene to Picture Viewer will sometimes do the same but also sometimes outputs a black frame or do a real crash with bugreport (the one attached happened in this context).

Here is the scene (1.4 gB zip)
https://drive.google.com/file/d/1nvBCK6 ... sp=sharing

I'm pretty proud of the optimisation job I did there. BC1 compression all around, Render Instances whenever possible... It all fits neatly in Vram with plenty of leftover!
There is what I think is a reasonable amount of materials, but the meshes are coming from all sorts of dank places, so maybe there is an issue in some data there but I couldn't find any clue to that in the logs.

I'm attaching some logs as well, with some info in the filenames to identify what happened in each.



Deleting the Null that contains the mountains removes the crashes in the LV so far! There is a lot going on in there:
Two Scatter Objects looking at a Vertex map generated by a terrain shader in a shader field, with a random effector on them.
Multiple render instances of a very high poly mountain geo
A material with triplanar mapping on those, to get that easy rocky slope - grassy flats look.

The black PV output could be the Sky objects not loading the HDR file for some reason. Still no idea why it's different from the LV...

[EDIT 2]
Further pinpointed the issue to the scatter objects on the mountains
(175.28 KiB) Downloaded 24 times
Cinema 4D / After Effects / Deadline / GTX 1080 galore
User avatar
Licensed Customer
Licensed Customer
Posts: 7
Joined: Thu Jan 12, 2017 10:53 pm

Return to Bug Reports

Who is online

Users browsing this forum: No registered users and 1 guest

Mon Nov 23, 2020 4:10 pm [ UTC ]