Nope, the bleed isolation valve is open.
Strange thing is that the left engine is starting normally.
Do you have a multi-lever throttle quadrant with mixture controls? If an assigned mixture control (only used for piston engines) is not fully forward, it can prevent a PMDG 737 engine from starting.
Iâm afraid thatâs also not the case.
I also tried changing liveries (a lesson from the past) but that also didnât help. I even disabled all my add-ons, of course with the exception of the PMDG 737.
Silly question but any failures active?
Post a video. Just capture it with OBS and upload to youtube
@Gorony Fair question. It wouldnât be the first time I overlooked a setting I apparently changed. But in this case there are no failures active.
This might be a good idea. Iâll try to record the procedure Iâm following and post a link here.
Btw. If I choose âLoad settingsâ from the FMC panel and select âTaxi-stateâ both engines are at idle. So itâs possible to fly the 737 but (of course) less fun.
I followed the startup procedure âby the bookâ. (Thanks to Jonathan Beckett). This is the procedure that always worked for me.
Thanks so far and Iâll try to get back with a Youtube link later today.
Edit: My apologies. I assumed all the 3 pages would have been separately saved. I noticed only page 1 was uploaded 
Are the Packs set to off?
Air cross bleed between left and right side open?
Yeah, those are mostly nonsense. Just download an FCOM and find the chapter NP (normal procedures).
The only conditions for starting the engines (ignoring the rest of the preflight steps) is that you need power and air, both provided by the APU. Packs off, all bleeds on, isolation valve open. Start one engine at a time.
Start switch to GND â Look for 25%N2 â Engine start lever to idle â wait for starter cutout. Repeat on the other engine. ENG GEN on busses.
If that doesnât work then thereâs some corrupted file in your addon.
This playlist is by a former colleague and itâs done as per real life procedures. At first itâll take you 40 minutes to get the airplane ready. After some practice it shouldnât take more than 5-10.
            
No, theyâre set to âautoâ which might not be the correct setting but never caused the engine(s) not to start.
No, I âlearnedâ this activates the fuel flow from the side fuel-tanks? On short flights they donât have to be switched on. Forgive me for being an absolute amateur but so far I managed to switch both engines on without using the cross bleed. But in future flights Iâll make sure I switch-on the cross feed knob, thanks  .
 .
Thanks for the link to the Youtube video from A330 Driver (Emanuel). I always enjoy watching his videoâs and even try to learn a thing or two. I know he must have a tutorial about the Startup procedure of the PMDG 737 but I couldnât find it.
The video below describes the procedure as I follow it (for over a year). Fast-forward or skip to 20:40 min!!
Jonathan Beckett already states this procedure isnât 100% correct but mainly to minimize the necessary official steps.
Iâll try to record and post my own procedure later today.
Packs should be off. Otherwise theyâll steal duct pressure and in certain weather conditions the other engine will not start correctly. Thereâs a way to use the right pack after starting the right engine but thatâs a whole different story (Isolated pack operation). Just follow the real procedure on any of Emiâs videos. If you need something specific I can do a 5 minute video with full startup like youâd do in real life at speed.
Yeah. Just had a quick look. Donât follow that video. Itâs full of nonsense. There are enough real 737 pilots on youtube making straight to the point videos.
Thanks for you reply,
I gave it another try but this time with the packs âoffâ as recommended. I also watched Emanuelâs âTutorial 6: Pushback, Startup, Before Taxi Procedureâ.
I have dual monitors so itâs easy to watch Youtube on the right monitor while I run MSFS 2020 on the left side.
Even though I followed every step I still get stuck when I try to start the Right engine (left is no problem). I still hope Iâm making a mistake and there isnât a software problem.
Your more than welcome to show me a video with the âreal lifeâ procedures. And again, I hope this will point me to the procedure I didnât follow correctly.
Then at this point I think itâs safe to say that your procedure isnât the problem and you may have a problem with your controllers triggering mixture cutoff (from a piston airplane) or a corrupted panel state.
Try to make that video. OBS Studio is free and easy to use. Capture MSFSs window, upload to youtube and weâll have a look.
Unlikely this is related, but Iâll throw this out there (I posted about this several weeks ago here) :
At random times during my flight, the Left engine knob mysteriously gets flipped from AUTO to GND. I use Spad.Next, and I combed the profile XML file extensively to see if there is some control conflict, none found. I went as far as setting up an event on Spadâs Script Panel to have a voice alert whenever the control gets changed - âMicrosoft Davidâ simply says âGroundâ when it changes. The alert works, and gets triggered even when Iâm not touching any of my physical controls.
The plane flies just fine when the knob is stuck on GND, so Iâm not losing sleep over this (though the FAA might have a few things to say about this :-)) . I probably should put in a ticket at PMDG one of these days.
Just wonder if there is some spurious event that is affecting us both in different ways.
RE: FMS Pushback > COMMS > VOICE missing. From PMDG via Ticket:
âThis has been removed from the FMC as MSFS is not capable disaplying the text as P3D/FSX wasâ
As stated, the issue was due to Headphone Simulation set to ON.
Again from PMDG:
âthe Headset Simulation option does cause issues with sounds in the simulator so we recommend it be selected OFF in the introductory section of the manual for the 737.â
Note, they recommend it be turned off, but the docs donât state it will conflict with the pushback comms.
Cross BLEED and cross FEED are two different things. Youâre talking about cross feed, here.
Boeing calls the cross bleed the isolation valve. It needs to open to start engine two from the APU; the auto position is fine (and what we use in reality) because as long as the packs are turned off, the valve will be open.
Do note that the isolation valve is a 3 position switch. If you think youâve got it open, but youâve really only got it in auto (the middle position), AND you arenât in the habit of turning your packs off for start like you should, then the number two engine will not spin.
Packs off, isolation valve in auto or open.
Update from my question in post #19.
As requested I uploaded a Youtube video. My apologies for the brightness but YT canât handle HDR-10 very well.
AnywayâŠProbably Iâm not following the correct and / or official procedure. Main problem is that I canât start my Right-engine.
If any of my settings are wrong I would assume none of both engines would start.
I disabled (disconnected) my Yoke to be sure it isnât the cause of the problem.
@FormerSnail5736 I hope you can pinpoint the step(s) I overlooked.
@TheSevenflyer Thanks for your reply.
@SteveKane Iâve had similar problems in the past but those ware due to a faulty Livery.
@ everyone: Thanks for your help, appreciate it 
Iâm seeing a couple of things here. First, the normal procedure is to start engine 2 first. But the big things that are keeping engine 2 from starting are that you are closing the isolation valve rather than having it Open and leaving the packs in Auto rather than Off.
Iâm aware of that. It was only to show the Left-engine started up normally. Also shouldnât the closed isolation valves be preventing both engines from starting?
Thanks for pointing my out to the closed valve, Iâll keep it in mind in future flights.
The APU pressurizes the left bleed air duct, so even with the isolation valve closed, the left engine can be started.
The isolation valve being closed isnât just a tip or suggestion here - it is the literal answer to your problem.  Open that valve and the right engine can start (turn the packs off too.)
Remember, Boeing switches operate âbackwardsâ; up is off. Down (forward, in Boeingâs philosophy) is on.

 
  