The lack of shadows is the only truly noticeable change, but for an experience that is outside the bounds of what the game supports, it works rather well. There are drops in moments of extreme intensity, but never low enough that it becomes unplayable. Doom Eternal is able to keep mostly to 60-45 FPS during intense combat while still looking surprisingly acceptable. I'm testing with the GPU at stock clocks, each setting adjusted to the lowest possible value, running at 1080p but with the resolution scale set to 50% (960 x 540 rendering resolution upscaled to 1920 x 1080). The Vega 8 graphics of the 3200G are not only surprisingly capable for an integrated GPU but also can overclock tremendously without the need for improved cooling. I will be trying the game on a $100 Ryzen 3200G paired with 8GB of dual-channel ram at 2400 MHz.
(Image credit: Tom's Hardware) Performance TestingĪs noted above, at the moment Doom Eternal crashes on Intel integrated graphics, but the situation is much better for AMD integrated GPUs. If you are using a non-English keyboard, whatever button is in this top-left position will usually open the console as well. Like many id games before it, Doom Eternal allows the user to access the developer console using the tilde ("~") key-usually next to the 1 key and under the Esc key on a full size keyboard. We'll update with performance data from Intel graphics at such a time and see if it's possible to keep performance above 30 FPS.Īnd with that preamble out of the way, let's dig into some of the less-obvious tweaks. Should Intel fix their driver problem, which it intends to as far as we can tell, the same tweaks should work on the various Core CPUs. That means our testing of integrated graphics will focus exclusively on AMD APUs for now. After the above warning message, the game would exit a few seconds later and we were back at Steam. "We’re aware and are currently working with id to resolve this." We did try running Doom Eternal on UHD Graphics 630 using a Core i9-9900K, but it never even reached the loading screen. We've reached out to Intel for comment, and perhaps a driver update, and received the following response.
0 kommentar(er)
