A310-300 dead on spawn

User Support Hub Aircraft & Systems
, ,
1

:wave: Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.

2 tags are required: One for platform, and one for aircraft.

Are you using Developer Mode or made changes in it?

No

Have you disabled/removed all your mods and addons? If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the Community Support section.

No

Which aircraft are you reporting an issue about? (Please also add the proper tag for it)

a310-300 (iniBuilds from MSFS 40th Anniversary Deluxe)

Which aircraft version are you experiencing this issue on? (You can find this listed in the Content Manager under the Aircraft Name)

a310-300 v1.1.12 & a310-300 Enhanced 1.1.7 (both installed).

Brief description of the issue:

When the a310 spawns at gate all controls and buttons are dead. The master caution light is lit along with many of the buttons on the overhead panel however none of those buttons work. You can press the battery and external power buttons with no effect. Flip switches with no effect. Same when spawning on runway. Worked fine earlier today. Cannot figure out what changed.

What I have tried: spawning at both add-on on default MSFS airports. Restarting MSFS. Rebooting computer.

Provide Screenshot(s)/video(s) of the issue encountered:

Detailed steps to reproduce the issue encountered:

PC specs and/or peripheral set up if relevant:

Build Version # when you first started experiencing this issue:

:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

2 Likes
2

I’ve been dealing with this for hours now. What finally fixed it for me is going into General Options, going to the Experimental tab and turning OFF “USE NANOVG FOR XML GAUGES”.

1 Like
3

Do you have the same issue if you follow the OP’s steps to reproduce it?

Yes

Provide extra information to complete the original description of the issue:

Spawning on runway all screens are black, flap handle moves but flaps do not, engines spool up but slow down before speed reaches takeoff speed. Changing XLM gauges as said in previous post did not fix. Uninstall/reinstall from content manager no help. Different airport same thing. Verified install integrity in steam, no help. Worked fine for 2 flights previously, no updates, nothing new installed between flights. Just decided to stop wanting to fly.

If relevant, provide additional screenshots/video:

4

Thank you for this. Very much appreciated. This fix worked for me as well however the USE NANOVG FOR XML GAUGES is getting switch back ON whenever I spawn so I am having to ESC to options, turn is OFF again, then go back into sim, but when I come back it all works.

Are you using GSX? When I turned off USE NANOVG FOR XML GAUGES I noticed is disabled GSX. Maybe just a coincidence.

2 Likes
5

Interesting. I think I might be having the same GSX issue but if the A310 is in it’s “dead” state you can toggle the XML GAUGES OFF and then back ON. I’m flying it again with it ON now and all seems to be working fine. Seemed like a weird screen/avionics glitch.And you’re welcome! Glad I could help!

6

Do you have the same issue if you follow the OP’s steps to reproduce it?

Yes

Provide extra information to complete the original description of the issue:

No matter where I spawn the aircraft, it always starts with black screens but with the overhead illuminated even when batteries and gpu are not connected.

If relevant, provide additional screenshots/video:

7

Do you have the same issue if you follow the OP’s steps to reproduce it?
I have the exact same issue

8

Suddenly having the same issue with the A310 dead on spawn. Seems several others are over on the Ini forums too, with a video posted showing exactly the state the 310 suddenly seems to be in.

2 Likes
9

I have the same problem :pensive:

10

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

11

Do you have the same issue if you follow the OP’s steps to reproduce it?

Yes

Provide extra information to complete the original description of the issue:

On XBOX we have the same problem.

If relevant, provide additional screenshots/video:

12

This is a known issue, Inibuilds have submitted a fix to Asobo, just needs to get tested and released now.

13

Thanks to everyone who responded to my post. I thought I was crazy but you have all proven I am not, or perhaps we all are. Either one. :laughing:

Seriously though, the problem seems to have manifested itself sometime between 2:00 PM and 7:00 PM EST yesterday (12/26/2023). As some have posted here, there is a thread on the official iniBuilds forums where iniBuilds stated today:

“We have identified the issue and are making the fix. Will send this to MS asap for testing and circulation.”

That’s good news. Our reporting got to the people who needed it, and a fix is on the way.

3 Likes
14

Seriously though, the problem seems to have manifested itself sometime between 2:00 PM and 7:00 PM EST yesterday (12/26/2023)

That is the weirdest part of this for me, how is it even possible that a plane breaks out of nowhere when no sim update was sent… Plane developers all over must be breaking out in cold sweat when they read this :upside_down_face:

15

Bug fix: change flight date to before 12/10/2023

1 Like
16

An addon with an expiration date? And coincidentally, right after iniBuilds launched the A300. Ironic

17

This has started happening to me again today - in FS2024!! Can’t fly the 320 because of the white screens. Tohught I’d try the 310. Dead. No power!