Products Support > GSX Support FSX/P3D
Cannot open the GSX menu from Add-ons in P3D v5.3 (Windows 10) **SOLVED**
virtuali:
--- Quote from: jsmcwilliam on April 16, 2022, 03:58:41 pm ---I have checked this and cannot find any conflict. It should still be possible to open the GSX Window by clicking on the Add-ons list.
--- End quote ---
Sure, but not if the program is still regenerating the airport cache.
Please do it again without regenerating the cache, because if you do that, it will only confuse my troubleshooting, because seeing it in all of your logs looked as a problem, since the program is not supposed to do that every time, and it's not needed for normal operation, it's only needed when you *know* you added a scenery, but the change cannot be detected by GSX, but you would see an error message about not finding the AFCAD in that case. That's the only case in which you need to regenerate the cache manually.
jsmcwilliam:
These are my actions:
- openned sim and placed my Q400 at the ramp, EKCH (Fly Tampa scenery).
- GSX-Settings to check that the log function is on.
- Ctr/Shft/F12 produced the black window. If I leave it it disappears after about 10 secs. (Clicking on the menu produces the same
result.
- Exit P3D v5.3
I include screen shots of my settings for troublshooting, the black window and my Add-ons list
virtuali:
Can you try another airport, one without a GSX custom profile ? Maybe the problem is the GSX profile itself because, other than that, your log and your screenshots are showing GSX is working fine.
jsmcwilliam:
I have earlier tried ESSA, ENGM, ENBR. I enclose the log from my Orbx version of ESSA. I have placed my Q400 at ramp 147 and tried to open the GSX menu from the Add-ons list and then using Ctr/Shft/F12 (Couatl.log1.txt). This time no black window was generated.
I installed SODE 1.7 and ran a new test at ESSA (Couatl.log2.txt). The restult was the same!
virtuali:
Both of your logs are made on an airport that does have a custom GSX profile, while I asked to try on one that doesn't have one, because I'm trying to understand if the profile itself is the problem so, please, try to do what I asked, and go to an airport that hasn't been customized.
Or, just remove (or move away in a different folder ) your custom GSX profile, and try without one.
Other than that, now your logs still don't show any errors on GSX part, but they show the simulator crashed on its own for some reason, and GSX was able to detect that crash and logged it, likely before it was brought down by the crashing sim as well, because of the abrupt disconnection.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version