I don’t want to presume anything about other people’s experiences but this is a new problem for me personally, only started seeing this after SU4 release
This happens on PC too. Making me regret paying 20 bucks for the longitude. It made me go back to the citation x
WHEN do we get a fix for this gamebreaker?
Any news from the beta testers? Is there a fix in SU5?
Flew 2.5 today after updating my PS5 Pro (which required a reboot) and also closing and relaunching MSFS to make sure it was a clean boot.
Dropped into free flight and immediately was having G5000 crashes on the Longitude. Throughout the 2.5 hour flight the AT disconnected dozens of times (eventually I just gave up and turned it off) and both PFDs, MFD, and all 4 GTCs all crashed dozens of times each.
Posted my images of these same crashes a couple months ago last time I played and became so tired of it I just stopped playing. I jumped back in today and was hoping it would’ve been fixed by now, but to my dismay it’s actually somehow worse.
Paid $130 for this game and it’s been broken since launch. ![]()
Same here. Flying any glas cockpit is a pain. They all crash constantly. You see them more rebooting than you see them operational. The longitude is an extreme example. And the broken avionics (Displays, Autothrust, APP-Mode losing track of a captured ILS glideslope) are this way since launch and NOT fixed. Also there is NO communication, when this will be fixed.
Neither is there an answer from the SU5-testers on xbox… I on PS5 can not test any beta, since we are excluded (like we are from the marketplace in fact). So I don’t see any reason to expect a fix in SU5 as nobody tells anything. Neither the devs, the mods nor the people who actually test the SU5 on pc and xbox.
Right now, flying any plane with modern instruments is NO FUN and almost unflyable. No real world pilot would set a foot into a plane, that has constantly crashing avionics, steeling the most crucial flight information in the most critical situations…
But yeah, we get psvr support, yay! To my mind this avionics issue should be much higher prioritized as it is right now - higher than adding new features for vr and so on. Right now, half of the vehicles are in fact almost unflyable. Yes, we can see the avionics crash in VR soon, … nice.
And the G1000… all planes with Gxxxx Garmin
All planes with glass cockpits. Even the Boeings… anything that has digital displays is constantly rebooting. It’s april rn, we have this constant rebooting now for too many months.
SU5 BETA on PS5 Pro:
Tested with a short flight (LOWK to EDDM) in the Vision Jet (because Longitude not available in beta):
While the overall performance of MSFS seems to have improved with SU5, the G1000/G3000 issue is NOT RESOLVED
The following faults occurred:
- Speed/Altitude Flags (unavailable) during taxi out
- PFD Settings Display reboot (Garmin Logo) during approach
- AT disconnect during go around
- AT disconnect during approach
- 2x SVT reboot/unavailable during taxi in
Why is this gamebreaker not a “must fix” bug for SU5?
SU5 BETA on PS5 Pro:
Cessna Citation Longitude, LOWW to EDDB:
Init/Taxi Out:
- PFD reboot (Garmin Logo)
- MFD Settings Screen reboot (Garmin Logo)
Climb:
- HSI Flag
- Speed/Altitude Flags
- AHRS align
Cruise:
- HSI Flag
- AHRS align + HSI Flag
- 5x HSI Flag
- 2x AHRS align + HSI Flag
- Speed/Altitude Flags
- HSI Flag
Decent:
- HSI Flag
- PFD reboot (Garmin Logo)
- HSI Flag
- PFD reboot (Garmin Logo)
- Speed/Altitude Flags
- PFD reboot (Garmin Logo)
Approach/Landing:
- Terrain Fail (GPWS)
Taxi In + Shutdown:
- -
Every issue lasts for around 5s.
(Photogrammetry, AI Aircraft, Fauna, turned off to lessen the load, all other settings default)
This was a fairly short flight with the Longitude, I don´t fly the plane that often (for obvious reasons) so the setup took me a little longer, however cold and dark to shutdown was around 2-3h.
25 faults in 2,5h that’s on avarage a fault every 5min.
For me this is game breaking, I can’t fly with affected aircraft
(which is more than half of MSFS included Aircraft).
In SU4 the only unaffected glass cockpit airplane was the SR22, I didn’t have a chance to test it in SU5 BETA yet.
Comparing SU5 BETA to SU4:
The glass cockpits don’t crash fully anymore. But the crashes of functions in the glass cockpits (Speed, HSI, AHRS…) are more frequently.
At least for me…
Is this issue not fixed on SU5 Beta?
I tested it last night and it isn’t fixed unfortunately.
This is bad. This equipment is needed for navigation.
Today it has failed me over and over and once each on take off and landing. ![]()
So now we can celebrate crashing avionics in psvr2… yay… How can psvr be a higher priority than an actually working game for SU5 ?!!! I am very dissatisfied with the situation !!! 3/4 of the vessels unplayable by unreliable avionics. Great!
This is not WE PAID REAL WORLD MONEY FOR! What’s the next more important thing on the fixing list? More beautiful clouds? More shiny reflections? Better audio? Or is it an actually working game?! I can’t find any words for my disappoiment that there is no fix for this gamebreaker in su5. How can this be okay for the internal game testers and devs? Don’t they ever boot up their compiled code and see what is actually going on in the planes?
@Mods: Can you please emphasize this issue to the devs ?!
And this is not meant offensive, it is just huuuuuuuuuge disappointment about a broken game, where new advertisable features are more important than actual fixes - sold for over 200€ ! Almost 3 times more than any new AAA title.
Yes, this one in CJ4 and the “Mission failure for straying off plan” in PS5, got me today, I am seriously miffed too. Everytime I try Career mode something crashes the mission. ![]()
I am pretty bummed too. I think because there hasn’t been much talk about these game-breaking bugs, and since there aren’t many PS5 players on the forum, the issue is just flying under the radar. It either hasn’t been noticed yet, or there just aren’t enough people running into it for them to bother fixing it.
It is bug logged, so they have to know about it. Just ignoring it or don’t know how to fix it? I wonder if this is a Working title thing or Asobo and which one broke it?
And now we need to wait for SU6… SU7… SU8… SU20 to get a playable game, that we paid for many many €/$/£/¥?
Guys, let’s stay fair here.
First of all SU5 is not released yet, we are currently only talking about SU5 Beta.
Secondly, the developers are definitely working hard on improving the game and in SU5 definitely some progress can be seen.
Multithreading was improved and planes which were previously effected (NXCub) don’t seem to be effected anymore (judging by my limited testing of SU5 Beta, around 10h)
Also please keep in mind that MSFS is quite a complex simulation and the developers managed to get it running fairly stable on 400$ Hardware!
(PS5 and PS5 Pro share basically the same CPU+Memory only GPU is majorly improved)
After testing on SU5 BETA it looks like the crashes happen when the PS5 is running out of compute power / memory. Furthermore with the new multi threading it can be seen, that it is not a single point of failure (AHRS,HSI,Speed, etc.). Instead it is different systems which fail depending on which one needs a lot of compute at the time.
So I don’t think there is an easy “fix” for this, other than performance optimisation of the whole game. This needs a lot of work, if it even can be done.
I definitely don’t want to down play this bug.
In my opinion it is by far the biggest issue the game currently has.
It makes many planes unflyable (if you want to follow realistic procedures).
However there are also many planes which are not effected by this bug and I guess we have to accept the there is no easy fix and give the developers some time.
So like I said, let´s stay fair to all the developers who managed to bring this game to PS5 and who continue to improve it constantly.