Software Support > GroovyMAME

*2nd Update proper CMD log file.txt added - some games not working??

<< < (2/2)

Calamity:
Hi Rattus,


--- Quote from: Rattus on November 14, 2025, 07:12:43 am ---880 views, so I guess about 100 AI Bots per day are reading my thread, and none of them are trying to help me  ::)

--- End quote ---

Yeah probably many bots but also some of us read you but didn't find a moment to post any helpful answer. Sorry for this. Usually an user that struggles to create a log in the first place scares away potential help because that's a sign that troubleshooting won't be a fluid process, but that's a nasty prejudice of mine and I should definitely spend more time helping users as I did in the past.

The lysergic log you finally posted, paired with that strange picture of what looks like the corner of the frontend, maybe added more confusion than help.

Anyway, after reading your post a second time, I believe that I now understand why you're getting a blank log. For some reason your using the "start" command to launch groovymame. This could be diverting the output somewhere else. Just cd into groovymame's folder, and run: groovymame.exe romname -v >romname.txt

----> Notice the "-v", not "v".

Frogger/Galaxian, etc. are rendered at 768x224 by MAME, to properly represent the starfield in the background. Once I see a log (which I need to see how you're system is configured), I'll be able to provide advice regarding what you should do to get these games shown properly.

Rattus:

--- Quote from: Calamity on November 14, 2025, 10:01:22 am ---For some reason your using the "start" command to launch groovymame.
--- End quote ---

Hi Calamity, thanks for your help, please excuse my inexperience with the CMD window, I have now attached a proper log.txt file.

I also noted that the CMD window said after the operation *switchres: could not find a video mode that meets your specs.

I have followed this guide and everything seemed to go OK. Installing CRT Emudriver 2.0 - HD 5450 - Windows 7 - super resolutions  http://geedorah.com/eiusdemmodi/forum/viewtopic.php?pid=1052#p1052

I'm also checking this guide. Groovy MAME: Installation and quick configuration (2019 guide) http://geedorah.com/eiusdemmodi/forum/viewtopic.php?id=433

As I stated above I get 31 video modes found - 28 redundant - 0 video modes dropped - 3 modelines generated and the mode lines seem to install ok. As far as I know it's only generating 3 mode lines because I'm using super resolutions.

I checked my notes on an older PC that I set up and found that had 3 mode lines generated also, and that runs all games without issues.

Hopefully this log file can help?



Calamity:
Hi Rattus,

It sounds like you've created all modes interlaced for some reason (maybe because you asked vmmaker to rotate the modes?):


--- Code: ---Switchres: Searching for custom video modes...
Switchres: [  0]  640x 480 @ 30i* : AMD ADL timing "640x480_30i 15.685000KHz 59.980881Hz" 13.050000 640 664 728 832 480 483 489 523 interlace  -hsync -vsync
Switchres: [  1]  664x 496 @ 60i : AMD ADL timing "664x496_60i 16.169000KHz 59.996288Hz" 14.100000 664 696 760 872 496 499 505 539 interlace  -hsync -vsync
Switchres: [  2]  768x 496 @ 60i : AMD ADL timing "768x496_60i 16.170000KHz 60.000000Hz" 16.170000 768 800 872 1000 496 499 505 539 interlace  -hsync -vsync
Switchres: [  3]  800x 496 @ 60i : AMD ADL timing "800x496_60i 16.173000KHz 60.011131Hz" 16.950000 800 832 912 1048 496 499 505 539 interlace  -hsync -vsync
Switchres: Found 4 custom of 3 active video modes
--- End code ---

A bit below, all 4 modes are shown as locked. This can be caused because you have manually disabled interlace, so GM can't select the only modes that exist.

So, start by creating a reasonable mode list. Run vmmaker again, and make sure you get some progressive modes shown in vmmaker's list. Then try again (and post a new log if things aren't still ok).

Rattus:

Thanks very much Calamity, you have given me some ideas what to look for and I will spend some time testing before I post my results.

Navigation

[0] Message Index

[*] Previous page

Go to full version