Changing a graphics card counts as a different PC, the same goes for the CPU. Oh, you can run it on up to four "different" PCs, but after that you get locked out for 24 hours. Our biggest complaint (about the DRM, not performance) is one that literally only affects people like us that benchmark games: It's tied to your PC hardware. We couldn't even install the game there because "another version of the game is already installed." So, backup the Steam version, uninstall, and then download the 133GB of data again. If you're going to release the game on Steam, Epic, or other launchers, do the work to make it function fully within that environment!Īlso fun: We borrowed a friend's account ( Aaron's, if you're wondering), which was not the Steam version but was instead purchased on the EA launcher. This sucks, and the same goes for Ubi games or products from anyone else.
and then still had to install the EA launcher app to play it. Like so many other EA games, Star Wars Jedi: Survivor has some draconian limitations on what you can do with the game. To see how the game now runs, we've tested the PC patch 3.5 version on some of the best graphics cards.įirst, let us rant for a moment about DRM. But patches and driver updates have landed that are supposed to fix some of the most egregious problems. As an AMD-promoted game, and one that AMD has used to suggest cards with less than 16GB of VRAM aren't sufficient (which would include its own RX 6700- and 6600-series parts), we probably shouldn't be surprised. Star Wars Jedi: Survivor officially released on April 27, and complaints about poor performance, stuttering, and excessive VRAM use appeared virtually seconds later.
0 kommentar(er)
