Shunt modding as a possible factor?
A few sentences I would like to lose now to “shunt modding”, which by the way also I made it at my RTX 3090. This mod allows the card to draw more power than originally intended by Nvidia, e.g. 600W instead of 400W, and thus achieve higher average performance.
However, it has to be said that the voltage regulation of the card can normally handle this without any problems and only the efficiency and arguably the longevity of the card suffers. However, no damage, overloading or destruction of components will occur. And also in the case of New World, a cleanly executed shunt mod would not make any difference, if the cause is really the ultra-short spikes. Because if the monitoring is not fast enough to intervene, it doesn’t matter what the threshold of the monitoring is set to.
Now you might say, “Oh that’s old hat with the incredibly high FPS, that’s exactly what FPS limiters are for, whoever doesn’t cap their FPS has only themselves to blame and nobody needs more than the monitor’s refresh rate anyway!” But again, the situation is not so simple. I’m going to go out on a limb and confess that I’ve never heard of using an FPS limiter to protect your graphics card from overloads. Even if I start a 20 year old game for the sake of nostalgia that runs at hundreds or thousands of FPS thanks to current hardware, I’ve never worried about my GPU.
Likewise, there are games, especially in the “competitive” realm, where you deliberately don’t use an FPS cap. The well-known FPS game Counter Strike: Global Offensive often reaches framerates of more than 400 FPS and is used without G-Sync, V-Sync or any limiters to simply guarantee the fastest possible updates on the monitor. The pro-gamers don’t care how broken or torn the picture looks, as long as they can react faster than the opponent.
Amazon is not aware of any guilt
Meanwhile, Amazon has also released a statement on the issue with New World:
Please read this message regarding recent concerns with graphics cards hardware. pic.twitter.com/L1gNeBBPQS
— New World (@playnewworld) July 21, 2021
In other words, from Amazon’s point of view, this means: We use the DirectX API like any other game, so it can’t be our fault. They say that the game is safe to play, but at the same time promises an FPS limit for the game’s menu as insurance.
Here we see on the one hand again a hint that speaks for the theory with the high FPS and ultra-short spikes, but on the other hand – if you’re honest – Amazon clearly wants to keep up the hype momentum of the game. They can afford it, because in case of doubt it’s not their GPUs that die or they are not liable if cards have to be replaced. Their legal department also knows what they are doing, as is well known from various other stories about the handling of warehouse workers, but that is another topic..
Recommendations and a plea
Back to the real problem and a possible solution. If the cause is really the very high FPS and the resulting spikes, then Nvidia could solve the problem relatively easily with a driver update as follows: Nvidia sets a FPS limit in the driver as a new standard, e.g. at 1000 FPS, beyond which a card cannot go by default. Only by manually changing the setting in the driver and confirming a warning of possible damage, a user could deactivate this limit. Of course, the disabling capability would be extremely important for diagnostic purposes or benchmarking.
So if you now have one of the EVGA cards with the questionable fan controller that burned out, or any other card that died to New World for that matter, you can of course contact support under normal warranty and get the card replaced. And to all those whose GPU is still alive, but who really want to play New World right away and can’t wait, they should urgently use an FPS limiter, like the one in the Nvidia driver.
That were my 2 cents on the matter. I only ask every reader to keep open ears and eyes and not blindly trust the statements of individual sources – actually a general principle of the internet. The cause of all New World casualties has not yet been confirmed with certainty, and until that changes, it’s better to be safe than sorry.
47 Antworten
Kommentar
Lade neue Kommentare
Veteran
Mitglied
1
Urgestein
Veteran
1
1
Veteran
Urgestein
Neuling
Veteran
Urgestein
Urgestein
Veteran
Urgestein
Urgestein
Urgestein
Urgestein
Mitglied
Alle Kommentare lesen unter igor´sLAB Community →