Silberpfeil

Thank you - please upload it when you get a chance. I'd like to see how your entries compare with what I'm using.

Nice, jeanba - have you modified your flightengine.ini files?

Good one, Erik!

Really neat, Geezer!

Pleased to see this, Ojcar! Your contributions to this series are much appreciated!

Looks great, Stephen1918 - thank you!

OK, I've investigated a little bit more, and you're correct. The pilot is there on external views (regardless of "In Air", "Near Target", or "Airfield"), but not there when using "free camera" Ctrl-F12. Even more interesting, the same thing seems to occur when flying in my Palestine and Italy installs, but not in the Cambrai or Verdun or North Sea or Galicia installs, and I've checked using a variety of other aircraft with their pilots to confirm. Never noticed this before, so I guess some more investigation is in order...anyway, I wanted to get back to you as it doesn't appear to be specific to the CR42's pilot!

Geezer - did you do something special with the CR42's pilot? Everything seems to work OK when I start the simulation "In Air", or "Near Target", but when I start at "Airfield", the pilot doesn't show. What am I missing?

OK, OK - here's another Chevy Nomad pix for all your trouble! Let's try this again - too fast on the POST button!

Claw's "howtogeek" link has a series of good tactical moves to offset Microsoft's Windows 10 initiative. Windows Update KB3035583 is the culprit, and I removed it from my system about eight months ago (after trying to turn off the icon and its notifications) with no aftereffects and it has not returned. I use Windows 7 because it works, and just like my old laptop still uses XP - it works! And I don't think I'm being overly naive - Windows 7 is dated and will run out of support someday, and if I build another system it will be with a clean install of Windows 10 (or 11 or 12...) anyway, so the upgrade software would have just taken up space.

Wow! A LOT more classy than those P-43 Lancers the 94th Pursuit was pushing around in that same timeframe! Of course, in another year or so, they'd get upgraded to P-38D's which had more firepower but were just about the same in performance...

See link below: http://www.businessinsider.com/ap-albania-to-auction-off-old-eastern-bloc-military-aircraft-2016-2

What do you have, like, old 5-1/4" and 3-1/2" discs chock full of this stuff? BTW, while not exactly in the Tie Fighter CD genre, here's a pix of a wannabe Nomad from a couple weeks back that I thought you'd enjoy!

Imperial add-ons are always the best! My two top clone pilots, SS396 and SL550, are most excited! Thank you!

Those shots are great! Appreciate it!

Outstanding detail and work - but can I make a request? Can you depress the angle of your shots next time to include what would be seen out to the horizon? I'm still struggling with incorporating all mue's "fading TOD's" upgrades into my test FE2 installation, and was looking for a reference on what others have in theirs. Thanks!

Great stuff - thank you! I have no idea how you have the patience to convert these "nightmare" add-ons AND do everything else you do for the CA crowd!

Wilco.

So impressive! This Gladiator/CR42 stuff just keeps getting better and better!

Reads like you're already well along and on your way - good luck!

Streakeagle, I saw your post from last month - your installation is fantastic! Nothing anywhere near that dedicated for me as my desktop PC (i5-3450 CPU @ 3.10 GHz) is used for a variety of tasks. My flight hardware is pretty basic with an old CH Products 568 CombatStick (since FE2 is mostly "blip switch" oriented, that's about all I need), and an even older set of CH ProPedals. I occasionally visit some of the online purchase sights for a deal on a ProThrottle, but not sure I really want one. PCPilot, If you're primarily interested in simulating GA aircraft (although I guess you could also use it for a P-38 Lightning), wouldn't you also want a yoke in addition to your stick? The CombatStick grip and buttons arrangement is similar to that found in both the CH-47 and SH-2, but not a Cessna (unless it's a Model 318!).

Been a pilot since the late 1970's, and as Streakeagle writes, the modern PC simulators are a very cost-effective substitute for learning procedures (not really sure about habits as there are both good ones and bad ones!). I've always been curious to use one of the "shaker sticks" to try and compare how it translates flight physics into the palm of your hand, but haven't done that yet so can't comment. I've always thought the old nautical saying about "hours and hours of boredom punctuated by moments of sheer terror" was also appropriate for flight, and the PC can't really simulate the onset of airframe shudder and vibration when you enter into a stall, the weightlessness you momentarily feel when the nose drops off, and the rush of adrenaline when you realize you'd better get the power off and kick in some opposite rudder to stop the rotation!

Thank you - really appreciate this and am looking forward to Red Squadron's next two lost mission sets! I'm finally getting caught up on installing all these XvT/BOP downloads with their improvements. From one of your previous posts, did I also understand that you had some advanced mission sets for the X-Wing Alliance story?

Thanks, Heck, that is helpful! While I'm sure some of the FE2 symptoms I experienced were the results of accidental and self-inflicted coding wounds, the way the program reacted was a little surprising. OTH, maybe I'm chasing down a path someone else has already been down and found to be a dead end. Not the first time that's happened, unfortunately!

UPDATED: This has been resolved. When I migrated the Sopwith Triplane folder into a newer install from a previous one, an older name in the Nations17.ini file apparently caused a conflict that resulted in the described condition (not sure why FE2 would only limit Single Mission aircraft to one and then let everything else proceed normally – anyone have an idea on this?). Circling back and recognizing which NationsXX.ini variant was controlling the “country” names in each install was the first step, and then further checking and correcting the various .ini and Texture sub-files for each aircraft finally straightened everything out. A time-consuming job but everything seems to run OK for the present!