Vray Render Problem

[payal]

Hello Friends

I am using 3d max 9 n vray1.5C2.

I made an interior scence with a file size of 110MB.As i put it on render,3d max got shut down without any warning.

Vray render settings were quite low.

Pc configuration is Core 2 Duo with 2gb ram.

Can anybody please tell me why did this happen?

[WAcky]

No.

 

Post your settings if you would like help.

 

 

 

I vote for some refresher forum rules or some sort of popup. This is getting rediculous.

[kippu]

maybe the hamsters running the cpu got tired ....am sure its your memory , 2gb wont do , add more ram

[Tim Fairbanks]

"add more ram "...

 

... and you'll need a 64-bit O.S. to be able to access RAM above 2gb (per application). A 32-bit O.S only allows each application to access 2gb of memory.

 

3dsmax WILL crash (or simply disappear without warning) when you reach approximately 1.85gb with a 32-bit O.S.. You have to keep an eye on your performance monitor (CTRL+Shift+ESC) to see how close you're getting to 2 gig.

 

Try rendering without a frame buffer - that will free up some memory, since max won't need to hold a full-size, uncompressed image in the memory buffer.

Vray can also save each render bucket to a file using the "Render to V-ray RAW image file" function, but it's a real hassle. Check the online docs if you want to try it:

 

http://www.spot3d.com/vray/help/150SP1/vfb_index.html

 

 

 

TimF

[Nic H]

110 mb?!

thats huge, what have you got in there?

[BrianKitts]

110 mb?!

thats huge, what have you got in there?

 

nic's on track... before you go upgrading to 64bit and buying more RAM it sounds like you need to work on your scene/memory management.

 

I would post some screen shots and tell us a bit more about the scene, my guess would be that you've got a ton of furniture in the scene that isn't instanced, or could be proxied to save on the memory that the scene takes up, that way you'll have more memory available at render time and keep you from crashing out of max.

[Tim Fairbanks]

110mb - musta' been imported from Revit

 

I'd concur that 110mb is really large for an interior, and some scene management is in order.

 

Kinda blew right past that in my previous post and got focused / sidetracked on the memory issue, since memory related crashes with max/Vray don't seem to be isolated incidents - if it happens once, it's going to happen again.

 

Payal - just be aware that if or when you decide to add memory, Your O.S. needs to make the additional RAM available to each application. Our office has not deployed a 64-bit O.S., so our 4 gigs of RAM don't help 3dsmax at all, and we have memory shortage crashes with max all the time.

 

Those four renderings I was expecting to be rendered overnight last night, for example...

 

 

TimF

[Tim Saunders]

Doesn't really sound like the problem was really resolved here.

 

I know this issue has been brought up dozens of times, but enough is enough. We have got to get to the bottom of this.

 

I'm in a similar situation (except for the fact that a 110mb file size is ginormous). I have an exterior scene with tons of plants (mostly 3d proxies, some 3d RPCs, and some Vray grass shrubs). My scene is about 38mb (file size). Not sure the polly count, but I'm sure it's up there. I have several cameras set up and the plants that aren't seen in the particular view are turned off (the layer that is).

 

I have super low settings (IRR map and LC). I even turned off the render frame window in max and in vray, and enabled the Vray raw image file saving. At some point after sending the job to render (not sure if it is while calculating GI or actually rendering) it crashes with no warning.

 

I have had this issue happen a few times. The other times this happened, the model didn't have RPCs or Vray grass, just proxies. Some minimal displacement grass was used in another scene though.

 

I just don't get how so many people are using all 3d entourage and not running into issues with this.

 

Oh, and I'm trying to render on a 64-bit machine with 8gigs of ram.

[gfa2]

I know this issue has been brought up dozens of times, but enough is enough. We have got to get to the bottom of this.

 

Tim, have you tried rendering it with all the proxies turned off? I've had this happen in the past and it always seems to come down to a bad proxy (either because of materials or geometry) and by process of elimination you can find the culprit. Lots of times the problem won't show itself at low res/low settings so you think everything is fine, then you go for high res and all hell breaks loose. I know you said it happens to you even at low res/low settings, but I suspect a proxy problem.

[e_cbautista]

i have just shifted from 32 bit to 64 bit, suddenly max crashed frequently even when i only manipulate objects (move, scale, merge).. reinstalling max and vray didnt solve it, upgrading video driver seems to hit it though.

[Thablanch]

Render size and amount of light can have a great impact as well on a scene crashing or not.

 

as well:

 

-3gb switch ( if not 64 bit OS)

-smaller bucket size

-Dynamic/static memory limit ajustments

-No other materials than Vray materials

-Avoid RGB 255,255,255, makes lightcache bounce for ever and can cause crash

-If displacement is used, the edge lenght should be ajusted to your render size.

-.vrimg

-Avoid using .tif and .psd as textures, they are loaded in memory

-Render using Backburner, even if it is your own machine, cause max main session will use more ressources than a fresh sesion in Backburner.

-Virtual memory of your computer. ( like +/- 2X your ram )

-Any bad geometry in the file can cause errors in the rendering process, even on a small file size.

-Use Light lister, do not use the lights you do not need.

 

You can install the 3gb Switch even if you only have 2gb of hardware.

http://technet.microsoft.com/en-us/library/bb124810.aspx

 

Hope it helps

Edited August 14, 2008 by Thablanch

[Nic H]

-Avoid using .tif and .psd as textures, they are loaded in memory

 

this is wrong, its pixel size that counts not megabyte size.

[Thablanch]

Sorry to argue with you here, but the soft still need to load the image file, and it will take more ressource if opening a big file. Try it for yourself and take a look at the task manager,

 

I just flipped a texture of 6k, just to see, save as .tif instead of .jpg, and my memory usaje passed from 467 484k to 468 992k for the max process.

 

Multiply this by dozens of maps in your scene, that could be the difference in between a scene crashing or not.

 

(A few months ago, I had this file crashing all the time, cause it was getting too big, maps were a mix of .psd, .tif and. jpg, so I did save them all to jpg, and the scene was able to rende)r

[Tim Saunders]

and png?

[Thablanch]

I am not really using them, but as I understand that, smaller the file size, better it is.

 

Mabee I was not clear here, I am not talking about the rendered output, but the maps in the scene

[Tim Saunders]

It makes sense.

[Dave Oliver]

if somebody made a wiki or something to refer people to with all the common vray issues i would rather contribute to that than read the same posts over and over

[fadi3d]

hello everybodi

i have to agree with alain as i once tried a background as a tiff and vray and Max kept crashing untill i converted it to Jpg.

also i thing most of my crashing is done by objects with displace running into other objects (i hope u know what i mean)

cheers