Yes, I can understand that Sorry

Gentleman,

Don't wanna' give false hopes, but I think I am on a right track finding no CTD on exit mission.
Here's last setup which didn't give me ctd, with joystick plugged in.
(actually didn't even bother unplugging darn thing, cause, no sense doing these thing w/out stick, believe me :D)

Actually it could be that this is relevant just for my (OLD), or any similar system, I cannot say how it will behave on others.
Too many factors, as always, HW and SW.

So, setup is like this:
CA.INI (remark these lines with semicolons)
[Backdoors]
;HEAP_PERCENT=0
;FullOnFlightModel=1
;env=c

Load up old +G's (pdb) database, with heap emu & global mem. lie, settings.
Check LB2.exe's compatibility, there must not be any. So, NO compatibility mode in exe's properties.

nGlide (configurator)
Only important option is VSYNC, and it must be on. (old thing...)

WinLauncherXP
Set, process priority = normal, select only CPU 1.

Fire up.

I haven't got CTD, las few times, after IA (instant action), on ALT+Q (end miss) and/or ALT+X (quit) case.
So... maybe, fingers crossed.

Joy hat is still a problem, other then that everything is normal.
FFARS are ok, system speed is normal without any type of cpu slowdown, guess, vsync takes care of that.

Oh, and D3D video card graphics option, are, in my ATI case:
No catalyst AI/ off
Vsync by app

As for now no AA / AF (app setting) - to test with these forced.

Will report yet.