Hi:

I posted this question on their discord but they never responded - they just keep talking about the A300.  Anybody know when the A310 is getting an update?  I'm waiting for a fix that stops fuel from burning when the sim is paused.  

Thanks!

I think that it's not an iniBuilds bug, but rather an MSFS feature. Active pause just pins the plane at its current position, but the engines run and time passes, etc. AFAIK all MSFS aircraft behave similarly. 

If you have a registered version of FSUIPC, set a button or key for Pause Toggle. This is the actual pause.

Correct me if I'm wrong, but isn't the best way to pause to hit the escape key so the in game menu appears? That seems to actually "freeze" everything for me.

If you need to use view changes or cockpit buttons or take screenshots, the next best thing is Pause Toggle in FSUIPC, as Luis stated. Active Pause seems to me to be more harm than help.

You don't need FSUIPC to use Pause Toggle...you can bind keystrokes or buttons to 'Pause On' and 'Pause Off' within the MSFS control settings.

The pause toggle with pmdg, fenix, Maddog, etc stops the fuel burn.  Not so with the a310, leave it long enough and it runs out of fuel.  I use Time Machine to pause and it works with all other planes except the A310. It continues to burn fuel as Aaron stated above. A fix to this issue would be great.

40 minutes ago, Beener said:

The pause toggle with pmdg, fenix, Maddog, etc stops the fuel burn.  Not so with the a310, leave it long enough and it runs out of fuel.  I use Time Machine to pause and it works with all other planes except the A310. It continues to burn fuel as Aaron stated above. A fix to this issue would be great.

If you hit the Escape key to go to the menu, doesn't it stop fuel burn then?

33 minutes ago, Mace said:

If you hit the Escape key to go to the menu, doesn't it stop fuel burn then?

Nope.  The A310 has a bug.

Also, when I un-pause the A310, it goes into uncontrolled & unrecoverable flight - for me. 

It did the first time for me, the the other times it fluctuates altitude by about 2K and stabilizes and then I can start descent.  But the cabin pressurization shoots up to a ridiculous 90000 altitude so I'm landing with a bunch of dead passengers......

They’ve had an update ready for the A310 for a number of months but Asobo is not publishing it. Reasons are not known….

37 minutes ago, B777ER said:

They’ve had an update ready for the A310 for a number of months but Asobo is not publishing it. Reasons are not known….

They usually roll all the fixes and updates in a Sim Update. This allows for a broad open beta test, and a large deployment (ie. a Sim Update deployment), which is more time efficient for the MSFS team.

There were a lot of Sim Updates in the first year of MSFS, in 2020 to the first half of 2021. The complaints were that it was wearing down the staff at Asobo, because after each Sim Update, they had to prepare another round of testing, and prepare for another deployment. So I think that's why they cut down on the Sim Updates. At the same time, the MSFS community was also annoyed at the frequent Sim Updates because stuff kept breaking after each Sim Update, so the MSFS community also asked for a lower frequency of Sim Updates.

Just now, abrams_tank said:

They usually roll all the fixes and updates in a Sim Update. This allows for a broad open beta test, and a large deployment (ie. a Sim Update deployment), which is more time efficient for the MSFS team.

There were a lot of Sim Updates in the first year of MSFS, in 2020 to the first half of 2021. The complaints were that it was wearing down the staff at Asobo, because after each Sim Update, they had to prepare another round of testing, and prepare for another deployment. So I think that's why they cut down on the Sim Updates. At the same time, the MSFS community was also annoyed at the frequent Sim Updates because stuff kept breaking after each Sim Update, so the MSFS community also asked for a lower frequency of Sim Updates.

They can deploy the patch anytime. Apparently, it's straight forward enough to push an update that they can even do it accidentally, as they did last week with the ATR. They just don't have it together. 

16 minutes ago, chapstick said:

They can deploy the patch anytime. Apparently, it's straight forward enough to push an update that they can even do it accidentally, as they did last week with the ATR. They just don't have it together. 

But from a testing viewpoint, they would need to separately test a version of the current version of MSFS on AAU2, with the Inibuilds A310. They would have to devote a testing team to do this, and make sure whatever code they deployed for the Inibuilds A310 fix, didn't cause wider problems. The issue is, from time to time if they deploy code for a specific airplane fix, they may accidentally deploy code that they didn't mean to deploy. Or sometimes they have new code that they do mean to deploy, but that code is meant to work for a specific branch, and not for another branch that they deploy. From an educated guess, I think that white cursor and white line box bug may have been code that was actually meant for Sim Update 13, but AAU2 also required that code to work so it became part of AAU2, but because that code was required for AAU2, they couldn't "undo" that code.  This could explain why the MSFS team decided to defer the complete fix for the white cursor and white line box bug to Sim Update 13.

And as for the public open beta test that we have, a public open beta test may also be required just for the Inibuilds A310 fix. That's a lot of public open beta tests and it leads to tester fatigue from the open beta testers. It's simply much better to have major designated open beta tests, where everything is tested, rather than a bunch of minor open beta tests, because the big open beta tests we have prior to a Sim Update is a much more comprehensive open beta test.

TLDR: Software testing is very, very, hard, especially when you have various branches. It's just easier and more time efficient for the testing team (and even for the development team), if the testing can be done in one fell swoop, rather than separated into a lot of separate tests.

Edited July 23, 20232 yr by abrams_tank

This issue was supposed to addressed with the last update of the A310 but it didn’t fix it.  What kinda makes me most frustrated is the lack off communication or even acknowledgement from ini & as usual with developers, they’ve moved onto their next project and appear to neglect their current product.