-= Gametoast.com =-

I believe some of you might already have faced the String pool is full: 32768 pool is not big enough! error.

I did it today. Now here's the what I find interesting. When I run my map in the debug exe (BF2_ModTools), the map crashes, as expected. But when I run it in the normal exe (BattlefrontII), everything runs fine.

Has someone ever gone through this or does know why is such thing occuring?

Could be something that was patched later on. The debug build of the game is pre-release if I remember right.

I managed to find the source of the problem, at least on my case. Apparently, it has to do with too many objects being loaded at once.

In the .lua that was getting the error, I was loading the base layer plus two extra layers which contained a reasonable number of objects. If I cut one of these extra layers, I get no error, but if I load them both, I get the string pool error.

As already mentioned in the first post, this happens only if the map is played in BF2_ModTools (the debug exe). In the normal executable (BattlefrontII.exe) everything runs fine.

I've had a few instances where the actual game exe ran the map fine but the debugger didn't. All of those instances, I was right at the edge of some limit - just about to run out of memory pool space or whatever. So, basically, if you can't play your map in the debugger, you ought to cut down on memory usage, even if the normal exe appears to run the map fine. Not really a surprise.