GSX and Addon Manager with P3D V3.4

[virtualflying]

Hi Umberto,

I'm from the AVSIM topic here: https://www.avsim.com/forums/topic/513741-fsdt-and-p3d-v34/

I'm on here to ask what can be done to fix my P3D V3.4? Before every flight I have to remove OldScenery.cfg and SceneryStatus.bin to get P3D to actually load.

[virtuali]

First, we should check if this issue is related to any of our products. After the sim starts correctly, try to disable it, by unchecking the Addon Manager entry from the Options->Addons menu, then exit and restart.

[virtualflying]

I disabled the Addon Manager and it started perfectly, without me having to tamper with the OldScenery.cfg and SceneryStatus.bin.

[virtuali]

I disabled the Addon Manager and it started perfectly, without me having to tamper with the OldScenery.cfg and SceneryStatus.bin

But since this doesn't happen to anybody else, it's clear there must be something unusual in your installation. The Addon Manager DOES NOT touch or even tries to read these two files.

The Oldscenery.cfg file is a backup used by the sim in case your main scenery.cfg gets corrupted but, again, even if the Addon Manager is reading from it, it doesn't WRITE to it so, it cannot corrupt it.

But some other external utility you might using to handle the scenery.cfg, which hasn't been updated to properly support P3D V4, might be the cause of the corruption, which forces the sim to use the Oldscenery.cfg. Most likely, an utility that doesn't recognize the scenery.cfg file encoding, which has changed from Ansi to UTF-16.

The scenerystatus.bin is also NOT read or used in any way by the Addon Manager, but it's used by the sim to store the last modification date of the sim scenery cache. Again, we DO NOT interact with this file, at all, but (again) a 3rd party scenery configuration editor will cause such file to be modified.