This update, again, mixed all my bindings for the cessna grand caravan and now i cannot even set the throttle/reverse thrust … its full up ot full down.
I have tried the sim just after the update, so the servers where probably overloaded with people playing and downloading, but it seems everything loads a bit quicker at least. At my lower end system I didnt feel or see massive improvement yet. But we’ll try again later this week and hope it was the server
MSFS 2024 (and 2020) seem to follow an in-house Asobo Alpha testing and development, then a Beta release to the dev community and user community. The part that is problematic is the direct to Full Release, even after a change to code and system requirements, without a testing phase.
I speak to the “requirement” to update to the latest NVIDIA gpu drivers and the release version 1.4.20, after all final beta testing was with 1.4.18.
Why is there no testing for a Release Candidate? The release of SU2 is again riddled with problems, CTDs, performance issues.
I do not believe that in-house testing of a beta release direct to Full release is a proper way to provide a stable product. There should have been a Release Candidate for devs and users to test that has minimal changes and no new external driver dependencies. If the RC is found to be problematic the make a change and make an RC2.
The next thing that I did not like is that the beta 1.4.18 was the last beta, where each beta had its own release document. This way as a developer you can home in on any changes and test. It is not helpful to have an 11 post release notes topic here, and hope developers can read it and find out what has changed in this last iteration.
I asked for a release document of changes for the differences between 1.4.18 and 1.4.20. I was told to figure it out for myself from the full release notes.
Please provide what changed in 1.4.20 from 1.4.18. If nothing then next time make it clear to all devs that the last beta was a Release Candidate.
Please do this for MSFS 2020 also.
FYI, there were only 2 changes between these builds:
https://forums.flightsimulator.com/t/su2-beta-general-feedback/713060/3466?u=smotheryvase665
I never thought I’d be writing this…
Did you also note too few trees in some places?
Hi,
SU2 is a big disappointment for me. I had hoped that MSFS 2024 would look better after the update. Sadly the opposite is true for me in VR.
Too many green blobs which eventually turn into trees at a one mile distance in VR.
I usually fly around Salzburg, Austria which is covered in a jungle. The surrounding mountains have trees where there should not be any. The meadows are a pale color instead of a lush green and the rocks of the mountains are brown instead of grey.
Not to mention how long it took me to assign my previously generated control profiles to a new aircraft.
So glad that I still have MSFS 2020 and X-plane.
When I open the EFB map and zoom in or out with the mouse wheel, the map no longer keeps the aircraft position in the center, and I have to manually click the recenter icon in order to turn it back on. This is very annoying and not acceptable with the number of times I have to zoom in and out of the map during the course of a flight.
I am not in, and never have been in the Beta, but this error persists every time I try to download the update.
Everything seems to work fine here, update went smooth. Only thing i can not understand is that they still did not fix the missing city markers. How hard can that be?
Same here - 15 hours later. Did you solve this at all?
Had three or four CTD’s in an hour just flying around and changing aircraft, had a WASM freeze in the ATR on startup and the performance is worse than ever (7800x3d, 4080s, 32gb ram, quest2). The SAAB340 still doesn’t show the route or fixes from the UNS on the ND despite being mentioned in the changelog. Oh well… let’s hope for SU3 to sort out at least some problems I guess
I’ve had had any ctd roll now and have had 3 in past hour
While performance and graphics are fine, I encountered 3-4 CTDs within 2 hours of using the SIM on SU2. I never ever had any CTDs before.
I have to say that I updated the NVIDIA driver from 576.28 to 576.40 before downloading the final release of SU2, so it might be an issue with the latest driver. I will revert to .28 if CTDs keep on happening.
Although I had a CTD upon starting a flight with the Inibuilds a320v2 I have observed good FPS and stability after the SIM has loaded and stabilised (downloading textures etc).
And although I have only spent a short time in the release, i feel like it is a step forward overall (a320 operated well, ground textures and good lod).
I’m optimistic that this sets a level for SIM update 3 - which I’m keeping my fingers crossed will be the one that makes me switch 100% from 2020.
Please sort out the regressions that have been mentioned and allow text scaling so that I can reduce text size and use it sensibly on my 40" TV.
A lot of people are frustrated that ‘their’ bug hasn’t been fixed yet (including myself by the way). Some bugs are very specific to use cases and others are in plain sight for everyone.. yet we’re still waiting for [BUG] to get a fix.
I think people really have to realize that MSFS 2024 was released way to early (I’d say about a year) given how many things are not working as should and given the inconsistency in quality overall, from core sim to planes and airports, stability and performance issues and even missing content.
They call them Sim Updates, as if it’s an update to an otherwise working product, while I think you should think of them as patches because they fix what was broken in the first place and they add functionality to the things that should have functioned at release.
I think that we as a community have every right to be angry/frustrated/sad about the state of the simulator and how it was released and it’s important to vent these emotions as well (if possible in a constructive way). I think we all want a good working product and be proud of our hobby.
I have to say that I can tell they are trying really hard to fix everything as fast as possible, given the long release notes and the fact that SU 3 Beta is about to start already.
I’m trying to remain patient and also keep letting them know what’s working and what is not (bug reporting) but sometimes I have a hard time understanding what’s been going on.
It should not have been like this, it’s not good for the hobby, it’s not good for the ‘name’ and it leads to a lot of anger and frustration… but, to end on a positive note; I’m hopeful we are getting there and I see a lot of improvements.
SU2 for me is okay so far. I had a CTD yesterday when trying to load cargo in the 748F, which I can’t reproduce. I’m instantly joining SU3 Beta when available.
Same here, never had to wait more the 5 seconds when switching peripherals. Now it’s 10+ seconds and once switched selecting a different profile on said peripheral takes 10+ every time. Switching from one plane say a single engine piston to a four engine airline takes 20+ minutes. Ridiculous!
VR certainly looks very washed out. When landing at 2024 3rd party airports the ground textures are very pale but when you get closer the ground texture tiles keep popping in and out which are richer in colour.
Just started to update, from SU1 to SU2, I have not participated in the beta, yet it is trying to install the feedback hub app? Is that normal?
The beta stopped at 18 so this seems to be a new and novel approach test/verification.
Real annoyed the update dropped with Asobo knowing the EFB was bricked on console with a controller. Can’t use checklist, can’t add fuel to aircraft, can’t look at map, can’t do anything associated with the EFB. If the EFB was like this on PC there’s no way they would have dropped the update to the public. Tired of feeling like a second class citizen for this game being on console.
Sad that hovering over undocked windows still disables all controls. When will this be fixed?
