Here's a few from the highly modified and experimental Savage Monster lol
(These are two uncharted airports at flightsim to - search for YellowJacket and Wiley Ranch - they are real strips though!)
It is indeed the RealAir model ported-over (an okay stopgap until the MSFS-native AH Spitfire - Spitfires hopefully). Having done no modifications whatsoever, it flies perfectly well using the Modern flight model setting. It is much easier to handle on takeoff than the recently released Carenado WACO. I actually think it might handle even more accurately in MSFS than in FSX/P3D - you can get the tail up quite fast in the takeoff roll in MSFS, just like the real Mk.IX Spitfire, and it is also easy to nose over if you come down on the brakes while taxiing, just like the real thing (I don't remember that being the case in FSX/P3D). Also, if you're flying it on a cross-country like I did, you can never let go of the stick for very long before it will start diverging in one direction or another, which is exactly what I've heard described of flying the real thing. Peter Teichman, who has owned Spitfires, a Hurricane, P-40 and P-51, once commented that the Spitfire was his least favorite of those four types to take on long trips for that reason. You can never trim it for completely hands-off flying, and it handles that way in MSFS. I however haven't done any rolls or inverted maneuvers with it yet, so I will have to check that the next time I fly it to see how it handles in that regard.
It is indeed the RealAir model ported-over (an okay stopgap until the MSFS-native AH Spitfire - Spitfires hopefully).
With port overs, the textures are cached in the CVT folder that's automatically created. Just delete that each time.John, I don't know if you have started skinning specifically for MSFS yet, but if so, have you happened to notice that MSFS does not immediately reflect the edits you've made to your skins, even when you close the sim and restart it? This drove me crazy for a while, but eventually I concluded that MSFS is caching the aircraft skins somewhere, and as long as you don't change the folder structure, it doesn't load your edited skin. The only way I've found to force it to load an edited skin is to change the name of the texture folder and edit the aircraft cfg to point to the new folder, then rebuild the layout.json. Turning off the rolling cache doesn't help; I guess that's not where it caches skins. I haven't looked whether there's something in the developer mode menus that forces it to refresh the entire plane.
August
With port overs, the textures are cached in the CVT folder that's automatically created. Just delete that each time.