I have reproduced the exact sequence of events that cause the overwing exits to open. I would love to supply a support log which I enabled in game. But when I looked for the log it was not in the location that the manual specifies, and when I opened MSFS to click on the open folder in troubleshooting, or course it over wrote the log I had created with all of its insights. I later found it in the my user name\APPDATA \ROAMING\ VIRTUALI folder.
Airport: KORD for MSFS Gate B 20
Aircraft PMDG 737 800
Exclude Third Party enabled
Loaded custom short turnaround panel with APU running in cockpit but nothing else done on FMC
First Officers FMC not touched
Call for catering:
Right rear door stays closed
Right front door opens
All Other doors remain closed
Catering progresses to both doors, despite one being closed.
ends, trucks depart
right front door closes so all are closed after catering
Call for boarding:
No confirmation of passenger count (Estimate passenger count automatically unchecked)
Jetway connects to left front passenger door which opens
Left rear passenger door remains closed.
Front and rear cargo doors open
No passenger boarding chatter
Boarding ends and luggage loading ends
All open doors remain open
Call for pushback:
Jetway pulls back
Front left passenger door closes
Cargo doors remain open
Hear “inserting bypass pin”
Cargo doors close
Left overwing doors open and remain open through pushback
Note that if one instead sets everthing up and executes Call for boarding first and all the events happen automatically, the left overwing doors do not open at any point, but only the front right passenger door opens for catering, and only the front cargo door opens for luggage loading. Both the front and back passenger doors open for boarding, but no stairs appear on the rear.
There does not seem to be consistency here and it appears door openings and closing depend on whether one starts with calling for boarding at the gate or whether one individually calls the services.