{"id":1106,"date":"2023-05-05T00:20:05","date_gmt":"2023-05-05T00:20:05","guid":{"rendered":"http:\/\/engadget.vip\/?p=1106"},"modified":"2023-05-05T00:20:05","modified_gmt":"2023-05-05T00:20:05","slug":"wolfenstein-2-the-new-colossus-pc-settings-and-performance-review","status":"publish","type":"post","link":"https:\/\/engadget.vip\/?p=1106","title":{"rendered":"Wolfenstein 2: The New Colossus PC Settings and Performance Review"},"content":{"rendered":"
<\/div>

Wolfenstein: The New Order<\/i> was a pleasant surprise to me, managing to have good shooting (without being a cover shooter), solid but inessential stealth, and a solidly told story. Also, if memory serves, it ran really rather well and looked a bit lovely too. Wolfenstein 2: The New Colossus<\/i> appears to be following in these footsteps rather well, based on 90 minutes of both playing the game and fiddling around with visual settings.<\/p>\n

I\u2019m going to do my best to explain most of the visual and control-y stuff here, but as ever, there is a minor issue in that my computer could probably have a go at arm-wrestling a minor deity. I have an i7-3820, 16GB RAM, and GeForce GTX 1080 Ti. Basically anything should run fine on this setup \u2013 although from what I\u2019ve seen, I think<\/i> that Wolfenstein 2<\/i> should run alright on significantly lower specifications.<\/p>\n

\"\"<\/p>\n

Also, LASERS.<\/p>\n

Two brief notes, though. First, the review build came with an accompanying list of known issues, most of which should be fixed by launch. Nonetheless, this does mean that there may be some issues I have that you won\u2019t, or \u2013 indeed \u2013 some issues that crop up in the launch build which aren\u2019t in the pre-release build. Secondly, Wolfenstein 2<\/i> currently doesn\u2019t support the Steam overlay. Achievements are in and work fine, but this does mean a lack of screenshot functionality, amongst other things. I\u2019m not<\/i> sure this\u2019ll be fixed by launch, but it is apparently being worked on.<\/p>\n

Alright, enough chatter. HAVE SOME MENUS IN YOUR FACE.<\/p>\n

\"\" \"\" \"\" \"\"<\/p>\n

Lots of stuff, there. Not on the fanciest of menus, but that\u2019s a pretty minor complaint when I get three pages of things to fiddle with. In terms of basic stuff there\u2019s Vsync, motion blur, anti-aliasing, and quality presets (ranging from \u201cLow\u201d up to \u201c\u00dcber\u201d and \u201cMein Leben!\u201d).<\/p>\n

Delving into the advanced video options reveals far more, including mysterious tweakables like \u201cDeferred rendering\u201d and \u201cGPU culling.\u201d I don\u2019t know what half of this stuff does, and the descriptions are generally amusingly unhelpful (Material Aniso Filter changes \u201cthe material textures anisotropic filtering quality\u201d), although a few are vaguely useful. If memory serves, GPU culling\u2019s description basically explains that it culls certain triangles and reckons \u201cTurn this on if you have an AMD card and off if you have a GeForce card\u201d, which is basically what I need to know. Again, there\u2019s no texture quality setting that I can see, which means we may have moved into an era where that\u2019s not a thing. At least not in Bethesda games.<\/p>\n

And yes, there\u2019s an FOV slider, which comes complete with a warning that changing it might cause some graphical artifacting. By default it sits at 90 which feels okay, although I was a bit happier once I ramped it up to 100, and didn\u2019t notice any real issues there. Push it up to its maximum of 120 and you get plenty of fish-eye weirdness and some other oddities, what with BJ Blazkowicz having a visible body at all times. The difference in the below shots is pretty noticeable, but the oddities are easiest to see in the third shot.<\/p>\n

\"\" \"\" \"\"<\/p>\n

Handily, considering the lack of Steam overlay, there\u2019s also an in-built set of performance metrics, which means I can talk FPS. As with The Evil Within 2<\/i> I have no idea what a fair bit of this stuff means, but I\u2019ve left the full metrics on in these screenshots. Perhaps you can divine more information from them than I can.<\/p>\n

What I can say is that, with the settings on Mein Leben (but a few personal stylistic bugbears like Motion Blur turned off for the sake of not having horrific screenshots) and the resolution at 2560\u00d71440, the framerate sits pretty happily around 120-130 FPS. Busier segments occasionally drop it further, with the lowest I\u2019ve seen being around 90, though that only lasted very briefly. Low settings boost the framerate by around 30-40FPS. Again, with an average framerate above 100 this doesn\u2019t feel like a major difference, but it might indicate something about Wolfenstein 2<\/i>\u2018s scalability.<\/p>\n

\"\"<\/p>\n

DOUBLE GUN-ISHMENT.<\/p>\n

The easiest comparison I can make is probably in the scene below, which I\u2019m also using to illustrate the differences between Low details and Mein Leben detail. It\u2019s not the best example \u2013 combat, with explosions and lasers and lighting effects and gore, would likely provide a bigger visual difference \u2013 but trying to capture the exact same scene twice in battle is a bit more problematic.<\/p>\n

\"\"<\/p>\n

High.<\/p>\n

\"\"<\/p>\n

Low.<\/p>\n

In any case, full visual detail here gives us 128 FPS, while Low ramps it up to 169 FPS. With the framerate constantly updating there\u2019s some variance either way, so those aren\u2019t hard numbers, but they\u2019re within a few frames of accuracy.<\/p>\n

Visually speaking, things don\u2019t actually look bad<\/i> on Low. Assuming I\u2019m not an idiot, that Low screenshot was taken after restarting the game (as certain settings don\u2019t have an impact unless you do that). The big differences are in the smaller details: the quality of the shadows, the lighting on the doorframe, and so on. Again, this doesn\u2019t seem to have any sort of texture quality settings, which means close up views don\u2019t always look mind-blowingly detailed, but the general effects are still really rather nice. Bits and pieces like extra detail on the shadows of, say, a cotton reel in a box of miscellaneous items do help, even if only in marginal ways.<\/p>\n

\"\" \"\"<\/p>\n

I don\u2019t have many issues with control definition, thankfully. Some controls are bound to the same key regardless of what you do \u2013 iron sights and fire left weapon will always be the same button, for instance \u2013 but everything is redefinable, and the controls themselves are simple enough to use. The one potential issue comes with the weapon wheel, which can generally be ignored in favour of the number keys, but comes into play more havily with dual-wielding. You can dual-wield basically any weapon by tapping the number key twice, but if you want to dual-wield a combination (a pistol and an assault rifle, say) then it looks like you need to use the wheel to select your second weapon. A minor issue that hopefully won\u2019t cause too many issues during actual play, though, and there is<\/em> a button dedicated to left hand cycling, though it\u2019s not one I\u2019ve experimented with overmuch as of the time of writing.<\/p>\n

As far as I can tell, then, this is a pretty strong showing for Wolfenstein 2<\/i> on the PC. It\u2019s plenty scaleable, runs smoothly, and handles just fine on a mouse and keyboard. The second-weapon selection may<\/i> prove to be a pain in the arse and I have a few minor issues with the lighting (specifically, exposure when looking into dark areas while standing somewhere brightly lit) but I\u2019ve seen nothing that\u2019d encourage me to warn you off.<\/p>\n

\"\"<\/p>\n

No need to do this to the developers, apparently.<\/p>\n","protected":false},"excerpt":{"rendered":"

Wolfenstein: The New Order was a pleasant surprise to me, managing to have good shooting (without being a cover shooter), solid but inessential stealth, and a solidly told story. Also, if memory serves, it ran really rather well and looked a bit lovely too. Wolfenstein 2: The New Colossus appears to be following in these […]<\/p>\n","protected":false},"author":1,"featured_media":1107,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[1406],"_links":{"self":[{"href":"https:\/\/engadget.vip\/index.php?rest_route=\/wp\/v2\/posts\/1106"}],"collection":[{"href":"https:\/\/engadget.vip\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/engadget.vip\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/engadget.vip\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/engadget.vip\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1106"}],"version-history":[{"count":0,"href":"https:\/\/engadget.vip\/index.php?rest_route=\/wp\/v2\/posts\/1106\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/engadget.vip\/index.php?rest_route=\/wp\/v2\/media\/1107"}],"wp:attachment":[{"href":"https:\/\/engadget.vip\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1106"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/engadget.vip\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1106"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/engadget.vip\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1106"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}