I don’t believe that to be the case no, artificially hampering features in old PC’s on this product in order to get them to buy an xbox is not something MS would bother with, hell I don’t even think MS wants to sell the xbox hardware per se, they want to sell gamepass as it’s making them a fortune and rightfully so it’s great value for money but I don’t think they care what platform you buy it on. I’m not a dev let alone a gfx technologies specialist so I can only guess that there is some feature implemented in the gfx engine which simply does not work with older GPU’s and causes this glitch and I’m not convinced Asobo themselves have an explanation for it. Maybe only Nvidia does but if there is certainly one conspiracy theory that we can entertain then that may indeed very well be that Nvidia has no interest in providing Asobo with a fix or explanation assuming that conversation would even be had as we can only speculate what happens when it comes to addressing issues like these but assuming they do they most likely would indeed be limited to maybe only a few generations of hardware, in practical terms if this happened on the 2000 or 3000 generation HW Nvidia/Asobo would be working overtime to fix it. On the older generations of hardware we are clearly at their mercy and I’m sure that they know very well that if they don’t fix it a lot of us will end up fixing it ourselves by throwing money at the problem because clearly that will fix the issue. But here’s hoping it doesn’t come to that coz 2020 has been rough and new hardware is not something many of us currently have the budget for. And hell if you do GL actually being able to find stock!
Let’s all make the zendesk report, made mine yersterday
Having the same problem with a GTX Titan Black; have reported to zendesk. It would be extremely disappointing if they stop supporting Kepler/Maxwell cards any time soon, as the top-end ones from that range have almost the performance of their recommended GPU, the GTX 970, far higher than minimum spec.
Very interesting. I have the GTX770 2Gb card. I will check the details tomorrow and report back here.
Of note, I had no issue at first after the update and completed two hours in the Mod G36 turbo. Its seemed after this time it was when I pressed ESC to go to the menus and returned was when the flickering cloud started. Since then it has persisted
I have 970M and I have this issue on FXAA or DLAA, but the problem is solved on TAA or OFF.
Edit: are we talking about sky color or something else? I see post for two different issues.
It is actually about the flickering clouds, you can see a demonstration of the issue in this thread.
The second poster confused this with the colour grading issue that happens with FXAA and DLAA.
Your GTX 970M is utilising the Maxwell 2.0 architecture, which means you are not affected by the flashing cloud issue.
Yes CS I agree. I have run on my GTX770 since day 1 (Sep 18) with around half of my settings on Medium with a few on High and have enjoyed the experience with average of 20-35fps and only a handful of CTD in two months. If clouds graphics have not changed something has
I have the ASUS ROG GL552VW with a 960M. It is unfortunate that the update invalidates all the support we have given to MSFS over the years. I purchased a PC clone (Seequa Chameleon) in 1981 and used Flight Simulator as the litmus test formPC compatibility. My only suggestion request short of asking Asobo/Microsoft to maintain compatibility with these older GPUs is to allow us the ability to revert to the last version so that we could have use of most of the features we paid for. It seems there are those of us who purchased MSFS 2020 who may not be able to upgrade our systems that would very much appreciate this option. It seems that during the automated update process this could be a decision point in deciding which sim version is installed. This is already being done by MS. My windows 10 will not update to 2004 yet due to my hardware. It seems that there are a significant number of us impacted by this.
I have a GTX 960M, turning the TAA on doesn’t make a difference. Looks like I will be going back to Steam for refund.
Is there a way to download a version the FS2020 pre patch #5 update?
He is talking about the AA of the Nvidia panel, not the AA of MSFS game. You need to turn the Nvidia ones OFF.
Same problem here since last FS2020 update.
Unfortunately there is no way to download an older version of the game. The only thing we can do is submit a Zendesk report and hope they will change their mind on this. The more people send a report, the better our chances are.
Ditto, I have a GTX 750TI and cloud flashing started yesterday.
2GB gpu and 6GB mainboard ram, giving a total allocation of 8GB.
Xeon cpu, barely more than one core used (one thread + kernel overhead), 16GB ram.
With Xplane + Vulkan I was getting 40+ fps.
I was getting 20-30 FPS in MSFS with Render scaling at 70% and the rest of the settings a mix of low & medium. Not perfect, but was playable. (Kepler based Quadro K4000 in my system)
Now with the cloud flicker issue, it is only possible to fly with clear skies enabled.
This does not make the sim 100% obsolete for me, but close to it.
I have been simming a long time, and while flying in good weather is nice - the challenge and looks of “bad” weather are essential to a flight sim for me.
Fortunately I have another sim installed on my rig as well, which runs between 20-45 FPS at almost maxed settings and has weather…
I think it is great that ChaoticSplendid is trying to wake up Asobo not to forget about those of us with older, but still fairly good systems.
Just it would be nice if there was a few more replies to this topic. The more voices, the more likely we get a bit of a time extension till our systems become obsolete for MSFS…
There are a few duplicate topics…I think I’ve found all of them but I’m hoping there’s enough to be a ‘critical mass’ of users affected.
I too am currently flying in clear skies only. Not the same!
Same over here. Gtx980Ti. DLAA got broken with the 1.10.7 update. In bright sunlight, clouds and horizon are awful. The bloom around the sun is no longer under “bloom” but under “lens flare” instead (really??)
No flickering clouds.
Those are the remaining ones I think, there were also a couple of replies in the Update #5 hotfix discussion thread, but they are kind of lost among other posts complaining about different problems.
I agree. I am in it mostly for the visuals, and not being able to enjoy the clouds and the way they affect the lighting, which is one of this simulator’s most gorgeous features in my opinion, is a huge blow. It also means I cannot play the Halloween challenge since there is no way to modify the weather, and even then I would be missing on the spooky cloud formations. Even if the issue is fixed eventually, the challenge will be removed in next week’s patch…
Unfortunately the amount of voices can only be as big as the amount of Kepler and Maxwell 1.0 users. While we are probably almost nothing compared to the entire userbase, based on the responses I’ve seen in the last two days I think it could be enough for Asobo to step up and do something. As always, the most direct way to communicate with the developers is Zendesk, and once they catch up with the reports we might get an update on what is going to happen.
Personally I’m not going to contact live support since they would just tell me that my GTX 750 is a lower number than the minimum GTX 770 even if it is a newer architecture, so I would suggest people using the GTX 780 Ti, GTX 960M or similar to contact support again once our Zendesk reports are marked as “Solved” I presume.
I don’t have a dog in this fight but this doesn’t seem legit. You bought a game with the understanding that you met the minimum requirements at purchase. They should offer you a full refund if this is the case.
Unfortunately it appears someone else with the same issue was denied a refund.
Same issue, discussed under the thread “flickering clouds”. With a GTX Titan I was getting 30 -40 fps GA flying. Everything was running smoothly. Till the patch.