So both tool and ahobov102 give me an 'out of memory' error when running lightmaps.

In ahobo, I can enter 'radiosity_quality 1' and it will run fine and count down, but when I go to enter in 'radiosity_save', after I enter the command, nothing happens. My inputted text disappears just like normal, but the lightmaps are never saved. I can enter that command all I want but nothing ever happens. The lighting is also completely black:


If it's at 0.01, that's pretty far into the lightmapping process and there should be some light coming from those objects by now. In debug.txt, this is what I get:

08.12.13 02:59:47  a hobo pc 01.01.00.0609 ----------------------------------------------
08.12.13 02:59:47  reference function: _write_to_error_file
08.12.13 02:59:47  reference address: 401b13
08.12.13 02:59:47  Couldn't read map file './a_hobobeta.map'
08.12.13 02:59:47  CreateDevice succeeded with refresh rate = 0
08.12.13 02:59:47  Sound card doesn't meet minimum hardware requirements.  Disabling hardware option.
08.12.13 02:59:47  Increasing sound decompression buffer size to 1048576 bytes
08.12.13 02:59:48  the model 'elefant\weapons\assault rifle\assault rifle' and the collision model 'elefant\weapons\assault rifle\assault rifle' don't match (node counts don't match)
08.12.13 02:59:48  the object 'elefant\weapons\assault rifle\assault rifle' will not be collidable
08.12.13 02:59:49  the model 'elefant\weapons\plasma pistol\plasma pistol' and the collision model 'elefant\weapons\plasma pistol\plasma pistol' don't match (node counts don't match)
08.12.13 02:59:49  the object 'elefant\weapons\plasma pistol\plasma pistol' will not be collidable
08.12.13 02:59:49  DirectInput: 'Acquire (keyboard)' returned (DIERR_OTHERAPPHASPRIO#-2147024891)
08.12.13 02:59:51  local player 0, weapon (0x0), deleted unexpectedly
08.12.13 04:02:30  radiosity error: out of memory

The unbolded stuff is stuff I get all the time and have successfully ran lightmaps even with those errors. The 'out of memory' is the new one. It should be noted that I turned everything off to run these lightmaps, although in the screenshot obviously tool, firefox, and VLC are on.

The thing is, quality 0 works fine as far as I have tested. It's quality 1 that causes this error.

In tool it runs similarly. I enter tool lightmaps (correct directory structure and all that) then quality 1 and threshold 0.15. It starts it up, then loads for a while, before displaying this:

08.11.13 04:22:39  start levels\innie\bsp1point5
08.11.13 09:11:07  radiosity error: out of memory 
08.11.13 09:11:07  0.000000
08.11.13 09:11:09  EAX: 0x00000000
08.11.13 09:11:09  EBX: 0x00613701
08.11.13 09:11:09  ECX: 0x00000000
08.11.13 09:11:09  EDX: 0x00000000
08.11.13 09:11:09  EDI: 0x0018F9C8
08.11.13 09:11:09  ESI: 0x00000000
08.11.13 09:11:09  EBP: 0x0018F8A0
08.11.13 09:11:09  ESP: 0x0018F890
08.11.13 09:11:09  EIP: 0x77A50C22, 83 C4 04 C2 ?????
08.11.13 09:11:09  EXCEPTION halt in \halopc\haloce\source\cseries\debug_memory.c,#183: Invalid pointer: header: 0x5d9f0020 signature: 0x3c424144 line: 103 file: 0x613748 size: 0xcd60f90 reason: Pointer has been disposed. (\halopc\haloce\source\memory\array.c:80)

Similar to sapien, in tool, I can run quality 0.95 just fine, I could probably even do 0.99, but if I bump it up to 1, suddenly this pops up. Obviously in sapien I can't do 0.9, as it only allows 0 or 1.

I'm running stock Halo as well. I had OS installed but recently removed it in an attempt to fix this, but that doesn't seem to have helped.

Is there already a lightmap bitmap created? Uhh delete that and try again? Just a guess

Also once a tag has touched OS, it usually becomes OS-ified and usually won't work on non-os.

I'll try the delete/retry method, but I only installed OS to play some OS maps, I didn't actually compile anything with OS or open any tags with it.

I've had this before. Its one of the following:

Your computer ran out of memory.

Your out of tag space.

Your tags folder is too big, delete some stuff you dont need and perhaps reorganize.

Sorry I forget where "bitmaps" takes part in this.

EDIT - Fixed.


Edited by hobbet360 on Aug 17, 2013 at 09:29 PM
Edited by hobbet360 on Aug 17, 2013 at 09:31 PM

It apparently has to do with portals and map size. Previously I had a map which was 40k wide x80k long max units with 55 portals, and it compiled fine. But, I went in and added a bunch of new details, which apparently pushed the poly count up. I tried creating more portals, but that only gave me portal flickering. I sized the map down considerably. It is now approximately 16k wide and 40k long with ~20 portals maximum and lightmaps run fine in both tool and sapien.

http://www.ntcore.com/4gb_patch.php

This tool has allowed me to do things no man should be able to do.

Seriously though, this patcher is like a gold mine for all applications developed before the "64-bit" era. Patching Halo tools seems to work very well, especially for big compiling operations such as lightmaps.

Note: I'm assuming you have a somewhat modern computer with 4gb or more of RAM...

Edited by lordofblake on Aug 16, 2013 at 09:29 PM

i got this error with my current WIP and the problem was that the map was too big and detailed but to make it worse most of the shader_environment had high "detail level" setting for the lighting so i just changed the quality of some of them to low or mid and the problem was fixed

so in conclusion from my own experience, if your map is huge but also is complex it's never a good idea to have high "detail level" quality on most of the shader_environment tags
Edited by ChBgt909 on Aug 17, 2013 at 06:33 PM

Honestly I would be inclined to say it's the size of the map which is the most important factor. I didn't change any details on my map other than halving the size of it, and my clusters actually went down, so they're more detailed, if anything.

The clusters could be a factor, as I only had a few clusters to divide the outer portions of the map. Higuy and Kirby both said it had to do with the size/detail of the clusters, so even if the clusters are relatively low detail, but they're 10k units wide (as in my case) this error could still occur.