TEMPORARY PERFORMANCE WORKAROUNDS AND HOW TO IMPLEMENT THEM
The two major fixes:
(UPDATE): It seems priorty is a result of alt-tabbing, and if you watch priority it switches back to normal once you tab back in. In the meantime, texture quality, TXAA, and view distance all seem to be the biggest framerate hits, so try dropping those for the time being.
This is just a quick guide for those looking for fixes to performance. They are short, simple, and easy.
nVdia users: Set pre-rendered frames to 1 or 2 - the game seems to render a LOT of pre-rendered frames by default causing massive input delay. I'm not familiar with AMD software, but I'm sure there's some equivalent software setting.
Secondly, and this is the big one - The game is automatically setting its process priority class to low (It's set to normal/high in the menus, then auto-sets to low every loading screen), which means it's not getting nearly the amount of cpu it should get. This is the primary source of massive framerate drop - especially when loading a lot of complex textures/models at once (IE the vegetation in the opening throne room scene) - I went from getting 35-45fps in open areas at 1080/60/gtx980/ultra oreset, to getting 60 with slight dips to 55. Keep in mind, the process priority will reset EVERY LOADING SCREEN, so unless you have a program that actively forces priority class, it will be an unfortunately very menual workaround for now.
The fix is quite easy, simply open task manager after each loading screen and set process priority to normal or higher. If you're on windows 10, you'll have to right click and click 'go to details' before you can right click and view the process priority option.
The good news in, this is easy to patch. Tweet @arkanestudios and @bethesdasupport and your favorite performance reviewing content creators and spread the word, the faster they know the faster we'll get a proper patch
This guide was created by its original author on the Steam Community. Are you the author and want it removed? Request removal.