PMDG 737-800: pushback does not proceed, and a few other issues

[kakugo]

I recently bought the PMDG 737-800 and, after carefully reading the GSX manual's section on the PMDG integration, I had a few problems when I tried to use GSX:
1) calling the GPU via GSX did not produce any effect: I had to do it manually using the FMC
2) the pushback stops after telling GSX in which direction I want it: from that moment on, nothing else happens and the GSX menu only offers the option to interrupt yes/no, and to change direction. Restarting Couatl reproduced the same behaviour
3) after resorting to using the PMDG pullback, I noticed that the rear door had been left open.
I tried this twice, using different gates of LIMJ (BMW version) with a GSX profile from Flightsim.to.
I had created an aircraft state with all the PMDG services away, and I never closed GSX from the taskbar.
The "connect pushback on boarding" option is enabled.
I assume that I am doing something wrong due to my inexperience with the PMDG 737. Any suggestions? Thanks in advance.

[kakugo]

I managed to successfully run the GSX pusback after doing these two actions: remove the PMDG GPU and remove the chocks. Not sure which one was the blocking factor (or if they both were). It would be nice though if the PMDG integration in GSX took care of those automatically.

[Captain Kevin]

Yeah, you can't move the plane with the GPU still hooked up and the chocks in place.

[virtuali]

If you use the GSX menu correctly ( never close it from the Toolbar until after all services are ended ), you would have seen a tooltip message on screen from GSX indicating you had to remove the GPU and the Chocks to continue Pushback.  These are called "Pushback Constraints", and change by airplane, and are only included if the airplane has an internal GSX profile.

Another reason why you might have missed the message (other than having closed the menu with the Toolbar instead of the Hotkey), is having the Verbosity slider too low, so messages that are not errors would be skipped.

[kakugo]

It must have been the verbosity level, as I indeed had lowered it some time ago. Thanks!