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: Polostar frequency switching fails sometimes  (Read 1775 times)

0 Members and 1 Guest are viewing this topic.

goldfisch

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 6
  • Last login:September 18, 2014, 04:52:23 pm
Polostar frequency switching fails sometimes
« on: February 25, 2013, 04:43:44 pm »
Hi,
setup my cabinet with xp64, Mala and Groovymame64. Everything works fine, but switching the frequency fails sometimes.
Read at an old thread (http://forum.arcadecontrols.com/index.php?topic=18785.0) that the solution is to disable the videosync for a second.
Is this possible with Groovymame? Or is there another solution?
My monitor is a new 25" Hantarex Polostar. The VGA Card is a Radeon 4350. The GM is 0.148 and self compiled.
Thanks

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 7411
  • Last login:March 14, 2024, 05:26:05 am
  • Quote me with care
Re: Polostar frequency switching fails sometimes
« Reply #1 on: February 26, 2013, 04:30:06 am »
I *think* that changing the sync polarity on the high resolutions does help. You'll need to recalculate the modes with VMMaker:

monitor_specs3    31500-31600, 45-80, 0.170, 0.350, 5.500, 0.040, 0.040, 0.640, 1, 1, 576, 800

Then, do the same in GM by creating a "custom" preset. You'll need to grab the presets used for "pstar" by creating a log, you'll find them on the top of it.
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

goldfisch

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 6
  • Last login:September 18, 2014, 04:52:23 pm
Re: Polostar frequency switching fails sometimes
« Reply #2 on: February 26, 2013, 05:11:01 am »
Thanks for your fast reply.
How can i create a logfile with GM to see the pstar presets?

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 7411
  • Last login:March 14, 2024, 05:26:05 am
  • Quote me with care
Re: Polostar frequency switching fails sometimes
« Reply #3 on: February 26, 2013, 05:41:34 am »
Ok, I just did it for you. Add the following in mame.ini (remind to replace the existing 'crt_range auto' options!!):

crt_range0 15700.00-15800.00,50.00-65.00,1.800,0.400,7.400,0.064,0.160,1.056,0,0,192,256,0,0
crt_range1 16200.00-16300.00,50.00-65.00,0.200,0.400,8.000,0.040,0.040,0.640,0,0,256,264,512,528
crt_range2 25300.00-25400.00,50.00-65.00,0.200,0.400,8.000,0.040,0.040,0.640,0,0,384,400,768,800
crt_range3 31500.00-31600.00,50.00-65.00,0.170,0.350,5.500,0.040,0.040,0.640,1,1,400,512,0,0
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

goldfisch

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 6
  • Last login:September 18, 2014, 04:52:23 pm
Re: Polostar frequency switching fails sometimes
« Reply #4 on: February 27, 2013, 03:29:00 am »
Many thanks for your support (and for the great GM!!), but with that config i have the same failures  :(
But no matter, i will use the frontend with 15khz