I am pulling my hair out trying to figure out what to do other than use aether and 3ds max and all of that. I am trying to change the sky and re-run lightmaps and it keeps giving me this crap

i.imgur.com/SLIStQy.jpg

I've tried everything but using aether because it is too complicated for me to understand currently. I've tried using tool, I've tried using sapien, nothing is fixing it.

Can someone please tell me what is going wrong and what I can do to fix this? I would really appreciate it.

04.30.15 01:01:17 tool pc 01.00.09.0620 ----------------------------------------------
04.30.15 01:01:18 reference function: _write_to_error_file
04.30.15 01:01:18 reference address: 42ca20
04.30.15 01:01:18 i'm going to render final lightmaps for tutorial of levels\test\tutorial\tutorial, and i'll stop when red+blue+green = 0.001000.
Hit control-c now if this isn't right.
04.30.15 01:01:18 start levels\test\tutorial\tutorial
04.30.15 01:01:18 0.000000
04.30.15 01:01:23 0.337352
04.30.15 01:01:27 0.192310
04.30.15 01:01:30 0.100107
04.30.15 01:01:33 0.048104
04.30.15 01:01:35 0.015623
04.30.15 01:01:39 0.003451
04.30.15 01:01:41 0.001166
04.30.15 01:01:43 finished levels\test\tutorial\tutorial
04.30.15 01:01:44 done

So nothing, *sigh*
Edited by S12Spark on Apr 30, 2015 at 02:01 AM

yes, why is it orange, I do not understand at all. Is there something stupid I have done? I did levels\test\tutorial\tutorial , it was the correct one, and it finished in tool and printed, yet its still orange. Have you ever had anything like this happen to you?
Edited by S12Spark on Apr 30, 2015 at 04:42 AM

If I delete the bitmap image then sapien would not be able to open it. It would just close.

I'm going to try to re-compile the map completely including the structure and whatnot under a different folder and name and change a few things and I will see how that goes.

I seem to have actually gotten it to work by doing that, I am running the lightmaps for a second time with scenery to test now. will update post again.

aaaaand it exploded after I added scenery, fantastic, I'm going to try removing the scenery and then try it and see what happens.

no luck, I give up on tutorial, I'm like 100% sure I have no other issues with other maps lightmaps when redoing them. I will try that now and make sure.

it died on bloodgulch as well, I'm getting a fresh tagset and trying again, after that if it doesn't work I am reinstalling HEK.

10/10 would hang myself again, I'm not sure what is going on but I renamed the folders of bloodgulch, files etc and changed the power in the sky tag from 1.8 to 2.9 and it fixed it. Going to try changing it back to 1.8 and see if it breaks it again.
Edited by S12Spark on Apr 30, 2015 at 05:51 PM

I don't think that would work but I will try soon but I actually figured out what was wrong. Data files from open sauce, I wasn't overwriting them and or creating anew so it was using multiple light maps at once I guess, I'm not sure. I will try that though with sapien just to test and confirm.

I will add you over Skype too
Edited by S12Spark on Apr 30, 2015 at 10:08 PM

looks funny, its like a rianbow hehehe

So I found a REAL solution to this, and figured out why it's happening, and it wasn't anything to do with opensauce I do not think. It's like sapien is showing the old lightmaps, then compiles them again and duplicates them/corrupts them, if I take the entire level folder, copy it, rename it, and rename everything inside besides shaders and bitmaps, so the scenario, the lightmap bitmap, and the structure bsp, then go fix the stuff in guerilla to the new filepaths, it will work correctly, so its not that much work for working lightmaps.

Thanks, that worked for me too :p

Whilst not exclusively related to lightmaps in general the same duplication/corruption error did affect me from time to time.

But once I switched to a 64bit archetecture the bug vanished.