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
Thanks for your advice. I did what you suggested (I like it, it's a neat little trick) but the same problem arises unfortunately.
These are the steps I've gone through the attempt to fix the problem with no success:
1) Completely clean reinstall of AMD drivers (used Display Driver Uninstaller in safe mode then reinstalled AMD Catalyst drivers v15.7.1 - I have a Raedon R9 280 GPU)
2) Run the game (MGS:V) using WIndows 8 compatibility settings
3) CharlestONE's aforementioned method
1) It's not Windows 10's problem, it's AMD's drivers. The latest update, 15.7.1, is causing it. All we can do is wait for an update. Actually, I've just had a thought - I'll roll back the drivers to 15.7 and see what happens, maybe with compatibility settings.
2) Windows 10 is not fully released for everyone yet, really. They're bringing it out in waves to address most obvious issues that we seem to be encountering now (I'm not talking about this thread's issue). Although you can jump the queue by downloading it from their website, they've only automatically shared it for people on the insider program (to the best of my knowledge, anyway)
It's not an AMD problem, I have the exact same problem and I don't have AMD. This is most probably a Steam problem with Windows 10, as I was able to play a DRM-Free version of Rogue Legacy but not the Steam version. I wrote to Steam support three weeks ago, still waiting for the answer (They gave me a fix that did not work, and it didn't even have instructions for Windows 10). It seems there are a lot of people having the same problem currently, hope it gets fixed.