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

[Rattus]

(Scroll down for newly added cmd log file)

My old PC running Groovymame on my Astro City cab (Vertical) was running a romset 8yrs old. So I decided to buy a newer PC and update my roms so I could play some of the more CPU intensive games.

I have it all running and most games look good, but I'm having an issue with some games, Amidar and Frogger run blind with a black screen and Space War (Sanritsu) doesn't look right sort of squased a bit.

I have googled and searched here and made a couple of changes to my mame.ini to try to fix this but no luck yet.

I tried to create a log file as per Calamity's sig but my PC creats a blank .txt file log as others have also reported here. now created properly thanks

I have attached my mame.ini file in the hope that helps.

I am using Windows 10 and have used the crt_eumdriver_&_tools_2.0_beta_15_16.2.1_W.7.8.10 64

And the latest groovymame_0281.22lf_win 7 8 10

I get 31 video modes found - 28 redundant - 0 video modes dropped - 3 modelines generated

They install fine and as I said most games play fine, but some are quirky, this is the last issue I need to fix before I re-calibrate my monitor to the new PC and call it job finished.

I have fingers crossed that someone can help me please, I have spent sooooo long trying to fix this myself.

(I couldn't work out how to "insert" the file instead of attaching)

[MK3FANATIC]

I tried to create a log file as per Calamity's sig but my PC creats a blank .txt file log as others have also reported here.

Try running the command prompt with administrator privileges.

[Rattus]

Try running the command prompt with administrator privileges.

OK thanks I will give that a try when I get time.

Tried with admin privileges and it created the .txt log in a different folder but it was still blank, I can see the cmd prompt running, but it's just not generating/writing the log file properly.

[Rattus]

Deleted post that may have been confusing and added WORKING log file below.

[Rattus]

880 views, so I guess about 100 AI Bots per day are reading my thread, and none of them are trying to help me 

I have sucessfully built and run 4 different Groovymame PCs in the past. But this time I have invested $1000 on a PC to run mame faster and can't get it running as it should. Seems everytime I update the mame.ini changes and gets more complicated and there is less and less help available.

I do wonder if there are maybe heaps of people reading this thread that also have no idea why my set up isn't working or why my cmd won't write a log file?

[Calamity]

Hi Rattus,

880 views, so I guess about 100 AI Bots per day are reading my thread, and none of them are trying to help me 

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]

For some reason your using the "start" command to launch groovymame.

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: [Select]

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
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).