Author Topic: GSX not launching (P3Dv4)  (Read 2216 times)

iMove Quick

  • Newbie
  • *
  • Posts: 47
GSX not launching (P3Dv4)
« on: July 02, 2019, 01:24:36 pm »
Hi there,

So I don't know if this a known issue, but whenever I try to start p3d GSX doesn't start. Only the addon manager does.

I tried re-installing, but that didn't seem to work...

Hope this might get resolved soon!

~iMoveQuick
« Last Edit: July 02, 2019, 01:30:51 pm by iMove Quick »

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51462
    • VIRTUALI Sagl
Re: GSX not launching (P3Dv4)
« Reply #1 on: July 02, 2019, 02:41:33 pm »
Be sure you configure the antivirus to exclude the whole Addon Manager folder from scanning, then run the FSDT Live Update again.

iMove Quick

  • Newbie
  • *
  • Posts: 47
Re: GSX not launching (P3Dv4)
« Reply #2 on: July 02, 2019, 05:26:05 pm »
I will try to do that. thanks.

Rustydog

  • Newbie
  • *
  • Posts: 41
Re: GSX not launching (P3Dv4)
« Reply #3 on: July 02, 2019, 06:28:37 pm »
Hi Virtuali,

After uninstalling GSX 2 from C drive and using full installer to install to E drive, Gsx did not start, no menu, nothing.
I looked in the add on xml to see most of the entries still pointed to the C drive. I manually edited these to point to the E drive and GSX started. So guessing the installer did not update the add on xml correctly. Only guessing though.
Only issue, after using the airport editor without actually editing anything, when I closed the editor GSX and all menus vanished again.
I only post as it might give you a pointer to other non start problems users are having.

Regards Steve
Intel Core i5 4690 (OC 4500Mhz), GeForce GTX1060 6gb GDDR5, P3Dv4.4, PMDG 737u,

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51462
    • VIRTUALI Sagl
Re: GSX not launching (P3Dv4)
« Reply #4 on: July 02, 2019, 06:42:55 pm »
So guessing the installer did not update the add on xml correctly. Only guessing though.

The installer will always update the add-on.xml. But another user reported that file to be read-only, for some reason (we surely don't create it like that)