4.12 limited resource usage refusing to render what previous versions can and will
dragoneyes002
Posts: 205
as the title says 4.12 including the latest version now tabulates the resources before rendering. you get a nice notice of how many Mib's or Gib's you'll be using in a render. well a render the one attached was a test since 4.12 has become problematic when 5 or more characters are added to a scene it will more often than resources require fail to render just straight up refuse to render (CPU fallback or not CPU/GPU both selected or not) the attached render was rendered in 4.11 (actual not 4.12 updated) no problemin fact could have included more characters by the amount of memory it settled on the fact it exists at all is not possible on 4.12 (Current version included) it flat out refused to render it and when retried suffered a fatal error shutting Daz3D down. reloading the scene deleting EVERY item not in the scene still refused to render. I don't think its too much to ask that Updates be INCREASED ability to do the job not making it less capable to do the job. If anything when 4.09 could render 15 characters in a scene 4.12 SHOULD at the very least be able to match that number if not exceed it.

Comments
HUH?
The resource usage given in the progress bar dialogue, with Show History enabled, is not produced by DS but by iray itself.
Yeah, I experience this too. What is too much for 4.12 to handle (makes the program simply crash out, won't even fallback to cpu) I can render in 4.11 no problem. It does have nothing to do with that resource log though, I'll get the same thing in both of them.
didn't say it had anything to do with the (this is how much being used) said 4.12 can't render what previous versions could I just mentioned the new feature to 4.12 in passing because its pretty useless if the amount is far below the systems limitations.
4.12 can't render the attached render 4.11 rendered it without issue. was that too hard to understand?
Again my mention of the (this is how much geometry is in the scene) was in passing about a 4.12 change we get while the new version can't do what the previous versions could. it was not written as a possible reason for the issue. its far more likely that someone running a 1970's AppleII was complaining that Daz3D was too hard to run on their system and someone tried to make it work
Had to same experience after updating to studio 4.12.1. All renders where done only in cpu mode, even if there was only 1 G8F in the scene.
Switched back to studio 4.12.0.86 and renders where as usual.
Yes big difference in amount of vram 4.12.1.118 uses compared to older versions.. With GPUZ running I loaded the FG Gamer Room into 4.11.0.383 and rendered it and it took about 5179 MB vram.. Saved the scene and loaded it into 4.12.1.118 and rendered and it used 5919 MB vram.. So there was a difference of about 740 MB of vram which when adding in figures and other things is a heck of a lot, so yes not sure what they did but the latest version of Daz Studio and iRay does look to be a huge resource hog..
If I remember rightly the newer version of iray used in 4.12 used a different way of processing the VRAM load on 10 series cards as they are not able to take advantage of the 20 series raytracing. I believe it ended up with 10 series card using more memory than the same scene on a 20 series card.
Interesting never knew that, looks like staying with the older version of Studio since I have a 1070Ti.. Still bit of a bummer though for those of us using Pascal cards, case of ah well..
if they decided to optomize specifically for the RTX it would explain the simply crashing issue. Problem is this version wont be worth snot by the end of sept when big navi and ampere release talk about shooting yourselves in the foot if that is why its crashing
I started another thread about this that didnt get much responses. I was wondering how I can revert back a version without the need to submit a ticket? If that is even possible. I have a 1080 Ti and after the latest update, the stability is horrible.
big navi is slated to include ray tracing according to what leaks are out there so it is relevant
how much it uses is 100% pointless if it crashes out the entire program so its not an upgrade is it?
Open a ticket. In future make sure you back up the packages from DIM.