DS4.6 Render crash solved: Uber environment

martinkeitel_e65f08430a

Hooray!
After weeks of struggling and looking for answers the render problem finally was solved.
Now you daz guys better make a mark of this, so that when others have the same problem you know what to tell them.

Somebody suggested me to update uber environment. I didn't figure the problem was there because the crashes occurred even when uber was disabled.

But it was not about whether it was disabled or not - it was enough just to be there in the scene, doing nothing.
Who would have thought of that??

The thing is that the scenes I work on are originally created on DS3 and apparently an old version of uber env has been carried with version 4, a version that apparently is not compatible. I deleted it and replaced it with uber env that comes with the Cloud9 global lighting sets.

At the moment I'm rendering an image series with Aiko and clothing in high resolution - no problem.
It's not uncrashable though - managed to crash it couple of times, but in more acceptable conditions.

I was just about to start exporting g my scenes to render with another 3D soft.. fortunately it occurred to me the problem was with lights. It's quite a job to make all the textures work with exported scenes.

Thanks for everybody who offered their help, there were all sorts of suggestions but none were right.

So unlike it's been suggested:
1. My hardware is ok.
2 .I t is possible to use DS4.6 without a brand new motherboard, 64-bit OS and 16 Gb RAM.

Richard Haseltine

If you mean the light node in the scene, that isn't the actual shader but rather a piece of data with links to the code and stored settings - so it sounds as if there may be some stored setting from the DS3 version that si causing an issue with DS4. Please make a bug report on this, by opening a support ticket for Technical Support.

Jaderail

Ah, DS3 scene files in DS4.6 often gave me fits until I just updated all the items in the scene from the newer content installed by DIM. All I had to do was load each item in the Scene to a FAKE scene so a NEW Data file was created from the NEW content. Then I could load the old scene files without errors. I just loaded each item once and never set the scene up Then saved as FAKE Scene. That created the Data from the updated content. I did sometimes need to SWAP a item in the DS3 scene by hand but not very often.

The advantage to DIM is if a item gets updated (many have been) you can update your content as soon as the Update is out.

Very Happy your back to Mostly stable. Hope it gets even better for you.

cm152335

mkeitel said:

Hooray!
Thanks for everybody who offered their help, there were all sorts of suggestions but none were right.

Q: do you update the UBER env? (via DIM)

it was my suggest question about your crash render in your previous post!

JonnyRay

Really glad to hear you worked this out.

This should serve as a warning to folks in a few ways...

1. If you're loading a saved scene from previous versions of DS, it is important to check to see if they use some of the advanced plug-ins (lights, surfaces, etc.). If so, making sure the references to the old versions get removed is going to be key to keeping DS stable.

2. When asking for help in the forums on troubleshooting, the more information you can provide the better. A section of the log file from startup to crash would be great so that we can see everything that is getting loaded at startup, scene load, rendering, etc.

3. ALL of us sometimes miss the simple things. I can tell you stories from my years as computer consultant of senior level engineers who have spent hours troubleshooting server problems that ended up being as simple as the network cable wasn't plugged in. Taking time to reset our thinking and start at the "Is it plugged in?" level is a good thing. :)