Author Topic: [Resolved] PMDG737 pushback problem when APU software bug strikes.  (Read 1572 times)

Ray Proudfoot

  • Sr. Member
  • ****
  • Posts: 485
    • Cheadle Hulme Weather
Hi Umberto. I have the PMDG737NGXu in P3D v5.3HF2. When the APU fires up all is well and I start the engines when prompted. The pushback completes as normal.

You may be aware there is a bug in the PMDG code that has never been fixed because it’s so random. When this happens there’s no APU power so I have to request the power truck at the gate to start the engines.

Whilst this gets them going I cannot request pushback with engines running. Is there any workaround you can suggest to request pushback with engines already running?

I also have FSL Concorde which has no APU so engines 2 and 3 gave to be started before pushback but this is catered for in GSX.
« Last Edit: April 21, 2024, 12:31:46 pm by Ray Proudfoot »
Cheers,
Ray.

P3Dv5.3HF2, i9-13900K @ 5.5Ghz, RTX4090, 32Gb RAM, 4Tb Crucial T700 NVMe SSD, BenQ 32” 30Hz monitor at 3840*2160 with VSync.

Captain Kevin

  • Beta tester
  • Hero Member
  • *****
  • Posts: 1872
  • Captain Kevin
    • Captain Kevin
Re: PMDG737 pushback problem when APU software bug strikes.
« Reply #1 on: April 20, 2024, 03:02:24 am »
Ray, there should be a setting in the aircraft profile that allows you to start the engines before pushback, so just a matter of changing it. It's also useful in case you need to start the engines at the gate because of an inoperative APU.
Captain Kevin

Ray Proudfoot

  • Sr. Member
  • ****
  • Posts: 485
    • Cheadle Hulme Weather
Re: PMDG737 pushback problem when APU software bug strikes.
« Reply #2 on: April 20, 2024, 09:37:35 am »
Ray, there should be a setting in the aircraft profile that allows you to start the engines before pushback, so just a matter of changing it. It's also useful in case you need to start the engines at the gate because of an inoperative APU.

Kev, but would that change the whole pushback procedure where I have to start engines before pushback irrespective of the APU state?
Cheers,
Ray.

P3Dv5.3HF2, i9-13900K @ 5.5Ghz, RTX4090, 32Gb RAM, 4Tb Crucial T700 NVMe SSD, BenQ 32” 30Hz monitor at 3840*2160 with VSync.

Captain Kevin

  • Beta tester
  • Hero Member
  • *****
  • Posts: 1872
  • Captain Kevin
    • Captain Kevin
Re: PMDG737 pushback problem when APU software bug strikes.
« Reply #3 on: April 20, 2024, 02:04:44 pm »
Kev, but would that change the whole pushback procedure where I have to start engines before pushback irrespective of the APU state?
It shouldn't, or at least I haven't had that issue. The only thing I can suggest is try it and find out. I was fairly certain this was in the GSX settings somewhere, but Umberto had corrected me saying it was in the aircraft profile the last time somebody had asked.
Captain Kevin

Ray Proudfoot

  • Sr. Member
  • ****
  • Posts: 485
    • Cheadle Hulme Weather
Re: PMDG737 pushback problem when APU software bug strikes.
« Reply #4 on: April 20, 2024, 02:38:46 pm »
It shouldn't, or at least I haven't had that issue. The only thing I can suggest is try it and find out. I was fairly certain this was in the GSX settings somewhere, but Umberto had corrected me saying it was in the aircraft profile the last time somebody had asked.

It's an option in Customise Aircraft. If checked the user is asked if they would like to start at least one engine. So optional. Sounds like a good solution. I shall try it this weekend.
Cheers,
Ray.

P3Dv5.3HF2, i9-13900K @ 5.5Ghz, RTX4090, 32Gb RAM, 4Tb Crucial T700 NVMe SSD, BenQ 32” 30Hz monitor at 3840*2160 with VSync.

Ray Proudfoot

  • Sr. Member
  • ****
  • Posts: 485
    • Cheadle Hulme Weather
Re: [Resolved] PMDG737 pushback problem when APU software bug strikes.
« Reply #5 on: April 21, 2024, 12:31:08 pm »
@Captain Kevin,

That option works, thanks! Sod's Law meant the APU started okay but when it doesn't I now have a good alternative.  ;D
Cheers,
Ray.

P3Dv5.3HF2, i9-13900K @ 5.5Ghz, RTX4090, 32Gb RAM, 4Tb Crucial T700 NVMe SSD, BenQ 32” 30Hz monitor at 3840*2160 with VSync.