Here is the problem - there is no patches for this game on the internet, no matter how hard i looked into Google and other search engines. If anyone has a "perfect" setup for this game - please post it in this thread.

Major lags occurring when on 10th level, that's where the game gives you a bunch of enemies and friendly "teammembers". Maybe that's CPU-dependant, i don't actually know. But if this problem could be solved - we can save at least a minute or two on these runs.

So, i tried several compatibility modes, even through Microsoft Application Compatibility Toolkit and still no results. Still have no technical proof that NPCs are causing so much lag.

Finally, changes in the air.

At last i can say that MAJOR lags can be "cured" by DxWnd. Unfortunately, it slows down the game a lot. I predict some timeloss with current configuration, about two or three minutes. Looking back at my run - it seems like a lot of time, especially with somewhat perfected first and second levels.

Still looking for a right config. Actually i really doubt that someone is interested in this game, but eh, progress is progress, i guess.

I certanly don't have any life. Kappa

Anyway, i found somewhat good config for the 25 To Life game. Sadly, i can't find the dxw file, so here is the .ini file for DXWnd that is configured for the game. http://www.mediafire.com/view/c0zoqm7s0fefd2q/dxwnd.ini

Quick update - the game has some issues with AMD videocards. Basically texture problems, but really nothing THAT serious. It still behaves exactly the same, except every second mission the textures are partially messed up. Probably render problems, quick change of settings in DXWnd didn't helped, so i'll look into that issue.

Maybe it's kinda late for that, but don't overclock your CPU and speedrun this game (like someone actually considered that, haha). AMD FX-8320E overclocked to 4.0 GHz - computer just restarts after random amount of time in game. Probably something with incompatibility with new CPUs/GPUs, but not really sure about this one, the game could've reboot my PC when in "non-overclocked" mode.