I recently replaced a previously working map's terrain with a tga2ter terrain with a grid size of 2. It munged fine, upon running the map on the main BattlefrontII.exe the game upon reaching unit select started suffering rendering problems consistent with a rendering engine (term?) overload, and after about 5 seconds completely locks up to the point that my PC needs to be restarted. When I run the map on BF2modtools.exe I can play the map just fine with the new terrain and there are no errors at all in the log related to rendering or graphics.

What gives? Also is there any workaround? I'm rather attached to my grid size of 2.

Many limitations are removed for testing purposes. It's probably just an instance of that. No workaround, unfortunately.

Teancum wrote:Many limitations are removed for testing purposes. It's probably just an instance of that. No workaround, unfortunately.

Has it been documented which limitations don't exist in the debugger?

It's a pity that some of these limitations were not removed in the final game if they were not needed. I'm assuming there's probably less limitations on the models and from the sounds of things there's less limitations on terrain size.

I am thinking it may be possible to compare the debugger exe against the regular game and see if anything an be changed for the good...

Teancum wrote:Many limitations are removed for testing purposes. It's probably just an instance of that. No workaround, unfortunately.

Hmm, so what is the smallest gridsize supported by the game engine? There where a number of posts in the tga2ter thread that suggested that a smaller gridsize than 8 was doable, but I keep getting crashes.

ZoomV wrote:Hmm, so what is the smallest gridsize supported by the game engine?

I'd probably say 4 at the smallest.