Hello all,

I've been making Halo CE mods for quite a while now.

This morning I came across the strangest issue. Whenever I try to run radiosity, the map looks like this when I compile using Tool:



It does not look like that in Sapien. I also went to a year-old backup of Halo CE and I still get this issue every time I run radiosity and compile a new map. (If I use the original lightmap that came with a scenario it works fine)

I believe this issue started this morning when I messed around with a bitmap and caused Sapien to crash. Ever since then, I haven't been able to get any map to look right.

I hope someone can help me with this. I seriously cannot figure it out! :'(

I already tried system restore and reverting to an old haloce installation from another HDD

Thanks, everyone!

Edit: I also noticed this error from Toolpro: Bitmaps: Tried to add item levels\test\sidewinder\sidewinder__pixels with different size (303616) than expected (422912)..done

I guess the bitmap compiler isn't working properly? The red and yellow dots look like the ones on any given lightmap. Maybe there's some kind of offset in the wrong place?
Edited by Origin on May 28, 2015 at 09:57 PM

EDIT: I seem to have found a bypass for it. If you put the BSP under a different name and run radiosity again, it will create a new bitmap under a new name. Perhaps the default lightmaps aren't meant to be altered, thus generating the error mentioned in the above edit? Seriously though I've changed those lightmaps many times and I never had this issue before this morning, but at least there's a way around it. O.o I'm going to keep trying.
Edited by Origin on May 28, 2015 at 10:34 PM

Maybe you have a problem with permisions, try deleting the appdata folder

These are all stock maps, and it looks fine in sapien? If so, then its because the bitmap name and path are in bitmaps.map, so its using that bitmap instead (halo trying to save space, etc). All you have to do is use a different location or name for the bitmap; you can open the bsp, re-reference the lightmap bitmap to elsewhere. Or, if you really dont want to go through that effort, you can put in more effort instead, and hex edit bitmaps.map so it cannot find that file path, so it will internalize the bitmap.

Thanks for the assistance once again Kirby. ;) You are the man!

I played around and it's definitely a build problem, not Sapien.

Like I said in my edit it worked when I used a different name. Now I know why! :D

Thing is though it didn't happen until yesterday and I've done this before without it screwing up the lighting. O.o Oh well I'm just happy it worked. :)