Daz Studio 4.15 + RTX 3090 not compatible?

[Lust&Passion]

I tried out every nvidia driver and even reinstalled Windows 10. But doesn't matter what I do or which nvidia driver I use, Iray preview always either freezes, falls back to CPU or just stops working (if for example you make some changes in the scene, hide show things or surfaces etc). I got two "MSI RTX 3090 Gaming X Trio" GPUs. I also got a Nvlink bridge. I tried it with and without it. It's the same problem. I tested the GPUs with 3D Mark. Everything was fine.

I'm getting this error for example: "CUDA error string: the launch timed out and was terminated, CUDA error code: 702"
For older drivers I get code 999.

I also found this information:

cudaErrorLaunchTimeout = 702

This indicates that the device kernel took too long to execute. This can only occur if timeouts are enabled - see the device property

You must be registered to see the links

for more information. This leaves the process in an inconsistent state and any further CUDA work will return the same error. To continue using CUDA, the process must be terminated and relaunched.

But how it must be done, I don't know. Does it mean one of my GPUs is defect (Cuda cores)?

I got a 1300W Seasonic PSU and even with a single 3090 it falls back to CPU, which takes a little bit longer. Error code: "CUDA device 1 (GeForce RTX 3090) ran out of memory and is temporarily unavailable for rendering." Which is a joke in a scene with only one character and no background. So, it also can't be a PSU problem.

My only explanation at the moment is that Daz Studio 4.15 and RTX 3090 are still not compatible together!

 

[zger]

im not sure but could be that it doesnt support it yet. u could try to install latest daz3d beta version this can help.

 

[probably_dave]

Hi Lust&Passion,

I'm currently running Daz 4.15.0.2 Pro Edition (64-bit) with an RTX 3090 and it seems to work ok.
Also using GeForce Game Ready Driver 461.09.

I haven't had any problems with any of the renders I've used (I still get some crashes, however I got these before the upgrade) so I don't think it's a full compatibility issue.

Is it specific models that are causing the issue or do standard models (like the base G8F) work alright?

 

[Olympus3DX]

Sometimes it might help to install the CUDA SDK, it solved my issues when running tests using iray server.

You must be registered to see the links

 

[Lust&Passion]

Interactive doesn't work with these cards firstly. Secondly my interior scenes always have a pretty complex lighting system and I won't change it just because Daz Studio isn't capable to work with the cards.
I also put one GPU out and put 3 different PCIe cables into the slots of the GPU to get the most out of the power of the PSU. But it still falls back to CPU with the cuda code 999 or 702 with the latest driver.
An example how it happens. I'm loading one of my character, with clothes and everything. Then in the Iray preview I'm playing around with the surface, changing clothes and then their surface settings etc. Sooner or later it falls back to CPU or if this option isn't available it either crashes or Iray just stops working.
Where to get the latest 4.14 versions of Daz Studio?

 

[Mr B0NES]

I'm running Daz 4.14.1.38 Beta build from a couple weeks back, maybe rolling back to an earlier 4.14 beta would be the answer? Also, I turned CPU fallback off in the Iray advanced options, obviously it's a slight performance loss but Daz does now properly use my 3090 properly it seems.

 

[Lust&Passion]

Well, if you turn CPU fallback off then Iray either just stops working or it crashes.
Where to get Daz 4.14.1.38 Beta? Since Daz Studio was so clever to remove older versions from DIM, I don't know where to get it now.

 

[Olympus3DX]

here you go:

You must be registered to see the links

Somehow I don't think it's Daz causing the problem, but it might be worth a shot

 

[probably_dave]

You mentioned previously that the issue occurred when loading a single character with no background.
Does the issue occur always with this character? Do other characters when loaded by themselves cause the issue?

I has a similar-ish issue (was at render time) with one of my characters and it turned out to be the Dicktator addon not liking the material on the main character (specifically Eli's stubble), If you don't get the issue with a basic G8 model, but do with your custom characters, there could be something up with what you're using on the characters.

 

[Lust&Passion]

You mentioned previously that the issue occurred when loading a single character with no background.
Does the issue occur always with this character? Do other characters when loaded by themselves cause the issue?

I has a similar-ish issue (was at render time) with one of my characters and it turned out to be the Dicktator addon not liking the material on the main character (specifically Eli's stubble), If you don't get the issue with a basic G8 model, but do with your custom characters, there could be something up with what you're using on the characters.

It happens with every scene I'm loading. Either it's a huge complex interior scene with more characters and complex lighting systems or just a single character where I want to adjust some things.

 

[Lust&Passion]

here you go:

You must be registered to see the links

Somehow I don't think it's Daz causing the problem, but it might be worth a shot

Thanks. But it also crashed with it as well. I also installed that cuda toolkit which also didn't help. So, I'm slowly but surely at my wit's end.

 

[Olympus3DX]

Does the card run games?
Or does it also crash when running stress tests like furmark or 3DMark benchmarks?

 

[probably_dave]

or just a single character

Is it a custom character or the base G8M or G8F?
If it doesn't occur with a base character but does with a custom, it would suggest the problem may be with something on the characters. If it also occurs with the generic models, it suggests it's something else.

If it occurs with the base model, the next part would be to check the render settings and disable things like the denoiser.

 

[Lust&Passion]

Does the card run games?
Or does it also crash when running stress tests like furmark or 3DMark benchmarks?

3D Mark test went flawlessly. So, the cards must be fine.
And it happens with G3 and G8 models. Like I said. It happens in every scene I load.

 

[Olympus3DX]

I'm sorry man, that really sucks. I know how frustrating it can be if you can't get it to work and don't know what the issue is.
Hope you can get it working somehow.

 

[probably_dave]

And it happens with G3 and G8 models

Sorry, it was referencing the base models that come with the Genesis 8 starter kit.
You also say it happens with every scene you "load", does it happen when creating a new scene, using only this base model? Or even just a primitive cube?

Another thing to look at is if you have any plugins (Animate 2 caused me some issues once) that may adjust how the rendering works?

I would also suggest raising a ticket with Daz themselves as they might be able to look into it further (using the primitive cube example if it occurs with that). I've seen your forum post, but you can also raise it to their help desk if you haven't done so already.

 

[Lust&Passion]

Well. I put the nvlink out and tested them with DS 4.15 public build. The same Iray preview stress tests as before. It worked for around a minute. Both cards were working as I watched in Afterburner. Then suddenly the preview looked like a graphic error. But only the preview screen. Not the entire PC screen. I still could turn the camera but it looked very weird. Then I hid a shirt the character was wearing and the preview was normal again. But only one GPU was working now. The error reason in the log file was "CUDA device 1 (GeForce RTX 3090) ran out of memory and is temporarily unavailable for rendering". But some other time it could jump again on CPU. It's like Daz Studio does what it feels like.
I had two Titans RTX before and they worked fine with DS 4.12. But also with a very old driver because the newer ones didn't work with Iray.
So, either Daz Studio and the driver have issues or I need a higher PSU than 1300W. I also don't know about if you really need to put one cable in every PCIe slot. I mean the cables have to slots at the end. Do you need to put only one into the GPU to get the most out of the power? If this would be the case then only the Corsair ax1600i and the evga 1600 t2 would offer you that.
I mean those on this pic also used two PCIe dual slots for the GPU and not 3 different dual ones.

 

[megaplayboy10k]

You can try upping the power supply to 1500 or 1600 watts, though most outlets max output is 1875. My own suggestion is to reach out to both daz and Nvidia to see if others have had these issues. You're running the most powerful combo they can support, short of twin a6000 or quadro 8000 cards. But they should support the combo.

Are you running at some super high resolution level, like 4k/8k with similar textures? That's the only way i can imagine getting an out of memory error.

 

[Lust&Passion]

No, I'm rendering in 1080p. But we're talking here just about the Iray preview.
I ordered a 1500W PSU from Be Quiet but I'd prefer the Corsair ax1600i or EVGA 1600 T2. But they're out of stock everywhere in Europe. I'm not sure if you really need 6 different PCIe dual slot cables for the all together 6 GPU PCIe slots or if you also can use two dual cables for 4 slots.

 

[31971207]

I have a single 3090 and Iray preview almost always ended in crash or BSOD for me. Rendering has been much better but I have to reset my overclocked CPU to non-overclocked default or otherwise rendering would caused crash or BSOD at some point as well. So far at non-overlcocked state rendering has been fine and I might start testing IRay preview again. Daz is the only program that caused BSOD after I undervot 3090 when it crashed during gaming due to Ampere power surge.

Daz memory management has always been garbage. Iray preview supposedly stays within DRAM while rendering does not, that rendering is less crash prone than Iray preview, and much more so in CPU overclocked state makes me think maybe this is more a memory leak problem within Daz Iray preview than 3090 driver issue.