Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
If you have Optix enabled in advance settings try unchecking that as this seems to cause problems on some scenes
Nope I keep it turned off. And checking CPU always slowed it down, which it can't handle now, so I never use that either. I'm just so frustrated with this whole thing. I usually wait a while to upgrade because I swear I have a problem 8 out of 10 times so I like to let others suss it out first. But I am in the middle of a project and I wanted to be sure it was good with the newer Iray... my mistake. :-(
Personally I'd wait to see what the 1080ti is like.
So what is the consensus view on the OP question? Is the new Iray too good to be true? The first flurry of responses seemed very positive with reports of quicker render times but after that things seem to have gone downhill and mostly negative. Grainy, even slower than before, not working at all in some cases. Is this another wait-for-the-bug-fixes release?
The vast majority of 'not working at all' are down to the minimum driver version requirements. This version of Iray needs a very recent driver version...372 or higher seems to be the case.
Are you sure the GPU is actually being used? Look at the log just after rendering, or just after cancelling a render. The slow render and the lack of completion in previews sounds very like falling back to CPU.
Try the beta if you are worried. I still have 4.8 installed along with the new beta. The beta is the same as the full release now, at least that is my understanding. If something doesn't work correctly in the new 4.9, I still have my trusty 4.8 ready to rumble. So there is nothing to fear, except fear itself. And bears.
I'm happy with the new IRAY render times and quality. In the benchmark scene, we noticed more graininess, but it wasn't extreme enough to worry about. In fact, it could just be the way the scene is lighted (tweaks to the way Iray handles lighting might impact that scene differenly [i.e., show more 'grain'] than whatever scene(s) Nvidia uses to inspect render quality)...and there are all kinds of ways to improve the final render with tweaks to lighting of course.
...so the Beta is still available then?
Seems most of the improved performance reports come from those doing GPU rendering. Unless I hit the Megabucks Lotto tonight, I'll be stuck in the CPU slow lane for the foreseeable future. Since 4.7, 3DL on the other hand has seen marked speed improvement even in standard (bucket) render mode.
I am liking the way the renders on the new Iray are looking.
Doubtless this will have been asked before, but I'm wondering if a useful boost for those struggling some might be if items not 'seen' in the render viewport weren't rendered by the engine.
I do appreciate light incidence has to be computed from out of the viewport, but if 'unseen' props & objects weren't computed, it would give a decent boost to all render times, I would have thought.
Or has this already been incorporated?
No bears in my part of the world, so it's just fear itself :)
Yes though, good suggestion about installing the beta. I was just trying to get an idea of whether the majority experience is positive or less so, now that a couple of days have passed.
It certainly is acting like it's not using the graphics card. I checked the "about your video card" it shows my Nvidia card. But it's not acting like it. It's as if the update to the graphics card messed up settings. It's not the Studio update, I know that because I reverted to the previous version when it wasn't working properly after updating the graphics card.
Ok, I started and cancelled a render. The bottom of my log file pertaining to this render says:
I'm seeing a lot of warnings in that regarding the Cathy hair, but even bald the iray preview doesn't clear up fully
nope I take that back - bald her preview is fine, also rendering faster, more on par with how it was before.
Interesting, because the other scene I tried had different hair and it was an issue - but it also used shaders from Outoftouch - from his iray hair pack. I wouldn't expect that to be affected by a graphics driver upgrade... I'll have to investigate this further, currently 18 minutes in at 65% completion (bald and earrings but no hair piece), will have to see how it looks when done
Another CPU only test, using SY's test render. Again DS 4.9.2.70 is faster but I can't rule out it's because the OS is Win 8. Will upgrade the Win 8 machine to DS 4.9.3.166 tomorrow and run the test again, that should answer that question I guess.
There's no Iray improvement that's going to make Iray usable in GPU mode for people with minimal GPU.
Iray in CPU mode is actually on par with 3DL, assuming you are doing the same sort of thing (IE: highly accurate PBR).
The big improvements Iray could really stand is a more intelligent ability to scale texture maps or better procedural technologies so that more and more content can avoid texture maps.
Ah, a mystery is solved. I just updated my drivers yesterday to the latest December (I think) offering. My card's sort of ancient, though, a GeForce GT 240, so the best version I could get from the NVidia website was only 342. I didn't realise older cards couldn't use the most recent drivers. And looking at the prices for 4GB 900-series cards — never mind the new ones — they're way out of my current budget. Looks like I'll be stuck with CPU-only rendering for the foreseeable future.
Come to think of it — is there an easy way to tell the minimum card spec that can use those v372 drivers?
Click on the tab of the drivers page that says Supported Products
JIT compilation was an issue with some of the previous betas - I thought the issues had largely been resolved but maybe not in some cases. Please bug report this, attaching your log and - if possible - the scene file with a note of the content used.
Greetings,
So...just for fun (this isn't about how much faster the new version is; I changed too many variables for that)... I rendered a scene a few days ago, to 5000 iterations on my GTX 740 with 4G of video memory; the scene uses pretty much all the card's memory for textures. I have to use the motherboard's on-board video so I don't take up any precious render memory. It took 7 hours, 49 minutes and 44.19 seconds.
Last night I went out and bought a GTX 1080 and a 750W PSU, not trusting my 600W PSU to be enough. This morning I installed them, and just now I rendered it to 5000 iterations. It took 20 minutes and 0.20 seconds.
Plus with the extra video memory, I can use it as my main display card AND a render supercharger...
Summary: I'm super-glad for the new version of Iray to be included in DAZ Studio!
-- Morgan
My latest (first complete) render with the new version of DAZ Studio. Took just under 2.5 hours on CPU (older HP 2000 laptop).
OutOfTouch's IrayPair hair shaders may use MDL that the new Iray 'fixed' and it may be causing issues. If so, OOT will have to update his shaders to work properly with the new Iray. Based on what is showing in the log you posted, it looks likely that they utilize a volume shader in a way that the new Iray (2016.3) isn't liking.....and that could cause the shaders to slow everything down to a crawl.....
It's also possible the Hairblending 2.0 stuff may be what's causing the issue, if it uses something in Iray that (again) has been 'fixed'. Try a straight IrayPair shader, without hairblending 2.0 stuff, and see if it still has the huge slowdown.
I'm really glad you mentioned this, as I use Out of Touch's hair shaders extensively and it would really affect my workflow if all of them are affected. Hairblending I can manage without, but I think about half my original characters are using IrayPair. Fortunately, I haven't downloaded the new version yet.
However, here's a question that I don't seem to see an answer to: As someone who DOESN'T have an NVIDIA card, and renders Iray using plain old CPU power, is there any benefit to upgrading right now or should I hold on until OOT's got an update? An early post said that they didn't see anything else new.
I was doing a scene and wanted it todo in Iray but all i get i a black screen for this scene. Other ones are fine but this one will not work
for 3delight i works, but doesn't everythin render for iray as well ?
2017-01-07 18:54:37.464 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Updating geometry.
2017-01-07 18:54:37.464 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Using built-in ray tracing (1.0.0).
2017-01-07 18:54:37.464 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Importing geometry.
2017-01-07 18:54:37.543 WARNING: dzneuraymgr.cpp(307): Iray WARNING - module:category(DISPLA:GEOMETRY): 1.0 DISPLA geo warn : Object DS_shape_1440_3506: displacement shader returned values up to 0.20077, clipped to max displace 0
2017-01-07 18:54:37.844 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Geometry import (1 object with 149k triangles, 1 instance yielding 149k triangles) took 0.373927
2017-01-07 18:54:37.844 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Updating materials.
2017-01-07 18:54:37.865 Iray INFO - module:category(MATCNV:RENDER): 1.0 MATCNV rend info : found 438 textures, 0 lambdas (0 unique)
2017-01-07 18:54:37.866 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Emitter geometry import (4 light sources with 1524 triangles, 1 instance) took 0.00s
2017-01-07 18:54:37.866 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Updating environment.
2017-01-07 18:54:37.881 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Updating lens.
2017-01-07 18:54:37.881 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Updating lights.
2017-01-07 18:54:37.881 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Updating object flags.
2017-01-07 18:54:37.881 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Updating caustic portals.
2017-01-07 18:54:37.881 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Updating decals.
2017-01-07 18:54:37.881 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Allocating 1 layer frame buffer
2017-01-07 18:54:37.881 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Using batch scheduling, architectural sampler disabled, caustic sampler disabled
2017-01-07 18:54:37.881 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Initializing local rendering.
2017-01-07 18:54:37.881 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Rendering with 1 device(s):
2017-01-07 18:54:37.881 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : CUDA device 0 (GeForce GTX 1070)
2017-01-07 18:54:37.881 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Rendering...
2017-01-07 18:54:37.881 Iray VERBOSE - module:category(IRAY:RENDER): 1.4 IRAY rend progr: CUDA device 0 (GeForce GTX 1070): Processing scene...
2017-01-07 18:54:38.066 Iray VERBOSE - module:category(IRAY:RENDER): 1.9 IRAY rend stat : Geometry memory consumption: 7.6181 MiB (device 0), 0 B (host)
2017-01-07 18:55:08.559 Iray INFO - module:category(IRAY:RENDER): 1.9 IRAY rend info : Initializing light hierarchy.
2017-01-07 18:55:08.559 Iray VERBOSE - module:category(IRAY:RENDER): 1.9 IRAY rend stat : Texture memory consumption: 1.3632 GiB (device 0)
2017-01-07 18:55:08.594 Iray INFO - module:category(IRAY:RENDER): 1.9 IRAY rend info : Light hierarchy initialization took 0.03s
2017-01-07 18:55:08.596 Iray VERBOSE - module:category(IRAY:RENDER): 1.9 IRAY rend stat : Lights memory consumption: 263.953 KiB (device 0)
2017-01-07 18:55:08.697 Iray VERBOSE - module:category(IRAY:RENDER): 1.9 IRAY rend stat : Material measurement memory consumption: 0 B (GPU)
2017-01-07 18:55:08.697 Iray VERBOSE - module:category(IRAY:RENDER): 1.9 IRAY rend stat : Materials memory consumption: 1.36243 MiB (GPU)
2017-01-07 18:55:08.876 Iray INFO - module:category(IRAY:RENDER): 1.4 IRAY rend info : CUDA device 0 (GeForce GTX 1070): Scene processed in 30.993s
2017-01-07 18:55:08.891 Iray INFO - module:category(IRAY:RENDER): 1.4 IRAY rend info : CUDA device 0 (GeForce GTX 1070): Allocated 12.4203 MiB for frame buffer
2017-01-07 18:55:08.893 Iray INFO - module:category(IRAY:RENDER): 1.4 IRAY rend info : CUDA device 0 (GeForce GTX 1070): Allocated 1.65625 GiB of work space (2048k active samples in 0.000s)
2017-01-07 18:55:08.893 Iray INFO - module:category(IRAY:RENDER): 1.4 IRAY rend info : CUDA device 0 (GeForce GTX 1070): Used for display, optimizing for interactive usage (performance could be sacrificed)
2017-01-07 18:55:09.076 Iray INFO - module:category(IRAY:RENDER): 1.4 IRAY rend info : Allocating 1 layer frame buffer
2017-01-07 18:55:09.098 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Received update to 00001 iterations after 31.204s.
2017-01-07 18:55:09.260 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Received update to 00002 iterations after 31.373s.
2017-01-07 18:55:09.576 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Received update to 00004 iterations after 31.685s.
2017-01-07 18:55:10.155 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Received update to 00008 iterations after 32.260s.
2017-01-07 18:55:11.016 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Received update to 00014 iterations after 33.124s.
2017-01-07 18:55:11.871 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Received update to 00020 iterations after 33.977s.
2017-01-07 18:55:12.727 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Received update to 00026 iterations after 34.833s.
2017-01-07 18:55:13.597 Iray VERBOSE - module:category(IRAY:RENDER): 1.0 IRAY rend progr: 100.00% of image converged
2017-01-07 18:55:13.597 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Received update to 00032 iterations after 35.717s.
2017-01-07 18:55:13.613 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Convergence threshold reached.
2017-01-07 18:55:14.521 Saved image: C:\Users\perry\AppData\Roaming\DAZ 3D\Studio4\temp\render\r.png
2017-01-07 18:55:14.563 Finished Rendering
2017-01-07 18:55:14.586 Total Rendering Time: 39.21 seconds
2017-01-07 18:55:14.595 Loaded image r.png
2017-01-07 18:55:14.604 Saved image: C:\Users\perry\AppData\Roaming\DAZ 3D\Studio4\temp\RenderAlbumTmp\Render 2.jpg
2017-01-07 18:55:19.856 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Device statistics:
2017-01-07 18:55:19.856 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : CUDA device 0 (GeForce GTX 1070): 38 iterations, 31.006s init, 5.556s render
A 740 GT with 4GB can be had pretty cheap these days. It'll run with the new drivers, and provides moderate Iray performance. Amazon.com has one (EVGA, uses DDR3 memory) for $100: https://www.amazon.com/EVGA-GeForce-Superclocked-Graphics-04G-P4-2744-KR/dp/B00KJGYOBQ and the GDDR5 memory version is $120.
Well, some are seeing performance improvements, some aren't. We really don't know what all has been 'broken' yet, and what's been improved......until they track down some of the issues (and can therefore say what the issues actually are) it's probably best to stay with the evil you know, rather than to update to the evil we don't.
Unless you NEED Pascal support, or you need one of the fixes provided in 4.9.3, wait until they've had a chance to sift through the bugs. A lot of people have got symptoms of buggy behavior.....but they too might be using some item or product that is not playing well with the new Iray. And that means it isn't DS that is bugged, but the product that needs updating. Some things may be actual DS bugs, and need to be fixed by DAZ.
Yes, the beta is always available. My understanding is that when Daz does a full release, the beta is updated as well. That means right now is probably the best time to try the beta because it is basically the same as the full version!
The beta is hidden in DIM. Remember you have to click the box to display hidden items, and then search for 'public beta'. The beta has no impact on my 4.8 install. But they can share saves and stuff. It is the best of both worlds!
And no, the renders times do not come remotely close to having a GPU, unless that GPU is just a piece of junk, (like a 730, which isn't worth the board its printed on.) BUT... CPU rendering is certainly improved, and can make a big difference to those stuck with CPU only. So this might very well cut hours of time off some renders.
And now my question. I see people talking about noise being reduced. There is a noise filter option in the render settings now. Does this need to be enabled, or are the renders better without it? Are there any drawbacks to the noise filter, like longer render times, or blurriness? And what do the settings for it do??? I have no idea what they mean, and what their impact would be. This is one of the features I was asking for last year, and I'm sure a lot of people were. Noise and graininess have been one of Iray's biggest flaws, so this is much, much appreciated.
Hopefully Iray will continue to be optimized further in 2017. A special CPU-GPU mode when the scene exceeds the GPU's vram would be a massive improvement.
What lights are you using? Are they set to photoreal mode?
(I ask because I've converted a 3DL scene to Iray before and had to redo the lights as they were 3DL light (an older scene though from a previous version of DS) and Iray wasn't seeing any light from them)
Hmm.. Using the Uberlight and it's a scene from the Bay Area (the one with all the houses etc) and Photoreal was selected..
changed it, and see something now.. thanks for the tip
Ah, you don't want to use 3DL lights with Iray. Some of them might work, but much better off making new lights.
Mind you, you can sometimes copy/paste settings (particularly to go from 3DL spots to Iray ones)
what lights should i use?
seems like its rendering differently since i dont see iray info
2017-01-07 19:44:54.196 Iray INFO - module:category(IRT:RENDER): 1.0 IRT rend info : Scene graph creation took 0.000033 seconds
2017-01-07 19:45:02.837 Iray INFO - module:category(IRT:RENDER): 1.0 IRT rend info : rendered frame 0127 in 8.641025s, 0.1fps (internal: 8.635783s, 0.1fps, overhead 0.1%)