Im using switchres with crtemudriver and a pvm and an ati 5000 card and having trouble with full screen and switching games on the fly.
If i toggle full screen it crushes the video vertically. If i try to switch games on the fly the same thing happens. However if i “close content” first and then switch games everything is fine.
These problems do not occur if i use an older video driver but the games look like ass. Im experiencing these issues with the “gl” video driver which makes the games look virtually perfect.
I’m going to put together a new PC with windows. I have been working a lot with Linux recently.
I have a bit of work to do on the windows version anyway. So I will look at this.
Firstly, what version of windows are you running?
When you say an old driver and it look like are what driver are you talking about?
What resolutions are you using? Native/Super what superes?
What RetoArch version are you using? Have you tried an older one?
There has been a recent influx of issues, most of which have been related to Windows 10. However, Many people have got it working perfectly in Windows 10 as well. Its going to be one of those hard issues to narrow down without a lot of information on it.
I’m using Windows 10. I could wipe my computer and load windows 7.pain in the @&& but i could. Should I do this?
When I use the dsd11 and dsd10 video drivers I have less resolution issues .I can toggle full screen but once I load a new game without “closing content” it crushes the image. dsd10 actually looks good but not as good as gl. dsd11 has very poor video quality. When I use dsd9 It almost always crushes the image no matter what I do and I have to keep toggleing menus and open and closing RA and intermitently refreshes the menu in proper resolution. I am using the gl video driver and the video quality is virtually perfect but it has the resolution issues I mentioned in my previous post (crushes image vertically any time I toggle fulscreen or change roms without “closing content”.
I’m using the following super resoulitouns:
2560 x 192 @ 60.000000 super
2560 x 200 @ 60.000000 super
2560 x 224 @ 60.000000 super
2560 x 237 @ 60.000000 super
2560 x 240 @ 60.000000 super
2560 x 248 @ 60.000000 super
2560 x 254 @ 60.000000 super
2560 x 254 @ 55.000000 super
2560 x 256 @ 60.000000 super
2560 x 256 @ 50.000000 super
2560 x 264 @ 60.000000 super
2560 x 272 @ 60.000000 super
2560 x 280 @ 60.000000 super
2560 x 288 @ 60.000000 super
2560 x 296 @ 60.000000 super
2560 x 304 @ 60.000000 super
2560 x 320 @ 60.000000 super
2560 x 336 @ 60.000000 super
2560 x 344 @ 60.000000 super
2560 x 352 @ 60.000000 super
2560 x 360 @ 60.000000 super
2560 x 368 @ 60.000000 super
2560 x 376 @ 60.000000 super
2560 x 384 @ 60.000000 super
2560 x 392 @ 60.000000 super
2560 x 400 @ 60.000000 super
2560 x 416 @ 60.000000 super
2560 x 432 @ 60.000000 super
2560 x 448 @ 60.000000 super
2560 x 464 @ 60.000000 super
2560 x 480 @ 60.000000 super
2560 x 496 @ 60.000000 super
2560 x 512 @ 59.000000 super
2560 x 544 @ 55.000000 super
2560 x 560 @ 54.000000 super
2560 x 768 @ 60.000000 super
2560 x 800 @ 60.000000 super
The RGUI menu driver I am using loads in 2560x240 60hz
I’m using RA 1.7.5-x64. It has latency options I need. I have not tried to a previous version. I’m new to Retroarch and I don’t know a lot of the acronyms people are using.
Yeah I think it would be good if there would be some sort of troubleshoot guide for Windows 10. Possibly most of these things are related to a broken CRT_Emudriver installation. I looked over the GM forum and found some possible workarounds for the issues that people may have. I quoted these issues below, the numbered points in BOLD are the summary of what to do.
1. It seems there are issues with using HD4000 and before cards in Windows 10. The 12.6 CRT_Emudriver may not be compatible with Windows 10. So the suggestion is that when you go the Windows 10 route that you have at least a HD5000 series card or newer and use the Crimson 16.2.1 version of CRT_Emudriver.
I’m trying to setup a cab using Windows 10 Pro version 1803 and an XFX HD 4350.
I was able to eventually install the driver (had to use Safe Mode otherwise it would always blue screen) and have installed modes using vmmaker.
I can’t help with your issue but can share my experience with Win10x64 1803. (Setup: Intel i5 4690s CPU + Intel H87 Chipset + Radeon HD 4350 + LCD Monitor)
Like you I got the blue screen when installing CRT Emudriver 2.0 legacy. Thanks for the tip with Safe Mode. Now I could at least install the driver.
Despite running as Admin, GroovyMame somehow cannot write into the registry:
Maybe part of the problem is that 12.6 is too old for 1803.
2. Make sure you update from the default microsoft driver (this possibly means the driver that comes with the default Windows 10 install, so not the one that gets installed after you get online)
I had only BSOD on windows 10 x64 and only when I tried update CRT emu driver 12.6 to 16.2.1. When I tried update default driver taken from microsoft to 16.2.1 everything was fine.
3a. Testmode is required to be enabled for the driver to work. During driver install test mode is normally enabled, but in case something goes wrong it may be useful to enable test mode manually first, reboot, check that test mode is enabled, and then try to install 16.2.1 CRT_Emudriver again
3b. If you’ve just set up a new Windows 10 install and it is connected online then the Windows update service may try to install a newer AMD driver. Possibly this can interfere with trying to install CRT_emudriver at that moment? As a safety precaution it may therefore be recommended to disable the internet connection before you start the CRT_Emudriver installation.
If Windows installed AMD’s driver after you had installed CRT Emudriver, then AMD’s driver will take control and the required features won’t be there. They can’t coexist. With regards to test mode, it’s 100% required for CRT Emudriver to load on Windows startup, disabling may bluescreen Windows 8/10.
If people have experience with using CRT Switchres and CRT_Emudriver on Windows 10, succes or not, please feel free to add points to this troubleshooting list.
