Products Support > GSX Support FSX/P3D
GSX Menu takes me to wrong position SOLVED
elac1:
G'day Umberto and thanks for the response.
I checked both the actual scenery path in the simulator and the path that the GSX editor is using and they are the same so I am ruling out the suggestion that the AFCAD has been discarded.
It must be a conflict but prior to yesterday when I first noticed this anomaly, OTHH was working perfectly well with GSX both on departure and arrival.
Nothing has changed on my machine (except for the addition of an Audigy soundcard - which has caused issues with frames on some aircraft add-ons but that's neither here nor there).
Any suggestions as to where I might look for possible scenery conflicts?
Cheers,
Tony
wim2000:
Thanks Captain Kevin, Tony and Umberto
My problem is when I ask the GSX menu to bring me to a runway or to bring me to a parking spot. It happens on all airports (ORBX, Aerosoft etc). GSX puts the plane about 2 miles near the right spot. When I use the P3D menu (navigation> go to airport) every thing works fine
virtuali:
--- Quote from: elac1 on January 18, 2021, 10:33:27 pm ---I checked both the actual scenery path in the simulator and the path that the GSX editor is using and they are the same so I am ruling out the suggestion that the AFCAD has been discarded.
--- End quote ---
If GSX is using what looks like the correct AFCAD, and it positions the airplane in the wrong position ( and HOW wrong ? Just a few meters, or some miles, like the other user reported ? ), you should then check if using the simulator own Go To Airport command send you to the correct position or not.
virtuali:
--- Quote from: wim2000 on January 19, 2021, 11:03:53 am ---My problem is when I ask the GSX menu to bring me to a runway or to bring me to a parking spot. It happens on all airports (ORBX, Aerosoft etc). GSX puts the plane about 2 miles near the right spot.
--- End quote ---
2 miles away on every airport is not a problem of reading the wrong AFCAD, it most likely the usual problem of having one of your joysticks not calibrated, possibly a joystick you don't even use, but the sim has assigned some Slew axes to it, just because it's installed in Windows.
The solution is either fix the joystick null zones, or remove all joystick axes connected to the Slew events from that joystick.
wim2000:
Thanks very very much, My Saitek pedals caused the problem. I am really happy it is solved now
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version