Flight director 1 disappears

[edaaaaaali123456]

Hi all,

I've recently encountered an issue where flight director 1 on the captain's side randomly disappears on the PFD and is replaced by a flag showing it is not working. At first I assumed I had accidentally clicked on something while looking around that caused it to break. I managed to complete the flight fine as the FD2 on the FO side was working fine. I just had it again and was wondering what could be the cause and how to avoid it happening, and its happened with both the GE pax and PW freighter variants. I've also noticed that the standby attitude indicator looks broken as well. Hope someone can help!

Thanks

[KorEl]

What version are you running?  After v1.1.0 this has been fixed (for me at least). 

FD1 failure is caused by pitch trim 1 disengaging, you can reconnect it and restore FD1. This bug also empties the main fuel tanks, you can refill  them inflight if you set refuelling to "not realistic" in settings. Stby horizon cannot be reset.

[edaaaaaali123456]

Hi,

I'm pretty sure I was running it with v1.1.0, anyway I uninstalled it and reinstalled the latest update (v1.1.1) and it happened again just now. Any ideas what might be causing it? I'm using FSLTL, GSX and a bunch of different addon airports, would anything like that be causing it?

 

Thanks

[Crabby]

3 hours ago, edaaaaaali123456 said:

Hi,

I'm pretty sure I was running it with v1.1.0, anyway I uninstalled it and reinstalled the latest update (v1.1.1) and it happened again just now. Any ideas what might be causing it? I'm using FSLTL, GSX and a bunch of different addon airports, would anything like that be causing it?

 

Thanks

If it is not a bug, and I don't see this on my system, then literally anything in your community folder could cause this.  It could be a livery (even from another plane) a scenery etc.  The only way to verify is to move/delete everything in your community folder and run the A300 with a default livery.  If it does not happen then you found the place your problem is coming from.  Now you have to add one thing at a time back until the culprit is found.  This is a pain in the butt but a byproduct of dumping everything into the community folder and forgetting it. 

I use MSAddons Linker from flightsim.to  This allows me to install NOTHING into my community folder and only use generated symbolic links.  Before a flight, I take about 15 seconds and activate the plane, livery and two airports I am going to use.  This way I run a clean community folder. 

If that does not do the trick I am out of options other than make sure you don't have some assignment (remember, MSFS does you the "favor" of making assignments across all your devices and many times there are multiple assignments) that could trigger it.  One of the many reasons all my in sim controller profiles are blank. 

[Barto]

Have also the same issue. On some point pitch one Came of and disable the autopilot. Had that issue also with the old version reinstall 110 and also now the new version 111.

[richboy2307]

Can't say i've seen this before. Do y'all have any keybind that you are using for the FD per chance? 

Also are you able to re-engage the FD1/Standby Horizon afterwards, or its completely unresponsive?

[Dodo]

I and some others I know also have this issue, at random times and intervals. I very much suspect it's something leftover from this issue.

Here's an excerpt from the similar topic on the iniBuilds Discord server:

  Pitch Trim 1 faulted, inhibiting FD1. Noticed the standby attitude indicator was rolled/failed. Then, checked all systems, and noticed any fuel in all tanks except the OUTERs were gone and zeroed. However, no other values noticed were affected, including APU Oil quantity. Fuel also proceeded to flow at a conspicuously high rate, and the FUEL USED counter on ENG 1 was jumbled and appeared to be a large number.

There are some additional posts and mentions in this topic on Discord

[edaaaaaali123456]

Thanks for all the replies, for what its worth I haven't noticed this happening recently, but when it does I'm able to re-engage FD1 after pitch trim 1 is re-engaged. I don't have any binding attached to FD1 (as far as I'm aware - I know MSFS has a thing for randomly making new bindings/changing control settings).

My experience sounds exactly like what you mentioned here.

13 hours ago, Dodo said:

Pitch Trim 1 faulted, inhibiting FD1. Noticed the standby attitude indicator was rolled/failed. Then, checked all systems, and noticed any fuel in all tanks except the OUTERs were gone and zeroed. However, no other values noticed were affected, including APU Oil quantity. Fuel also proceeded to flow at a conspicuously high rate, and the FUEL USED counter on ENG 1 was jumbled and appeared to be a large number.

 

[Crabby]

23 hours ago, edaaaaaali123456 said:

Thanks for all the replies, for what its worth I haven't noticed this happening recently, but when it does I'm able to re-engage FD1 after pitch trim 1 is re-engaged. I don't have any binding attached to FD1 (as far as I'm aware - I know MSFS has a thing for randomly making new bindings/changing control settings).

My experience sounds exactly like what you mentioned here.

 

Did you look for a binding to pitch trim1?  Don't forget, you may not have created the binding, and that binding could literally be on any of your controllers including keyboard and mouse.  MSFS loves to create bindings it thinks you need. 

[richboy2307]

Please report if anyone has had this issue on v1.1.1 and SU15 update. 
Thanks!

[edaaaaaali123456]

Hiya, 

Fired up the a300 for the first time post update today and had this issue again. Was flying the pax GE variant.

Hope that helps

[unreadierblock]

I have the same problem with V1.1.1 and SU15 installed.

[Samuel Ronnin]

Count me in. Happened one time only, lost the FD and the fuel....

[K8BCO]

This has happened a couple of times for me. Last night, I was cruising on autopilot when suddenly, the AP cut off, and the plane began to dive. After hand-flying for a while, I realized that the Pitch Trim and Yaw Damper switches had been turned off. Once I switched them back on, I could re-engage AP and finish the flight. Until I figured that out, I could not turn on FD 1 or engage AP.

I'll try to gather more info if it happens again.

[savvysigma]

I can confirm that this sequence of bugs is still very much happening on the latest version.

I hadn't noticed it before due to mostly flying short-haul, but on my last 3 medium-haul flights (i.e at least 1hr+ into cruise) the following happens, as quoted below:

 

On 5/8/2024 at 1:40 AM, Dodo said:

Pitch Trim 1 faulted, inhibiting FD1. Noticed the standby attitude indicator was rolled/failed. Then, checked all systems, and noticed any fuel in all tanks except the OUTERs were gone and zeroed. However, no other values noticed were affected, including APU Oil quantity. Fuel also proceeded to flow at a conspicuously high rate, and the FUEL USED counter on ENG 1 was jumbled and appeared to be a large number.

ALL of the above happens at once, and other than the Pitch-trim and FD1, the rest cannot be rectified in-flight.

Edited June 18 by savvysigma

[Nick H]

On 5/27/2024 at 6:01 PM, richboy2307 said:

Please report if anyone has had this issue on v1.1.1 and SU15 update. 
Thanks!

Yes, I had the Pitch Trim 1 trip and the standby indicator rolled/failed. I reengaged Pitch Trim 1, but the standby indicator remained failed. I noticed a drop in fuel quantity, but the FD1 remained engaged I believe.

[richboy2307]

Thanks for the reports all.

Next time this happens, could you guys go into developer mode and check if there is any WASM module crash?
If yes, please copy-paste the message here so it could help to narrow down the faulting module.

Instructions on how to access the console:

• Enable developer mode  (Settings > General > Developers > Developer Mode - ON)
• Open the console (Press the ` key on your keyboard or from the top DevMode toolbar via Debug > Console)
  
   
•  On the search bar type WASM, and look for error messages (marked with red crosses). YOu can use the filters on top (red box) to make it easier to find them.
  
   
• Look for error messages such as 'WASM: Exception...'  or  'WASM: Module...'. You can click on it and hit the 'Details' button on the bottom to get more information. The WASM crashes related to the a300 will mention 'inibuilds-aircraft' or 'a300' in them.
   
• Press the 'Copy' button to copy the selected message to your clipboard, and then please share them here, such as example:

  WASM: Exception c0000005 in gauge Systems in module vfs://inibuilds-aircraft-a300-600/SimObjects/Airplanes/inibuilds-aircraft-a306f-pw/panel/inibuilds-A300.wasm

   

As we haven't been able to reproduce this issue internally or via the testers as yet, we'd appreciate this information to help with the investigation.

Thanks!

[Dodo]

Hello again, 

After multiple flights over the past week ranging in 1-4hrs duration, I encountered no issues. However, this bug happened again randomly, approximately 4hrs into a 5.5hr flight, in which case all aforementioned issues happened EXCEPT the standby attitude indicator error. Additionally, though, the ECAM did not display any messages and there were no indications of errors/warnings even when tested (i.e. main landing gear indicator test, fire tests, etc.). 

I checked in the console and found no WASM errors. I don't know if this is universal, but there is a slew of FuelSystem errors and some ElectricalSystem errors. I don't know exactly when or what time it happened (no aural alert sounded and I was not paying attention), but there was nothing remarkable in the console during that timeframe.

I was flying a custom livery (for a VA that others report no issues with), with FSUIPC, if that matters.

I'm looking for recommendations on things to try or if anybody with this error before had it resolved. Things I tried to resolve include clearing the "work" folder entry, uninstalling/reinstalling aircraft, updated/downgraded FSUIPC, changing liveries, and different loading sequences for fuel/cargo. Note that the only thing I did differently during this flight was select "Finish Now" when refueling was in-progress.

Thanks!

Here's a sample of the ElectricalSystem FuelSystem errors:

ElectricalSystem [A300-600RF GE Special Missions Air (N139AT)]: Undefined circuit CIRCUIT_XML:3 when at least one circuit with a higher index is defined (most likely due to this index missing in system.cfg)
ElectricalSystem [A300-600RF GE Special Missions Air (N139AT)]: Undefined circuit CIRCUIT_XML:8 when at least one circuit with a higher index is defined (most likely due to this index missing in system.cfg)
ElectricalSystem [A300-600RF GE Special Missions Air (N139AT)]: Undefined circuit CIRCUIT_XML:9 when at least one circuit with a higher index is defined (most likely due to this index missing in system.cfg)
ElectricalSystem [A300-600RF GE Special Missions Air (N139AT)]: Undefined circuit CIRCUIT_XML:10 when at least one circuit with a higher index is defined (most likely due to this index missing in system.cfg)
ElectricalSystem [A300-600RF GE Special Missions Air (N139AT)]: Undefined circuit CIRCUIT_XML:11 when at least one circuit with a higher index is defined (most likely due to this index missing in system.cfg)
ElectricalSystem [A300-600RF GE Special Missions Air (N139AT)]: Undefined circuit CIRCUIT_XML:12 when at least one circuit with a higher index is defined (most likely due to this index missing in system.cfg)
ElectricalSystem [A300-600RF GE Special Missions Air (N139AT)]: Undefined circuit CIRCUIT_XML:13 when at least one circuit with a higher index is defined (most likely due to this index missing in system.cfg)
ElectricalSystem [A300-600RF GE Special Missions Air (N139AT)]: Undefined circuit CIRCUIT_XML:14 when at least one circuit with a higher index is defined (most likely due to this index missing in system.cfg)
ElectricalSystem [A300-600RF GE Special Missions Air (N139AT)]: Undefined circuit CIRCUIT_XML:15 when at least one circuit with a higher index is defined (most likely due to this index missing in system.cfg)
...
[FuelSystem]Engine APU does not have a valid source line.
[FuelSystem]Engine LeftEngine does not have a valid source line.
[FuelSystem]Engine RightEngine does not have a valid source line.
[FuelSystem]Could not create Pump #2 of type Electrical (LeftInnerTankPump1) as the plane's Electrical System doesn't have a circuit at Index 64. Ignoring.
[FuelSystem]Could not create Pump #3 of type Electrical (RightInnerTankPump1) as the plane's Electrical System doesn't have a circuit at Index 65. Ignoring.
[FuelSystem]Could not create Pump #5 of type Electrical (LeftInnerTankPump2) as the plane's Electrical System doesn't have a circuit at Index 66. Ignoring.
[FuelSystem]Could not create Pump #6 of type Electrical (RightInnerTankPump2) as the plane's Electrical System doesn't have a circuit at Index 67. Ignoring.
[FuelSystem]Could not find Component 10424721316047076014. Ignoring.
[FuelSystem]Could not find Component 16490562297229306832. Ignoring.
[FuelSystem]Could not find Component 6742165202923352363. Ignoring.
[FuelSystem]Could not find Component 7548378436910047622. Ignoring.
[FuelSystem]Could not find Component 18019561748527990483. Ignoring.
[FuelSystem]Could not find Component 1202506699661051124. Ignoring.
[FuelSystem]Could not find Component 6751050659546758993. Ignoring.
[FuelSystem]Could not find Component 3797295004946634319. Ignoring.
[FuelSystem]Could not find Component 323895669355634023. Ignoring.
[FuelSystem]Could not find Component 8369951844793638479. Ignoring.
[FuelSystem]Could not find Component 3877670216685801894. Ignoring.
[FuelSystem]Could not find Component 2435339283068009738. Ignoring.
[FuelSystem]Could not find Component 3430574313194653936. Ignoring.
[FuelSystem]Could not find Component 1390804071367126474. Ignoring.
[FuelSystem]Could not find Component 3995131149383821012. Ignoring.
[FuelSystem]Could not find Component 17037753251352800809. Ignoring.
[FuelSystem]Could not find Component 12861724917931963503. Ignoring.
[FuelSystem]Could not find Component 1784994504759446746. Ignoring.
[FuelSystem]Could not find Component 6642383146788619801. Ignoring.
[FuelSystem]Could not find Component 15284303970454305188. Ignoring.
[FuelSystem]Could not find Component 5422660755273518495. Ignoring.
[FuelSystem]Could not find Component 7986487994844128089. Ignoring.
[FuelSystem]Could not find Component 5438730550633641878. Ignoring.
[FuelSystem]Could not find Component 1697285186822050528. Ignoring.
[FuelSystem]Could not find Component 600961235955378443. Ignoring.
[FuelSystem]Could not find Component 2404225923332968598. Ignoring.
[FuelSystem]Could not find Component 8152019711890910819. Ignoring.
[FuelSystem]Could not find Component 7729421033720529711. Ignoring.
[FuelSystem]Could not find Component 4551387437857124030. Ignoring.
[FuelSystem]Could not create Pump #2 of type Electrical (LeftInnerTankPump1) as the plane's Electrical System doesn't have a circuit at Index 64. Ignoring.
[FuelSystem]Could not create Pump #3 of type Electrical (RightInnerTankPump1) as the plane's Electrical System doesn't have a circuit at Index 65. Ignoring.
[FuelSystem]Could not create Pump #5 of type Electrical (LeftInnerTankPump2) as the plane's Electrical System doesn't have a circuit at Index 66. Ignoring.
[FuelSystem]Could not create Pump #6 of type Electrical (RightInnerTankPump2) as the plane's Electrical System doesn't have a circuit at Index 67. Ignoring.
[FuelSystem]Engine APU does not have a valid source line.
[FuelSystem]Engine LeftEngine does not have a valid source line.
[FuelSystem]Engine RightEngine does not have a valid source line.
[FuelSystem]Could not create Pump #2 of type Electrical (LeftInnerTankPump1) as the plane's Electrical System doesn't have a circuit at Index 64. Ignoring.
[FuelSystem]Could not create Pump #3 of type Electrical (RightInnerTankPump1) as the plane's Electrical System doesn't have a circuit at Index 65. Ignoring.
[FuelSystem]Could not create Pump #5 of type Electrical (LeftInnerTankPump2) as the plane's Electrical System doesn't have a circuit at Index 66. Ignoring.
[FuelSystem]Could not create Pump #6 of type Electrical (RightInnerTankPump2) as the plane's Electrical System doesn't have a circuit at Index 67. Ignoring.
[FuelSystem]Could not find Component 7127570437776227257. Ignoring.
[FuelSystem]Could not find Component 13005443298400054089. Ignoring.
[FuelSystem]Could not find Component 4757778715552959128. Ignoring.
[FuelSystem]Could not find Component 10404496548777374735. Ignoring.
[FuelSystem]Could not find Component 15591987115252620015. Ignoring.
[FuelSystem]Could not find Component 14297992192638937910. Ignoring.
[FuelSystem]Could not find Component 7567986566264738838. Ignoring.
[FuelSystem]Could not find Component 12955253955449773663. Ignoring.
[FuelSystem]Could not find Component 14496405016460480373. Ignoring.
[FuelSystem]Could not find Component 17956023032863043535. Ignoring.
[FuelSystem]Could not find Component 14081667779881642871. Ignoring.
[FuelSystem]Could not find Component 4137785164281244433. Ignoring.
[FuelSystem]Could not find Component 14312295979304599219. Ignoring.
[FuelSystem]Could not find Component 4597146055946284007. Ignoring.
[FuelSystem]Could not find Component 8075212059039172667. Ignoring.
[FuelSystem]Could not find Component 7656319456535288110. Ignoring.
[FuelSystem]Could not find Component 14064079484947725399. Ignoring.
[FuelSystem]Could not find Component 13656695853185674093. Ignoring.
[FuelSystem]Could not find Component 10328795880212501264. Ignoring.
[FuelSystem]Could not find Component 11880891124177270776. Ignoring.
[FuelSystem]Could not find Component 10078486100294445645. Ignoring.
[FuelSystem]Could not find Component 10945166301853837182. Ignoring.
[FuelSystem]Could not find Component 4554522823229861448. Ignoring.
[FuelSystem]Could not find Component 6801440739598543020. Ignoring.
[FuelSystem]Could not find Component 3945953948204972367. Ignoring.
[FuelSystem]Could not find Component 107314924498985190. Ignoring.
[FuelSystem]Could not find Component 4259227239972064359. Ignoring.
[FuelSystem]Could not find Component 1994652733747290887. Ignoring.
[FuelSystem]Could not find Component 9438877797116312209. Ignoring.
[FuelSystem]Engine APU does not have a valid source line.
[FuelSystem]Engine LeftEngine does not have a valid source line.
[FuelSystem]Engine RightEngine does not have a valid source line.
[FuelSystem]Could not create Pump #2 of type Electrical (LeftInnerTankPump1) as the plane's Electrical System doesn't have a circuit at Index 64. Ignoring.
[FuelSystem]Could not create Pump #3 of type Electrical (RightInnerTankPump1) as the plane's Electrical System doesn't have a circuit at Index 65. Ignoring.
[FuelSystem]Could not create Pump #5 of type Electrical (LeftInnerTankPump2) as the plane's Electrical System doesn't have a circuit at Index 66. Ignoring.
[FuelSystem]Could not create Pump #6 of type Electrical (RightInnerTankPump2) as the plane's Electrical System doesn't have a circuit at Index 67. Ignoring.
[FuelSystem]Could not find Component 7127570437776227257. Ignoring.
[FuelSystem]Could not find Component 13005443298400054089. Ignoring.
[FuelSystem]Could not find Component 4757778715552959128. Ignoring.
[FuelSystem]Could not find Component 10404496548777374735. Ignoring.
[FuelSystem]Could not find Component 15591987115252620015. Ignoring.
[FuelSystem]Could not find Component 14297992192638937910. Ignoring.
[FuelSystem]Could not find Component 7567986566264738838. Ignoring.
[FuelSystem]Could not find Component 12955253955449773663. Ignoring.
[FuelSystem]Could not find Component 14496405016460480373. Ignoring.
[FuelSystem]Could not find Component 17956023032863043535. Ignoring.
[FuelSystem]Could not find Component 14081667779881642871. Ignoring.
[FuelSystem]Could not find Component 4137785164281244433. Ignoring.
[FuelSystem]Could not find Component 14312295979304599219. Ignoring.
[FuelSystem]Could not find Component 4597146055946284007. Ignoring.
[FuelSystem]Could not find Component 8075212059039172667. Ignoring.
[FuelSystem]Could not find Component 7656319456535288110. Ignoring.
[FuelSystem]Could not find Component 14064079484947725399. Ignoring.
[FuelSystem]Could not find Component 13656695853185674093. Ignoring.
[FuelSystem]Could not find Component 10328795880212501264. Ignoring.
[FuelSystem]Could not find Component 11880891124177270776. Ignoring.
[FuelSystem]Could not find Component 10078486100294445645. Ignoring.
[FuelSystem]Could not find Component 10945166301853837182. Ignoring.
[FuelSystem]Could not find Component 4554522823229861448. Ignoring.
[FuelSystem]Could not find Component 6801440739598543020. Ignoring.
[FuelSystem]Could not find Component 3945953948204972367. Ignoring.
[FuelSystem]Could not find Component 107314924498985190. Ignoring.
[FuelSystem]Could not find Component 4259227239972064359. Ignoring.
[FuelSystem]Could not find Component 1994652733747290887. Ignoring.
[FuelSystem]Could not find Component 9438877797116312209. Ignoring.
[FuelSystem]Engine APU does not have a valid source line.
[FuelSystem]Engine LeftEngine does not have a valid source line.
[FuelSystem]Tank Center does not have a valid destination line.
[FuelSystem]Pump CenterTankPump1 does not have a valid destination line.
[FuelSystem]Pump CenterTankPump1 does not have a valid source line.
[FuelSystem]Valve CrossFeedValve does not have a valid source line.
[FuelSystem]Junction LeftJunction should have at least one outgoing Line.
[FuelSystem]Junction LeftJunction should have at least one incoming Line.
[FuelSystem]Could not create Pump #1 of type Electrical (CenterTankPump1) as the plane's Electrical System doesn't support circuits. Ignoring.
[FuelSystem]Could not find Component 9312753157947950831. Ignoring.
[FuelSystem]Could not find Component 8323826259742538309. Ignoring.
[FuelSystem]Could not find Component 13012317544260559344. Ignoring.
[FuelSystem]Engine APU does not have a valid source line.

 

[richboy2307]

9 hours ago, Dodo said:

However, this bug happened again randomly, approximately 4hrs into a 5.5hr flight, in which case all aforementioned issues happened EXCEPT the standby attitude indicator error. Additionally, though, the ECAM did not display any messages and there were no indications of errors/warnings even when tested (i.e. main landing gear indicator test, fire tests, etc.). 

9 hours ago, Dodo said:

I was flying a custom livery (for a VA that others report no issues with), with FSUIPC, if that matters.

9 hours ago, Dodo said:

Note that the only thing I did differently during this flight was select "Finish Now" when refueling was in-progress.

Hi, thanks for the report.

I'll share the log with the team to see if there's any hints there. However, none of those items you've mentioned should cause such issues. Personally I run with FSUIPC7, SPAD.Next, LittleNavMap, Vpilot and occasionally VA trackers... and unless specifically testing fuelling features, also always use the "Finish Now" button and have yet to encounter such crashes.

Also just additional context/information, there are no known instances of such crashes (i.e. not a WASM Crash) internally or through any beta testers in over 200 hours of collective testing of this particular build.  Certainly an odd issue and hopefully we can find its source from this info.

As this bug is also not reliably reproducible by affected users, it is really hart to ascertain the root cause.

Thanks!

[Dodo]

Quote

Personally I run with FSUIPC7, SPAD.Next, LittleNavMap, Vpilot and occasionally VA trackers... and unless specifically testing fuelling features, also always use the "Finish Now" button and have yet to encounter such crashes.

This was reassuring and gave me some peace of mind. So for the past week, I flew only the A306F (GE variant) and throughout 12+ hours until today, it was going well and without error, even with different manipulations. This was also after reconfiguring the entire Community folder in the case there was an incompatibility in that.

Today while on a short hop, though, the same issue occurred except in this case, both pitch trims and yaw dampers switched off and the plane rolled over right but recovered. This is the first time I had this "variation" of it. I was able to continue and checked the console. The console, at the time of incident, indicated an error with ElectricalSystem and FuelSystem - it mentioned that Fuel Pump 1 had no line or source of power, and then ignored approximately four Components. I'd attach the log but the sim CTD'd when I attempted to print it to a log (very inconveniently). There was no mention of WASM errors again.

Note that the only difference in this case was that I inputted the block fuel in the FMC during refueling, although I did this same thing before. I do believe that perhaps the weights were off, however, with a discrepancy of approximately 2,000 lbs, which I though was strange but I had seen it before. It was a very light load, compared to prior successful flights. I was reminded of this: https://discord.com/channels/535246634448191499/1202402575261900810/1202610391998537748 

I also attached an image of the fuel used integer overflow on the display that happens every occurrence.

Hope this might help! Thanks again

[richboy2307]

Hi thanks for getting back.

13 hours ago, Dodo said:

There was no mention of WASM errors again.

Yeah this does not sound like a WASM crash either, as in those instances all the systems will stop responding/updating values completely.

Here, as with the screenshots it does appear as if there is some invalid fuel value (particularly burn) being sent that is causing the system to trip. Or there is a very momentary loss of fuel flow which will trip things like the overhead AP switches. 

Can you just cross check your bindings and ensure there is nothing that affects fuel by chance (e.g. Mixture, Fuel / Condition Levers). Also anything that could affect electricals (generator/battery etc)? 

At the moment, I think the electrical issues are a result of the fuel system fault which is tripping the generators perhaps. But anyways, will add the above info to your report for the team to investigate further.

Thanks again!

[Travon999]

Same issue here with the A306 GE(Passenger) this is my second time experiencing the issue in the last 2 weeks (I did a total of 13 flights in that time). The first time it happened I had used a saved flight, so I figured that messed the panel state. This time, however, was a normal load-in/startup for the GPU panel state and around 3 hours into the flight, I noticed FD1 and pitch trim 1 were both disengaged, and the ENG 1 FU gauge was all messed up. The screenshot below was taken after reengaging the pitch trim and FD, but shows the fuel used bug.

 

[richboy2307]

On 10/29/2024 at 10:20 PM, Travon999 said:

I noticed FD1 and pitch trim 1 were both disengaged, and the ENG 1 FU gauge was all messed up. The screenshot below was taken after reengaging the pitch trim and FD, but shows the fuel used bug.

Ok thanks, also added above to the report. To me it is seeming more likely related to the engine tripping momentarily, possibly due to some null fuel value output being provided. But in any case, dev team will look into it and action for next update in case they find something.

Apologies for inconvenience caused. Thanks!