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
These are what the log is showing after a render crash.
Do I need to send more lines from the log? I figured I got everything from todays render crash.
It has to be something with 4.14 as 4.12 was working fine all this week.
I was going to ask the same thing. Is there any way to download a previous version? I'm on meltdown mode and I have to get work done, due on the 27th. Now that I'm updated on Big Sur, will the previous versions not even work? Again, I cant even download DS or the DIM on my laptop still running on catalina.
Iray has been updated since then
https://www.daz3d.com/forums/discussion/449311/daz-studio-pro-4-14-nvidia-iray#latest
The only way to get a previous version is to ask customer support.
I'm at a loss and you can't get a hold of tech support anymore. they claim they're all working on something else. I sent in a help ticket for a problem I was having last August, it has NEVER been touched.
I can't imagine having this kind of an issue where you work using this software and have this happening. I'm only a hobbist. I can open and play using my Windows PC. I'll just keep waiting for updates to happen, if they do.
My Nvidia driver is newly installed this week. I can't get a hold of customer support, unless theres a way I don't know about, which there probably is.
Only 2GB? That is going to be very limiting, especially as extra code is now set to non-RTX cards to implement the features RTX cards have built in. But what I wanted to see are the messages during and after the render, not the start up messages.
That's just about starting DS, you are not loading any scene or characters in it, nothing to render.
Heres from yesterdays render crash.
studio 4.14 render crash log \Genesis8\FemaleBase\G8FBaseEyelashes_1006.jpg", pixel type "Rgb", 2048x2048x1 pixels, 1 miplevel.
2020-11-12 21:05:17.860 Iray [INFO] - IMAGE:IO :: 1.0 IMAGE io info : Loading image "C:\Daz 3D\Applications\64-bit\DAZ 3D\DAZStudio4\shaders\iray\resources\DTHDR-RuinsB-500.hdr", pixel type "Rgb_fp", 512x256x1 pixels, 1 miplevel.
2020-11-12 21:05:18.253 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating geometry.
2020-11-12 21:05:18.253 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating motion transforms.
2020-11-12 21:05:18.253 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Importing scene graph.
2020-11-12 21:05:18.292 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Auto instancing compression ratio 1.00 (Full instancing compression ratio 1.00)
2020-11-12 21:05:18.292 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Importing geometry for motion time 0
2020-11-12 21:05:18.359 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Geometry import (1 triangle object with 527k triangles, 0 fiber objects with 0 fibers (0 segments), 1 triangle instance yielding 527k triangles, 0 fiber instances yielding 0 segments) took 0.068s
2020-11-12 21:05:18.360 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating materials.
2020-11-12 21:05:18.376 Iray [INFO] - MATCNV:RENDER :: 1.0 MATCNV rend info : found 112 textures, 0 lambdas (0 unique)
2020-11-12 21:05:18.380 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Computing 6 flux compensation factors took 0.001s
2020-11-12 21:05:18.380 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Emitter geometry import (6 light sources with 12 triangles, 1 instance) took 0.001s
2020-11-12 21:05:18.380 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating environment.
2020-11-12 21:05:18.390 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating backplate.
2020-11-12 21:05:18.390 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating lens.
2020-11-12 21:05:18.390 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating lights.
2020-11-12 21:05:18.390 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating object flags.
2020-11-12 21:05:18.390 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating caustic portals.
2020-11-12 21:05:18.391 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating decals.
2020-11-12 21:05:18.527 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Using iray core convergence estimate.
2020-11-12 21:05:18.527 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Allocating 1-layer frame buffer
2020-11-12 21:05:18.696 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Using batch scheduling, caustic sampler disabled
2020-11-12 21:05:18.696 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.0 IRAY rend error: Cannot render: found no usable devices.
2020-11-12 21:05:18.697 Iray Render error: Invalid parameters (NULL pointer).
This the problem, your GPU isn't supported.
So from 4.12 to 4.14 I no longer can do a thing? Is this a memory problem?
No. Basically, Iray 2020.0 was the last major release to support Kepler based cards. The current version is 2020.1.1, which dropped support for Kepler based cards (which is what your card is).
I did a full uninstalll today on one of my iMacs and reinstalled using Daz Central. This did nothing I still get the message that this program isn't supported on Big Sur. I have't upgraded to Big Sur on this iMac and will wait untill there is an update to fix this issue.
I upgraded to Big Sur and, right now, I would really really like Daz not to crash on launch so I could use my new iMac instead of my old MacPro.
It wont even work on Catalina for me. Big Sur is an issue, yes. but Catalina I cant even download the program anymore. So now new mac users cant use the program full stop. because downloading it isn't an option.
I used Daz on Catalina and it worked fine. Now DIM and DazStudio just crash. Daz had access to all the Big Sur's beta builds and yet their software doesn't work with the release version. Take Affinity, for instance: today I updated to Big Sur and to Affinity Photo, Affinity Design and Affinity Publisher (the older versions still worked). UnReal, Unity and Blender worked with Ctalina and the same versions still work with Big Sur. DaVinci Resolve 16 (pre Big Sur) also keeps happily working. Office (whose code base certainly is not for the faint of heart) keeps working. So, why not DazStudio?
We obviously don't know - perhaps it's a Qt issue, perhaps some other factor such as one of the licensed plug-ins. All we know is that, unfortunately, Big Sur is not currently supported. All I can suggest is keeping an eye on the change log.
I had the same exact issue. It's a waiting game. But I have work to do. I'm desperate right now. So desperate that I'm literally going to drive two states down to use my brothers gaming computer to get these commissions done for clients.
Always back up your install folders and downloaded zip files before updating, they're located in: C:\program files\DAZ 3D\DAZStudio4 and/or DAZStudio4 Public Build <=(Default location, though you can install it anywhere on any drive) and DAZ 3D\InstallManager\DOWNLOADS. In fact, you should back up your files now so you won't forget for the next time!
Assuming of course you can get the previous version from support!
Here a log with my very new 3090, it falls to cpu (which I have disabled) when there is a iray section plane. Happens both with the studio driver and the 457.3 game ready driver
I have found a weird problem with the way the Environment Options are being handled in 4.14.
If I have a scene using one of the Painter's Lights environments that does not use an Environment Map, like for example "Painter's Lights Sunset" and I save the scene, exit DAZ Studio, kill the process in the task manager, start DAZ Studio again and reload the scene, then the default Environment Map is set and the scene renders wrong. I have to manually go change the Environment Map to none every time I load the scene.
Richard: If section planes are causing the revert to CPU rendering, that is my problem because I'm using them. I'll check GPU drivers, but I updated about a week ago and have a 2080ti.
Do you have a link for that set, so that I can try it myself.
Since Nvidia can't seem to get me a driver past 442.92 that can support dual Quadro cards, I won't be upgrading either. 4.14 is looking like a big miss.
Painter's Lights does not seem to be listed in the store anymore. At least I cannot find it and the link from my product library to the store page is broken. Must have been removed.
The product index is 22135.
Good News Update:
I downloaded and installed the latest version of Install Manager 1.4.0.67 and things seem to be downloading and installing fine now. :-)
Now let's see how Daz Studio Pro 4.14 works on my old machine!
--------------------------------------------
I tried to download Daz Studio Pro 4.14 several times yesterday and today.
Although it appears to download 100% Install Manager says "Download Failed".
The Install Manager log file says:
WARNING: Network Error while downloading to file "C:/Users/Public/Documents/DAZ 3D/InstallManager/Downloads/IM00013176-02_DAZStudio414Win64bit.zip.{78af245c-9523-5582-bf66-403abcab32d8}.part":
Could not complete download, file guid does not match; 66d32b91-1b29-a64e-8ba0-24f44c0ebf00 != 78af245c-9523-5582-bf66-403abcab32d8.
Any suggestions for what to try next?
I think a Windows update came on my computer last night and screwed everything up. I just got this computer last Friday and the past two days it's been a dream since 4.14 came out. I have a 3090 card and I couldn't be happier. I woke up today to find my computer restarted during the night (I had a shot rendering for my animated Movember submission and it was at the login page) and all day long now it'll render 40-75 frames and then suddenly crash. Having to constantly reload it every twenty-five minutes and start from the next batch of frames is annoying but doable if I'm sitting here, but I want to let my 800 frame shot render overnight and don't think that's going to happen. I wish I knew what version of Windows it was on by default. I had the most updated Nvidia driver from two days ago as well.