Engine doesn't start

[Gunn]

When I follow the Milviz startup video or the startup procedures in the manual, the engine doesn't start. I only hear a click and 2 red lights blink.
When I select 'ready to fly' in MVAMS, the engine is started and I can fly it but the red and yellow warning lights are on and I have no fuel or oil flow on the gauges.
A simconnect problem? I reinstalled it. (All my A2A airplanes work fine).
I started P3D as administrator and with and without the dll.xml and exe.xml files for possible conflicts with add-ons.

Configuration: Prepar3D v3.4 (3.4.22.19868), Windows 10 Pro x64

Gunther

[SkyHawk024]

I also noticed from cold start with a auto start command ctrl+e the manifold pressure stays at zero, have you noticed that as well?

[Simondix]

Yes I have noticed the problem with the MP Gauge.

[Gunn]

Indeed, no manifold pressure, fuel and oil flow with MVAMS to 'ready to fly' or ctrl+e. And not possible to start the engine.
(Fuel & oil warning lamps are on to confirm the oil and fuel pressure problems.)

[Tobus]

Same problem here, FSX:SE

unable to start except for ctrl-e.
Gauges MP, oil temp, oil press and fuel press stay 0, indicator lights on.

[ojsron1948]

same here

[ncooper]

Hello,
I can't replicate this in FSX Acceleration.
I have selected the "Cold and Dark" option and the engine will start with either
the correct procedure or with CTRL+E.
If I use CTRL+E, several switches remain off but there is manifold pressure, oil
pressure and fuel pressure.
All the other gauges work just as they should and the switches can be quickly turned on.

I wonder if there is something saved in the default flight, if you have a custom one,
that is preventing the correct operation.
In FSX, I use the default Cessna with everything off except the fuel switch.
Perhaps create a flight with the Cessna in that state, save it as the default flight
and try again.
It might get you going.

I have copied this from elsewhere in the hope that it might be useful.

It allows you to configure start-up one of three ways: A) Cold and Dark, always, regardless of how your previous flight may of been saved. B) Ready to Start, which means that it doesn't start running, but switches & battery are on. Again, this is regardless of how your previous flight may of been saved. C) Ready to Fly. This isn't quite an 'engines running' scenario - what this does is it simply loads the aircraft according to how your previous flight was saved, or how your previous aircraft load state was (as in, if you're in a running aircraft, and you switch to the Beaver, it'll stay running).

Regards,
Nick

[kaosfere]

I am seeing this as well in P3D 3.4 -- can't start manually, I get one turn of the starter then it freezes. Auto-start works, but as soon as you're running the MP starts drifting down to 0. This is even with a "basic" default flight with the standard Cub.

[Chuck Jodry]

Important Elements , Fuel pressure must be over 5 psi , the Engine must be primed , its on the floor left front seat , three times is enough ,mags on . Remember > have mixture set rich and

When very cold the battery life is short and you may well kill it before getting started , use the Cold cover and heater to get things warmed up first .

Best CJ

Tested In P3D and FSX

[Taguilo]

Hi,
Those issues you are reporting are most likely because of Xmtools not properly installed. Could you please check that XMLTools.dll (FSX) or XMLTools3D.dll is present in FSX/P3D main folder?
Besides, could you please tell which gps variante are you using?

Thanks

Tom Aguilo
Beaver Systems Programmer

[Gunn]

On my system in %AppData%\Lockheed Martin\Prepar3D v3\dll.xml
The XMLTools3D section had <Disabled>True</Disabled>. I set it to False and everything is working now. (startup & ready to fly)
Thanks!

[Simondix]

XMLTools.dll installed in my main folder and I am using the Milviz 530/430 GPS.

[Simondix]

Further to my previous post I tried the No GPS version and there is no difference. I am using Steam.

[kaosfere]

Hi,
Those issues you are reporting are most likely because of Xmtools not properly installed. Could you please check that XMLTools.dll (FSX) or XMLTools3D.dll is present in FSX/P3D main folder?

That was exactly the problem! I'd already had XMLTools installed, but I routinely disable in my DLL config any libraries that I'm not using. And this was one of them. I re-enabled XMLTools and everything works a charm!

[Simondix]

Quite correct when loading XML tools it had set it up in an FSX folder in Appdata. Copied that and put it in the FSX-SE folder and all is working fine. Thanks everybody who helped.