P3D v 5.4.9.28482 CTD after having installed FSUIPC6 (enabling it or not, it's the same)

[Croniat]

I installed P3D v 5.4.9.28482

I run P3D, all were good.

I installed PMDG 777, all were good, a flight could be done.

I installed FSUIPC6, when I execute P3D it ask me Enable add-on: "FSUIPC6"? Yes/No 

- No, it creates the file %AppData%\Lockheed Martin\Prepar3D v5\add-ons.cfg with the value ACTIVE=false, then it crashes to desktop

If I remove the file add-ons.cfg, when I execute P3D it ask me Enable add-on: "FSUIPC6"? Yes/No again

- Yes, it creates the file %AppData%\Lockheed Martin\Prepar3D v5\add-ons.cfg with the value ACTIVE=true, then it crashes to desktop

I cannot see anything on the Event viewer about this CTD.

Any idea? Did I do anything bad?

Edited October 15, 2023 by Croniat
spelling

[Croniat]

In addition, now I uninstalled FSUIPC6 removed the file %AppData%\Lockheed Martin\Prepar3D v5\add-ons.cfg and P3D CTD always.

[John Dowson]

Installing FSUIPC6 does not change P3D in any way - it just creates an add-on.xml file so that P3D can load the FSUIPC6.dll. If you do not allow this to be loaded (by clicking 'No') then FSUIPC6 is in no way involved in the CTD. And if you uninstall FSUIPC6, then it certainly isn't doing anything. and it will not have changed P3D in any way. It is therefore something else that is causing this.

Check the windows events viewer to see what module is causing the crash, and try searching for this on the P3D support forums as well as on avsim. Also check your GC card driver to make sure this is up-to-date and when the last update was installed - you may need to revert to the previous release.

...and you shouldn't be manually editing the add-ons.cfg file, as that is controlled by P3D.. You can activate/de-activate add-ons from the P3D add-on management panel, if you wish to do this. You always have to manually allow add-on activation when a new add-on is picked-up via the add-on.xml method.