February 19, 20215 yr Ian, Let us know whether the problem is resolved or not after you had some more time to test. We are all curious. SpoilerSystem specs: MFG Crosswind pedals| ACE B747 yoke |Honeycomb Bravo throttleNow built: P3Dv5.3HF2: Intel i5-12600K @4.8Ghz | MSI Z690-A PRO | Asus Dual RTX 4070 Super OC 12Gb| 32Gb Corsair Vengeance LPX DDR4 3200Mhz |Samsung 980Evo Pro PCIe 500Gb | WD Black SN850 PCIe 2Tb | WD SA510 4Tb |beQuiet 802 Tower Case|Corsair RM850 PSU | Acer Predator X34P 3440x1440pMark AldridgeMSFS2024 SU5 & P3D v5.3 HF2
February 19, 20215 yr Author 8 minutes ago, aldridgem said: Ian, Let us know whether the problem is resolved or not after you had some more time to test. We are all curious. Fellow Simmers. Firstly, thank you for all the suggestions. Like most Computer "errors", the real reasons are buried in the depth of programming, which most of us don't understand. What I did was to delete and re-allocate the brakes assignment to the Joystick Button 1, change the Joystick USB to another port and check that there are no other conflicting bindings. (There aren't). All that has resulted in a plane which pushed back properly and disconnected properly and ...........wait for it.............Taxied properly. As I said, we will probably never know the real reason. Ian Intel i7 6700K @4.3. 32gb Gskill 3200 RAM. Z170x Gigabyte m/b. 28" LG HD monitor. Win 10 Home. 500g Samsung 960 as Windows home. 1 Gb Mushkin SSD for P3D. GTX 1080 8gb.
February 19, 20215 yr Good job Ian. Thanks for reporting back. I am glad you got it sorted in the end. Happy taxiing! 😉 SpoilerSystem specs: MFG Crosswind pedals| ACE B747 yoke |Honeycomb Bravo throttleNow built: P3Dv5.3HF2: Intel i5-12600K @4.8Ghz | MSI Z690-A PRO | Asus Dual RTX 4070 Super OC 12Gb| 32Gb Corsair Vengeance LPX DDR4 3200Mhz |Samsung 980Evo Pro PCIe 500Gb | WD Black SN850 PCIe 2Tb | WD SA510 4Tb |beQuiet 802 Tower Case|Corsair RM850 PSU | Acer Predator X34P 3440x1440pMark AldridgeMSFS2024 SU5 & P3D v5.3 HF2
February 20, 20215 yr I believe I saw this once. After push-back, the plane wouldn't move. When I added some thrust, the raindrops on the windshield would start flowing towards the aft of the plane, as if the plane were moving. I eventually switched to an outside view and saw the tug was still connected. I got rid of it, PROBABLY by resetting GSX (I don't remember 100 %), and everything was back to normal. Best regards, Dimitrios 9950X3D - 64 GB - RX 7900 XTX - TrackIR - Power-LC M39 WQHD - Honeycomb Alpha yoke, Saitek pedals & throttles in a crummy home-cockpit - MSFS for props, P3D for jets
March 3, 20215 yr Author A further bit of news. After a few weeks of trouble-free flying, the problem returned last week. The only thing that had updated was a further attempt by Windows to install the "feature update". I spent about 4 hours this morning trying different scenarios/combinations of actions and eventually came to the conclusion that it is the Controls and key binding menu config. that is the cause of the problem. The reason for this conclusion was that I changed the brakes button on the fly while the plane was stuck and no change. When I changed it when the plane was moving (after a shift+P pushback, not GSX) the nosewheel immediately locked in the left turn position and I had no control. After restoring all default controls, I painstakingly went through every one, removing all not used and updating to what I use. This has resulted in a plane that works with GSX as it should. I will now see if it continues to work and what might upset it again. Ian Intel i7 6700K @4.3. 32gb Gskill 3200 RAM. Z170x Gigabyte m/b. 28" LG HD monitor. Win 10 Home. 500g Samsung 960 as Windows home. 1 Gb Mushkin SSD for P3D. GTX 1080 8gb.
Archived
This topic is now archived and is closed to further replies.