Products Support > GSX Support FSX/P3D

Cannot open the GSX menu from Add-ons in P3D v5.3 (Windows 10) **SOLVED**

<< < (3/5) > >>

jsmcwilliam:
" custom GSX profile"
I am unsure whate you mean by the above term. Previously I had exclusion files for both EKCH and ESSA but since I reinstalled GSX they no longer exist - I think. See Couatl1.jpg. I know that no such file was created for ENBR so I repeated the above test with my Q400 at this airport (Couatl.log3.txt). Please let me know if I have misunderstood your instructions

"simulator crashed"
Again I am unsure as to the meaning of this. For me the sim does not crash and I can go ahead and fly as planned. I just am unable to gain access to the GSX menu.

virtuali:

--- Quote from: jsmcwilliam on April 18, 2022, 05:10:25 pm ---I am unsure whate you mean by the above term
--- End quote ---

A custom profile is created in your %APPDATA%\Virtuali\GSX folder each time you change something using the GSX editor, like a custom pushback route, or a change in the vehicles starting positions, or a change in the preferred operator. Have a look at your log, it shows the name and the path of your customization file.


--- Quote ---Again I am unsure as to the meaning of this. For me the sim does not crash and I can go ahead and fly as planned. I just am unable to gain access to the GSX menu
--- End quote ---

Well, if you are sure the sim didn't crash on that session, it means that for some reason the connection between GSX and the sim was interrupted. Strictly speaking, GSX is not trying to understand if the sim *really* crashed, but only if the communication with it stopped, which from its point of view is the same, is the sim stopped talking to us, it might as well crashed, the end result it's the same: GSX cannot work with a sim that stopped talking to it. That's why there's a question mark on the log message:

"Connection with Prepar3D v5 lost (has it crashed?)"

So, perhaps it didn't crash, but it surely had an issue with communication. This might be a DIFFERENT issue to the one I'm still waiting for a report with a log made without a custom profile, the Simconnect communication might be interrupted for one of these reasons:

- The sim crashed. Ok, you said it hasn't, so we might skip this

- The antivirus/firewall is blocking communication between the sim and the app, because it might be seen as potentially dangerous ( it obviously isn't, but there's no end of how bugged antivirus are. In some cases, they are seen as internal networking activity, because it can run on TCP/IP as well, depending on the configuration )

- Another add-on is doing something wrong with Simconnect, causing to fail, for example spamming it with too many commands in too few time, so the sim cannot keep up with all the requests, and it drops communication with GSX, which detects it as a possible crash, even if it isn't. We have seen this with 3rd party weather engines, camera utilities, etc.

You keep mentioning the Q400. Does this mean you have these issues with only that airplane, or it's the only one you tested ? Is it any different with another airplane ?

jsmcwilliam:
You must be patient with a user who has limited understanding of the software we are trying to run. Since reinstalling GSX I have not used the editor. The files in the GSX folder mentioned above are shown in Couatl2.jpg My previous log was generated when at ENBR and as far as I can see there is no custom profile (? *.ini).

On the subject of crashes I did the following:
- turned virus protection off.
-started the sim and placed the Mooney Bravo at the default KRND -active runway.
-did not start EZCA since you seem suspicious of it's affect on things.
-tried to open the GSX menu using both methods but did not get any responce (not even the black window).
- Exit sim.

My SimConnection is v 10.0.61259

virtuali:

--- Quote from: jsmcwilliam on April 19, 2022, 12:22:52 pm --- Since reinstalling GSX I have not used the editor.
--- End quote ---

That doesn't matter, uninstalling/reinstalling GSX will never remove your stuff!


--- Quote ---My SimConnection is v 10.0.61259
--- End quote ---

How did you check for this version ? This is the FSX version, which we don't use and it this is the only Simconnect you have in P3D, it explains why GSX doesn't work, since it requires the P3D version of Simconnect, and won't work without it. The P3D version should be 5.3.0.0 and it's supposed to be installed in the sim.

jsmcwilliam:
The plot thickens! I was asked some time ago by HiFi to install a simconnect.msi file on both my server and remote. Examination of the properties gave this version and it matched my EZCA equivalent. Since networking ASP3D and EFB work fine I assumed that this was the correct version. I ran a search for the simconnect.dll on my C and D drives (P3D v5.3 is on the D drive). As you can see there are a number of versions including some which are very old. Should I delete all but the LockheedMartin.Prepar3D.SimConnect.dll I don't know of coarse which of these are active but the FsIPanel probably is and I think EZCA has it's own version.

Navigation

[0] Message Index

[#] Next page

[*] Previous page