Hi, I had munged my map (it is very close to the object limit) and it worked great in-game until about 5 min. into it, it crashed. I tried using the mod-tools and it crashed at the last second. I got the bfront2.log thankfully and the weirdest thing was this.
I couldn't believe my eyes . It was "the error code of doom" that would always crash the map at the last second in both the mod-tools and the game. But for some reason it didn't crash at the last second in the game. I had to try it again in game just to see if I was lucky. Well... it wasn't luck. Now I'm sitting here wondering "Why in the world did it not crash!". This isn't making sense, is there any sort of explanation?

EDIT: Ok, I think I've narrowed it down a bit. I have 3 areas: Kashyyyk, Geonosis, and Utapau. When I enter Utapau from the outside using a vehicle it crashes. It didn't do this before, so why now?

i guess battlefront crashes beause it cant handle the number of objects it has to render (you can see)

DarthD.U.C.K. wrote:i guess battlefront crashes beause it cant handle the number of objects it has to render (you can see)

Ok, I will get to moving it somewhere else sometime. Also, I was wondering why the Utapau wall/rock thing is hollow. I couldn't find anything in an msh.option file that has "-nocollision" in it. Is there any way to make this solid?

NOTE: I still can't figure out why the string pool error won't crash the map immediately (like it used to).

linksith wrote: Also, I was wondering why the Utapau wall/rock thing is hollow.

Hollow you mean by you can go through it? Yes, you can go through it.

linksith wrote:Also, I was wondering why the Utapau wall/rock thing is hollow.

*sigh


@linksith: the reason is that the msh contains one collisionprimitive which prevents the creating of a collision by visualmunge