First and second flight on a new installation of MSFS 2024 with no mods or addons. MSFS 2020 is also installed on this PC.
Cessna 172 Skyhawk does not have functioning electrical systems. Could not start engines after following startup checklist and current gauge indicates 0 regardless of lights or fuel pump. Lights, fuel pump, and starter are also non-functional.
When starting a new flight in the air, the engine is running but most avionics are not functional and no lights nor avonics (except for one garmin device) are functioning. In the image I have lights ON, yet the current indication is that 0 amps are being drawn, and no lights are on in the exterior view.
I wanted to add that after some frustrating attempts to fly the 172 G530 and 150, I had a wonderful experience with the 172 G1000 and the new atmospheric effects and lighting are fantastic. I absolutely loved that flight.
Isn’t it incredible? One of the primary aircraft of the MSFS lineage through the years and it is broken on day one. Sad to see this, because I have the same problem and it amazes me how this got through to release day. Was BETA testing a pool of a few people?
I am also having the same problem. I can’t start with Ctrl + E or with the checklist. This is very frustrating. I’ve been waiting hours for the Sim to load and now this…smh.
Same exact issue. I can turn the power on and the 430 powers up and I see annunciator lights. However the fuel pump won’t turn on, the starter won’t energize/engage, CTRL+E also does not work. Avionics will not turn on either. Analog Basic 172 for what it’s worth.
I enabled dev mode and checked the console logs. There’s a bunch of Eletrical errors in the airplanes configuration file like:
[Error] Couldn’t find a component with name: “flapsmotor” make sure it is defined before it’s being referred to ; while parsing “Name:BUS_1_To_FlapsMotor # Connection:Con_CB_10A(BUS_1,FlapsMotor)#WearAndTearCollision:NoseDamageHigh,TailTopDamageHigh,TailBottomDamageHigh,LeftWingDamageLow,RightWingDamageLow”
File: SimObjects\Airplanes\asobo_c172sp\presets\asobo\c172sp_classic_passengers\config\systems.cfg
Now how did that get out with those errors is beyond my comprehension. Can only imagine files got corrupted in their server cache â– â– â– â– and is serving us bad files.
Same issue. I thought it was me. Completely unacceptable for the most iconic plane is broken on day one. Its almost like they’ve given the simmers who start their planes cold and dark the finger. Insulting. My co-worker with the worse performance review in the company could have found this problem during testing.
Do you guys see the upwind end marker in career mode, cause I don’t. Can’t even get past the familiarization flight I can see the marker but it’s 3400 nm away.
What is really annoying is that since those files are now in the cloud we can’t even fix them! At least your post motivated me to go figure out how to turn on developer mode lol.
It’s amazing that they can’t even get a basic aircraft like this to properly work. There seems to be little to no quality control and testing with this project.
Can confirm all the same issues. Top Garmin does not turn on, no lights at all, wont start, fuel pump does not turn on, autopilot, and transponder also do not turn on, crono doesnt work. Crazy… Just fix this please.
There are currently 8 total threads in this section of the Bug Reporting Hub about this issue with the C172 (basic), but this one has the most votes and attention.
That’s a lot of helpful beta testers, hopefully they can get this fixed before it sh… oh wait…
