One thing I've seen is that if you reposition a PMDG acft on the field (e.g. with GSX) with the parking brakes set, it'll overheat the brakes and blow the fuse plugs as if you'd taxiied there with locked brakes, giving you flat tires.  The red-glowing wheels are a dead giveaway when this happens.

Also, check in the ground services menu in the FMC to ensure that somehow you or an addon didn't accidentally set the wheel chocks.

If you're running FSUIPC, you can use the logging feature to look at the brake axis values (offsets 0BC4 and 0BC6 as 16-bit unsigned integers) to tell if something is making a brake input.

 

35 minutes ago, w6kd said:

One thing I've seen is that if you reposition a PMDG acft on the field (e.g. with GSX) with the parking brakes set, it'll overheat the brakes and blow the fuse plugs as if you'd taxiied there with locked brakes, giving you flat tires.  The red-glowing wheels are a dead giveaway when this happens.

Also, check in the ground services menu in the FMC to ensure that somehow you or an addon didn't accidentally set the wheel chocks.

If you're running FSUIPC, you can use the logging feature to look at the brake axis values (offsets 0BC4 and 0BC6 as 16-bit unsigned integers) to tell if something is making a brake input.

 

Thanks Bob,

I don't reposition usually, the position is as set in P3D menu. I have not noticed red hot wheels, so don't think that is a problem. Ground services: I have had the connection menu open when this happens and the chocks are shown as removed.

I like your suggestion of FSUIPC logging. I have set this up and will see next flight what shows up.

In the meantime, I will try removing all my PMDG planes completely and re- install them, to see if that clears some weird error/corruption.

6 hours ago, w6kd said:

One thing I've seen is that if you reposition a PMDG acft on the field (e.g. with GSX) with the parking brakes set, it'll overheat the brakes and blow the fuse plugs as if you'd taxiied there with locked brakes, giving you flat tires.  The red-glowing wheels are a dead giveaway when this happens.

Also, check in the ground services menu in the FMC to ensure that somehow you or an addon didn't accidentally set the wheel chocks.

If you're running FSUIPC, you can use the logging feature to look at the brake axis values (offsets 0BC4 and 0BC6 as 16-bit unsigned integers) to tell if something is making a brake input.

 

Mice idea buy I actually thought of that and it was  not the reason. I actually flew in, brakes normal, refiled for next destination and pushed back normally.  The. The issue showed up. I personally think somehow the PMDG software and the interaction with GSX makes it think it is still hooked up to the tug when its not. But I am not even bothering to tell PMDG/FSDT as each will say it's the others issue and nothing will get done.

On 2/17/2021 at 9:56 AM, IanHarrison said:

Thanks Bob,

I don't reposition usually, the position is as set in P3D menu. I have not noticed red hot wheels, so don't think that is a problem. Ground services: I have had the connection menu open when this happens and the chocks are shown as removed.

I like your suggestion of FSUIPC logging. I have set this up and will see next flight what shows up.

In the meantime, I will try removing all my PMDG planes completely and re- install them, to see if that clears some weird error/corruption.

Failure. No brakes operating according to the FSUIUPC logging. Re-install does nothing. And just to cap it all PMDG say not their problem (seems they are not talking to FSDT due to some dispute?)

Ian,

Was this from the Cold and Dark panel state or some other PMDG or custom panel state?

Also if the joystick is your only controller (ie. no other controllers causing axis binding conflicts), perhaps remove the joystick from the USB port and plug it into a different one.

You dont have any toe brakes configured do you by chance?

 

29 minutes ago, aldridgem said:

Ian,

Was this from the Cold and Dark panel state or some other PMDG or custom panel state?

Also if the joystick is your only controller (ie. no other controllers causing axis binding conflicts), perhaps remove the joystick from the USB port and plug it into a different one.

You dont have any toe brakes configured do you by chance?

 

Yes, C & D.

Only joystick, no toe brakes.

Will try another USB, can't hurt!

I have completely removed and reinstalled the QOTS II and no difference, so is not a faulty install.

31 minutes ago, aldridgem said:

Ian,

Was this from the Cold and Dark panel state or some other PMDG or custom panel state?

Also if the joystick is your only controller (ie. no other controllers causing axis binding conflicts), perhaps remove the joystick from the USB port and plug it into a different one.

You dont have any toe brakes configured do you by chance?

 

It's none of this.  Again,  when it happened to me, it was in the second leg with panel fully up and running. I'm pretty  confident it is a bug in GSX. But like posted above, PMDG and FSDT don't communicate much if at all.  Hence why we have GSX integrated into the FSL Airbus and PMDG has none of that. One of many reasons I've uninstalled the NGXu and solely fly the FSL stuff for my narrowbody flying. 

5 minutes ago, B777ER said:

It's none of this.  Again,  when it happened to me, it was in the second leg with panel fully up and running. I'm pretty  confident it is a bug in GSX. But like posted above, PMDG and FSDT don't communicate much if at all.  Hence why we have GSX integrated into the FSL Airbus and PMDG has none of that. One of many reasons I've uninstalled the NGXu and solely fly the FSL stuff for my narrowbody flying. 

Umberto  of FSDT sent me a quite detailed description of how it works and I really don't think it is their problem at all. PMDG seem to have a problem with FSDT and don't have GSX on any of their computers to even test compatibility. So draw your own conclusions.

Two other things I'd consider trying are to cycle in/out of slew mode, and perhaps briefly engage the PMDG pushback in the FMC and push a few feet straight back and see if that changes anything.

Fortunately, I've never seen this problem here, so all I can do is make some educated guesses.

I am not putting the flags out just yet BUT a quick test tonight (with the joystick plugged into another port), has resulted in a plane that moves after disconnecting from the pushback vehicle.

I will do a proper flight tomorrow with full pre-flight GSX and then report back.

Thanks for all the suggestions.

Let's just hope that it was an OS problem (Windows update?)

Ian

Just now, IanHarrison said:

I am not putting the flags out just yet BUT a quick test tonight (with the joystick plugged into another port), has resulted in a plane that moves after disconnecting from the pushback vehicle.

I will do a proper flight tomorrow with full pre-flight GSX and then report back.

Thanks for all the suggestions.

Let's just hope that it was an OS problem (Windows update?)

Ian

This points back to what I said originally in terms of joystick calibration.  Do you ONLY have brakes mapped to a keyboard command?  Have you gone through every device connected to ensure nothing has the brakes bound to a button?    When I have seen this it is quickly and easily fixed by going in and re-calibrating the brakes. What is your brake assignment?

7 minutes ago, psolk said:

This points back to what I said originally in terms of joystick calibration.  Do you ONLY have brakes mapped to a keyboard command?  Have you gone through every device connected to ensure nothing has the brakes bound to a button?    When I have seen this it is quickly and easily fixed by going in and re-calibrating the brakes. What is your brake assignment?

Brakes only mapped to Joystick "fire" trigger , Button 1 and on the keyboard only the standard ctrl + . (Full stop)

Nothing has ever been bound to any other button regarding brakes.

2 hours ago, IanHarrison said:

Umberto  of FSDT sent me a quite detailed description of how it works and I really don't think it is their problem at all. PMDG seem to have a problem with FSDT and don't have GSX on any of their computers to even test compatibility. So draw your own conclusions.

I actually believe this statement. PMDG tend to be quite arrogant at times with some elitist attitudes (Kyle Rogers who moderated their forums was infamous for his arrogance). I would not surprise me in the least that PMDG couldn't bother to assist the end user by collaborating with FSDT and trying to resolve this issue instead of adopting the stance of, not our problem,  don't use GSX.

21 minutes ago, B777ER said:

I actually believe this statement. PMDG tend to be quite arrogant at times with some elitist attitudes (Kyle Rogers who moderated their forums was infamous for his arrogance). I would not surprise me in the least that PMDG couldn't bother to assist the end user by collaborating with FSDT and trying to resolve this issue instead of adopting the stance of, not our problem,  don't use GSX.

To be fair, I get this with the QW787 pretty randomly as that's my go to AC and it has the same issue...    I would actually start by removing the trigger button mapping next time it happens and see if the plane starts to taxi...   Just to rule it out.  

I've expereinced this on occasions. Never discovered the reason why, but it seems to always clear itself after a restart.