• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

I rolled back Prepar3d V2.1 back to 2.0 :)

Messages
10,158
Country
us-arizona
With the new Prepar3d '2.1' update, a lot of gauges were broke on my planes due to the new Parser which doesn't like to use certain symbols and has no leeway for tolerance on XML spelling. But... I need to continue to work and didn't want to slow down for updates, news of updates, etc, etc, so I set out to revert my P3D installation back to 2.0. This wouldn't work. No matter how much I uninstalled it, it wouldn't totally erase, even with deleting Registry bits, an odd GUID file in the Windows Installer folder, etc, etc. Even with the 2.0 uninstaller, it didn't uninstall all the main DLL's and other files in the main P3D folder.

Then I found out the V2.1 uninstaller did the trick for cleaning up remnants. How I found this out, was my way to going to trying a trick, I was going to install V2.1 again, then erase the main folder bits and put in a copy from my laptop hoping that might run. But when I fired up the 2.1 installer, it said 'uninstall or repair'. I clicked uninstall, it ran, quit, then I tried the V2.0 installer again, and this time it worked! (It crashes if any signs of V2.1 are in your computer, stating its a newer version of P3D so it cannot continue and closes). So the 2.1 Uninstaller is needed to revert back to 2.0. This is only in the main (full version) installer, not the patch.

Also note below, I have a backup copy of the 2.0 installer. You will need that, as the only one available at P3D.com is the 2.1 and you will need the 2.0 to reinstall it.

Note, this is my own trek I did getting it to work. This took me a while to figure out.

What I had to do is find a copy of the installer for V2.0. You must then run Windows Uninstaller, delete remnant files left over. On my computer, most all of the main program files and DLL's 'did not' uninstall, so I had to delete all of those. (It caused my first attempt to fail). Then you must use the 2.1 Setup program (EXE, full version) to do 'its' own Uninstall also. (This also kept me from being able to run the Setup installer for V2.0 was 'something' is left in the computer drive that is from V2.1. Without running the 2.1 Uninstaller built into the V2.1 Setup program, you cannot load the V2.0 version, as the Setup will crash stating you have a 'newer' version of P3D on your computer, so you must uninstall it first 'with' the V2.1 uninstaller located in the Setup program). When you run the 2.1 Setup, your options are 'Repair or Uninstall'. Select Uninstall.

Next, check your folders that no DLL's and things are left in the V2 Sim folder.
Now, just run the V2.0 installer. When it is finished, you should now have all of your functions and gauges working once again.

The main thing about this is to get V2.1 uninstalled and its only done (fully) by the 2.1 uninstaller.

NOTE: Remember to backup your planes and folders, gauges, etc. Most of them will not be deleted when you uninstall, but you might wish to be careful.

NOTE 2: I found a 'ConfigParser.DLL' file in the main P3D folder. I wonder if that 'might' be what caused the gauges to crash? The one for V2.0 is dated 5/11/2013 and is build 2.0.5073.41754 The new file in V2.1 'might' be the issue that is causing the crashes but I have 'not' tested this theory. I have only just got V2.0 running and have to get it all setup and running smoothly. This is 'only' a theory. This could be the parser that supposedly crashes the FS9 GPS systems.
 
Last edited:
Phew. Thanks Bill

Sent from my Sony Xperia with Tapatalk
 
Bill,

My Prepar3d is 2.1 as you may know. I did an update from vanilla 2.0 to 2.1 - the only thing I have is your DA40.

My ConfigParser.dll is ver 2.0.5154.21143 dated 2014-02-10 and is 24k. Anyone with 2.1 full install? - What version do you have?

Most all of the dll's are date 2014-02-10 and are 2.1.9936.0 or 2.0.5154 - interesting
 
I would think that ConfigParser.dll is used to parse ".CFG" files, but I could be wrong... :laughing:
 
Back
Top