Amazon’s latest game New World kills GeForce RTX 3090 GPUs



[ad_1]

Amazon has tried to break into the game with internal efforts for the past two years. However, the business was not overly successful. Last year he released Crucible after six years of development, and shortly after its release, it sent the game back to beta before canceling it altogether. But that’s not as bad as some gamers are reporting with the company’s latest game. Several users on Reddit and the game forums (via Games pot) reported that New world brick their EVGA-branded GeForce RTX 3090.

The problem appears to specifically involve the EVGA RTX 3090 FTW3, which is by no means an affordable GPU. The Founders Edition of the RTX 3090 already has an MSRP of $ 1,499, but this EVGA model actually costs $ 1,889, according to the EVGA website. And considering GPU price inflation over the past year or so, there’s a good chance some gamers have spent a lot more than that. User reports mention that the game suddenly stops working in various scenarios, so it doesn’t appear to be triggered by a specific action.

Most of the reports seem to be from EVGA users, but some have also mentioned the same issue with Gigabyte’s GPUs. It seems like New world causes severe overheating of RTX 3090 GPUs, and the New world the team has since responded to the game’s forums. The developer has acknowledged the issue, and for now it is recommended that users turn off all overrides set in the graphics settings of the NVIDIA Control Panel. The company also suggests limiting the frame rate to 60 fps in game settings to reduce GPU usage. However, he said nothing about a permanent solution.

In fairness to Amazon Games, this is a beta version of the game, so some issues are expected. However, with New world slated for release on August 31, breaking a GeForce RTX 3090 GPU is a serious issue at this stage of development. Hopefully the company will release a patch soon and GPU owners can get a replacement pretty soon. This could be tricky given the number of reports and ongoing component shortages, however.

[ad_2]

Source link