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: Some resolutions shows up as natives after VMMaker install  (Read 1364 times)

0 Members and 1 Guest are viewing this topic.

haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1471
  • Last login:April 22, 2024, 03:17:30 am
  • retro maniac
Some resolutions shows up as natives after VMMaker install
« on: January 01, 2016, 04:41:10 pm »
Today I've reinstalled windows 7 and installed again latest CRT driver (I'm using Asus 4350) and latest VMMaker/ArcadeOSD.

Some modes shows up on ArcadeOSD list as native even those are generated by VMMaker like 288x240@60 or 352x256@55. On the first run many interlaced modes also shows up as natives but after using previous ArcadeOSD to test newer ArcadeOSD hangs during installing modes. So I reinstalled driver and this time interlaced modes returned but some resolutions like 288x240@60 shows twice (one with 59 Hz as native and second as custom). Some like 352x256@55 are only native and they cannot be used by groovymame.

I use here monitor arcade_15.
« Last Edit: October 15, 2016, 06:38:10 am by haynor666 »

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 7414
  • Last login:April 10, 2024, 02:02:31 pm
  • Quote me with care
Re: Some resolutions shows up as natives after VMMaker install
« Reply #1 on: January 01, 2016, 05:10:10 pm »
Duplication of some modes as @59 is a "feature" of windows 7, just ignore it.

However having some modes only as native is a problem, I hadn't noticed that, I'll need to check.
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

haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1471
  • Last login:April 22, 2024, 03:17:30 am
  • retro maniac
Re: Some resolutions shows up as natives after VMMaker install
« Reply #2 on: January 01, 2016, 05:55:34 pm »
For a first time many interlaced resolutions like 704x480@60i or 768x576@50i but also 1024x240@60p shows up as native. But why for a second time those modes were fine  ???

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 7414
  • Last login:April 10, 2024, 02:02:31 pm
  • Quote me with care
Re: Some resolutions shows up as natives after VMMaker install
« Reply #3 on: January 01, 2016, 05:59:48 pm »
For a first time many interlaced resolutions like 704x480@60i or 768x576@50i but also 1024x240@60p shows up as native. But why for a second time those modes were fine  ???

I don't understand what you mean by first time and second time.
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

haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1471
  • Last login:April 22, 2024, 03:17:30 am
  • retro maniac
Re: Some resolutions shows up as natives after VMMaker install
« Reply #4 on: January 01, 2016, 06:15:10 pm »
I've installed modes twice. For a first time when I noticed those problems I tried install modes using older VMMaker. Since it didn't help I reinstalled driver and installed modes using again new VMMaker. Then many modes that previously shows as native this time shows as custom.

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 7414
  • Last login:April 10, 2024, 02:02:31 pm
  • Quote me with care
Re: Some resolutions shows up as natives after VMMaker install
« Reply #5 on: January 02, 2016, 07:37:40 am »
I've added a fix for the issue you posted. I indeed had already fixed this for 13.1 but thought it was not required any more....... it is  :)

Quote
I've installed modes twice. For a first time when I noticed those problems I tried install modes using older VMMaker. Since it didn't help I reinstalled driver and installed modes using again new VMMaker. Then many modes that previously shows as native this time shows as custom.

There was a problem with beta 2 regarding the version of the certificate, hopefully that was a random side effect and is gone in beta 3.
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

haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1471
  • Last login:April 22, 2024, 03:17:30 am
  • retro maniac
Re: Some resolutions shows up as natives after VMMaker install
« Reply #6 on: January 02, 2016, 08:18:49 am »
Solved, all modes are now custom except those that should be native :)

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 7414
  • Last login:April 10, 2024, 02:02:31 pm
  • Quote me with care
Re: Some resolutions shows up as natives after VMMaker install
« Reply #7 on: January 02, 2016, 09:52:29 am »
Great! Thanks for testing.
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