Forum Groups
  All forums
    Help & Feedback
      Questions
      Work in progress
      Finished Art
      Non-Max related
    Community
      Offtopic
      News
    Hardware
    Photography


Featured Threads
  inspiration alert!!!
(36 replies)
  Indespensible MaxScripts, Plugins and 3rd Party Tools
(37 replies)
  The allmighty FREE Resources Thread !
(17 replies)
  spam alert!!!
(4886 replies)
  Maxforums member photo gallery index
(114 replies)
  Maxforums Member Tutorials
(89 replies)
  three cheers to maxforums...
(240 replies)
  101 Things you didnt know in Max...
(198 replies)
  A Face tutorial from MDB101 :D
(95 replies)
  Maxforums.org Members Gallery
(516 replies)
  SON OF POST YOURSELF
(637 replies)
  Dub's Maxscript Tutorial Index
(119 replies)

Maxunderground news unavailable

Out of memory errors when rendering - help!
show user profile  Asura
Recently I've been working on a scene comprising of around 40,000 polygons, in which are around 30-40 objects (so relatively low-poly).

Previously in MAX I've never had problems with rendering - I just hit "render" and it 'works'. With this scene though I'm having massive problems with supposed "out of memory" errors. I'm running Windows XP, updated to recent standards, and I have a gig of RAM.

I start to render, and before it gets to the actual rendering (around the "preparing lights" phase), the renderer crashes, with the message "The application has run out of memory and will now close; would you like to save a copy of the scene?" (it always saves flawlessly by the way). Usually it happens on the 2nd or third render since I booted MAX, but if I have the whole scene in view it can happen on the first render.

I'm only rendering at around 700x400 resolution (widescreen). Each object has (usually) three textures (Diffuse, Specular and Bump) which are always under 1024x1024. At first I thought it was because all my textures were TGAs, so I changed them to JPGs to save memory (compressing them from 300mb to around 12mb).

I also reduced the shadow map resolution from around 10,000 to 1024, in an effort to see if it would fix the problem, but it still hasn't. I tried increasing the size of my windows page file, still no effect. Tried using the bitmap pager, no effect. Turned on "conserve memory", no effect. It still claims to be running out of memory, despite me having 600mb of physical memory free, as well as a 3gb page file. I just don't understand what's wrong.

I'm starting to suspect that it's a bug, but I've looked online and can't seem to find acceptable precedents. One stated that MAX's default renderer just can't handle renders above 1.8gb of size in memory, but I don't understand why my scene has such a large memory footprint.

As a last resort I switched the render from MAX's default to Mental Ray. This did actually work, and it rendered - but for it to render properly I'd have to remake all my materials with mr's shaders and I don't want to do that if I can avoid it.

I could use Render to Texture, and merely render out all my shadows etc. The problem is that I still need the surfaces to have specular and bump interaction, so merely rendering out a Complete Map and turning off all the lighting isn't an option.

Can anyone help me out with this?
read 492 times
4/22/2008 9:13:12 PM (last edit: 4/22/2008 9:13:12 PM)
show user profile  VKotek
check the task manager, you might have some programs running eating away your RAM
Vojtech Kotek

read 459 times
4/23/2008 12:15:26 AM (last edit: 4/23/2008 12:15:26 AM)
show user profile  Pantas
You can also try rendering by "region" and compose your full shot piece per piece, if this is a still frame. I also ran into some memory errors when i tried rendering a not so large file and stats and this technique made it for me.. choose an acceptable amount of space to render and then another and then another until your full frame is completed.

Hope this helps.
read 457 times
4/23/2008 12:19:22 AM (last edit: 4/23/2008 12:19:22 AM)
#Maxforums IRC
Open chat window


Support Maxforums.org