OTOY Forums

Does anybody else have issues of crashes when loading more complex scenes?

I've saved a few scenes that just makes DAZ crash on loading, and it's getting really annoying, because I have to go back to saving in multiple different ways (scene+various scene subsets) to avoid risk losing everything

It's also not 100% consistant, on one of them I kept trying, and it loaded on one occasion!?

Sadly yes I have had that issue as well. I've learned to save different versions along the way because of it. But I have also found that if I keep trying eventually it will open. Might take 7 tries, but eventually it will open.

Fortunately lately I've only wanted to do simple stuff so I haven't seen this issue in a few weeks.

This is likely due to the issue I think I posted somewhere in this thread about the shader limit. If it's not around, I'll post the info I got from t_3, but I'm pretty sure it's here somewhere, so that thread of known issues might not be a bad idea. Basically, there's a limit (hardware limit), and the new features Octane has requires all of them to be loaded upon opening a scene/subset/whatever, even if they ultimately are not used, so when it gets more complex, it may or may not hit that limit, causing the load to fail. The issue is that because there are so many new things that apply to any given object/surface/material, it's a lot easier to hit this limit now, especially the more complex the scene is. Not sure of a valid workaround, as the way it was presented, it's how Octane API does things, so it's not really controllable by t_3.

Im reporting a bug.

New scene- Create primitive sphere

Add random octane material (tried glass) to sphere

Go to environment tab, Default Hdri- set rgb image, add Hdri to scene.

Render-all OK

save scene

Reload scene -> Instant crash
------------------------------
tried same thing but with default material on sphere and had instant crash also.

if scene is saved with no hdri image it reloads and can continue.

Using Daz 4.6

Going to try update to 4.7

sorry for inglish errors

Same problems here, I'm not even using any third party HDR images, just the ones supplied with OcDS.
I didn't know they were the cause (or one of the possible causes anyway) for crashes while loading my scenes.
Like Linvanchene says it sometimes loads, and other times it crashes... (I'd say about 50-50 chance of one or the other) so all I do is keep trying till it loads okay.

Im not sure how i did this, but i reinstaled 1.2 version out of frustration, a couple hours after decided to give it another try, and i can now load scenes with hdri environment.

i will keep you posted if i can figure out whats happening

sikotik13 wrote:This is likely due to the issue I think I posted somewhere in this thread about the shader limit. If it's not around, I'll post the info I got from t_3, but I'm pretty sure it's here somewhere, so that thread of known issues might not be a bad idea. Basically, there's a limit (hardware limit), and the new features Octane has requires all of them to be loaded upon opening a scene/subset/whatever, even if they ultimately are not used, so when it gets more complex, it may or may not hit that limit, causing the load to fail. The issue is that because there are so many new things that apply to any given object/surface/material, it's a lot easier to hit this limit now, especially the more complex the scene is. Not sure of a valid workaround, as the way it was presented, it's how Octane API does things, so it's not really controllable by t_3.

Scenes are not THAT complicated (2*genesis and some walls), and as Lars said, if I keep trying they'll open fine one out of 10 times.

Also, on the occation that it loaded, I saved all the items into the same subset, and opening that is not a problem. I'm also getting crashes now on loading some of my earlier test scenes that I haven't touched since they worked perfectly fine. I just tried reinstalling DAZ+Octane and clearing out any temp files I could find. Now I can load the old scenes, but the new one is still not working.

The crashes happen also when I disable auto material creation, so it shouldn't even have loaded the shaders at that point.

As in the above posts I was using HDRI, so maybe that's the issue?

Oops, quote is not edit.

Ah, I was going off of the statement you made of "more complex scenes." I was unaware of the HDRI issue, since I haven't used them in version 2 at all, so that very well may be the factor causing the issue. I can occasionally get things to load, but opening the viewport may cause either a freeze or crash with those scenes, so the symptoms seemed similar to me.

I'm vaguely curious how many of these issues are all interdependent/related, code-wise.