Thank you so much for the explanation mkubani. It seems that the culprit is the already aged IL2 engine, as when it was conceived GPU's didn't have a speck of the performance they have today and processors seemed to do a better job when resource-intensive situations arose. Therefore, the designers of IL2 took this road, and when a load of information needs to be processed, the engine ends up overloading the processor when it actually should be doing the opposite and transferring graphic solutions to the GPU.
Guess I'll have to stick with that and simply not use these maps. It's too sad because they are beautiful maps which are hampered in use for an engine that has been pushed way beyond its limits.
There are other map areas that also yield this kind of behavior. There is one from our old map set that causes the exact same reaction. It's the Berlin map. How cool wouldn't it be to have a dogfight right over Berlin skies? Well, too bad, the engine can't handle that many objects. =( Stick to less populated areas.
It's interesting that I've been flying IL2 since the very day it came out back in 2001 and only recently I've able to mathematically notice what was going on behind those poor fps I was having.
I wish this problem could be solved through Drivers, but it's definitely an engine limitation on the way it deals with too many objects on screen.
Still, thanks a lot for all the help. It was very clarifying. Best regards!
|
12-11-2009, 01:39 PM
Hybrid Mode
