I have done the following:
Reinstalled latest Nvidia graphics driver using a custom clean install
Restarted computer
Deleted P3D Shaders and P3d.cfg (recommended by many users on another forum)
Restarted computer
Ran P3D using default airplane at default location and did a quick test flight to ensure P3D recreated the shaders and P3D.CFG files - No issues found and sim worked wonderfuly
Closed P3D
Waited 30 minutes (got lunch)
Ran FSDT Live Update
Restarted computer
Opened P3D, running alone with no other add-ons
Loaded PMDG 747 to ZBAA gate 403
Allowed GSX to finish starting and PMDG to load aircraft
Changed panel state to cold and dark so i could edit freely and allowed PMDG to load the panel state (it at this point has been about 3 minutes since the flight had been "launched" from P3D main menu)
Opened GSX menu with Ctrl+F9 (key command I set for GSX as to not interfere with UTLive key commands)
At this point, GSX has fully loaded along with P3D and GSX has imported/replaced all standard FSX gates with default GSX SODE gates, however some are still showing black gate numbers)
Selected "Customize this parking location" from the GSX menu
Selected all gates with /J using the button at the top left of the gate editor screen and selected to change them all to a different type of gate with bridge and gate numbers
Clicked Apply
GSX started replacing gates, but even after a 5 minute wait, some gates did not change from default GSX SODE gates to the newly selected ones and still some had black gate numbers
P3D had not froze at that point so I tried to enter the customize mode by selecting the gate I was loaded into (403) and clicked "Customize Parking" from the editor screen, where GSX loaded the customization mode placing the sim into SLEW mode, as it should.
Noticed the jetway at the spot I was editing disconnected from the jetway additional options (AC unit, elec plug, etc) and the gate was then rotated facing away from the aircraft (90 degrees from the location it should have been with head facing opposite direction) but the ground markings and jetway additions were still where they should have been.
I moved the parking position back slightly to test if controls were still working, and the parking spot moved. Moving the Jetway moved the unit, marking, and addons but while still 90 degrees misaligned.
I pushed "Y" to exit SLEW/Edit mode and P3D immediately became unresponsive and was forced to shut down. The GSX gate editor screen remained open and functional between P3D freezing and when I shut it down using ctrl+alt+delete (verified while in there that no other programs were running other than those listed with the 4th screenshot. Couatl.exe*32 was showing as running in the "Processes" tab, but not using any CPU at that time, however after P3D was forced shut down, Couatl.exe*32 began using CPU without GSX or P3D running, using about 20-25% of the CPU usage (out of 28-30% usage for the entire computer usage)
Below are the screenshots:
https://prnt.sc/l2aylo - in Edit mode with jetway disconnected from the ground makings, additions, and rotated 90 degrees and facing away from aircraft
https://prnt.sc/l2aywl - GSX gate edit screen showing gate Number is still not generating correctly, and jetway /jetway options selected for all gates with /J.
https://prnt.sc/l2az3f - Top title bar of P3D now shows as "Not Responding" immediately after exiting Edit/SLEW mode
https://prnt.sc/l2aza1 - showing P3D not responding, no other programs running with P3D aside from GSX gate editor and GSX Control Panel (Firefox opened to post the thread and see screenshots). Also, notice in the upper right corner of this image that the gate did not change from the GSX default SODE jetway.
2 things tested but faild to yield results: Graphics Driver reinstalled using Custom Clean install and ability to edit parking position/jetway positions with no other addons running.
Windows Event Viewer did not generate a critical error, but did see it as an "Application hang" ... here is the report from Event Viewer:
The program Prepar3D.exe version 4.1.7.22841 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: e70
Start Time: 01d45c29e32d6874
Termination Time: 380
Application Path: C:\Users\Steven\Desktop\P3Dv4\Prepar3D.exe
Report Id: 1c582dbd-c81f-11e8-9952-d43d7e4c88bd
What's interesting in this report, it that it sees P3D as version 4.1.7.22841, where as the windows control panel of installed programs shows P3D installed as 4.3.29.25520
Perhaps this has something to do with the issues?
screenshot attached - From within P3D Help/About menu showing P3D V 4.1 installed
http://prntscr.com/l2bf02 - Windows control panel showing P3D V4.3 installed
Since all of my addons are stored outside P3D main folder, I will try to uninstall P3D and reinstall and then verify addons working including GSX. It seems to me that there is something that didn't happen correctly with the P3D update to 4.3 (I knew I should have stayed with 4.1(
). I'll see if that fixes anything and if P3d shows that it is actually 4.3 now. Also, notice in the last screenshot that Simconnect is still reading as 4.1, but P3D 4.2 installed simconnect 4.2 as I've seen from other users. I'm leaning more toward this is an issue/conflict with P3D update and simconnect rather than a GSX issue.