Scoot Magee Posted February 13, 2017 Posted February 13, 2017 I didn't boot game ex for a while and the only change I can think of in between the last time I used it and now is that I replaced my broken gtx 670 with a new one. All the drivers are up to date as far as I know. So basically what happens is when I boot a mame rom from game ex the screen loads black and after some time I can hear the game struggling to run in the background. The sound is slow and choppy and the screen stays black until I back into the game ex menu again. Windows 10 64bit AMD fx 4100 quad core gtx 670 I also attached a log. Thanks! log.txt
tthurman Posted February 13, 2017 Posted February 13, 2017 Are you running as administrator? You may want to see if changing to full screen windowed mode is more successful.
Scoot Magee Posted February 13, 2017 Author Posted February 13, 2017 I forgot to mention I haven't used it since I updated to windows 10. I'll give that a shot when I get home and let you know how it went.
Scoot Magee Posted February 13, 2017 Author Posted February 13, 2017 Ok so I set to admin but that didn't work. Here's another log. I actually got an error every time I tried to boot anything at all. NES, SNES, Genesis and etc all give different errors related to d3d and direct draw. I'm guessing these weren't working all along but I was only trying to use mame. log.txt
tthurman Posted February 13, 2017 Posted February 13, 2017 Did you try setting the properties to run full screen windowed. Also, who knows what the Win 10 update could have done. Ensure you have .NET Framework 3.5 installed. If you have an extensive config, I would recommend backup up your GameEx.ini, You could download the latest version, and do an over the top installation. This "should" work without issue, as this is how the incremental updates are applied.
Scoot Magee Posted February 13, 2017 Author Posted February 13, 2017 I had limited time to try so I didn't try windowed full screen. Is that a gameex setting in the wizard? Also ill go through and check out if I have the right framework. If that doesnt work I'll try a new install as suggested.
tthurman Posted February 13, 2017 Posted February 13, 2017 Yes, it's in the display settings. I have my doubts it'll help, but it will be an easy enough thing to test.
DazzleHP Posted February 14, 2017 Posted February 14, 2017 If you haven't already since W10 i would make sure you have all OS updates. If you have an integrated GPU, i would then download the latest drivers for your dedicated GPU, uninstall them completely, reboot and then install them (your GPU drivers) again. Like many decent programs, GameEx is not very portable, this applies across OS versions too.
Scoot Magee Posted February 14, 2017 Author Posted February 14, 2017 Thanks for your helps guys. I ended up just uninstalling gameex and switched to gameex arcade edition and it's working. I'm going to try a fresh install of gameex later as well but I'm not too worried about console games at the moment. Anyway I now ran into some minor issues with arcade edition. For some reason I cant get themes and etc to display even after setting to the correct directory. My arcade art and etc shows up but no themes, preview videos or snaps show up. These are my paths C:\GameEx Arcade Edition\MEDIA\DOWNLOADED ARTWORK\MAME\VIDEO C:\GameEx Arcade Edition\MEDIA\DOWNLOADED ARTWORK\MAME\VIDEOTHEME Is there something I'm doing wrong? I had all the video themes and etc put into those folders. I didn't know if I should make a new thread for this.
tthurman Posted February 14, 2017 Posted February 14, 2017 Don't hold me to this, because I don't run the Arcade Edition. I seem to recall a post; which I cannot find, that things are automated with the Arcade Edition, which I'm guessing means it will pull down the system pack, and place the files in the appropriate directories.
Scoot Magee Posted February 14, 2017 Author Posted February 14, 2017 Thanks for your help. I'm going to create a new thread for this issue. As far as my original issue I think it was due to driver issues and the windows 10 installation. I'm confident a fresh install will fix that problem. Thanks again!
Recommended Posts