"High Performance" GPU Setting Causes Crash On Startup (Windows 10, 0.46)
Posted: 12 Oct 2021, 21:19
Hi all,
I recently installed OpenMW 0.46.0 on a fresh install of Windows 10. I noticed that, while using my CPU's integrated graphics, I could only pull 30 FPS in exteriors, so in Windows 10's Display settings, I changed OpenMW to use 'High Performance' (aka: my GPU) instead of my CPU, thinking that would solve the issue.
However, attempting to start OpenMW with this setting enabled causes the program to freak out on startup. The screen is completely black, and the cursor is changed to a purple dot. After a few seconds of being stuck like this, the game crashes to desktop.
It still runs fine using my integrated CPU, but I'd really like to get more than 30 FPS. I have no mods of any kind installed, and Tribunal and Bloodmoon are both installed in the correct order. My graphics card is an AMD Radeon 7800 with the most recent drivers installed. Underclocking my GPU with MSI Afterburner hasn't done anything to solve the problem, either.
Any ideas on what might be going wrong? I've searched high and low but haven't run into anyone else having this problem.
Thanks!
I recently installed OpenMW 0.46.0 on a fresh install of Windows 10. I noticed that, while using my CPU's integrated graphics, I could only pull 30 FPS in exteriors, so in Windows 10's Display settings, I changed OpenMW to use 'High Performance' (aka: my GPU) instead of my CPU, thinking that would solve the issue.
However, attempting to start OpenMW with this setting enabled causes the program to freak out on startup. The screen is completely black, and the cursor is changed to a purple dot. After a few seconds of being stuck like this, the game crashes to desktop.
It still runs fine using my integrated CPU, but I'd really like to get more than 30 FPS. I have no mods of any kind installed, and Tribunal and Bloodmoon are both installed in the correct order. My graphics card is an AMD Radeon 7800 with the most recent drivers installed. Underclocking my GPU with MSI Afterburner hasn't done anything to solve the problem, either.
Any ideas on what might be going wrong? I've searched high and low but haven't run into anyone else having this problem.
Thanks!