Daz Studio Pro BETA - version 4.11.0.335! (*UPDATED*)
This discussion has been closed.
Adding to Cart…
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.You currently have no notifications.
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
If it only refers to Kepler, then there would be no reason to list the Maxwell-based 900m, and again, I tried the 430.39 driver, and it fails (black screen and cannot find GPU device) for both 4.10 and 4.11 (though it works fine for Steam Games). It seems like the DS Beta's are getting worse in their support of older cards. Hate to be passed by in the next release.
"Integrated Iray 2018.1."
Does this include the Iray 3d camera ability? I would like to not render every scene twice.
I had installed the latest Public Build Beta and was getting nothing but black screen when I tried to render in Iray. Once I downloaded the latest NVidia driver for my card it fixed the issue. The driver was updated on 4-23, have you tried installing the latest driver since then?
Hm. So I haven't downloaded the very newest beta, but at least in the last version Texture Compression doesn't seem to be working at all.
I've set it at 4000 and 512, and 2 GiB is being sent over to my GPU's no matter what.
Can anyone else replicate?
The 900M is a family, not a single card, and in that family the 920M is indeed Kepler based though the other members are Maxwel and so not affected. I would try doing a complete uninstall of your driver, then reinstall and see if that helps. For what it's worth, I am using the 419.35 with a 750Ti under Windows 10 and it renders OK so I'd certainly expect your card to be supported.
I can try 419.35 will take 20 minutes or so to remove and reinstall.
430.39 fails with these errors in both 4.10 and 4.11:
EDIT, Nevermind, I have tried 419.35 before to no avail, see: https://www.daz3d.com/forums/discussion/comment/4441441/#Comment_4441441
I did not try 419.67 or 425.31 yet, so I will give them a shot.
It was more the full uninstall and reinstall that I was stressing - sometimes a driver update will leave bits behind and that can cause issues.
I use DDU for uninstall, and make sure to boot into safe mode for a clean uninstall as recommended. The I choose "Clean Install" from the nVidia Driver, after the reboot is done. Should be a pretty full/clean un and install.
Rolling back to 4.17 so I can keep using DS 4.10.
Did you un-check and then re-check your GPU(s) under Photoreal Render Devices after updating the driver but before attempting to render? Depending on how major the driver update is it may cause Windows to assign new hardware IDs to your existing graphics card(s). Due to an oversight in the way Daz Studio remembers your preferences, it retains which devices were checked/unchecked between driver updates but with their old hardware IDs - leading to "no available render devices" type errors unless you actively uncheck/check everything after an update.
Also, I would avoid ... like the plague ... the Geoforce Experience. I've had horrible luck with that. It gives me BSOD. I do basically what you did, and make absolutely sure I only install the drivers. You still get the control panel with that. And definitely clean install. Then you need to restart.
Precisely what I do too - GeForce Experience seems to be aimed at gamers and I am certainly not that. So drivers only (clean install) and uncheck the rest.
I did that with 430.39, but not with the lat two. I never have to do that when I go all the way back to 417, it just works. For the last two I did the final reboot again, and no help. I have chose not to add the experience as well, during these tests, but I will eventually add it back, as I am a gamer, and I like it, and it always works well for me.
Thanks all for the help. I will sit with 417 again until this "fix" they talk abut in the release notes in May. It's obvious something ain't right for my card, the new drivers and DS.
If anyone could do an accurate speed test comparing the newest beta to the previous one and 4.10 that would be highly appreciated - maybe even with RTX cards?
After seeing all this talk about issues I'm not sure it's worth updating from the previous beta build if there isn't any signifcant speed increase for the RTX cards.
Working on it. Check back here or in the Sickleyield benchmarking thread early next week for results (have a boatload to do before Monday.)
Not sure if it's possible, but it'd be great if we could save both a denoised and noised version of our renders.
Nvidia's algorithm can be too aggressive even on renders with 10,000+ iterations. I'm currently using the denoising feature outside of DAZ so I can combine the images in photoshop and get the best of both worlds.
I agree completely. Non-destructive editing is always the way to go if possible. I believe you’re not losing anything since the denoising algorithm is only working with the 8-bit output and no other information from Iray (no canvases). This is my understanding of the current situation.
I don’t render using Iray often, but when I do I always render out a 32-bit beauty canvas and tonemap/denoise outside of DS.
- Greg
This is correct, but also baffling. Outside of Daz Studio, I use the denoiser on 32-bit HDR canvases to great effect. But being able to get both the noised / denoised from Daz would save me a couple steps!
try File>Save Last Render, which will save without closing the render, then toggle the denoiser and resume the render for a few iterations so it updates and save that.
I don't know .. that seems more a blur than a denoiser. Is the nvidia denoiser really working like that ? Then there's nothing more there than applying a blur filter in GIMP. A denoiser should be aware of bump maps and be able to distinguish between details and noise by analyzing the rendering buffers. That doesn't seem to do so.
EDIT. I'm wondering if 4.11 is passing all the rendering buffers to the denoiser or just the beauty canvas .. that would explain why the denoiser performs so bad.
Clever, Richard! I'll try that tonight and see how it goes. Thank you for the suggestion.
I don't believe it's passing over anything other than the beauty pass. Unfortunately, skin details (pores) and even clothing textures tend to get obliterated. The denoiser works really well on inorganic items and shadowed areas.
Weird bugs: I've already menitioned that the camera PAN tends to stck. Also weird is that the undo feature is a bit off. Sometime it undoes something from a few changes before instead of the latest change.
Not every action is undoable.
Word to live by!
Well learnt one thing do not install over a previous beta, as it completely borked the Studio's layout. And that was mainly due to DiM not installing it correctly, had to delete the beta folder entirely before I could get DiM to install this current build properly..
When 4.11 Release???
Can't wait it,because my DIM never work,can't link to the sever,and can't download the beta version...LOL~~~
Sure it can. You just need to make sure that Public download is checked in settings.
I never even knew that...thanks for sharing Richard!
Thanks for the reply! but my problem is thay DIM can't even connect to the sever...LOL~~~
Hm. Did this, but unfotunately it doesn't save any canvases. I need the HDR beauty pass.
Have you checked your firewall permissions? DIM can't do anything unless it has authorization to contact the outside world.