Dornil

Yes, I have the BDG applied - TIR works great! I could use the Huff skin - couldn't get it out of Wayback machine. What I really want and could not find are winter terrain and AI MiGs skins with historic markings.

Graphics mostly. Skins, terrains, etc.

Pretty straightforward, actually. I simly used the new version of DDrawCompat (0.6.0): https://github.com/narzoul/DDrawCompat/releases Earlier versions had some problems; this one provides excellent picture and compatibility. With this MA is running well under Win10 even without any compatibility settings. Unfortunately, it's not perfect after all - CTDs happen often during long missions :( Although it could well be inherent problem of the Mig Alley itself - I vaguely remember something like this from the days when it was a relatively new game. There is a couple of very nice guides here: https://www.tales-from-darkenedroom.com/post/mig-alley-running-in-windows-10 https://www.tales-from-darkenedroom.com/post/mig-alley-running-in-pcem

I finally got this masterpiece of the yesteryear working perrfectly on modern hardware under Win10. Unfortunately, all the sites with mods for this sim are long gone by now, and Wayback machine can only help so much... Hence, my request: does anyone happen to have MiG Alley used-made mods from long ago still archived somewhere? If yes, could you please share those?

Don't judge everyone by the same standard of hand-biting, please. I, for one, am simply unable to effect the subscription payment due to certain... geographic deficiency :(

I vaguely remember solving the same problem by putting the attached dll into game's folder (where WV.exe is). But I am using Win7, so no idea whether it will work with Win10. msvcr71.dll

MiG-17, MiG-19, F-100, F-8.

Thanks for the infor guys! One question, unrelated to FM: the F-86K available here, in downloads, has its aelirons and flaps somewhat misaligned in-game. However, their positioning is just fine when viewed in LODviewer. I tried tweaking some values in data.ini, but did not succeed. Is it even possible to fix this in data, or does this require access to original 3D model?

So, does this mean that the 3D model somehow influence the flight model? Thanks! But what do they do exactly? I mean, does EmptyMass have to be a sum of MassFraction values of all hte components? If the [AircraftData] values contradict those in specific components sections, the what takes priority?

Thanks' VonS! That was comprehensive! Strange thing happenned yesterday, btw: I took everything related to FM from KAW Sabre and put into Capun's data.ini. And it still spinned, while original KAW 86F-30 did not... Some kind of magic involved?:) A little unrelated note: what do MinExtentPosition/MaxExtentPosition values do? Also, values from [AircraftData] section (EmptyMass, EmptyInertia, ReferenceArea, ReferenceSpan, ReferenceChord, DragArea, CGPosition) - how do they influence the flight behavior of AI or player? Is there some sort of "data.ini for dummies" somewhere?

I trust you all the way, but still, spin makes flying much more interesting:) That's why I'm trying to understand how to add this "function".

Thank you for clarifying this for me! But I still can't understand the "spin technology"... For one, this is the extract from KAW F-86F-30 data.ini (LeftWing section): This one does not spin when stalled. And this is from Capun's F-86F (same section): This one spins. What is the difference between them?! Or should there be an assymetry between some post-stall values in left and right surface to produce a spin?

What I mean is: for example I have data.ini's of, say, F-4 and F-86. If I just copy [FlightControl] section (and everything under AI data) from F-86 to F-4's data, does this mean that AI Phantoms will fly exactly as AI Sabres? Or do they take other airframe/engine figures into account as well? Another question: some of the modded aircraft have spin and spin recovery modelled. How was this done? I mean, what sections of data.ini are responsible for spin behaviour?