I have a retail copy of this game, and it installs perfectly on Windows 10

But as soon as the game starts up, the frame rate drops. Horribly. Often it drops to 5 or 6 fps, rendering it nigh-impossible to play.

I am amazed a game from 2000 would have horrendous frame rate issues on a modern operating system. Perhaps this is why GOG never released the first version of this game?

*lol*

I've heard before that this game was notoriously difficult to run on older computers. But I would have expected no frame rate issues for a game 16 years old.

You should try the goldbox games without dosbox.

It's not actually that unusual. Games from that particular era have really wonky compatibility with the most recent Windows systems. Often, the reason is that Microsoft decided to drop actual support for older graphics APIs or other components that aren't used by any current software anymore. For example, they decided to get rid of DirectDraw, which a lot of games tended to use, and replaced it with shoddy emulation. That's why games like Shogo - Mobile Armor Division run like crap if you try to run them in Windows 8 or 10 (unless you're using software mode for the graphics). Sometimes, there are ways around that. I heard some games can be fixed by using graphics wrappers like dgVoodoo 2, though.

I had a similar issue with No One Lives Forever. Because I have an Intel, the screen would turn completely black during the underwater stages (although the HUD would still be visible). Installed dgVoodoo and now the underwater scenes work flawlessly.

Also, what's the "Client MFC" error that LithTech games from that era often have mean?

Good question. I suspect it may merely be a general crash issue, since the actual game executable for titles like Shogo is simply called Client.exe. It probably just wasn't the most stable of engines.

Unreal and id Tech engine games from that same era almost _never_ crash or have problems on modern OS, by contrast.

EG: Unreal, Deus Ex, Rune, Sin, RTCW and the Raven Jedi Knight titles.

i had similar problem with call of juarez bound in blood until i tried the directx web install. i understand directx 11 doesn't come with files for 9 or less. idk more but you pretty low imo - i don't see a bright future for you on this site... :-/ maybe you should leave before things get... "complicated"... :-(

The Client MFC error for LithTech games never happens in-game or during a cutscene. It typically happens during a loading screen.

This may not help much; but I thought I'd toss it in as an anecdote:

My current PC is now almost 2 years old. I'm running Windows 7 (which is why I say this may not help much - because it isn't W10).

I have a retail copy of IGI 1 ( and 2). It's one of those games that you can just install once; and then just copy the igi game subdirectory to newer PC's as you acquire them; and it will play (it doesn't need to be "installed" except once; if you instead just copy the dir to another PC).

The "uninstall.log" date on my install is from 2002; so I assume that's my original install date. My subdirectory creation date is 2009 - I assume that's when I last copied it to the current hard drive that it is on. As noted above, this PC is almost 2 years old; so it's fairly recent.

In any case, I've not yet played igi 1 on this PC, so I loaded it up (at some point I apparently renamed the startup shortcut with the words "run as admin"; so I right-clicked it and ran it as Administrator).

It started just fine - I changed the graphics driver from "Primary Display Device" (or whatever the exact words were) to my actual graphics card (Geforce GTX660); and set the game rez to match my display (1920 x 1200 x32). I edited the controls (which were unexpectedly the defaults - I figured they'd have been "saved" from whenever I last played - but they weren't).


ANYWAYS - I started Trainyard - and played it a short ways (infiltrated the yard; mosied around a bit).

It plays just fine - no framerate issues at all. There is some screen tearing now and then - I might be able to fix that by setting a synch to monitor setting in the nvidia app - but I didn't.


Not sure any of that helps you specifically - but it does show that igi 1 can run fine on newer'ish hardware.

You may want to cehck your system as per ciomalau's post - and ensure you have older Direct X on that PC - could be a good place to start..

I have the most recent version of Direct X installed.

The point was ensuring you have an appropriate OLDER version; not the most recent version.


As ciomalau's said:

That's what was being suggested - that you check that you have the appropriate OLDER version of Direct X; because MAYBE the most recent version isn't fully backwards supported to older versions. (Disclaimer: I don't know what the most recent version supports - but it makes sense to double-check that it might not support the older version capabilities needed by igi 1)

here is directx web installer:

https://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=35

if you have new version and try to install older, it will always tell you that you are up to date. but this web installer might fix you