You want to know what has to stop, little pilot ? People opening topics in General discussion digging up old versions and wining about past failures, without spending any effort to search for new information. The 466.63 link has been around for weeks now. It was put 20x or something.
I will wait. I have heard Nvidia is about to release 466.63a next week. The first release version will also have beta status and be marked by 466.63a-b1.01.2021. Let’s see, I can not wait to give it a try.
I have always kept my Nvidia drivers update and have yet experienced a CTD nor abysmal performance. While optimizing for VR, followed the hype and downgraded with little or any substantial improvement.
Of course, started tinkering with computers in the late ‘70s and PC’s in the ‘80s to the point were IT consulting became m livelihood, I really spend very little time tweaking my flight sim machine —- keep driver current, keep,OS current, keep running programs and background tasks to a reasonable amount and make sure FPS counters are turned OFF. If the simulation seems smooth to the naked eye, enjoy the flight.
At this point one should accept that none of this will ever stop.
Nvidia will release a new driver every 2 weeks and people will claim that version xxx solved all their problems but all the other drivers are ■■■■.
And btw I have just installed 466.63 - no difference again. All the drivers before were just as good in terms of fps.
P.S. The whole thing reminds me of the story of the bagel seller by Kishon. In which he thinks the baker fools him into buying only the old, lower quality bagels and spends his whole life trying to recognize the good one, only to find out at the end of his life that all bagels are the same. Not all drivers are the same of course, but it makes no real difference if you get one from 2 months ago, unless there was a major problem which almost never happens.
On my 2080 the latest drivers are performing equally if not slightly better than 457.30. There were a few in between which caused stutters, but this one is fine.
Whether you get 54Fps or 57Fps is not the point with this 466.63 release. What counts is stability. The issue is not framerate, it’s CTD’s.. a lot of drivers will (indeed) perform similarly on framerate. When you have a good GPU board, the CPU will be the limiting factor. the NVidia driver can only optimize CPU-GPU transfers, not improve your RAM or harddisk or CPU.
this is so true. I wonder what happens with all these complaints when every non-VR player would simply put a VSync-cap at 30Fps.. it will keep your device cool, your fan off.. and science sais an adult person won’t notice the difference with 35
fps cap has tremendous influence on temperatures that is true. I got average temperatures from high 70C to high 40s by setting frame limiter to my lowest to average fps.
It won’t occur to most people to set anything lower because they don’t measure temperatures or think that 80C is fine. Ironically both frame limiting and the low temps can increase overall performance. Overheating cards will throttle and with such high fluctuation one should better measure frames per minute/60 and set that as limit.
I had 3 CTDS within the last month and I don’t know if lower temps have anything to with that. But it’s something that I will keep monitoring.
I’m staying with 457.30 for now as it definitely gives me the best experience on my 2070 Super card. I keep trying the latest versions for a few days but so far none have beaten the old one.
The downside to keeping older drivers has recently been highlighted by the fact that Nvidia has said that drivers before a certain release are vulnerable to some security problems that can be exploited by hackers.
I’ve no idea how vulnerable it makes my machine (if at all) as I have a hardware based firewall and antimalware software scanning regularly.
Also this machine, which I use exclusively for MSFS is fully backed up with a disk image that allows me to reinstall completely in about 20 minutes (an image I took after a clean install of Windows, MSFS and with a “secure” later version of an Nvidia driver).
I can then just use DDU to reinstall the 457.30 driver again.
Your mileage may vary but it seems to me there are valid technical reasons why 457.30 was the best for a long time, and these are related to core system and drivers changes in all subsequent versions:
It is the last driver prior the addition of the HAGS setting
It doesn’t include the new NVidia FrameWave SDK (known to cause problems since its introduction)
It is among the last for which the release notes are not mentioning a performance bug with SteamVR
It is vastly reported for both 20XX and 30XX users as the one giving the smoothest stutter free experience, even more so in VR (not necessarily the most fps but this is not what matters the most)
Having said this, 466.27 is giving me close if not identical experience than 457.30 now, except a few things I can’t yet attribute to the driver or FS2020.
yes, indeed, and since msfs is coming to xbox too, why not, way way less hassle .
ofcourse there are drawbacks too, mainly mods …and in a short tmie pc’s are always faster, still..i play a lot on xbox, just like you tired of all the tuning.
Atlast for non-VR, there is absolutely no difference between the latest drivers. I have yet to see an evidence or benchmark that 457.30 is better than the latest driver…
A lot of us 457.30 users are preaching it because we use vr. As for people not seeing any difference with updates it probably is because your cpu or ram are holding you back more than the gpu.
Staying with an old driver is not always needed, when it behaves the same as 457.30 for you, replace it now by 466.63 I would say. Go with the flow. One day MS/Asobo will use a feature that requires 466.xx and distribute that with updates, or Windows will come with a major update in November.. NVidia will adjust things. As is the case with Windows, we’re a quite big customer ! People buy NVidia products because of MSFS. They’ll improve. So in the end you’ll end up with 466.xx anyway, or another future version that will be tested and found ok. We’re the guinea pigs, learn to live with it. The more people test the 466.63 version, the more development will benefit.
This kind of discussions give me flashbacks from fsx, jesus altuve and NickN’s guide, defragging the whole drive 3 times after installing, a long list of tweaks, that thing was hilarious. We spent three days setting up the system and bluescreen happened no matter what. What a time, what a time