Hi,

Just about ready to throw in the towel! Yesterday I get some BS crash while taxing out after spending 45 minutes getting the flight setup. Today another 40 odd minutes setting up the ride and the reversers don't work right (worked fine for the last few flight - nothing changed), wanted to back out on my own power don't like the tug and with good reason!!!

So forced to use the tug, get done with pushback and now the aircraft won't budge! complete waste of time!

Jump to 32:00 into the video to see the entire mess!

 

The gods are not being kind to you!

I watched your video yesterday, of the invisible crash.  The only thing I could think of was a possible problem with the airport scenery you were using.  Was it custom?   I have had similar collisions with airports that were made for MS2020 and used in MS2024.   The ground resolution is much higher in 2024 and that includes at airports.   I have some 2020 airports in 2024 that have crazy gradients between the apron and the runway, or that have some chunks of ground sticking through the tarmac.

About the problem today - would it not have been worth changing to the external view, to see if there was a pushback truck or anything visible still attached to the aircraft?  I noticed you were changing from the Home Cockpit to the VC view, but you didn't check the external view to see if there was any evidence if an issue there.

Edited January 12Jan 12 by JYW

15 minutes ago, JYW said:

The gods are not being kind to you!

I watched your video yesterday, of the invisible crash.  The only thing I could think of was a possible problem with the airport scenery you were using.  Was it custom?   I have had similar collisions with airports that were made for MS2020 and used in MS2024.   The ground resolution is much higher in 2024 and that includes at airports.   I have some 2020 airports in 2024 that have crazy gradients between the apron and the runway, or that have some chunks of ground sticking through the tarmac.

About the problem today - would it not have been worth changing to the external view, to see if there was a pushback truck or anything visible still attached to the aircraft?  I noticed you were changing from the Home Cockpit to the VC view, but you didn't check the external view to see if there was any evidence if an issue there.

All default airports, I keep it as clean as I can. Extra stuff introduces stutters/flickers over time. When I went out before exiting you could see no tug. Think I'll start all my flights in 2024 facing away from the gate, no tug and they will have to use the air stairs.

2024 airports have the same crazy gradients. Today's departure airport for instance, it's default 2024 and the hills and valleys are very big. 

Edited January 12Jan 12 by Mike_CFII_MEL

The tug is rubbish, so I have removed it for all of my PMDG planes.

You only use default airports with that setup? I guess that running all of that takes a considerable amount of power, but the thought of seeing something like a Pyreegue airport from your cockpit makes me drool uncontrollably!!

Sorry, I haven't watched the video so not sure if this is applicable but I have had similar occasional issues with MFS2020 when using third party pushback tools that I couldn't taxi after pushback. Sometime you also need to "contact" the built-in ATC ground to release the tug.

Sounds like brake or parking brake getting stuck on … I’d look at hardware connectivity in the FlightDeck Solutions side … sounds very much like a loose or damaged wire and/or circuit board.  I think FlightDeck Solutions provide a diagnostic module you can run to put the hardware thru it’s paces?

Complex bit-o-kit you have there, so just like real aircraft, it needs regular maintenance … or just an INOP sticker 😉 

Hi @Mike_CFII_MEL

Well - other than my rig is a 'bit' more modest than yours (ie just a Honeycomb Alpha and Bravo set up 😁 ) - this is pretty much a carbon copy of stuff I've wasted a week on.

It wasn't just the PMDG737-800 - it was ALL of my Airbus's too.

With the PMDG it was the pushback and then, being in a clear parking area, trying to just move forwards without pushback and EXACTLY the same stuff happened.  Everything said it was OK, the engines spooled up - but it wouldn't budge.

I tried the 'false chocks/parking brake command delete fix' learned when similar stuff that happened when SU3 was introduced (In my case, 5 spurious Park Brake commands had been silently added across 3 HOTAS units) but, in SU4 there were no spurious Park Brake commands on any HOTAS item.

With the Airbus aircraft it was that the engines simply wouldn't spool up - whether starting cold and dark, or at a runway, or with State set to 'Ready/Take Off'

I have eventually sorted it.  PMDG Support said 'Delete ALL of your Hotas settings - even the ones that look right and set them up from scratch'

I had already checked my HOTAS commands and they had looked OK but, out of other ideas, I did that and the PMDG then worked fine!!  I then switched each HOTAS units back on one-by-one and, in my case, found it was the Honeycomb Alpha Yoke that was causing the issues  

I then checked my Airbus controls commands and they also looked OK.  Here it was throttle response that was the problem - the thrust levers moved but the idling engines wouldn't spool up.   Hmmm...but on the PMDG, it had been the yoke, not the throttles that had been changed.  But what the heck - so I switched the yoke settings for the PMDG738 to the Airbus...and the throttles on the Bravo unit (unchanged) now spooled the engines up!!!!

 

So my conclusions:

- The cause and solution makes no sense

but

- it is clear that SU4 - for some of us - has added some spurious, random and, in some cases, invisible commands to our controller settings

 

In my case, moving all my aircraft to clean Honeycomb Alpha settings has got me back to being able to taxi and fly the 738 AND all of the Airbus models that were stuck (Inibuilds A340, Fenix A320, Stock A320 Neo V2, Stock Airbus Transporter).  

Edited January 13Jan 13 by AJZip2

10 minutes ago, AJZip2 said:

In my case

yep, remember that it was your post that I had in mind when mentioning it above

 

51 minutes ago, AJZip2 said:

Hi @Mike_CFII_MEL

Well - other than my rig is a 'bit' more modest than yours (ie just a Honeycomb Alpha and Bravo set up 😁 ) - this is pretty much a carbon copy of stuff I've wasted a week on.

It wasn't just the PMDG737-800 - it was ALL of my Airbus's too.

With the PMDG it was the pushback and then, being in a clear parking area, trying to just move forwards without pushback and EXACTLY the same stuff happened.  Everything said it was OK, the engines spooled up - but it wouldn't budge.

I tried the 'false chocks/parking brake command delete fix' learned when similar stuff that happened when SU3 was introduced (In my case, 5 spurious Park Brake commands had been silently added across 3 HOTAS units) but, in SU4 there were no spurious Park Brake commands on any HOTAS item.

With the Airbus aircraft it was that the engines simply wouldn't spool up - whether starting cold and dark, or at a runway, or with State set to 'Ready/Take Off'

I have eventually sorted it.  PMDG Support said 'Delete ALL of your Hotas settings - even the ones that look right and set them up from scratch'

I had already checked my HOTAS commands and they had looked OK but, out of other ideas, I did that and the PMDG then worked fine!!  I then switched each HOTAS units back on one-by-one and, in my case, found it was the Honeycomb Alpha Yoke that was causing the issues  

I then checked my Airbus controls commands and they also looked OK.  Here it was throttle response that was the problem - the thrust levers moved but the idling engines wouldn't spool up.   Hmmm...but on the PMDG, it had been the yoke, not the throttles that had been changed.  But what the heck - so I switched the yoke settings for the PMDG738 to the Airbus...and the throttles on the Bravo unit (unchanged) now spooled the engines up!!!!

 

So my conclusions:

- The cause and solution makes no sense

but

- it is clear that SU4 - for some of us - has added some spurious, random and, in some cases, invisible commands to our controller settings

 

In my case, moving all my aircraft to clean Honeycomb Alpha settings has got me back to being able to taxi and fly the 738 AND all of the Airbus models that were stuck (Inibuilds A340, Fenix A320, Stock A320 Neo V2, Stock Airbus Transporter).  

I try and push everything through FSUIPC7 as far as the throttle quad, yoke, rudder and tiller, I keep 2024 clean of any controls.

1 hour ago, Mike_CFII_MEL said:

I try and push everything through FSUIPC7 as far as the throttle quad, yoke, rudder and tiller, I keep 2024 clean of any controls.

OK  - another quirk somewhere else, then.  Hope you are able to bottom it soon   

5 hours ago, AJZip2 said:

- it is clear that SU4 - for some of us - has added some spurious, random and, in some cases, invisible commands to our controller settings

I've been having all sorts of weird issues for a while now, all post SU4. GSX not showing in the menu bar, even though it is apparently installed and correctly set up according to its own installer. Issues with the PMDG 738 - if I terminate a flight (esc/end flight) the sim freezes. Random misbehaviour with the CSS 737-500. Plus disappearing control profiles and spurious key allocations to some buttons. Plus a couple of missing City Updates (a confirmed SU4 error on the official site).

It all got so bad I've just gone through a complete re-install of 2024, first time I've ever felt the need to do that with either 2020 or 2024. So now I've got all the fun of getting everything back how I want it, and I'm already feeling that it may not have resolved all the issues. GSX is working now, the control profiles have settled down, but some of the other stuff is still happening.

On one level, MSFS2024 is the most wonderful thing I've ever seen, sim-wise, but on another level it's also the most loathsome and appalling pile of **** I've ever used. I've spent way more time fiddling with the cursed thing than actually flying it for a couple of weeks now.

(but I will say the re-install was of itself surprisingly painless - all done and dusted in just a few minutes. Helped by a fair bit of precautionary backing up and the fact that I use the addons linker, but even so - impressive)

@andy1252  I should have added that I did a full reinstall as my first action.  It didn't make any difference.

I should add, as you also make a nod to, that - once I'd gone through the lost week of confusion and frustration to finally correct it all - it is the best sim I have ever used.

 But, at times during that week, for two hoots I might have abandoned it...

FWIW I just had a similar situation as the OP (not having watched his video though) where starting at gate and the plane did not move. used the pushback through MSFS24 and it barely pushed the 738, it creeped forward. once untugged though I applied thrust and the ac did not move an inch. checked chocks off, also MSFS tug off. still no move. then I checked the FMC menue and - well - under FS Actions --> Pushback THAT truck was connected. So disabled that and all fine. happily airborn now.