What is the largest size I can render in DS4.6?
Granville
Posts: 696
I have been trying to render a scene for a book cover in DS4.6.2.120 but the entire computer crashes after rendering for 9 hours every time. I don't get any feedback about what went wrong. The last lines of the log files have no evidence of what brought the whole rig down. So I have two questions
What is the largest render size? I am trying to do 5178 x 3375
What could be a work around to render in two passes but end up with that size?
Post edited by Granville on
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
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
The resolution of the image is probably not the problem. The amount of memory and processing power 3DeLight needs is based on the number of objects in the scene, the number and resolution of textures used, and the Bucket Size used for rendering. The easiest thing to try first is lowering the bucket size to absolute minimum.
Is it crashing at the same point everytime? If so, is it if the render reaches a particular point? Both HD morphs and AoA's SSS shader will pause when they reach an object using them and calculate (other things may do this as well, they're just the two I know off the top of my head). If your render's already taxing your ram, the extra memory needed for the calculation (or for the subdivided mesh) might be what's pushing it over the edge into crashing.
The largest dimensions you can enter into the render settings are 10000 a side. I typoed the other day and got a warning on it, or I'd probably never have known.
Looks like an out of memory issue, how much RAM do you have? jestmart is right I myself have run out of memory on more than few occasions.
I have 8 cores and 12 gig of ram
have you tried rendering to disk? another option might be to render to the 3de standalone.
I got the same results rendering to a file, but I have not tried the stand alone renderer. Does anyone know of a tutorial on how to render to RIB and use the standalone renderer?
If the entire computer is crashing that is usually caused by one of three things.
Out of Memory error
The drive the temp directory is on is full, especially if it is on the C Drive
Overheating of the computer, especially the CPU.
32 bit or 64 bit DS?
Is your CPU overclocked?
Desktop or Laptop?
I have just rendered test scene in Daz Studio with the resolution like yours and all goes fine.
Rendering time 12 minutes 25 seconds, RAM usage: 8.64 GB.
I have 32 GB RAM in my computer. May be you need to decrease the complexity of your scene...
I could not post the render because of limits (2000 x 2000 pixels), but I attach a smaller version of it.
Could also be bad memory.
Incidentally, to answer the first question, I believe the maximum resolution is 10,000 x 10,000 pixels size.
i been following this thread on the standalone 3de :) http://www.daz3d.com/forums/discussion/40569/
How much virtual memory do you have allocated in Windows?
If its set to less than 8GB or Auto, change it to 8GB.
There's also the possibility that its one rogue item in your scene.
Troubleshooting computer problems can be a tricky business and the worst thing you can do is jump to conclusions and start fixing things that aren't broken. With respect, everyone is assuming that the problem is with 3Delight and the render job. While that may prove to be the case, it may also simply be what the computer happens to be working on when the problem occurs, particularly since large render jobs are going to stress the system. A systematic approach to troubleshooting is always best. The OP says the render log file does not indicate any problems and that may very well be because the problem is with the system. Assuming the OP is using Windows, the system event log is where they should be looking for the cause. Having said that, the error codes used in the SEL are cryptic to say the least and often decodable only using the secret decoder ring issued only to Microsoft certified wizards. Nevertheless, check the logs and post what you find and we may be able to help. As Richard suggested, there can be a number of issues that cause the entire system to crash and many are hardware-related (memory errors, hard drive errors, power supply voltages, overheating, etc.)
It would be helpful if you could be a little more specific about your system specifications. For example, you say you have eight cpu cores. Is that an eight-core AMD processor? Or a quad core Intel with hyper-threading enabled?. Etc., etc.
Thanks everyone for all the great ideas to try. This have been very informative. I'm sure that I will have to try all the solutions on projects in the future.
I was finally able to render it by reducing the bucket size. This is great news. Now I don't have to buy a new computer. :-) I was amazed by how beautiful the results were and how long it took:
Total Rendering Time: 1 days -6.-65 seconds.
Now the fun starts.
I was also thinking about trying to use lIght dome pro -r
Thanks DAZ spooky. That is a great suggestion. I'm so excited that I can render for large print format at 300 dpi
With the ability to use 64 bit we have been looking at increasing the 10000x10000 limit because if you want to print posters you hit it in a hurry especially when you take bleed into account. There are trade offs though, crashes from people that don't realize you can run out of RAM. :)
What about adding the option to render in quadrants/slices? Here's my 30k by 30k total image, but rendered in 2k by 2k chunks and Studio takes care of creating all the separate render jobs for the user to merge together in their favorite 2D editor? Complexity/RAM requirements for objects in the scene will remain the same (or does 3Delight support demand-loading of objects on ray intersection of a pre-computed bounding box like some other render engines do?) but the memory used by the frame buffer(s) will be reduced using this approach.