Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
No issues here with GTX1080.
Edit: I disabled the wallpaper and it worked thank you
Open up the doometernalconfig.local in notepad and make sure the video settings are correct and once that's verified, check the "read-only" box under attributes on that file on the bottom.
*Remember now, that the file is in read-only mode, the Doom Eternal game no longer has permission to write to that file, so remember that in the future if you have to change your graphics setting in the game. Let me know if you have any questions.
Doom 2016 had similar issues on Vega 56, which IMO were driver related and probably not an issue anymore aside from whatever driver version caused it.
My issue was specifically caused by the video card entering a "low power" state when opening a menu or automap, and not smoothly boosting back to game clocks. Desktop clock speed will obviously tank framerate.
Vulkan is a new API that doesn't have decades of bugfixes like Directx, so there probably is good excuses for this. I bet the driver is getting confused on what it is doing, and that gets compounded with aggressive power saving algorithms and OSD software.
I have also heard doom eternal had memory leaks in the past on certain videocards, which usually were cards with less than 8GB. Add in the incompatibility with OSD software, and there probably is some sort of optimization issue which could be on both ends.
Considering that my Vega 56 doesn't get 144FPS @ 1440p, I would speculate that the game's optimization is still garbage. None of these issues should happen with a properly optimized game, and console performance points out the desktop version is rather poor.
Another issue I would point out with this game, is that it uses variable quality settings that only use your settings as a "recommendation". This means the game can run internally at settings you did not choose. The Variable resolution option has also been reported broken, and can ruin performance when enabled. All this points to poor optimization in the game, not to mention driver support. Driver support in particular might affect boost clocks when the variable resolution kicks in. This is why everyone recommends turning off OSD and variable resolution, because these functions don't work correctly, and not all of them are game related.
*Update, never mind this "fix" doesn't work. The only bandaid fix I know is loading the last checkpoint.