December 27, 20232 yr Greetings! Last night I was simming with the A310 when there was a power outage at my house (nasty ice storm up here in SE North Dakota). Late this afternoon, I loaded up MSFS to start the flight over. Upon loading the A310 in a cold and dark state, I went to the overhead panel to turn on the batteries and engage the external power. The aircraft made none of its usual noises when clicking those buttons, and the displays on the main panel did not power on. I checked other aircraft and they are working fine. Currently in a flight with the B789 and there are not any issues. Anyone have any ideas on how this might be fixed (yes, I know - I need an automatic power backup battery for my gaming computer). Regards, Scott "...now let's get this thing on the hump - we've got some flyin' to do!" ~ Major Kong from "Dr. Stranglove" Scott Cebula
December 27, 20232 yr 13 minutes ago, ndflieger said: Greetings! Last night I was simming with the A310 when there was a power outage at my house (nasty ice storm up here in SE North Dakota). Late this afternoon, I loaded up MSFS to start the flight over. Upon loading the A310 in a cold and dark state, I went to the overhead panel to turn on the batteries and engage the external power. The aircraft made none of its usual noises when clicking those buttons, and the displays on the main panel did not power on. I checked other aircraft and they are working fine. Currently in a flight with the B789 and there are not any issues. Anyone have any ideas on how this might be fixed (yes, I know - I need an automatic power backup battery for my gaming computer). Regards, Scott All I can think of is maybe the state saving got confused with the sudden power failure. I'd suggest re-loading the A310 with a new flight and see if it straightens itself out. Rhett 7800X3D ♣ 96 GB G.Skill Flare ♣ Gigabyte 4090 ♣ Crucial P5 Plus 2TB
December 27, 20232 yr Author Thanks for the reply, I did load the aircraft 3 or 4 times. I could not load a flight since there was not any power on the aircraft. "...now let's get this thing on the hump - we've got some flyin' to do!" ~ Major Kong from "Dr. Stranglove" Scott Cebula
December 27, 20232 yr 7 minutes ago, Mace said: All I can think of is maybe the state saving got confused with the sudden power failure This is the other issue I reported in a recent thread. Any way to reset this state saving? Best regards,Luis Hernández Main rig: self built, AMD Ryzen 7 5700X3D (with SMT off and CO -50 mV), 2x16 GB DDR4-3200 RAM, Nvidia RTX 5060Ti 16GB, 256 GB M.2 SSD (OS+apps) + 2x1 TB SATA III SSD (sims) + 1 TB 7200 rpm HDD (storage), ID-Cooling SE-224-XTS air cooler, Viewsonic VX2458-MHD 1920x1080@120-144 Hz (G-sync compatible), Windows 11. Running P3D v5.4 (with v4.5 scenery objects as an additional library, just in case), FSX-SE, MSFS2020, MSFS2024 and even FS9! Lossless Scaling for all my sims. What a godsend...Mobile rig: ASUS Zenbook UM425QA (AMD Ryzen 7 5800H APU @3.2 GHz and boost disabled, 1 TB M.2 SSD, 16 GB RAM, Windows 11 Pro). Running FS9 there .VKB Gladiator NXT Premium Left + GNX THQ as primary controllers. Xbox Series X|S wireless controller as standby/mobile.
December 27, 20232 yr 3 minutes ago, Luis Hernandez said: This is the other issue I reported in a recent thread. Any way to reset this state saving? I would go into the EFB and select a different state (i.e. "ready for takeoff") and then close out the sim and then re-load. Rhett 7800X3D ♣ 96 GB G.Skill Flare ♣ Gigabyte 4090 ♣ Crucial P5 Plus 2TB
December 27, 20232 yr Author Yes, that is what I am planning to do tomorrow morning. "...now let's get this thing on the hump - we've got some flyin' to do!" ~ Major Kong from "Dr. Stranglove" Scott Cebula
December 28, 20232 yr Author I just tried loading different panel states, didn't make any difference. My A310 appears to be dead 😦 I'm glad to hear that IniBuilds is looking into it. Edited December 28, 20232 yr by ndflieger Typo "...now let's get this thing on the hump - we've got some flyin' to do!" ~ Major Kong from "Dr. Stranglove" Scott Cebula
December 28, 20232 yr Try delete it from content manager and install it again Life time flight sim enthusiast, current airplane owner 172P (past C182F). FAA CP/IR ASEL/AMEL, FI ASELMy System: AMD Ryzen 9 9950X3D , MSI X870 GAMING PLUS, 64G RAM, ASUS RTX5090, 4T SSDPut my hands on (pic/dual/given)7GCAA, 8KCAB, BE24, BE76, BE35-C33, BE35, C150, C152, C172B/N/P/R/SP, 182F, M20E,M20C, M20J, AT6(SNJ4), PA28-140,PA28-151, PA28-161,PA28-181,PA28RT-201,PA28R-180/201T, PA24-250, PA32-300R, PA44, AC114, YAK-18T, YAK-52, SR22
December 28, 20232 yr Author Yes, that is going to be my next step. Thanks! "...now let's get this thing on the hump - we've got some flyin' to do!" ~ Major Kong from "Dr. Stranglove" Scott Cebula
December 28, 20232 yr Author I removed the A310 via the Content Manager, exited the sim and rebooted the computer. Started MSFS and reinstalled the A310 via the Content Manager and loaded the aircraft at an airport. Unfortunately, no difference. The aircraft is still dead. "...now let's get this thing on the hump - we've got some flyin' to do!" ~ Major Kong from "Dr. Stranglove" Scott Cebula
December 28, 20232 yr 4 hours ago, ndflieger said: I removed the A310 via the Content Manager, exited the sim and rebooted the computer. Started MSFS and reinstalled the A310 via the Content Manager and loaded the aircraft at an airport. Unfortunately, no difference. The aircraft is still dead. And an empty Community folder? That's really a stumper. I just flew the A310 yesterday and all went well. If there is some procedure to activate this bug, I have never found it. I know I have never touched any of the state-saving buttons. Rhett 7800X3D ♣ 96 GB G.Skill Flare ♣ Gigabyte 4090 ♣ Crucial P5 Plus 2TB
December 28, 20232 yr It's a bug introduced by MSFS with the latest navdata update. Ini already fixed it, but it's Microsoft that has to deliver the fix (which will take ages). For transparency: I'm a community mentor at the BATC discord. However, I do not get paid for it in any way.
Archived
This topic is now archived and is closed to further replies.