TMM not allocating enough memory to compile a lightmap
by Jesse McKinney · in Artist Corner · 11/06/2005 (11:44 pm) · 6 replies
I'm having a problem when ever I try and compile my map with map2dif plus
Everything goes fine until I get to the light map stage. It will act like it is compiling the light map but after working on it for about 20 minutes the following error pops up
Torque Memory Manager
Error Allocating Memory, Shutting down.
I was wondering if there was a way to force it to allocate more memory via a console command or script. I was watching my mem usage from the windows task manager and it was not using enough to cause problems. The level is rather large and there is nothing I really can do about shrinking the light map since its an indoor DM level. I'm using map2dif Plus and any I thank you for any help you can provide.
Everything goes fine until I get to the light map stage. It will act like it is compiling the light map but after working on it for about 20 minutes the following error pops up
Torque Memory Manager
Error Allocating Memory, Shutting down.
I was wondering if there was a way to force it to allocate more memory via a console command or script. I was watching my mem usage from the windows task manager and it was not using enough to cause problems. The level is rather large and there is nothing I really can do about shrinking the light map since its an indoor DM level. I'm using map2dif Plus and any I thank you for any help you can provide.
#2
11/07/2005 (2:04 pm)
Not a bad Idea but there is one major drawback. Areas outside portaled zones like in the areas connecting sections of base will be lit by the sun which will create odd lighting in areas where the sun lights part if the interior and then cuts out when it hits a portal. 
#3
12/22/2005 (10:12 am)
Jesse - I have the same problem with a very large map! Have you had any luck? I've tried map2dif and map2dif_plus, changed some memory settings, etc. No luck...
#4
Once feature that would be nice to see in future instances of map2dif is per zone ambient and emergency light values, or light bounce :)
12/23/2005 (5:20 pm)
Yes I did, but it involved a complete redesign of that section of the interior. Lights with casting distanced over 3000-3500 cause the error. I was using them to fake ambient light in an area that needed a different color than the default ambient light value.Once feature that would be nice to see in future instances of map2dif is per zone ambient and emergency light values, or light bounce :)
#5
12/31/2005 (11:47 pm)
It also seems that having lots of lights in a zone causes the error. It is a very frustrating process to build and light big areas just to have the compiler choke during the compile. It would be nice if someone could look into this, I would be more than happy to send in some sample maps
#6
img130.imageshack.us/img130/9803/allocationerrorux1.png
The map is only 3483 surfaces at last count its not that large. Any help would be appreciated
The Debug EXE did not tell me anything new and I have tried both an older version and new fresh off the TSE head versions of map2dif, none of which worked.
10/29/2006 (11:07 am)
I am still having this issue. On a different interior though. I even made a pretty picture....img130.imageshack.us/img130/9803/allocationerrorux1.png
The map is only 3483 surfaces at last count its not that large. Any help would be appreciated
The Debug EXE did not tell me anything new and I have tried both an older version and new fresh off the TSE head versions of map2dif, none of which worked.
Torque Owner Jonathan Rose