Give it a few days. The step forward is definitely there, it’s just not working correctly yet. Unfortunately.
yeah I kind of figure that was the case.
Patch list looks impressive - clearly been working on this whilst the release has been brought to market in parallel
unfortunately for me that is not the case. In Controls menu, trying to assign key bind to my Alpha and bravo, the sim just hangs. only doing this because after the update, all my settings and log book was wiped out.
I’m rather thinking that this is proof of what @Coppersens tries to explain above, namely that the beta group was a big success!!
We were talking about the Legacy cockpit interaction system. You’re talking about something entirely different.
I stand corrected. Just noticed that ![]()
At least they are listening, thats encouraging but they really need to address the graphics nerf and give us more control over it. Its ok if you are just coming into the game now, but when you saw what it used to be like in SU4, its a big disappointment over something that was core to the attractiveness of the game and probably got many people upgrading their system to enjoy it.
Its actually very weird for a game to have a graphics nerf, I don’t think I’ve ever known a game patch to nerf its graphics.
I wouldn’t say a big success since I never participated in any beta that I’d call this way ![]()
But clearly the devs are not sitting weeks when the scope of a build is complete and waiting for the release until they start working on the next update or patch. They are continuously monitoring the feedback, reproducing issues, finding fixes, doing more tests, committing the changes.
And at some point there is a decision made whether shortly before release a fix is to be included (risking regression and stability issues) or if it’s okay to postpone it.
That’s just how ANY beta works. It doesn’t make it a big success, but neither is it just show. It’s just a way of working with given boundaries (manpower, timelines etc.).
They certainly will. Just that CTDs and severe fixes as well as very limited small glitches have a higher priority for a “hotfix”.
Changes on the engine or the graphics setup require thorough testing again, so don’t expect such things to be delivered with a hotfix. It’s not like the sim is unplayable (opposed to when having CTDs) - we will have to live with the current graphics state for some weeks at least, I guess.
As written above, it might as well be that there is already a fix for the LOD in development or even ready and in testing, we will never know.
Options > general options > accessibility
Decrease interface scale and minimum text size.
Tried that, makes the rest of the interface unreadable.
Now it’s official.
Hotfix Friday at 1500Z
I’m not invisible so I have to be more cautious than you… But to be honest, I don’t experience any issues that would keep me from having an enjoyable experience, at least for a week or two.
Yes, I can see many people are suffering severe CTD issues - maybe I’m just lucky, but CTDs don’t seem to affect me that much. I did all I could to alleviate the situation before updating to 1.18.13 - emptied my Community folder, added back the add-ons one by one only after downloading an SU5-compatible update, deleted Content.xml, and disabled all traffic. This may not be sufficient for other users, I know, but I only had a couple of random crashes on the 27th, in the hours after the release, afterwards I was fine except for very few CTDs when loading a flight with the FBW A32nx. From what I could gather, this is a known issue with the A32nx. The random CTDs I had seem to be correlated with the server load, at least that’s my working hypothesis for now ![]()
The altitude issue is certainly annoying, especially for those flying on VATSIM, but for others too. I don’t use VATSIM yet, and for the time being I can reduce the impact of the bug by flying in standard pressure / temp. Far from ideal, but makes it bearable for some time.
I don’t mind some scenery popping in a second after I pan my view direction, I really appreciate the smoothness and boost in fps, especially when flying in a glass cockpit in demanding scenery such as NYC. I don’t think the situation is ideal for those with high-end hardware, using all possible tricks to keep VRAM usage below 6 GB (and RAM below 10) when there’s plenty available. I’m pretty sure though that this can be tuned quite easily in the future.
There are plenty of other minor bugs and issues, but they’ll get resolved in due time. One thing I really hate though is the overexposure of the sky. In the cockpit of the DC6, which is relatively dark, the landscape is exceedingly bright when I try to keep some instruments in my field of view. I tried some of the suggested usercfg.opt settings, and played around with the sliders in the Radeon Software, but to no avail.
So yeah, it seems I’m a bit luckier than others, not suffering from constant CTDs, I don’t deny SU5 has its issues, but hey, I enjoy that my flights are a lot smoother than before, even after going from High to Ultra. Some of the bugs and issues are more annoying than others, but for me the sim is far from broken.
You just followed the path as paved out by our dear CM! And it worked? Now that’s magical, don’t you think?
Same here!
Thanks for posting.
Nobody is angry about the performance. Everyone welcomes the performance improvements. The issue is they FORCED the reduction of graphics on EVERY setting, and that’s the only reason why people are vocal and angry, and rightfully so.
Nevermind the fact it’s not a “little soft here and there”. It would be a nonissue if they just included the option for such thing, so people who prefer performance can get their performance, and people who prefer the graphic quality can get the quality. People right now who prefer the graphics are forced to pay the price for performance, and that’s where the issue is.
Hehe yep, but I think there are some issues that also affect people with an empty community folder and without add-ons. Anyway, for now I’m using the updated WT Garmins (including the new experimental NXi), the G530 mod, Bijan’s trees, Ither’s NoHandleBar mod, the DC-6, the A32nx (which worked ok if I made it into the flight without a CTD while loading), the JustFlight Arrow, and various add-on airports. Now that I think of it, some of these airports exhibited some flickering and texture issues - but no CTDs due to airports yet.
Thanks again for this great post!
I’m sure that something in the core was amiss. Hence the patch. Bu even with this patch people with non-updated stuff might suffer the same issues, I’m afraid.
Good to know re. airports. I’ve been holding off adding any of my payware ones - though it’s made me visit a few of the in-game handcrafted variety that I hadn’t got round to before.
I too haven’t had any major issues with this update, though I’m using hardly any add-ons until they get updated. I don’t like the pop-in, but haven’t seen it that much - it’s not a major issue for me (though I understand people being annoyed with Asobo, because they definitely gave the impression that nothing would be downgraded to pay for the performance improvement). Other than that, though, graphically it’s been good. Running everything at ultra or high now and still getting 50 fps.
Hope the patch fixes things for those having problems.
I suppose the hotfix / patch was already planned before the release of SU5. In a project this size you can’t just push a last minute fix to a build, everything takes some time for integrating, testing etc, even when they already have a working implementation internally.
Yeh I did that before I started the update, and made sure windows was up to date, updated any items via the MS store, rebooted, shut down all apps including anything on the taskbar and basically left MSFS to use all the resources as unhindered as possible. Ended up reinstalling the whole sim because the update got stuck in a loop again. Despite all the time and frustration that caused I have still ended up with a sim that simply CTD’s as the UI is about to load/appear.
I am certain a lot of issues are not helped by users, but when then forum is buzzing with a prominent problem then clearly something unexpected or undetected during testing is going on. I don’t think a short official post acknowledging the existence of such an issue is a bad thing and would perhaps encourage those suffering the problem to submit support ticket. The devs would have more information to work with and would at least promote a proactive and constructive user interaction rather than a reactive rant.