The pictures idea has some merit, but on the other hand, I imagine GTVA fightercraft already record most of their sensor data. And pictures won't really tell you much. Not everyone has nameplates, and nobody says you have to paint the correct name on the side either. The main use for an image like that would be to confirm class, and if you hit it recently, assess its damage.
If you want positive ID you'd need to close within a couple of klicks and stay there, preferably with your own engines stopped, and record his emissions for a minute or two. It's surprisingly difficult to make a radar or an engine with exactly the same characteristics, but the differences are subtle and it takes time to spot them. A fighter probably wouldn't have the gear necessary for that kind of signals processing work. But it could record the information and bring it back to base.
Well...
Is there any way to incorporate actual screen captures as temporary interface files?
Meaning that by some SEXP or script, you could take, say, five screenshots with some special keypress, not the normal Print Screen, and those would be saved on /mod/data/interface/recon_capture_1.tga and so on, and then those would be used in an intermission phase (like the "Welcome to Aquitaine" and other similar stuff in FS2 campaign) as graphics?
Or perhaps even saved as an EFF animation frames (do EFF animations work on the interface anyway...?) and use the animation as a slow slideshow in the next mission's briefing.
