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 Try the site in https mode Site News

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

  

Author Topic: Manually adding 321x240  (Read 2971 times)

0 Members and 1 Guest are viewing this topic.

ahofle

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 4544
  • Last login:August 30, 2023, 05:10:22 pm
    • Arcade Ambience Project
Manually adding 321x240
« on: February 21, 2012, 01:09:57 am »
I need to manually add a 321x240@60 resolution in vmmaker for some non-MAME emulators (and because windows overrides my 320x240 with a fake 31khz one).  I assume I just need to add the modeline to reslList.txt and rerun vmmaker?  I know a modeline was posted around here somewhere but I can't seem to find it.  I'm using the magic resolutions patch.

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 7418
  • Last login:May 02, 2024, 04:59:06 am
  • Quote me with care
Re: Manually adding 321x240
« Reply #1 on: February 21, 2012, 11:18:17 am »
I need to manually add a 321x240@60 resolution in vmmaker for some non-MAME emulators (and because windows overrides my 320x240 with a fake 31khz one).

This shouldn't happen. Are you still using the patched drivers or trying with plain Catalyst?

 I assume I just need to add the modeline to reslList.txt and rerun vmmaker?  I know a modeline was posted around here somewhere but I can't seem to find it.  I'm using the magic resolutions patch.

That won't work because x resolutions are rounded to 8 multiples by the modeline generator. Actually, the feature of using fake label numbers as 321, 322, etc. is reserved by the generator for the cases where it needs it (disambiguation of video modes with very close refresh rates), so you can't manually do it.

However, you can use Winmodelines to manually add that modeline. Make sure to use the 321 label for the numbers between quotations and that will do the trick.
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 of pasting it.

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

ahofle

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 4544
  • Last login:August 30, 2023, 05:10:22 pm
    • Arcade Ambience Project
Re: Manually adding 321x240
« Reply #2 on: February 21, 2012, 10:53:23 pm »
I'm using the patched driver with the magic resolutions.  My reslList.txt does not contain a 320x240@60 resolution, only 320x240@50.  So it sort of makes sense that I don't have that resolution.  Do I just need to add 320x240@60 to reslList.txt and then rerun vmmaker?  I've attached my list as well as a screenshot of ArcadeOSD.

ahofle

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 4544
  • Last login:August 30, 2023, 05:10:22 pm
    • Arcade Ambience Project
Re: Manually adding 321x240
« Reply #3 on: February 21, 2012, 11:09:23 pm »
I changed the '50' to '60' in reslList.txt, ran vmmaker and rebooted and all is good now!  The fake 320x240 is gone!
Is the 320x240@50 a typo? 

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 7418
  • Last login:May 02, 2024, 04:59:06 am
  • Quote me with care
Re: Manually adding 321x240
« Reply #4 on: February 22, 2012, 11:41:40 am »
I changed the '50' to '60' in reslList.txt, ran vmmaker and rebooted and all is good now!  The fake 320x240 is gone!
Is the 320x240@50 a typo? 

I see. The problem was there was no 320x240@60 defined, so the 'fake' one was actually the default 320x240 mode defined by the driver.

The 320x240@50 was defined for PAL Megadrive games but I'll probably remove those in next release.
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 of pasting it.

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