Build Your Own Arcade Controls Forum
Software Support => GroovyMAME => Topic started by: Psicosis on December 15, 2014, 05:49:05 pm
-
I have been trying and trying to get this working for the past 4 days :dizzy:. I decided to upgrade my cabinet to windows 7 64 from windows xp64 so I formatted the computer and started from scratch. I am using a 15khz arcade crt in my cabinet with a radeon 4870. I got the crt emu drivers installed and working. I got vmmaker working and installing video modes and I am able to get groovymame working and loading games, if I set up vmmaker the old way with a bunch of standard resolutions. They show up normally in arcade osd but it appears the interlaced ones including my 640x480i only show when I select lock unsupported modes to no in arcade osd. Here is where the problems start, when I run vmmaker to set up super resolutions it installs them but they are only visible in arcade osd if I select lock unsupported modes to no in arcade osd. Is that correct? Can someone give me exact directions to setting up groovymame to run super resolutions so I am not missing anything. Can someone post their mame.ini that is using groovymame with super resolutions so I can see exactly how everything should be set.
-
Hi Psicosis,
Check this:
http://geedorah.com/eiusdemmodi/forum/viewtopic.php?id=259 (http://geedorah.com/eiusdemmodi/forum/viewtopic.php?id=259)
And this:
http://forum.arcadecontrols.com/index.php/topic,142237.msg1473316.html#msg1473316 (http://forum.arcadecontrols.com/index.php/topic,142237.msg1473316.html#msg1473316)
-
thanks for the quick response Calamity I have read these posts and believe me I have been reading and trying things for days, I am able to select 640x480i 15khz by right clicking on desktop/ screen resolution/advanced settings/adapter/list all modes and my cabinet boots fine everytime in 640x480 15khz. I also did the lock_unsupported_modes 0 in mame.ini thinking that it would let mame use the 2560 super resolutions that are only visible in arcade osd if I select lock unsupported modes to no in arcade osd. but It still didnt work. Am I putting resolution 2560x0 in mame.ini in the correct place? Where exactly should this be in mame.ini? thanks
-
when I first found capitaineflam25 post I thought I had found the answer to my problem because he was having what appears to be some of the same problems and error screen. But when I use video ddraw in mame.ini groovymame does finally load a game but it is not correct, when I hit tab and look at the game info it doesn't show a switchres resolution below the games resolution it just shows the games resolution.
-
Hi Psicosis,
You must be doing something wrong in your .ini. Post your mame.ini and create a log of a sample game: http://forum.arcadecontrols.com/index.php/topic,135823.0.html (http://forum.arcadecontrols.com/index.php/topic,135823.0.html)
-
Where does 2560x0 go at in mame.ini? I wont be able to post anything till later today when im home
-
Look for 'resolution auto' in mame.ini, change it for 'resolution 2560x0'. I'm assuming you created mame.ini using the groovymame executable.
-
ok Calamity I got it working correctly and switchres is showing the 2560 resolution in game info screen now, in all my hours of switching things on and off in mame.ini I ended up putting the 2560x0 under screen instead of resolution the last time I added it, when I originally had it in the correct spot. :banghead: So my question now is why do people like me and capitaineflam25 have to run it with "lock_unsupported_modes 0" and "video ddraw" in mame.ini and what I am most concerned about is What are the drawbacks, concerns and problems to having to run in ddraw mode instead of d3d? slower? more input lag? etc. anything I should know?
-
there is some info about ddraw vs. direct3d in this link below if you wanted to check it out:
http://forum.arcadecontrols.com/index.php?topic=139130.0 (http://forum.arcadecontrols.com/index.php?topic=139130.0)
-
thanks jadder, it sounds like ddraw is perfectly fine until i get to this sentence,("But ddraw is terribly flawed with W7, its set-display-mode api just can't handle interlaced/progressive mode switching and bilinear filtering is only supported with flipping surfaces. So some dirty workarounds had to be implemented in GM to make ddraw an usable option".) I am not sure what it exactly means tho.
-
I am not sure what it exactly means tho.
It means that despite of those problems, a lot of effort was put into making DDraw usable in GroovyMAME without any issues.