FSX not allowing change of airport from default location

[SSI01]

Now have a bugbear having to do with scenery - sim will now load only that for the default flight in Washington State - any attempt to move to another scenery, even if I have started a flight using a default aircraft, ends w/the sim showing the two error/restart boxes, at which time I have to shut the thing down. I thought paring down the number of aircraft it would have to load from dozens to maybe two or three would have helped this thing but it's not to be, apparently. I don't have this problem with other iterations of the same sim on this computer. What is the file that tells the sim where to transport the aircraft once you choose a new airport? I'm wondering if the one in the "FSX Prop" installation is just tired or worn out but I don't have any ideas about a fix for this.

[mrzippy]

Does it matter which aircraft you choose to start this new flight?

[SSI01]

Hello Mr. Zippy.

 

Here's what happens:

Default flight (mid-air in WA state)/powered glider (default aircraft) - starts fine.

Default flight (same situation)/add-on aircraft (He-219) - starts fine.

Flight from runway on ground, in GA/powered glider (default aircraft) - I get sound and view of runway, stays like that for about 10 seconds, then two boxes, re: error found/FSX restarting.

Flight from runway on ground, in GA/add-on aircraft (He-219) - same response as w/default aircraft.

 

So, in short, I can fly anything in the hangar from the default flight - mid-air in WA state - but can not start any flight anywhere on the ground with any aircraft, including the default aircraft.

 

Incidentally - after the 4th restart in this series, I got a notice saying FSX had a problem with a gauge file - "FDav.dll" - and recommended the file be deleted. Here's what it says:

 

 

"Flight Simulator has detected a problem with a third-party software program (add-on)

 

NAME: FSXGauge

 

VERSION: 1.7

 

COMPANY:

 

FILE: Gauges\FDav.dll"

 

 

 

The FSX .cfg file changes every time there is that refusal to fly anything other than the default flight.

[mrzippy]

https://steamcommunity.com/app/314160/discussions/0/350542683207445843/?l=ukrainian

 

Maybe this will help?

[SSI01]

Hello again.

 

I took your suggestion re: FSdav.dll but no soap, sim still will accept an add-on aircraft (Aeroplane Art Bristol F2B) and will not allow it to start at any other airport other than that designated by the sim when first logging on (that is, default flight). However, I have noted something else - when starting the sim, after it goes through the initial start-up screen ("FSX Flight Simuulator" blue screen), and then tells me Red Panda (has to do with the SSW F-104 aircraft) is disabled, I get the sim going black for a moment, after which I get the initial "run" screen (same as start-up screen), but when looking at the bottom bar on the computer screen, I see two small "FSX" icons in that bar, one superimposed on the other, which is just barely sticking out from beneath the right side of the upper icon. Move the cursor over these icons, and they appear side by side above the bottom bar. One has a black screen in it and in the upper corner a small red rectangle with a white "x" in it - standard Windows "exit" symbology for open window in any program; the other has a white screen and a small, square green icon (like you find in the Device Manager window) in the upper corner, also with a red rectangle with the white "x" in the other corner. I clicked on and closed the square with the green icon in it and the FSX "choose aircraft/airport/date-time etc" screen came up. I went ahead and selected the F2B for the flight, and chose another airport I had not been at yet - and the sim started perfectly at the new airport with the add-on aircraft placed exactly where selected, engine running and ready for flight.

 

I may be wrong but it almost seems like the computer is somehow detecting two "fsx prop.exe" files in it somewhere. I have one right in the program, and a shortcut in a desktop folder marked "fsx prop.exe shortcut," created by the Windows program, not me. There seem to be two copies of the sim starting up and it remains that way until I do as I described above, at which time one icon immediately goes away and the other expands to the full-fledged, ready-to-fly screen.

 

Please let me try this with a few different aircraft over the next day or two to see if I've found something significant. I'll let you know progress.

[SSI01]

Hello again.

 

Well, Mr. Zippy, nothing has changed from the above description. The sim will start fine from either the shortcut in its desktop folder, or by accessing it directly by going into the sim's base folder and double-clicking the ".exe" file. Things work fine as long as when the "lapped" FSX screens in the task bar appear on the bottom of the screen, the cursor is held directly over the center of the lapped display and left-clicked once. At this point, the two miniatures of the large FSX screen on the desktop are displayed side by side above the bar. One shows a black inner filling; one shows a white inner filling. One shows a small blue "FSX" icon in its upper-left corner; one shows a small green/white control-panel-type icon in its upper-left corner. Click on the screen that shows the blue FSX icon, and the other screen will fade away and the large FSX viewing/dialog box screen will then show in the center of the desktop. Make the aircraft/airport selection from this screen, and there are no problems with any flights from that point on.

 

I don't know how to describe the second FSX screen showing under the first except to say, again, it seems like there is another "ghost" version of the sim running somewhere. Clicking on things as I've described shuts down that ghost and must free up those resources to use in the real thing.

 

This is most unusual although a fix to the hex appears to have been found. Maybe if anyone else runs into this situation this post may help them.

[mrzippy]

If you can, post a screenshot of what you are describing.

[SSI01]

I'll get started on that. Hopefully it won't exceed upload limits.

[SSI01]

Mr. Zippy, I have a screenshot of the lapped icons, still trying to figure out a way of getting a shot of the two miniature screens side by side just above the tool bar. Here are the lapped icons.

 

[f16jockey_2]

When I get that double icon in the taskbar, it mostly indicates a popup dialogue needs to be answered.

Like a gauge needing to be registered.

 

Hovering over the icons with the mouse allows me to select the popup and answering/closing it.

 

 

On some occasions it happened the popup was hidden by the FSX loading splash screen (was behind it).

So it wasn't apparent the program expected some input (making it look like it was frozen).

 

Wim

Edited August 22, 2021 by f16jockey_2
pic and additional info

[SSI01]

Hello Wim

 

I hear what you're saying - and I'm glad you posted that image because I made repeated tries to get an image of my problem which was almost exactly what you've posted - my difference is I get the right-side image with a black screen, the left-side image is identical to the left-hand screen you've got except it's only a white screen (same dimensions as the white screen in your right-hand box), but it has the same icon in the upper-left corner and the same print across the top. Just no dialog box as seen in your left half of the image. I DO get a different dialog box about the Red Panda program in my FSX Prop program, though - it's not the standard framing on that dialog box that's in the other programs' Red Panda boxes.

 

I do take the same actions you are taking in that I raise both boxes by hovering the cursor over the double-icons on the taskbar. Although there is no text in the left-hand box - just the white screen as in the right-hand box, with the same title info across the top - I take the same action, just "X" out of it, and at this point the problems seem to be resolved.