No Ext. Power and Batteries Not Working - No Systems Avail

[Adam T]

Extremely dissatisfied after just downloading the 350. As per the title, upon spawning in on runway or gate, no buttons work. The battery and ext power buttons are clickable but doesn’t do anything. 

 

Ext power shows AVAIL but clicking does nothing. I spawn in -> straight into cockpit -> turn on all batteries but this does not do anything. Same story with the external power. Cannot access the EFB due to no power. 

Tired: Restarting sim; trying different liveries/airports; restarting sim; clearing WASM folder; uninstalling and reinstalling; spawning on runway; etc. Spawning on runway spawns cold and dark. 

Any fixes for this? Was exited to fly this aircraft but have been left disappointed. Seems I’m not the only one with this issue too.

[çağrı]

Yes. I have exactly the same problem as you said and I can't find a solution.

[ChunkyMonkeyHustler]

18 hours ago, Adam T said:

Extremely dissatisfied after just downloading the 350. As per the title, upon spawning in on runway or gate, no buttons work. The battery and ext power buttons are clickable but doesn’t do anything. 

 

Ext power shows AVAIL but clicking does nothing. I spawn in -> straight into cockpit -> turn on all batteries but this does not do anything. Same story with the external power. Cannot access the EFB due to no power. 

Tired: Restarting sim; trying different liveries/airports; restarting sim; clearing WASM folder; uninstalling and reinstalling; spawning on runway; etc. Spawning on runway spawns cold and dark. 

Any fixes for this? Was exited to fly this aircraft but have been left disappointed. Seems I’m not the only one with this issue too.

Questions for both of you: Is MSFS2020 crashing on exit? Do you have to use Task Manager to End Process? And, have you tried spawning a new flight in a new A350 livery at a new position?

[stratfordman]

I am having the same issue too ,Ext Power 1 and 2 not clickable and therefore have a total dead aircraft.

 

Michael

[çağrı]

8 hours ago, ChunkyMonkeyHustler said:

Questions for both of you: Is MSFS2020 crashing on exit? Do you have to use Task Manager to End Process? And, have you tried spawning a new flight in a new A350 livery at a new position?

I didn't have any crashes in the game, I tried with different liveries but the plane is dead. There is no electrical energy.

[gxs]

Same here with A350 -1000.  Althought 350-900 and ULR are working for now.  I tried uninstall and reinstall, deleting community folders and wasm folders.  Nothing would help me start a350-1000.  It shows external power available, but nothing happens after I click them.

[stratfordman]

Trying  to understand what is causing this issue and what the solution might be.

 

Hope Inbuilds come back to us.

[gxs]

So I figured something out.   It seems 900 url and 900/1000 are on separate initial setting.  I am no comp engineer, so I don’t know the exact term or how it works.   Somehow the cold start for 900/1000 doesn’t register GPU even though external power shows available.   900 ulr however can be started without the gpu.   So I use 900 ulr to set the panel state to gpu.   This for some reasons made 900/1000 starts on gpu.   And for all the subsequent RESTART, I have no issue cold starting 900/1000.  However if I end the session and begin a new session with cold start, 900/1000 won’t work again.   Not sure if this makes sense.   So now I keep the panel state at gpu on, and 900/1000 works for now.

[gxs]

If anything, maybe there is some logic issue between gsx, and flight system.  lol no idea.

[ChunkyMonkeyHustler]

I too am suffering from this issue, and was curious if any of the before mentioned items were relevant to you. I seem to be able to just reload the flight and the plane comes up on GPU power, which is the profile i have load when starting iniBuilds A350. I'm hopeful iniBuilds will begin to address this as these reports are starting to popup all over the forums. I have tried all the alleged "fixes" to no avail.

 

Thanks,

ChunkyMonkeyHustler

[balus]

It's a WASM crash, for me it suddenly started yesterday, the day before I was flying fine - see 

[dafan21]

I am also having this issue while using FS2020.  I have been able to get past this by ending my session and then starting a new flight.  I have sometimes changed where I start (gate vs runway).  Not sure if this is related.  ALSO, I noticed that if you power up and then restart your flight from FS then you will not be able to turn on ext power after you turn on the batteries.  Basic stuff!

 

@iniBuilds

* Let's have more unit testing

* Let's have more integration testing

* Let's automate testing of the startup sequence after each build

* Let's not always test the happy path...get creative

[Eddie]

Hello,

I apologize for the inconvenience. There is a similar thread already on this and attempting to diagnose. I have asked for footage of this happening, any kind of video would help as it is hard to understand via text. We have not been able to reproduce this internally so any kind of help to visually show us would be appreciated.

Thank you 

[Tyler Buehlmann]

@Eddie 

 

[foliainfx]

2 hours ago, Tyler Buehlmann said:

@Eddie 

 

Does this happen if you go to the main menu and then load in? I've found that "restart" causes issues

[Tyler Buehlmann]

1 hour ago, foliainfx said:

Does this happen if you go to the main menu and then load in? I've found that "restart" causes issues

the only time it does not happen is when I load the aircraft AFTER clearing the WASM folder. every other scenario it does occur. I just was restarting to show the issue and fmaking it quicker