Got a bunch of warnings after a prolonged time on the ground, prepping a flight LSGG-LEPA

Have following indications: DUAL ADS FAIL, L ENGINE FAULT, CB TRIP, AT FAIL, DMC 2B FAIL, DMC 1B FAIL.

Do not understand why and how to solve.

Went ahead and got airborne (I know I shouldnt), unable to engage AT

Found the solution: resetting circuit breakers.
Hadn't thought of it as I've read failures were not implemented

5 hours ago, Fly_ebos said:

Got a bunch of warnings after a prolonged time on the ground, prepping a flight LSGG-LEPA

Have following indications: DUAL ADS FAIL, L ENGINE FAULT, CB TRIP, AT FAIL, DMC 2B FAIL, DMC 1B FAIL.

Do not understand why and how to solve.

Went ahead and got airborne (I know I shouldnt), unable to engage AT

Curious Question, did you turnaround when this happened or was this from cold and dark from the menus for LSGG-LEPA?

5 hours ago, Fly_ebos said:

Found the solution: resetting circuit breakers.
Hadn't thought of it as I've read failures were not implemented

I don't think failures are modelled but the CBs are.

57 minutes ago, IniJamir said:

Curious Question, did you turnaround when this happened or was this from cold and dark from the menus for LSGG-LEPA?

I had this issue just now as well. Resetting the CBs resolved the issue. This was during a turnaround and for me happened on the ground at the gate. It seems to not happen when the aircraft is initially loaded into its cold and dark state.

18 minutes ago, Anelson7751 said:

I had this issue just now as well. Resetting the CBs resolved the issue. This was during a turnaround and for me happened on the ground at the gate. It seems to not happen when the aircraft is initially loaded into its cold and dark state.

That would be why, the turnaround doesn't fully state clear currently unless the aircraft is fully powered down in the current iteration which will be fixed in v1.0.3 (v.1.0.2 will be skipped on PC due to how the MP Ingestion Process works; this in turn will resync version numbers between FS20 and FS24)

Thank you for understanding.
https://docs.synapticsim.com/changelog#known-issues

I was not doing a turnaround. However, when running on GPU, and then turning on the beacon light, the GPU would get disconnected, causing my FO DEU's to go dark. Perhaps this triggers a turnaround state?