Hi,

i think you all know this Memory Pool Message in the BF2 log. For me it says:

Message Severity: 2
C:\Battlefront2\main\RedEngineFL\Memory\RedMemoryPool.cpp(170)
Memory pool "ParticleTransformer::ColorTrans" is full; raise count to at least 2352

but in my lua i have this:
SetMemoryPoolSize("ParticleTransformer::ColorTrans", 3000)

So why did this stupid log say raise up to 2352 while it even is at 3000??

==EDIT==

ok i got it. just moved the setMemoryPoolSize line somewhere else in the lua

But now there are things like that:

Message Severity: 2
C:\Battlefront2\main\Battlefront2\Source\FLEffect.cpp(214)
FLEffect::Read: duplicate effect class name (9e59f92b)!

And

Message Severity: 2
C:\Battlefront2\main\Battlefront2\Source\VOHelper.cpp(183)
VOSound (cis1_inf_pc_com_transport_inVehicle): unknown modifier "InVehicle"

how to fix them??

Regarding last two messages, they're completely harmless and there's no need to fix them.

Yes i know, but it's really annoying to fix real problems (there are also MS 3 errors not crashing the game) when you have to scroll throug an error with 1000 messages. So i would like to fix them to shorten the log.

Notepad has a build-in function that lets you search for specific lines.
For you, click on Bearbeiten -> Suchen, type in and the program will move you right to the next Message Severity: 3 error.
if you wan't to continue your search for evil errors, click on
Bearbeiten -> Weitersuchen.

Happy purging.

Anakin wrote:Hi,

i think you all know this Memory Pool Message in the BF2 log. For me it says:

Message Severity: 2
C:\Battlefront2\main\RedEngineFL\Memory\RedMemoryPool.cpp(170)
Memory pool "ParticleTransformer::ColorTrans" is full; raise count to at least 2352

but in my lua i have this:
SetMemoryPoolSize("ParticleTransformer::ColorTrans", 3000)

So why did this stupid log say raise up to 2352 while it even is at 3000??

Interesting. Can you post your lua? I'd like to see where you moved them to.

First i had the red one. than i deleted it and now it's the green position. And there it works

Interesting. Thanks

I'm pretty sure it dynamically raises the memory pools for particle related things, at least until it completely breaks like it loves to do.

In other words, adding the memory pool line does nothing and you don't need to worry about it.

THEWULFMAN wrote:I'm pretty sure it dynamically raises the memory pools for particle related things

Remember which engine we're dealing with; chances are, the outcome will be polar opposite to its intended design, knowing Zero.

From personal experience, raising these pools to something high via LUA instead of letting the game raise them while running will increase stability by ~5% on maps that are in danger of crashing because of matrix overload.

The effect is marginal and not needed on most maps

Bob wrote:From personal experience, raising these pools to something high via LUA instead of letting the game raise them while running will increase stability by ~5% on maps that are in danger of crashing because of matrix overload.

Yep. One should always try to eliminate all memory pool errors. There's hard evidence that supports this increasing stability. From what I've been told the game only updates memory pools shortly after runtime, so if those pools increase later on it doesn't compensate the second, third, etc time around. That's why things become more unstable when adding units dynamically via the fake console and also (partially) why a map can be fine in single player but have problems online.

about "ParticleTransformer::SizeTransf" always put it on this section from lua:
only on that place it will work fine , give it a try and tell me