There is no official fix. Did you try this? I quoted it from the post.

"It did happen every time unless I started the APU before I clicked on any FSX menu items. the APU gen was on.
I tried using the external power and air start when this happens but no joy. I tried the same as Markoz, and the default aircraft with engines running and still no battery power and the engines would not start. I even tried the CTRL E... nothing. Shut down FSX and re-started. No issues everything was working. This happened a couple of times until I put in the electric_always_available=1 line in the config. I know it's not realistic or a fix." Marvic

electric_always_available=1

Hello, thanks for your quick answer.

Do you mean have I tried the "electric always available" fix?  No, not yet.

Is this likely to be something that gets fixed in a future pack do we know?

It is worth noting that if you own a registered version of FSUIPC, you can increase the life of the battery by a factor of X (with 0 (zero) being infinite), which could help with avoiding the problem. In all honesty, I only use this on the Flight1 Cessna Mustang because the battery on that is usually flat before I finish inserting the flight plan!

Hello you have Fsuipc on payware?

electric_always_available=1 did not work for me, I had to use FSUIPC unlimited battery.

Then there is still the problem of gauges/controls locking up occasionally after accessing the FSX menu bar before engines are running.

I too have this problem.. have been following this (these) threads.. for a while now..

Let's try looking at it, "forest from the trees"... meaning, it shouldn't matter how inept the user might be, as far as power management goes..

Even if he jumps in, turns just the battery on, and then powers up the avionics and all the lights.. then goes for a walk (obviously draining the battery).. comes back hours later.. ground-power should allow him to fire-up the APU, and start the engines.. right ?

I think it's power hierarchy/logic problem.. like the only way the the engine-start-sequencer can be powered, is by the FSX battery.. and the only way to charge, or keep the FSX battery charged, is via engine driven generators.

The engine-start-sequencer should be able to get power from ground-power, or the APU.. OR the battery itself should be able to maintain a charge (or get re-charged) by either (or both) the ground-power, or the APU .. right ?

I've poked around all the XML gauge folders, and I've seen no reference to, "Aircraft Variables" .. only references to "Local Variables". My guess is, that CS needed to define a lot of stuff independent of FSX, to make its systems "work".. and along the lines, the battery/avionics/starters, ect.. ended up with an illogical set of interactions... leaving "broken" connections.

All of the gauge folders, and XML files, and local-variables are named by proprietory/cryptic conventions.. so I can't debug this. My XML skills are limited to my own, freeware work (found under the name, "Brett Henderson"), but I know enough to know that this can be a simple, "hot fix", long overdue. It severly limits a sim-pilot from using realistic, emmersive pre-flight practices.. a large reason for why we but these beautiful models..

Quote:


Right..  ground-power would be all you need even IF you let the battery drain..

And the start-sequencer/avionics should see power by any three of the sources (battery, ground-power, APU)..

The problem is that if you let the battery drain.. that's it.. no avionics\start-sequencer/APU startup.. nothing, no matter what you do..

The simplest fix would only need to let the start-sequencer work off APu or ground-power.. so at least you could charge the battery via engine-driven generators..