How to render huge (like 300dpi) images?
-
Whenever I try to render in like 8000x6000, sometimes even smaller (like 5000x3000) or something like that, I get error messages...
Tried to render smaller areas but not much success. Isnt a way to render directly to a file?
Does rendering multiple channels (diffuse, alpha, etc) overburdens the memory thus creating the error?
-
Can you update your profile so that we can know which OS you are using and what SU Version you have installed?
Also you don't mention what version of Vray you are using?
-
+1 Rich. This information is important.
@aceshigh said:
I get error messages...
But what is even more important is what the error messages say. They explain exactly what is going on. Without knowing these it is just guesswork. )Like going to the doctor and saying "I'm sick! Fix me!")
-
@aceshigh said:
Whenever I try to render in like 8000x6000, sometimes even smaller (like 5000x3000) or something like that, I get error messages...
Tried to render smaller areas but not much success. Isnt a way to render directly to a file?
Does rendering multiple channels (diffuse, alpha, etc) overburdens the memory thus creating the error?
I'm guessing that your computer is running out of RAM, if you want to avoid this you need to render directly to vrimage, this can be found in the output drop down menu, and you are going to want to select .exr as the save type.
the downside of this is that vfb channels are not stored or saved but I think are still processed annoyingly (someone might have to correct me on that) but generally yes using the extra channels will slow your render down.
-
You need the latest SU 8 and VR 1.49.01 and render directly to EXR.
Go to Options - Output - Under VRAY Raw Image File, click Render To VRImage box, Then under file name make sure you save as an EXR file. I usually VFB mode is on preview so you can see whats going on. This will eleviate some RAM issues.
Also, you need to turn your settings down on displacement if you are using it. A high res file will not need edge length of 4 or less like the defaults. I use 30 or higher. If you can get away with no displacement, even better. This is a memory killer.
-
Why the need for SU8? Thought VfSU worked the same across versions...
-
You don't need to render at such huge sizes:
http://www.forums.sketchucation.com/viewtopic.php?f=18&t=38373To get the final printing size @300dpi, use Smilla Enlarger:
http://sourceforge.net/projects/imageenlarger/ -
@thomthom said:
Why the need for SU8? Thought VfSU worked the same across versions...
My understanding was that the latest update for SU8 allowed for allocation of 4GB of RAM. Gives ya a little more to work with. Am I wrong?
-
@valerostudio said:
@thomthom said:
Why the need for SU8? Thought VfSU worked the same across versions...
My understanding was that the latest update for SU8 allowed for allocation of 4GB of RAM. Gives ya a little more to work with. Am I wrong?
Ah, yes! SU8 M1 added LARGE_ADDRESS_AWARE support - so if you are under 64bit Windows you can address up to 4GB of memory. You're absolutely right.
-
Every little bit counts.
I am on a 64 bit Windows 7 machine with SU 8 Pro and 1.49.01 VR and rendered a 10,000 pixel wide image to EXR and it did not crash on me.
-
-
DPI as nothing to see, it's just the number of pixels!
-
@thomthom said:
Ah, yes! SU8 M1 added LARGE_ADDRESS_AWARE support - so if you are under 64bit Windows you can address up to 4GB of memory. You're absolutely right.
WHY DON'T I EVER UPDATE
sorry for the rude off-topic interruption
-
@eidam655 said:
WHY DON'T I EVER UPDATE
Yes, why not? Updates aren't there to annoy you - they include fixes and improvements. It's always best to ensure you are up to date before debugging a problem with a software.
-
@thomthom said:
Yes, why not? Updates aren't there to annoy you - they include fixes and improvements. It's always best to ensure you are up to date before debugging a problem with a software.
while i usually enjoy watching the progressbar of an update taking place (srsly, i do), i had had some issues when i was updating to the latest vray and hence have decided that if it works, i'm not going to mess with it until some major new release (like SU 9) comes along. but now i've updated and there were no problems so far, yay
-
@valerostudio said:
Every little bit counts.
I am on a 64 bit Windows 7 machine with SU 8 Pro and 1.49.01 VR and rendered a 10,000 pixel wide image to EXR and it did not crash on me.
what was the file size of your skp file.and how long it took to render an image of that size.my computer would rather faint or take a week to render.i guess. 
-
@shri said:
@valerostudio said:
Every little bit counts.
I am on a 64 bit Windows 7 machine with SU 8 Pro and 1.49.01 VR and rendered a 10,000 pixel wide image to EXR and it did not crash on me.
what was the file size of your skp file.and how long it took to render an image of that size.my computer would rather faint or take a week to render.i guess. File has means very little for model complexity. Textures often take up a large portion of a file, and watermarks - especially if you don't resize them for your needs and just leave them in their original sizes. You can have a model of a cube and fill the model with large images so the SketchUp file is 200MB+. If you want to compare model complexity you must look at polygon - or more accurately number of triangles.
-
HI,
I'm a newbie here. recently I'm facing the same problem. I ve done all the suggestion made above but all in vein. My skp file size some where around 250mb. Either SU is crashing or vary is not starting at all once I hit render. I'm using mountain lion on mac with 8GB ram. Pls advise. thnx.
Rgds,
Sanjeev
Advertisement