Games crashing in full screen on windows 10 - Printable Version +- RPCS3 Forums (https://forums.rpcs3.net) +-- Forum: Support & Issues (https://forums.rpcs3.net/forumdisplay.php?fid=17) +--- Forum: Support (https://forums.rpcs3.net/forumdisplay.php?fid=18) +--- Thread: Games crashing in full screen on windows 10 (/showthread.php?tid=199967) |
Games crashing in full screen on windows 10 - Nyan Noodles - 01-09-2019 Hi, that's my first post, my english is kinda bad so, sorry, huh, I had Windows 8.1 installed on my computer, and the Full Screen mode was working fine, no crashes, no lag, it was normal, but then, I upgraded to windows 10, and now Full Screen mode keeps crashing after a while, like, I open the game, put it in Full Screen mode, and after 2 minutes or less playing, the emulator just crashes, and I need to press Ctrl + Alt + Del to get out, yesterday I was testing Windows 7 on my computer, and Full Screen mode runs fine, it's the same computer, the same drivers version, and it works with no problems, but for some reason, it keeps crashing on windows 10, pls help me, playing on Window mode is terrible on my monitor. I attached my configs for you to see, maybe it's bad configuration but I don't think so, it's the same configs as Windows 7 and 8.1. RE: Games crashing in full screen on windows 10 - Ani - 01-10-2019 Do not use Full Screen mode, or if you want to use it, revert back to NVIDIA 398/399 drivers, as the newer ones are broken Issue report: https://devtalk.nvidia.com/default/topic/1045980/vulkan/-windows-possible-vulkan-driver-bug-with-recent-driver-versions-likely-related-to-swapchain/ RE: Games crashing in full screen on windows 10 - IceLancer - 09-15-2019 problem with fullscreen switch /on /off happens like crazy for me 7/10 times. latest nvidia drv. But i found solution. In GPU settings enable "resize game window on boot" and set your resolution in there. It will act as window borderless RE: Games crashing in full screen on windows 10 - Ani - 09-15-2019 Vulkan is already borderless mode by default, but the issue mentioned in this thread was fixed a few months ago |