Hmm, if your goal is BMS, I think you're better off starting with it - right away. Some key-things
are different in BMS. Also, the mod adds more functionality that you must get used to, in BMS, but
you had not in AF. The first impact with it can be disheartening, beware.
But back on your weird problem...
No need for fraps to take just a screenshot
Simply hit the
PrintScreen key on your keyboard. Or it may be called
PrtScrn, or even
just
Stamp. There may also be the words
R Sist on it. Every keyboard names it the hell
they want, and laptop keyboards make it even worse. But it *is* in there (usually up top, on the right).
Hitting that key will create a screenshot (duh!).
If the screenshot was taken during flight, you will have a picture inside your
C:\...\FalconAF\Pictures\Simulation folder.
If the screenshot was taken NOT during flight, you will have a picture inside your
C:\...\FalconAF\Pictures\UI folder
(that's where your debrief screenshot will be).
To tell that you DirectX is version 9 is vague indeed. Dx9 was released in a crapload of flavors. You
have Dx9.0, Dx9.0a, Dx9.0b, Dx9.0c. Then every few months a new Dx9.0c version would come out, and so
their month and year of release would become part of the name (example: Dx9.0c Aug2008) this thing
continued for a couple of years. Then they made Dx9.0d and finally someone had the idea of upgrading
the whole thing to Dx10 and so on...
But anyway, so long you have any DirectX 9.0c you should be fine. To check for that do the following:
1) On your keyboard, hit
Win + R (the Win key is any of the two Windows keys).
2) A little window shall open. In its text field type:
dxdiag, then hit the
Ok button.
3) A big window will open, with lots of info in.
4) Inside this last window, look at the bottom-center of it. There will be a line
DirectX version:,
or something similar (my Windows is not in english). And there will be what looks like a long version string.
You should be reading something like:
DirectX 9.0c (4.09.0000.0904), though your line may differ.
Please tell me the exact version string you read.
About your ACMI recordings... do you record a lot, by any chance? And by 'a lot' I mean anything longer than
10 minutes? ACMI is meant for short recordings - it's to review specific maneuvers, not whole flights.
When going to debrief, AF will collect all your ACMI data and convert it to files you can review later.
This process can take
many minutes even on a fast present day CPU (to the point you'd think the
game has frozen for good, hanging your computer for an eternity). I can't exclude that this might have to
do with your weird problem.
Does your debrief problem show up even if you do *not* record with the ACMI?