Build Your Own Arcade Controls Forum
Software Support => GroovyMAME => Topic started by: Saneless on November 18, 2014, 11:25:09 am
-
I have a standard NTSC TV, S-Video so no chance of running 15khz.
Would not changing the .ini, or deleting it entirely, mean I'm defaulting to generic_15 and that's why, after installing your custom ATI drivers my system throws a wavy BSOD?
It was driving me nuts but this is such a simple solution if that's the case. Groovymame ran with standard ATI drivers, but doesn't quite work right (sync issues). But with the hacked drivers it crashes every time.
-
Hi Saneless,
(Just splitting this topic as had no relation with to other thread).
If you're getting a BSOD it's probably because the driver is not properly installed (e.g. old driver files getting mixed up with the new ones, etc.)
Another possible cause is that your installing more modelines than allowed (>120, unlikely).
I'm not sure what .ini you mean. If it's GM's .ini, then it has nothing to do with your BSOD (either deleting or leaving it unchanged can't do that).
Running GM with standard drivers is too suboptimal because it can't set the required refresh rates. Anyway, you wouldn't get custom refresh rates at all running through S-Video. GM only starts making sense through RGB or component->RGB.
-
Thanks for splitting it.
I tried using ATI's standard uninstaller in the ATI/Support directory, and I've downloaded the catuninstaller.exe I've seen around here, so I'll try that tonight.
My guess was some driver issue because it didn't happen on the standard Catalyst install, but I'm not sure what's going on. After I did a system restore I didn't get BSODs anymore, but I did get a fast dark wavy line image that looks like what would happen if I picked a resolution I shouldn't have from quickres.
Hopefully the catuninstaller does the trick. I've seen you mention wiping out the standard MS VGA driver as wel, but I'm not sure how to do that. And your driver package wouldn't let me install from safe mode (F8).
If that doesn't do it, are there registry entries to wipe out and dlls to delete?
-
I've seen you mention wiping out the standard MS VGA driver as wel, but I'm not sure how to do that.
Not exactly that, but the defaut one from ATI that is shipped with your XP "distribution". That's the one that requires hot water to be removed. Enter the device manager, display devices, and cicking on your video card, remove the driver from there manually.
-
the free program called winmodelines is a good way to have a look at the registry to see whats going on regarding your video installation. it will also give you the location (path) in the registry, incase you need to manually delete (using eg. regedit) something causing a problem
-
I've seen you mention wiping out the standard MS VGA driver as wel, but I'm not sure how to do that.
Not exactly that, but the defaut one from ATI that is shipped with your XP "distribution". That's the one that requires hot water to be removed. Enter the device manager, display devices, and cicking on your video card, remove the driver from there manually.
Now that, I've done. On a reboot it installs something, maybe generic VGA. I thought I did all that but maybe I didn't do it right.
I'm also 90% sure that I did have this working just fine at one point, but screwed something up along the way when I tried to reinstall catalyst drivers to get HLSL to work (which it didn't, and still doesn't).
-
Now that, I've done. On a reboot it installs something, maybe generic VGA. I thought I did all that but maybe I didn't do it right.
If it's generic VGA, congrats, install CRT Emudriver now. If it's a default ATI driver what gets installed on boot, remove it again, and without rebooting, install CRT Emudriver (don't give it a chance to install the default one).
-
Well if that's the case then it probably wasn't generic, I've rebooted after removing it. I'll try that, thanks for the help.
And before I go through such problems.. When I ran GM with the standard ATI drivers, I'm not getting good vsync results in games automatically. Black Tiger, Simpsons, TMNT, all are terrible. If I set vsync to 1 manually in the .ini it's perfectly fine, but I don't want to set that since it breaks sound in the vertical games.
Will I see those issues still on the Emu drivers? Again, 90% sure when I got it to run before with the drivers those issues weren't there.
-
It should be all fine out of the box with the Emudrivers, specially vsync.
-
Still no go. No idea what else to do at this point.
And going back to your original post about custom refresh rates, will GM and the drivers do better sound and video sync even with s video compared to standard mames or should I just not bother anymore?
Final edit: fresh install, same issue. And oddly enough the standard MAME does the same thing. Guess my system doesn't like these drivers for my Radeon 8500
-
Yes, maybe the Radeon 8500 is too old to work although advertised as working... are you testing 32 or 64 bits?. I'd say it should work on 32 at least, but the 64 bit version of the 6.5 driver was never an officially supported ATI package.
Anyway, as I said I wouldn't bother setting up all this if you're going to use s-video, it's not a matter of faith but something obvious since s-video outputs are locked to 50/60 Hz and 480i/576i.
-
32 bits all the way. I'm just not sure why it hasn't been working when I know it was working at some point. Hell, after I did a system restore a different variant of MAME was working, but now even the standard one breaks. It just doesn't make sense.
I guess I'll just move on, and if I break out another TV that has component, I'll also bring out the Radeon 9700 and hopefully will have better results.
-
it might be an idea to try mameuifx, as you can use the soundsync option with that mame version (because your video will be set on 60hz due to how you are outputting from pc/inputting into your tv) but the soundsync option will allow you to force all games to run at 60hz while still remaining smooth in gameplay and sound. regular mame does have some options to try to achieve this but i believe they dont work properly (see this: http://geedorah.com/eiusdemmodi/forum/viewtopic.php?id=42 (http://geedorah.com/eiusdemmodi/forum/viewtopic.php?id=42))