Main Restorations Software Audio/Jukebox/MP3 Everything Else Buy/Sell/Trade
Project Announcements Monitor/Video GroovyMAME Merit/JVL Touchscreen Meet Up Retail Vendors
Driving & Racing Woodworking Software Support Forums Consoles Project Arcade Reviews
Automated Projects Artwork Frontend Support Forums Pinball Forum Discussion Old Boards
Raspberry Pi & Dev Board controls.dat Linux Miscellaneous Arcade Wiki Discussion Old Archives
Lightguns Arcade1Up --- Bug Reports --- Site News

Unread posts | New Replies | Recent posts | Rules | Chatroom | Wiki | File Repository | RSS | Submit news

  

Author Topic: strange magic resolution behavior  (Read 1859 times)

0 Members and 1 Guest are viewing this topic.

ahofle

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 4532
  • Last login:May 12, 2019, 09:32:11 pm
    • Arcade Ambience Project
strange magic resolution behavior
« on: March 17, 2012, 01:54:02 pm »
I'm getting some really weird behavior when groovymame is picking resolutions.  This is running on a D9400 multisync.  It's changing the resolution 3 times, the last one being the wrong refresh rate (and sometimes a strange resolution).  It causes donpachi to crash, and games like Pacman to run at 84% (because they are synced to the wrong refresh rate.  Any ideas?  I've attached my mame.ini.

e:\mame>mame donpachi
SwitchRes v0.013: [donpachi] (1) vertical (320x240@57.55)->(432x320@57.55)->(664
x496@57.55)

-----------------------------------------------------
Exception at EIP=015FC0EF (not found): ACCESS VIOLATION
While attempting to read memory at 0000011C
-----------------------------------------------------
EAX=001D3530 EBX=0D39E108 ECX=0C7FED80 EDX=00000000
ESI=00000000 EDI=0022F304 EBP=0C83B94C ESP=001D3520
-----------------------------------------------------
Stack crawl:
  0C83B94C: 015FC0EF (not found)

e:\mame>mame pacman
SwitchRes v0.013: [pacman] (1) vertical (288x224@60.61)->(400x288@60.61)->(400x2
88@50.97)

e:\mame>mame spectar
SwitchRes v0.013: [spectar] (1) horizontal (256x256@60.00)->(256x256@60.00)->(25
6x256@56.88)

e:\mame>

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Online Online
  • Posts: 6562
  • Last login:Today at 03:16:04 pm
Re: strange magic resolution behavior
« Reply #1 on: March 17, 2012, 02:27:13 pm »
Hi ahofle,

Try using "d9400" instead of "D9400", that could be the issue, as it seems to be defaulting to cga. These case sensitivity issues are really annoying, I know, that would need to be fixed.



Important note: posts reporting GM issues without a log will be IGNORED.
Steps to create a log:
 - From command line, run: groovymame.exe -v romname >romname.txt
 - Attach resulting romname.txt file to your post, instead or pasting it.

CRT Emudriver, VMMaker & Arcade OSD downloads, documentation and discussion:  Eiusdemmodi

ahofle

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 4532
  • Last login:May 12, 2019, 09:32:11 pm
    • Arcade Ambience Project
Re: strange magic resolution behavior
« Reply #2 on: March 17, 2012, 03:11:41 pm »
Thanks Calamity, I'll give it a shot and report back.

ahofle

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 4532
  • Last login:May 12, 2019, 09:32:11 pm
    • Arcade Ambience Project
Re: strange magic resolution behavior
« Reply #3 on: March 17, 2012, 03:35:04 pm »
Well that certainly helped most of the games:

e:\mame>mame digdug
SwitchRes v0.013: [digdug] (1) vertical (288x224@60.61)->(400x288@60.61)->(400x2
88@60.61)
Average speed: 103.26% (10 seconds)

e:\mame>mame pacman
SwitchRes v0.013: [pacman] (1) vertical (288x224@60.61)->(400x288@60.61)->(400x2
88@60.61)
Average speed: 124.34% (5 seconds)


However, the 300-320 line ones still seem to be picking some crazy resolutions:

e:\mame>mame fshark
SwitchRes v0.013: [fshark] (1) vertical (320x240@54.88)->(432x320@54.88)->(792x5
92@54.88)
Average speed: 101.22% (9 seconds)

I only made the d9400 change to mame.ini.  Do I also need to change vmmaker.ini and regen the resolutions in vmmaker?

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Online Online
  • Posts: 6562
  • Last login:Today at 03:16:04 pm
Re: strange magic resolution behavior
« Reply #4 on: March 17, 2012, 04:57:05 pm »
You need to check the logs to see which resolution it's initially trying to pick for those games. The problem when it doesn't find the one it wants, is that it just goes for a virtualized resolution most of the times. The resolution it's picking is not so crazy as it's calculated to match the proper refresh, but definitely there should be a better match for a multisync monitor.
Important note: posts reporting GM issues without a log will be IGNORED.
Steps to create a log:
 - From command line, run: groovymame.exe -v romname >romname.txt
 - Attach resulting romname.txt file to your post, instead or pasting it.

CRT Emudriver, VMMaker & Arcade OSD downloads, documentation and discussion:  Eiusdemmodi

ahofle

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 4532
  • Last login:May 12, 2019, 09:32:11 pm
    • Arcade Ambience Project
Re: strange magic resolution behavior
« Reply #5 on: March 17, 2012, 05:44:21 pm »
Well the monitor limits certainly don't look right.  Should be 15khz - 38khz.  Attached the verbose debug output.


Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Online Online
  • Posts: 6562
  • Last login:Today at 03:16:04 pm
Re: strange magic resolution behavior
« Reply #6 on: March 18, 2012, 02:26:14 pm »
Hi ahofle,

The monitor ranges are fine, if you look through the log you'll see how the 15-38kHz range is subdivided in separate smaller ranges where different settings apply, as indicated by the monitor_specs lines.

However, I've just noticed that the monitor_specs2 range is wrong for the D9800/D9400, and it's different from what's stated in the Monitor presets thread. I remind having modified it for VMMaker but it seems the definition inside GroovyMAME is not updated. By now, try adding this line into mame.ini:

monitor_specs2    20001-29000, 40-80, 2.910, 3.000, 4.440, 0.451, 0.164, 1.048, 0, 0, 384, 576

This should make the 288-384 lines modes available for GroovyMAME.
Important note: posts reporting GM issues without a log will be IGNORED.
Steps to create a log:
 - From command line, run: groovymame.exe -v romname >romname.txt
 - Attach resulting romname.txt file to your post, instead or pasting it.

CRT Emudriver, VMMaker & Arcade OSD downloads, documentation and discussion:  Eiusdemmodi

ahofle

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 4532
  • Last login:May 12, 2019, 09:32:11 pm
    • Arcade Ambience Project
Re: strange magic resolution behavior
« Reply #7 on: March 18, 2012, 06:48:29 pm »
Thanks.  I tried adding that line (and commenting out the existing specs2 one) and it's still behaving the same (picking the 576 line interlaced res).  My monitor_specs0 and monitor_specs1 lines are both set to auto, is that right?  Attached the log.

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Online Online
  • Posts: 6562
  • Last login:Today at 03:16:04 pm
Re: strange magic resolution behavior
« Reply #8 on: March 18, 2012, 07:00:16 pm »
Well, something is wrong definitely as the log still shows the old default range:

SwitchRes: MonitorLimits 20501.00-29000.00,40.00-80.00,2.910,3.000,4.440,0.451,0.164,1.048,0,0,480.0,768

Also make sure to grab a newer GroovyMAME build, there was a bug in some older versions that didn't pick the ranges from mame.ini (just picked the first one or something).

Yes leave the others as auto.
Important note: posts reporting GM issues without a log will be IGNORED.
Steps to create a log:
 - From command line, run: groovymame.exe -v romname >romname.txt
 - Attach resulting romname.txt file to your post, instead or pasting it.

CRT Emudriver, VMMaker & Arcade OSD downloads, documentation and discussion:  Eiusdemmodi

ahofle

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 4532
  • Last login:May 12, 2019, 09:32:11 pm
    • Arcade Ambience Project
Re: strange magic resolution behavior
« Reply #9 on: March 19, 2012, 12:32:27 am »
I'm using 0.144...is there a more recent version?

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Online Online
  • Posts: 6562
  • Last login:Today at 03:16:04 pm
Re: strange magic resolution behavior
« Reply #10 on: March 19, 2012, 04:37:40 am »
Hi ahofle,

It seems that it only works if we replace the whole monitor definition, by adding these lines:

monitor_specs0    15250-18000, 40-80, 2.187, 4.688, 6.719, 0.190, 0.191, 1.018, 0, 0, 288, 448
monitor_specs1    18001-19000, 40-80, 2.187, 4.688, 6.719, 0.140, 0.191, 0.950, 0, 0, 320, 448
monitor_specs2    20001-29000, 40-80, 2.910, 3.000, 4.440, 0.451, 0.164, 1.048, 0, 0, 384, 576
monitor_specs3    29001-32000, 40-80, 0.636, 3.813, 1.906, 0.318, 0.064, 1.048, 0, 0, 576, 768
monitor_specs4    32001-34000, 40-80, 0.636, 3.813, 1.906, 0.020, 0.106, 0.607, 0, 0, 576, 768
monitor_specs5    34001-38000, 40-80, 1.000, 3.200, 2.200, 0.020, 0.106, 0.607, 0, 0, 600, 768

I'll need to fix this, anyway try this because I'm getting 320 lines resolutions now with these settings.
Important note: posts reporting GM issues without a log will be IGNORED.
Steps to create a log:
 - From command line, run: groovymame.exe -v romname >romname.txt
 - Attach resulting romname.txt file to your post, instead or pasting it.

CRT Emudriver, VMMaker & Arcade OSD downloads, documentation and discussion:  Eiusdemmodi

ahofle

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 4532
  • Last login:May 12, 2019, 09:32:11 pm
    • Arcade Ambience Project
Re: strange magic resolution behavior
« Reply #11 on: March 19, 2012, 09:59:58 am »
Thanks again Calamity for your support!  Works beautifully now!  :notworthy:

Gray_Area

  • -Banned-
  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 3363
  • Last login:June 23, 2013, 06:52:30 pm
  • -Banned-
Re: strange magic resolution behavior
« Reply #12 on: March 19, 2012, 03:44:41 pm »
By the way, GM is updated to 145, with current diffs provided, although these all are not where you'd think.
-Banned-