Dozens of files created with DAZ Studio 4.10.0.123 cause DAZ Studio 4.11.0.383 to crash.

CA415

Has anyone else experienced file load problems with DAZ Studio 4.11.0.383?

I have dozens of project files, many of them very complex with hundreds of objects in them, that load perfectly under DAZ Studio 4.10.0.123, but when I attempt to load them using DAZ Studio 4.11.0.383, the application crashes. The log file reveals nothing about the cause of the crash.

Fortunately, I always keep the previous version of DAZ Studio available when a new version is released in case of problems.

At this point I've had to abandon DAZ Studio 4.11.0.383 and revert back to DAZ Studio 4.10.0.123.

Any guidance would be appreciated.

 

Richard Haseltine

Are you getting a crash report, or does it go straight to desktop? What preview mode(s) are on in the Viewport?

CA415

Thanks for the quick response.

No, a crash report isn't generated and it crashes directly to the desktop.

I keep the viewport in "Texture Shaded" mode.

I've uninstalled and reinstalled DS 4.11.0.383 several times, but nothing seems to help.  Also, I use 3Delight rendering exclusively, so all of my files have had Iray materials converted to 3Delight.

 

Richard Haseltine

What are your system specifications, and what security software are you using?

CA415

Dell XPS-8910 - Intel i7-6700K @ 4 GHz, 32 GB RAM, 5TB hard drive storage.

Windows 10 Pro 64-bit (1809)

nVidia GeForce GTX 1080 - 8GB RAM - nVidia Studio Driver 430.86

Anti-virus: Windows Defender Security + Firewall

Anti-Malware: Malwarebytes

 

Richard Haseltine

Nothing screamingly obvious as a potential issue there, though we have had cases in which the Windows bult-in security software was a possible cuase of trouble (but so many people use that without issues I wouldn't want to point a definite finger). Is this all files or just some? I'm not sure what to suggset next - it sounds as if uploading an example file for someone lse to try might be tricky.

AZDigitalArtist

I am also having a similar problem, except that in addition to the crashes and freezes, Nvidia produces a yellow figure that will not go to preview, and will not render.   I just wanted to do a simple figure in a simple outfit, in a simple premade pose, to render and bring into Photoshop for an art piece.  Not a mega-gb scene with lots of figures and accessories.  It seems unable to do this simple task, and this is getting frustrating.

CA415

Thanks, again, for your help.

No, it appears to be only some files.  Unfortunately, they are mission critical scene files that contain "legacy" products such as Powerage's "The Castle," and Cybertenko's "Sci-Fi Villa."  It's puzzling, since all of the products load flawlessly under DS 4.10.0.123.

Does the latest version of DS sacrifice compatibility and interoperability for resource-intensive enhancements?

I agree that providing a .duf file for analysis would be next to useless since my runtime is loaded with hundreds of product .obj files.

CA415

After spending hours re-creating a group of scene files that caused DS 4.11 to crash, I've found the "cause" but not the reason.

I make extensive use of primitives (cubes, planes, spheres and cylinders) to create custom objects in DAZ Studio.  Apparently, DS 4.11 has changed the way it handles the cylinder primitive.  Specific cylinder-based objects created under previous versions of DAZ Studio are no longer loadable under DS 4.11. Finding all of the instances of cylinder-based objects in all of my project files is a daunting task.  At least I now know "what" to look for.

I've opened a ticket with DAZ Support and provided extensive notes, but I'm still waiting since the sample file is too large to upload through the support ticket form.  It would be great if DAZ developers could find a solution to this issue so I don't have to re-create all affected files - probably in the hundreds!

CA415

Update:

I just downloaded and installed the latest DAZ Studio BETA 4.12.0.33, and the issue with primitive cylinder objects causing a crash appears to have been resolved.

Thanky you DAZ for quickly addressing this issue.

Cyberdene

.I wish I could figure out how to use other rendering engines with DAZ content instead like Blender or something while continuing to support DAZ content, all the crashes, and freezes in IRAY/DAZ really has made it incredibly hard and difficult for me to enjoy rendering at all. And this is coming from someone who used Poser for years, and dealt with painfully slow renders. Yet at the same time, Poser never gave me crashes/freezing issues either regardless if my driver was outdated, or how old my machine was, program always did what it was suppose to do and that's render. Seems like no matter how much people report issues with IRAY/DAZ software nothing seems to be getting done to make it as good as other rendering engines are that none of us can really afford. I spent 1K on my new PC just so I could render cause I thought my 980 card was the reason behind why DAZ/RAY was working so poorly, but seems like even with my 2070 I get crashe/freezes happening on me.

I almost ended up buying a new renderer so I can still use poser content, but like the majority DAZ content just looked so good, the realism and everything is what pursuaded me to drop Poser in favor of using IRAY. For the most part I like the way my renders look compared to waht they use to look like with Poser...But the only thing thats stopping me from fully enjoying DAZ other than difficulties with lighting scenes sometimes is the crashing/Severe Freezes. When this happens a crash report cant be created either, it freezes to the point where I have to always hard reset the machine.