huskydude

Oh.  Thanks for your feedback.

Skywatcher,

How is FS9 being majorly damaged?  I haven't noticed any problems.  FS9 runs great, FS8 runs great, except one cannot "lock Spot Plane View or not having the view gradually  zoom in on your aircraft).  Could you provide examples?

Warmest regards, Husky

Agree with Tom.  Like most of us, we are the Administrators of our systems.  I've had applications either not launch or function incorrectly which were resolved instantly by "Running as Administrator".  Perhaps the issue is one of those many "value-added" features of the newer Windows Releases.

Things were much more simpler in DOS, Windows 3.1 up to Windows XP, but I digress.....

I've installed FS8, FS9, and FSX on my Windows 11 System.  FSX runs a bit slow, FS9 runs great, and FS8 runs great with a few nuances.  I run each program as Administrator.  Reloaded all my addons without issue.  FSX runs slow because my system is a laptop.

Hope this helps.

There is a way to capture METAR, TAF, and WINDS for ActiveSky wxRE.  It's a bit cumbersome, but it does work.  It involves copying each weather type and pasting it into the respective defmetar.met, deftaf.taf, defwinds.wmo files located in the ActiveSky wxRE Folder.

Thoughts?

Hi,

This may be "very" old, but I use FSNAV in both FS8 and FS9 (and yes, I have FSX/FSTRAMP as well). I discovered a means to "edit" the "aircraft.ini" file to adjust the aircraft listing to pertinent aircraft that I fly, deleting those I do not - and retaining ONLY my changes.

After reading a couple discussions regarding the aircraft.ini file issues regarding changes being ignored by appending the original FSNAV aircraft loadset again and again, I determined a means to prevent this from occurring.

First, always make a copy backup of the original (even though that's not really necessary, FSNAV will re-write it - BUT...)

Second, make your desired changes to the aircraft.ini file located in the FS2004/MODULES/FSNavigator Folder and save it. Once saved, open Windows File Explorer, navigating to FS2004/MODULES/FSNavigator.

Lastly, Right-click aircraft.ini file, and select Properties and set the file to "READ ONLY" and FSNAV will not be able to change the file until either deleted, or READ ONLY is removed (using the same method described to set it).

Of course, if you want to edit it, just turn off the READ ONLY, edit it, and turn on the READ ONLY back on the aircraft.ini file (if desired).

Hope this helps, Husky