rainerk

Too bad the scenery requires "Crash Detection" to be turned off.

It is because of a difference in altitude between AFD File (AFCAD) and ground. That is why usually a "flatten" will help, because AFD and ground are "forced" to the same altitude. It has to be done for each faulty airport because the flatten file has to be told what altitude to use.

What do you mean? Where can the aircraft be found for download? To be more specific: where can the B-24 with the update date April 08 be found?

You can try to add Landing Lights with ACM (Aircraft Container Manager). Trouble is this tool does not seem to be available anymore. If and when the lights (Taxi, Landing) are hardcoded in the air file it is difficult or impossible to change the lights.

Glad you made it. Despite my somehat misleading "advice"

Not a texture issue at all. It is a LC issue.

The default Baron doesn't have a view section in the panel.cfg. Therefor you have to create one. Copy both of the lines below into your panel.cfg [VIEWS] View_Forward_Zoom=0.60 This will work for FS9.

For me it's C:\Users\rainerk\Documents\Flight Simulator Files This is the same for W8, W8.1 and W10 and contains files like current.WX current.FLT and the like.

Would you care to let us know where you downloaded it?

You may want to try this: in your FS9.cfg under the label [DISPLAY.Device.NVIDIA GeForce GTX 260.0] RendertoTexture=0 I suggest to make a back up copy of FS9.cfg before editing the file.

System Restore has not been disabled by any MS update. Open Control Panel - System - System Properties and finally the tab System Restore. There you can enable drives to be monitored.

This is the FS9 forum I understand.

Better provide the correct link so more can enjoy.

No need to change your Operating System. Just go here http://www.guru3d.com/files-categories/videocards-nvidia-geforce-(xp-32-bit).html and select a driver which will work for you. I'm using 266.58 and everything is fine. Warning: MS does not offer Security Updates for XP anymore. The least you have to do is to install a good virus Scanner. Or operate your FS9 PC disconnected from the net.

Before installing another driver you may want to go to http://www.guru3d.com/files/index.html and download Display Driver Uninstaller version 13.6.4.1. This will ensure your system doesn't contain any "remnants" from earlier video driver installations.

Looks like autogen objects. You need an exclude file indeed. Excludes can be made with either exclude builder (exclude_builderv2.zip) or with ADE. There is even a tutorial how to use Exclude Builder here at Avsim (excbld_tutorial.zip).

No key required. However, to run the sim you need to have disc 1 in the CD drive.

You do not open panels by right-clicking. You open panels by either clicking the appropriate icons (if the panel designer provided any) or by using Shift-1, Shift-2 etc. BTW, full screen or windowed mode has nothing to do with this. EDIT: Correction: Full screen does eliminate the Windows Frames in VC. Sorry N60JBravo.

Y is the slew key. Looks like your key assignments have been spoiled somehow. I suggest you delete (or rename) your FS9.cfg after making a copy. This way the default key assignments will be restored. The other possibility is that your mixture setting is wrong (which only applies to combustion engines, not to jets). To reset Mixture to lean try Ctrl-Shift-F4.

ERROR ALERT! ERROR ALERT! Do NOT - repeat do NOT- delete or rename the file "magdec.bgl" in the BASE folder. If you do your FS9 may be unable to start and produce the message "Your computer has run out of memory ..." (the dreaded OOM message). Leave the file in the BASE folder, and you'll be OK. Having both files active seems to be no problem. Sorry for the confusion.

You're right, the copy in the BASE folder can be deleted. Or better yet - rename it, so it is not loaded but still there if the need to access or check the file arises. I usually rename those files - mostly FS9 default files I'm reluctant to delete - to *.bgx. So in this case "magdec.bgl" becomes "magdec.bgx".

You may want to try this: "I have moved my default magdec.bgl to a high scenery layer so that it loads after all other sceneries and this seems to ensure that FS's intended settings survive." (Advice from Flightsim Forum). I followed this suggestion and never had the problem again. Step by step: - Create a new folder (I named mine "_MagDec") - in that folder create a subfolder named "scenery" - copy the file "magdec.bgl" from the folder G:\Flight Simulator 9\Scenery\BASE\Scenery to the scenery folder you just created - register your new scenery entry and make sure it is the highest entry in your scenery.cfg You may also want to check if the file "magdec.bgl" is the FS9 default one. If so it should be dated 04-Mar-03 and weigh 128 kB.

Uncheck "Just report bad files (no files will be changed)". Oops, I just saw you said "not in simulated mode", sorry. Anyway, in my very large collection of sceneries (> 1000) I found a very small number of files reported by AlphaSearcher to have no active alpha channel and DXT3fixer did not fix them. So I fixed these with DXTBmp. Again, a very small number of files. You may also want to check if the files are write protected, and in case you're running Vista/W7/W8 if you have the appropriate rights to change the files.

Google for the meaning of . Both of you may be surprised ...

First make a backup of the original aircraft.cfg (most easy to copy and paste in the same location. You will then have a file "aircraft.cfg" and another one "copy of aircraft.cfg"). Then open the file "aircraft.cfg" with an editor like Wordpad. Find the secion [lights] and within something like light.2=3, -20.19, -56.46, 3.84, fx_navwhi The three values -20.19 -56.46 3.84 are the coordinates of the light. When you change these values you will see the light change its location. I believe the values are feet. Play around and see what happens. BTW, fx_navwhi stands for Navigation Light White, so the two lines light.2=3, -20.19, -56.46, 3.84, fx_navwhi light.3=3, -20.19, 56.46, 3.84, fx_navwhi are probably the ones you want to deal with. Try first to change 3.84 to, say, 3.24. Beware: the values given here are examples only. Yours may differ.