Software Support > GroovyMAME
GroovyMAME 0.227 - Switchres v0.017t
keropi:
@Doozer
ah, so you say that this is a base mame problem... I would love to be able to compile GM myself (now that Calamity said he won't put any extra patches in it like the no-nag one) but I don't know what environment I need to install on my windows machines. I have a functional environment to grab SVN sources and build the XT-IDE BIOS but there was a tutorial on how to do that. If there is something similar for MAME please do tell as I am very interested in doing that :)
@haynor666
just tried Violent Storm and Virtua Fighter Kids, both work fine (win7/x64, 6450 gpu)
@tom5151
the game is called "DoDonPachi Dai-Fukkatsu Ver 1.5" , a glorious shooter
edit: is this a good guide to follow on how to compile mame? http://forum.attractmode.org/index.php?topic=348.0
Doozer:
@keropi
It is not a stock mame issue, but something that must be fixed inside groovymame. The patch is only at alpha stage. Even Calamity considers that a lot of work is needed to get it ready, especially with the new bgfx rendering method to be worked out. RC version might only come with later mame releases.
It is possible to have mkchamp patch installed (for hiscore) and groovy patch together. First install mkchamp hi.diff and then apply the groovy patch. There is only one manual fix to perform due to the exact same insert location for both of them. Not a big deal.
Under windows, I know that the compilation is done via MingGW with complete explanations given here https://github.com/mamedev/buildtools
It explains how to get a mame development environment under Windows.
keropi:
^ thanks for that
I started compiling with the info on the link I posted above, first applied MK's patch and then the GM one - did not make any other manual fix though since I had no idea... it's been ~10mins now and the program still compiles - using my office pc (Q9300/8GB ram) - any estimate how long the process takes?
So I suspect it will fail at some point because I did not make that fix, right?
edit:
yep it failed ;D
--- Quote ---Compiling src/devices/cpu/mcs96/i8xc196.cpp...
Compiling src/devices/cpu/mcs96/mcs96.cpp...
Archiving liboptional.a...
makefile:959: recipe for target 'windows_x64' failed
make: *** [windows_x64] Error 2
--- End quote ---
Doozer:
Check the following file ./src/emu/emuopts.cpp , the goovy section to add is the following (must be applied manually):
--- Code: ------ src/emu/emuopts.cpp 2016-07-27 10:58:06.000000000 +0200
+++ src/emu/emuopts.cpp 2016-08-06 19:23:59.000000000 +0200
@@ -201,6 +203,39 @@
{ OPTION_PLUGIN, nullptr, OPTION_STRING, "list of plugins to enable" },
{ OPTION_NO_PLUGIN, nullptr, OPTION_STRING, "list of plugins to disable" },
{ OPTION_LANGUAGE ";lang", "English", OPTION_STRING, "display language" },
+
+ // Switchres options
+ { nullptr, nullptr, OPTION_HEADER, "CORE SWITCHRES OPTIONS" },
+ { OPTION_MODELINE_GENERATION ";ml", "1", OPTION_BOOLEAN, "Automatic generation of modelines based on the specified monitor type" },
+ { OPTION_MONITOR ";m", "generic_15",OPTION_STRING, "Monitor type, e.g.: generic_15, arcade_15, lcd, custom, etc." },
+ { OPTION_ORIENTATION ";or", "horizontal",OPTION_STRING, "Monitor orientation (horizontal|vertical|rotate|rotate_r|rotate_l)" },
+ { OPTION_CONNECTOR ";cn", "auto", OPTION_STRING, "[Linux] video card output (VGA-0|VGA-1|DVI-0|DVI-1)" },
+ { OPTION_INTERLACE ";in", "1", OPTION_BOOLEAN, "Enable interlaced scanning when necessary" },
+ { OPTION_DOUBLESCAN ";ds", "1", OPTION_BOOLEAN, "Enable double scanning when necessary (unsupported under Windows)" },
+ { OPTION_SUPER_WIDTH ";cs", "2560", OPTION_INTEGER, "Automatically apply -unevenstretchx if resolution width is equal or greater than this value" },
+ { OPTION_CHANGERES ";cr", "1", OPTION_BOOLEAN, "Enable dynamic in-game video mode switching" },
+ { OPTION_POWERSTRIP ";ps", "0", OPTION_BOOLEAN, "Use Powerstrip API for dynamic setting of custom video timings" },
+ { OPTION_LOCK_SYSTEM_MODES ";lsm", "1", OPTION_BOOLEAN, "Lock system (non-custom) video modes, only use modes created by us" },
+ { OPTION_LOCK_UNSUPPORTED_MODES ";lum", "1", OPTION_BOOLEAN, "Lock video modes reported as unsupported by your monitor's EDID" },
+ { OPTION_REFRESH_DONT_CARE ";rdc", "0", OPTION_BOOLEAN, "Ignore video mode's refresh reported by OS when checking ranges" },
+ { OPTION_DOTCLOCK_MIN ";dcm", "0", OPTION_STRING, "Lowest pixel clock supported by video card, in MHz, default is 0" },
+ { OPTION_SYNC_REFRESH_TOLERANCE ";srt", "2.0", OPTION_STRING, "Maximum refresh difference, in Hz, allowed in order to synchronize" },
+ { OPTION_FRAME_DELAY ";fd", "0", OPTION_INTEGER, "Delays the start of each frame to minimize input lag (0-9)"},
+ { OPTION_VSYNC_OFFSET, "0", OPTION_INTEGER, "Offset vsync position by this many lines to prevent tearing with frame_delay and high-resolution displays" },
+ { OPTION_BLACK_FRAME_INSERTION ";bfi", "0", OPTION_BOOLEAN, "Inserts a black frame after each normal frame, intended to reduce motion blur on 120 Hz monitors" },
+ { OPTION_MODELINE ";mode", "auto", OPTION_STRING, "Use custom defined modeline" },
+ { OPTION_PS_TIMING ";pst", "auto", OPTION_STRING, "Use custom Powertrip timing string" },
+ { OPTION_LCD_RANGE ";lcd", "auto", OPTION_STRING, "Add custom LCD range, VfreqMin-VfreqMax, in Hz, e.g.: 55.50-61.00" },
+ { OPTION_CRT_RANGE0 ";crt0", "auto", OPTION_STRING, "Add custom CRT range, see documentation for details." },
+ { OPTION_CRT_RANGE1 ";crt1", "auto", OPTION_STRING, "Add custom CRT range" },
+ { OPTION_CRT_RANGE2 ";crt2", "auto", OPTION_STRING, "Add custom CRT range" },
+ { OPTION_CRT_RANGE3 ";crt3", "auto", OPTION_STRING, "Add custom CRT range" },
+ { OPTION_CRT_RANGE4 ";crt4", "auto", OPTION_STRING, "Add custom CRT range" },
+ { OPTION_CRT_RANGE5 ";crt5", "auto", OPTION_STRING, "Add custom CRT range" },
+ { OPTION_CRT_RANGE6 ";crt6", "auto", OPTION_STRING, "Add custom CRT range" },
+ { OPTION_CRT_RANGE7 ";crt7", "auto", OPTION_STRING, "Add custom CRT range" },
+ { OPTION_CRT_RANGE8 ";crt8", "auto", OPTION_STRING, "Add custom CRT range" },
+ { OPTION_CRT_RANGE9 ";crt9", "auto", OPTION_STRING, "Add custom CRT range" },
{ nullptr }
};
--- End code ---
keropi:
@Doozer
That's a .diff file you posted right?
So I apply:
a. hi-score/no-nag .diff
b. GM .diff
c. the .diff you posted
correct? Sorry if this seems a simple question but I don't have experience in this :)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version