Blank Renders
DekeSlade
Posts: 127
Not sure what changed here but suddenly Im getting blank renders, itll go for a few minutes with the usual "Rendering Image" details, then stop with a completely blank transparent background "render." Only work around I've found so far is to tick "CPU Mode" in addition to CUDA which competely borgs my machine and seems to throttle my CPU to 100% and takes way frikin longer.
Any insight would be mad love appreciated.
Comments
Me too.
That means your GPU has run out of memory and thus the render has failed. With CPU Fallback disabled it can't then use your CPU to do the render so you wind up with a blank render. With CPU Fallback enabled, it will render, but only on your CPU, so yes, it will be very slow.
Yes, but identifying something is part of the problem or possible solution. This happened after the updates from Daz and nVidia, under the same conditions, although without updates, everything was normal.
A litle re-edit: when i mean 'normal' - its like, no many insues/less black screen on render (in old gpu, 1650gtx 4gb). How i avoid this insue (with old nvidia driver and Daz)? Just reestart the software (Daz).
"your GPU has run out of memory and thus the render has failed."
I get that, but the question I should have phrased better is "Why?" This wasnt happening with any project Ive worked on for years and now, suddenly, thats the default. Creating in Daz has become my full time vocation and though I dont, by any streatch, consider myself an expert with it, I am able to recognize when something is acting out of character. This is out of character ... and frustrating.
...
Rolling back won't help. Each new iteration of DS demand more resources. Even a 8Gb nVidia GPU won't be adequate fpr a simple iray render., GTX cards will lose some resources to RTX emulation right off the top.
My 6GB 1660 GTX manged to render a very simple scene, Genesis 9 with clothes and hair from Starter Essentails, for 212+ iterations before it dropped to CPU to finish. I would think an 8GB would still manage simple scenes in the current General Release.
I got a 1080TI and I can tell ya, Ive built WAY larger/more complicated scenes and NEVER had to use CPU and the difference is night and day. With CPU not only takes way longer but effectively cant multitask at all.
I've had both the 1080Ti and 2080Ti and experienced CPU fallback on those in older DS. usually with 3+ figures.
I sometimes had to restart,reboot, run thre SceneOptimizer and pray and make sacrificial contributions to the 3D gods just to get a render going.
So, all these issues are not new with new or older DS users.
I'm sure Richard will come up with some explainations or solutions.
Meantime we just have to be content with making simple renders.
Yeah, dunno whats up but this is deffinatly a new issue with the latest builds, not that I havent had crashes or issues in the past but with what Im doing, its totally uncharacteristic. Ive rendered over 40 different similar scenes, same figure, same lights, same hair, same everything yet this just cropped up. I am grateful that I tracked it down and at least Im able to render, but never needed CPU before and shouldnt need it now. Sumfin got nudged outta whack somewhere.
Maybe increasing texture compression can help?
Normally people want to decrease it because they find compression artefacts in their renders, but in your case it might help to render at all.
Have a look into the settings (these are not the default values):
Medium Threshold: Any texture with a resolution below this or equal to this value will not get compressed
Inbetween Medium and High Threshold: Any Texture with a resolution in this range will get medium compression
High Threshold: Any texture with equal or greater resolution will get maximum compression
Yeah, Im one of those who hasta have the best quality possible and am willing to wait for it if I have to, though thats a great tip for test renders.
The issue is that I shouldnt have to now reply on CPU for something that I didnt have to in the past. Same exact settings and scene new rendering blank transperent nothingness UNLESS I opt in to use CPU. Clearly, this was a step backwards and an unintended consequence of someones update somewhere. Im grateful there is a workaround with falling back on the CPU but I shouldnt need to. What worked a week ago isn't working now.