I'm actually rather proud of myself that I haven't had to post about any crash-related things in what, 4 days? .

But I got another one. Ok, scenario, I make a few minor adjustments in ZeroEdit, i.e. I added another "teleport" (I already had 2 working ones) and I change some of the color and height of the map. I munge, it crashes as soon as I spawn and try to turn my character. Nothing new in the Bfront2 error log. Munge log had some about not reading the .lua, but when I undid the changes I made to the lua, it still crashed. I undid everything in zeroedit that I changed ("teleports," lighting back to default, and height and painting back to the way it was before I changed). I remunge, and it STILL crashes, however, there's no Errors in the munge log, and still nothing in the Bfront2 error log. I tried a normal clean, I tried a manual clean, nothing has helped at all. I can post whatever logs you need, just I seriously need help!

Thanks for help in advance
-Blade

Need to see munge and bf2 logs

Here's Bfront2 Error Log.

Your mungelog was irrelevant, just a bunch of warnings that wouldn't do anything, so I deleted it. Your bf2log is showing two sev 3 errors, both related to control regions of command posts. That's wherein your error lies.

Well I have had a control region error that said it was 3 but never crashed, just vehicles wouldn't spawn, but maybe its just me.

Well, those severity: 3's have been there for I don't know how long. It was from when I added new CP's, before I knew how to. But I guess I'll check and make sure they both have control regions, anyway. Thanks.


EDIT: I checked, and one of the CPs didn't have a control region... but it still crashed


EDIT2
Wait, does the visibilty range in ZeroEditor just affect ZeroEditor? Or is that for gameplay as well? Because I had mine on the highest, and... I don't know, could it have made it so that the game is overloaded with too much visibility?

Thats ZE range not game range. You change game visibiliy in the .SKY