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
Site News

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


  

Author Topic: Games with ISSUES: report here!  (Read 29930 times)

0 Members and 1 Guest are viewing this topic.

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Games with ISSUES: report here!
« on: July 29, 2011, 07:48:23 am »
In case you find a game that shows any kind of problem with GroovyMAME, please use this thread to report it.

FIRST: Test the game with mainline MAME to make sure the issue is not related to GroovyMAME patches.

SECOND: Get a proper log of your game by using the following command line:

             groovymame.exe romname -v >romname.txt

THIRD: Post a brief report of the issue, attaching your romname.txt (Go to "Additional Options...", Attach). Make sure you mention at least:
           - rom name (use the name of the rom file, so we can find it easier)
           - video card model
           - monitor type
           - video drivers and Windows versions.

« Last Edit: January 27, 2013, 05:10:44 pm by Calamity »
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

retrorepair

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 205
Re: Games with ISSUES: report here!
« Reply #1 on: January 19, 2012, 05:41:42 pm »
I have random crashes with Nebua Model 2 v0.9 using the custom drivers. It can take 1 hour or 1 minute, I can't narrow it down to a certain event.

Was fine with my old soft15khz setup with a GeForce so I assume it must be down to the driver version?

Radeon 3850
Nanao MS9 (15/24khz)
Win XP64

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #2 on: January 20, 2012, 09:20:16 am »
BubbleBobble fail start:
Code: [Select]
Parsing mame.ini
Parsing mame.ini
SwitchRes: Found output connector 'VGA-0'
SwitchRes: Monitor: pal Orientation: horizontal Aspect 4:3
SwitchRes: MonitorLimits 15625.00-15800.00,49.50-61.00,2.000,4.700,8.000,0.064,0.160,1.056,0,0,288.0,448
SwitchRes: Raw limits (59.1856Hz)-> YresMin= 243p, YresMax= 246p(492i)
SwitchRes: Logical limit YresMin (448/2) = 224p
SwitchRes: Setup monitor limits min=184x224 max=0x492
SwitchRes: Starting with Horizontal freq of 14.344 and Vertical refresh of 59.19
SwitchRes: Increased horizontal frequency from 14.344 to 15.625
SwitchRes: Using 20 lines padding
SwitchRes: # 15.625Khz -> 15.800Khz: ( | Hfreq Change | Vpad +20 lines | )
SwitchRes: # bublbobl [4] 256x224@59.19 15.6250Khz
SwitchRes: ModeLine          "256x224x59.19" 5.500000 256 272 304 352 224 235 238 264 -HSync -VSync

SwitchRes v0.013: [bublbobl] (1) horizontal (256x224@59.19)->(256x224@59.19)->(256x224@59.19)
SwitchRes: # bublbobl 256x224@59.19 15.6250Khz
SwitchRes:      ModeLine          "256x224x59.19" 5.500000 256 272 304 352 224 235 238 264 -HSync -VSync
SwitchRes: Setting Option -redraw 0
SwitchRes: Setting Option -rotate
SwitchRes: Setting Option -nothrottle
SwitchRes: Setting Option -refreshspeed
SwitchRes: Setting Option -waitvsync
SwitchRes: Xrandr ADD VGA-0:    ModeLine          "256x224x59.19" 5.500000 256 272 304 352 224 235 238 264 -HSync -VSync
SwitchRes: Running 'xrandr  --newmode      "256x224x59.19" 5.500000 256 272 304 352 224 235 238 264 -HSync -VSync'
SwitchRes: Running 'xrandr  --addmode VGA-0 256x224x59.19'
SwitchRes: Setting Option -resolution 256x224x32@59.185606
Setting SDL audiodriver 'dsp' ...
Build version:      0.144u6 (Jan 18 2012)
Build architecure:  SDLMAME_ARCH=
Build defines 1:    SDLMAME_UNIX=1 SDLMAME_X11=1 SDLMAME_LINUX=1
Build defines 1:    LSB_FIRST=1 PTR64=1 DISTRO=generic SYNC_IMPLEMENTATION=tc
SDL/OpenGL defines: SDL_COMPILEDVERSION=1214 USE_OPENGL=1 USE_DISPATCH_GL=1
Compiler defines A: __GNUC__=4 __GNUC_MINOR__=5 __GNUC_PATCHLEVEL__=2 __VERSION__="4.5.2"
Compiler defines B: __amd64__=1 __x86_64__=1 __unix__=1
Compiler defines C: __USE_FORTIFY_LEVEL=0
SDL Device Driver     : x11
SDL Monitor Dimensions: 768 x 576
Enter sdlwindow_init
Using SDL single-window OpenGL driver (SDL 1.2)
Leave sdlwindow_init
 768x 576 -> 0.001156
 256x 224 -> 2.000000
Loaded opengl shared library: <default>
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  149 (RANDR)
  Minor opcode of failed request:  2 (RRSetScreenConfig)
  Value in failed request:  0x100
  Serial number of failed request:  100
  Current serial number in output stream:  100
Rom name: bublbobl
Videocard: ati radeon hd5450
Monitor: pal tv
OS: slackware64 13.37
Earth could be the hell of another world

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #3 on: January 23, 2012, 11:39:27 am »
I have random crashes with Nebua Model 2 v0.9 using the custom drivers. It can take 1 hour or 1 minute, I can't narrow it down to a certain event.

Was fine with my old soft15khz setup with a GeForce so I assume it must be down to the driver version?

Radeon 3850
Nanao MS9 (15/24khz)
Win XP64

Hi retrorepair,

Do you mean a blue screen type crash, where the ati2mtag.sys file is mentioned as guilty or something different?
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

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #4 on: January 23, 2012, 11:42:05 am »
Rom name: bublbobl
Videocard: ati radeon hd5450
Monitor: pal tv
OS: slackware64 13.37

Hi Ansa89,

Thanks for the log. It seems to be related with xrandr not liking some of our params.

I checked bublbobl myself using last GA unofficial release (MAME v0.144u2) and it works just fine.

Please check snowbros and toki games too, to discard the classic low-dotclock issue.
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

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #5 on: January 23, 2012, 11:52:29 am »
Ok, I will check and post the log.
Earth could be the hell of another world

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #6 on: January 23, 2012, 12:50:44 pm »
Snowbros:
Code: [Select]
Parsing mame.ini
Parsing mame.ini
SwitchRes: Found output connector 'VGA-0'
SwitchRes: Monitor: pal Orientation: horizontal Aspect 4:3
SwitchRes: MonitorLimits 15625.00-15800.00,49.50-61.00,2.000,4.700,8.000,0.064,0.160,1.056,0,0,288.0,448
SwitchRes: Raw limits (57.5000Hz)-> YresMin= 251p, YresMax= 254p(508i)
SwitchRes: Logical limit YresMin (448/2) = 224p
SwitchRes: Setup monitor limits min=184x224 max=0x508
SwitchRes: Starting with Horizontal freq of 13.903 and Vertical refresh of 57.50
SwitchRes: Increased horizontal frequency from 13.903 to 15.625
SwitchRes: Using 28 lines padding
SwitchRes: # 15.625Khz -> 15.800Khz: ( | Hfreq Change | Vpad +28 lines | )
SwitchRes: # snowbros [5] 256x224@57.50 15.6400Khz
SwitchRes: ModeLine          "256x224x57.50" 5.505280 256 272 304 352 224 239 242 272 -HSync -VSync

SwitchRes v0.013: [snowbros] (1) horizontal (256x224@57.50)->(256x224@57.50)->(256x224@57.50)
SwitchRes: # snowbros 256x224@57.50 15.6400Khz
SwitchRes:      ModeLine          "256x224x57.50" 5.505280 256 272 304 352 224 239 242 272 -HSync -VSync
SwitchRes: Setting Option -redraw 0
SwitchRes: Setting Option -rotate
SwitchRes: Setting Option -nothrottle
SwitchRes: Setting Option -refreshspeed
SwitchRes: Setting Option -waitvsync
SwitchRes: Xrandr ADD VGA-0:    ModeLine          "256x224x57.50" 5.505280 256 272 304 352 224 239 242 272 -HSync -VSync
SwitchRes: Running 'xrandr  --newmode      "256x224x57.50" 5.505280 256 272 304 352 224 239 242 272 -HSync -VSync'
SwitchRes: Running 'xrandr  --addmode VGA-0 256x224x57.50'
SwitchRes: Setting Option -resolution 256x224x32@57.500000
Setting SDL audiodriver 'dsp' ...
Build version:      0.144u6 (Jan 18 2012)
Build architecure:  SDLMAME_ARCH=
Build defines 1:    SDLMAME_UNIX=1 SDLMAME_X11=1 SDLMAME_LINUX=1
Build defines 1:    LSB_FIRST=1 PTR64=1 DISTRO=generic SYNC_IMPLEMENTATION=tc
SDL/OpenGL defines: SDL_COMPILEDVERSION=1214 USE_OPENGL=1 USE_DISPATCH_GL=1
Compiler defines A: __GNUC__=4 __GNUC_MINOR__=5 __GNUC_PATCHLEVEL__=2 __VERSION__="4.5.2"
Compiler defines B: __amd64__=1 __x86_64__=1 __unix__=1
Compiler defines C: __USE_FORTIFY_LEVEL=0
SDL Device Driver     : x11
SDL Monitor Dimensions: 768 x 576
Enter sdlwindow_init
Using SDL single-window OpenGL driver (SDL 1.2)
Leave sdlwindow_init
 768x 576 -> 0.001156
 256x 224 -> 2.000000
Loaded opengl shared library: <default>


Toki:
Code: [Select]
Parsing mame.ini
Parsing mame.ini
SwitchRes: Found output connector 'VGA-0'
SwitchRes: Monitor: pal Orientation: horizontal Aspect 4:3
SwitchRes: MonitorLimits 15625.00-15800.00,49.50-61.00,2.000,4.700,8.000,0.064,0.160,1.056,0,0,288.0,448
SwitchRes: Raw limits (59.6100Hz)-> YresMin= 242p, YresMax= 245p(490i)
SwitchRes: Logical limit YresMin (448/2) = 224p
SwitchRes: Setup monitor limits min=184x224 max=0x490
SwitchRes: Starting with Horizontal freq of 14.456 and Vertical refresh of 59.61
SwitchRes: Increased horizontal frequency from 14.456 to 15.625
SwitchRes: Increasing 1 line from horizontal freq 15617.820 to 15677.430
SwitchRes: Using 19 lines padding
SwitchRes: # 15.625Khz -> 15.800Khz: ( | Hfreq Change | Vpad +19 lines | )
SwitchRes: # toki [4] 256x224@59.61 15.6774Khz
SwitchRes: ModeLine          "256x224x59.61" 5.518455 256 272 304 352 224 235 238 263 -HSync -VSync

SwitchRes v0.013: [toki] (1) horizontal (256x224@59.61)->(256x224@59.61)->(256x224@59.61)
SwitchRes: # toki 256x224@59.61 15.6774Khz
SwitchRes:      ModeLine          "256x224x59.61" 5.518455 256 272 304 352 224 235 238 263 -HSync -VSync
SwitchRes: Setting Option -redraw 0
SwitchRes: Setting Option -rotate
SwitchRes: Setting Option -nothrottle
SwitchRes: Setting Option -refreshspeed
SwitchRes: Setting Option -waitvsync
SwitchRes: Xrandr ADD VGA-0:    ModeLine          "256x224x59.61" 5.518455 256 272 304 352 224 235 238 263 -HSync -VSync
SwitchRes: Running 'xrandr  --newmode      "256x224x59.61" 5.518455 256 272 304 352 224 235 238 263 -HSync -VSync'
SwitchRes: Running 'xrandr  --addmode VGA-0 256x224x59.61'
SwitchRes: Setting Option -resolution 256x224x32@59.609996
Setting SDL audiodriver 'dsp' ...
Build version:      0.144u6 (Jan 18 2012)
Build architecure:  SDLMAME_ARCH=
Build defines 1:    SDLMAME_UNIX=1 SDLMAME_X11=1 SDLMAME_LINUX=1
Build defines 1:    LSB_FIRST=1 PTR64=1 DISTRO=generic SYNC_IMPLEMENTATION=tc
SDL/OpenGL defines: SDL_COMPILEDVERSION=1214 USE_OPENGL=1 USE_DISPATCH_GL=1
Compiler defines A: __GNUC__=4 __GNUC_MINOR__=5 __GNUC_PATCHLEVEL__=2 __VERSION__="4.5.2"
Compiler defines B: __amd64__=1 __x86_64__=1 __unix__=1
Compiler defines C: __USE_FORTIFY_LEVEL=0
SDL Device Driver     : x11
SDL Monitor Dimensions: 768 x 576
Enter sdlwindow_init
Using SDL single-window OpenGL driver (SDL 1.2)
Leave sdlwindow_init
 768x 576 -> 0.001156
 256x 224 -> 2.000000
Loaded opengl shared library: <default>

Both games don't start, but I found this and following these instructions (create "bublbobl.ini" file with "cleanstretch 1" and "switchres 0") BubbleBobble starts with a really crappy sound.
Why with a dedicated config file it starts? I have to create a config file for every game which doesn't start (it sounds a bit ugly)?
If you need the log of running bublbobl, just ask me.
« Last Edit: January 23, 2012, 01:06:48 pm by Ansa89 »
Earth could be the hell of another world

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #7 on: January 23, 2012, 01:42:39 pm »
Why with a dedicated config file it starts?

It just works because you're disabling the switchres engine so xrand is not invoked.

Yes, that's the classic low dotclock issue. I was going to refer you to that specific thread, it's a pity that it didn't get solved.

The only thing I can think of right now is that a folk who has ported Groovy patches to an Ubuntu distribution needed to make additional patches in order to make xorg accept resolutions below 320x240:
http://david.dantoine.org/destacado/922/
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

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #8 on: January 26, 2012, 08:04:25 am »
Got the patch! 8)
Now BubbleBobble, Toki and SnowBros are displayed well, but...

MetalSlug (mslug) doesn't start at all (nothing new: also before patching it didn't start):
Code: [Select]
Parsing mame.ini
Parsing mame.ini
SwitchRes: Found output connector 'VGA-0'
SwitchRes: Monitor: pal Orientation: horizontal Aspect 4:3
SwitchRes: MonitorLimits 15625.00-15800.00,49.50-61.00,2.000,4.700,8.000,0.064,0.160,1.056,0,0,288.0,448
SwitchRes: Raw limits (59.1856Hz)-> YresMin= 243p, YresMax= 246p(492i)
SwitchRes: Logical limit YresMin (448/2) = 224p
SwitchRes: Setup monitor limits min=184x224 max=0x492
SwitchRes: Starting with Horizontal freq of 14.344 and Vertical refresh of 59.19
SwitchRes: Increased horizontal frequency from 14.344 to 15.625
SwitchRes: Using 20 lines padding
SwitchRes: # 15.625Khz -> 15.800Khz: ( | Hfreq Change | Vpad +20 lines | )
SwitchRes: # mslug.zip [4] 320x224@59.19 15.6250Khz
SwitchRes: ModeLine          "320x224x59.19" 6.625000 320 336 368 424 224 235 238 264 -HSync -VSync

SwitchRes v0.013: [mslug.zip] (1) horizontal (320x224@59.19)->(320x224@59.19)->(320x224@59.19)
SwitchRes: # mslug.zip 320x224@59.19 15.6250Khz
SwitchRes:      ModeLine          "320x224x59.19" 6.625000 320 336 368 424 224 235 238 264 -HSync -VSync
SwitchRes: Setting Option -redraw 0
SwitchRes: Setting Option -rotate
SwitchRes: Setting Option -nothrottle
SwitchRes: Setting Option -refreshspeed
SwitchRes: Setting Option -waitvsync
SwitchRes: Xrandr ADD VGA-0:    ModeLine          "320x224x59.19" 6.625000 320 336 368 424 224 235 238 264 -HSync -VSync
SwitchRes: Running 'xrandr  --newmode      "320x224x59.19" 6.625000 320 336 368 424 224 235 238 264 -HSync -VSync'
SwitchRes: Running 'xrandr  --addmode VGA-0 320x224x59.19'
SwitchRes: Setting Option -resolution 320x224x32@59.185606
Setting SDL audiodriver 'dsp' ...
Build version:      0.144u6 (Jan 25 2012)
Build architecure:  SDLMAME_ARCH=
Build defines 1:    SDLMAME_UNIX=1 SDLMAME_X11=1 SDLMAME_LINUX=1
Build defines 1:    LSB_FIRST=1 PTR64=1 DISTRO=generic SYNC_IMPLEMENTATION=tc
SDL/OpenGL defines: SDL_COMPILEDVERSION=1214 USE_OPENGL=1 USE_DISPATCH_GL=1
Compiler defines A: __GNUC__=4 __GNUC_MINOR__=5 __GNUC_PATCHLEVEL__=2 __VERSION__="4.5.2"
Compiler defines B: __amd64__=1 __x86_64__=1 __unix__=1
Compiler defines C: __USE_FORTIFY_LEVEL=0
SDL Device Driver     : x11
SDL Monitor Dimensions: 768 x 576
Enter sdlwindow_init
Using SDL single-window OpenGL driver (SDL 1.2)
Leave sdlwindow_init
 768x 576 -> 0.001248
 320x 224 -> 2.000000
Loaded opengl shared library: <default>
OpenGL: Advanced Micro Devices, Inc.
OpenGL: Mesa DRI R600 (CEDAR 68F9) 20090101  TCL DRI2
OpenGL: 2.1 Mesa 7.9.2
OpenGL: texture rectangle supported
OpenGL: non-power-of-2 textures supported (new method)
OpenGL: vertex buffer supported
OpenGL: pixel buffers supported
OpenGL: framebuffer object supported
OpenGL: GLSL supported, but disabled
OpenGL: max texture size 4096 x 4096
Keyboard: Start initialization
Input: Adding Kbd #0: System keyboard
Keyboard: Registered System keyboard
Keyboard: End initialization
Mouse: Start initialization
Input: Adding Mouse #0: System mouse
Mouse: Registered System mouse
Mouse: End initialization
Joystick: Start initialization
Joystick: End initialization
Audio: Start initialization
Audio: Driver is dsp
Audio: frequency: 48000, channels: 2, samples: 512
sdl_create_buffers: creating stream buffer of 114688 bytes
Audio: End initialization
ouput: unable to open output notifier file /tmp/sdlmame_out
Searching font Liberation Sans in -fontpath
Matching font: /usr/share/fonts/TTF/LiberationSans-Regular.ttf
Starting Driver Device 'root'
  (missing dependencies; rescheduling)
Starting 68000 'maincpu'
Starting Z80 'audiocpu'
Starting NVRAM 'saveram'
Starting Video Screen 'screen'
Starting Speaker 'lspeaker'
  (missing dependencies; rescheduling)
Starting Speaker 'rspeaker'
  (missing dependencies; rescheduling)
Starting YM2610 'ymsnd'
Starting NEC uPD4990A 'upd4990a'
Starting Driver Device 'root'
  (missing dependencies; rescheduling)
Starting Speaker 'lspeaker'
Starting Speaker 'rspeaker'
Starting Driver Device 'root'
Loading cheats file from /home/roms/cheat/mslug.xml

BubbleBobble2 (bublbob2) graphic is screwed up (before patching it was playable without problems):
Code: [Select]
Parsing mame.ini
Parsing mame.ini
SwitchRes: Found output connector 'VGA-0'
SwitchRes: Monitor: pal Orientation: horizontal Aspect 4:3
SwitchRes: MonitorLimits 15625.00-15800.00,49.50-61.00,2.000,4.700,8.000,0.064,0.160,1.056,0,0,288.0,448
SwitchRes: Raw limits (58.9700Hz)-> YresMin= 244p, YresMax= 247p(494i)
SwitchRes: Logical limit YresMin (448/2) = 224p
SwitchRes: Setup monitor limits min=184x224 max=0x494
SwitchRes: Starting with Horizontal freq of 14.288 and Vertical refresh of 58.97
SwitchRes: Increased horizontal frequency from 14.288 to 15.625
SwitchRes: Using 21 lines padding
SwitchRes: # 15.625Khz -> 15.800Khz: ( | Hfreq Change | Vpad +21 lines | )
SwitchRes: # bublbob2.zip [4] 320x224@58.97 15.6270Khz
SwitchRes: ModeLine          "320x224x58.97" 6.625869 320 336 368 424 224 236 239 265 -HSync -VSync

SwitchRes v0.013: [bublbob2.zip] (1) horizontal (320x224@58.97)->(320x224@58.97)->(320x224@58.97)
SwitchRes: # bublbob2.zip 320x224@58.97 15.6270Khz
SwitchRes:      ModeLine          "320x224x58.97" 6.625869 320 336 368 424 224 236 239 265 -HSync -VSync
SwitchRes: Setting Option -redraw 0
SwitchRes: Setting Option -rotate
SwitchRes: Setting Option -nothrottle
SwitchRes: Setting Option -refreshspeed
SwitchRes: Setting Option -waitvsync
SwitchRes: Xrandr ADD VGA-0:    ModeLine          "320x224x58.97" 6.625869 320 336 368 424 224 236 239 265 -HSync -VSync
SwitchRes: Running 'xrandr  --newmode      "320x224x58.97" 6.625869 320 336 368 424 224 236 239 265 -HSync -VSync'
SwitchRes: Running 'xrandr  --addmode VGA-0 320x224x58.97'
SwitchRes: Setting Option -resolution 320x224x32@58.969998
Setting SDL audiodriver 'dsp' ...
Build version:      0.144u6 (Jan 25 2012)
Build architecure:  SDLMAME_ARCH=
Build defines 1:    SDLMAME_UNIX=1 SDLMAME_X11=1 SDLMAME_LINUX=1
Build defines 1:    LSB_FIRST=1 PTR64=1 DISTRO=generic SYNC_IMPLEMENTATION=tc
SDL/OpenGL defines: SDL_COMPILEDVERSION=1214 USE_OPENGL=1 USE_DISPATCH_GL=1
Compiler defines A: __GNUC__=4 __GNUC_MINOR__=5 __GNUC_PATCHLEVEL__=2 __VERSION__="4.5.2"
Compiler defines B: __amd64__=1 __x86_64__=1 __unix__=1
Compiler defines C: __USE_FORTIFY_LEVEL=0
SDL Device Driver     : x11
SDL Monitor Dimensions: 320 x 224
Enter sdlwindow_init
Using SDL single-window OpenGL driver (SDL 1.2)
Leave sdlwindow_init
 768x 576 -> 0.001248
 320x 224 -> 2.000000
Loaded opengl shared library: <default>
OpenGL: Advanced Micro Devices, Inc.
OpenGL: Mesa DRI R600 (CEDAR 68F9) 20090101  TCL DRI2
OpenGL: 2.1 Mesa 7.9.2
OpenGL: texture rectangle supported
OpenGL: non-power-of-2 textures supported (new method)
OpenGL: vertex buffer supported
OpenGL: pixel buffers supported
OpenGL: framebuffer object supported
OpenGL: GLSL supported, but disabled
OpenGL: max texture size 4096 x 4096
Keyboard: Start initialization
Input: Adding Kbd #0: System keyboard
Keyboard: Registered System keyboard
Keyboard: End initialization
Mouse: Start initialization
Input: Adding Mouse #0: System mouse
Mouse: Registered System mouse
Mouse: End initialization
Joystick: Start initialization
Joystick: End initialization
Audio: Start initialization
Audio: Driver is dsp
Audio: frequency: 48000, channels: 2, samples: 512
sdl_create_buffers: creating stream buffer of 114688 bytes
Audio: End initialization
ouput: unable to open output notifier file /tmp/sdlmame_out
Searching font Liberation Sans in -fontpath
Matching font: /usr/share/fonts/TTF/LiberationSans-Regular.ttf
Starting Driver Device 'root'
  (missing dependencies; rescheduling)
Starting 68EC020 'maincpu'
Starting EEPROM 'eeprom'
Starting Video Screen 'screen'
Starting Timer 'timer_68681'
Starting 68000 'audiocpu'
Starting Speaker 'lspeaker'
  (missing dependencies; rescheduling)
Starting Speaker 'rspeaker'
  (missing dependencies; rescheduling)
Starting ES5505 'ensoniq'
Starting Driver Device 'root'
  (missing dependencies; rescheduling)
Starting Speaker 'lspeaker'
Starting Speaker 'rspeaker'
Starting Driver Device 'root'
Loading cheats file from /home/roms/cheat/bublbob2.xml
OpenGL: VBO supported
OpenGL: PBO supported
OpenGL: FBO supported
OpenGL: using vid filter: 0
GL texture: copy 0, shader 0, dynamic 0, 320x224 320x224 [RGB32, Equal: 1, Palette: 0,
            scale 1x1, border 0, pitch 416,320/4096], colors: 8192, bytes/pix 4
GL texture: copy 0, shader 0, dynamic 0, 320x224 320x224 [RGB32, Equal: 1, Palette: 0,
            scale 1x1, border 0, pitch 416,320/4096], colors: 8192, bytes/pix 4
Average speed: 100.39% (75 seconds)
sdl_kill: closing audio
Sound buffer: overflows=3 underflows=0
Joystick: Start deinitialization
Joystick: End deinitialization
Enter sdlwindow_exit
Leave sdlwindow_exit
SwitchRes: Xrandr REMOVE VGA-0:         ModeLine     320x224x58.97
SwitchRes: Running 'xrandr  --delmode VGA-0 "320x224x58.97"'
SwitchRes: Running 'xrandr  --rmmode "320x224x58.97"'

Videocard: ati radeon hd5450
Monitor: pal tv
OS: slackware64 13.37
Earth could be the hell of another world

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #9 on: January 26, 2012, 11:53:23 am »
So that patch work partially, that's good! I guess why Groovy Arcade doesn't seem to need that patch. You're probably in better possition than me to have a global vision of what's going on in the Linux patch, I appreciate your efforts.

Definitely don't have a clue with the other issue. Is the resolution actually set before mslug exits?
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

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #10 on: January 26, 2012, 12:47:59 pm »
So that patch work partially, that's good! I guess why Groovy Arcade doesn't seem to need that patch. You're probably in better possition than me to have a global vision of what's going on in the Linux patch, I appreciate your efforts.
Well, I don't know why GA doesn't need this patch, but we must remember that computer-science is not a "precise-science" (specially when talking about linux).
What I mean is that everyone have to check his own system and find a way to achieve the goal (there are too many software, each one with major/minor changes between two release...that's a lot of mess).
I know that gentoo (the base of GA) often patch its packages before compilation, so it could be the emerge script will apply a patch (involuntary) which resolve that problem. Maybe a day I will investigate this.


Definitely don't have a clue with the other issue. Is the resolution actually set before mslug exits?
The monitor become black and I don't see nothing, so I don't know if the resolution change before groovymame gives up :-\ .
Earth could be the hell of another world

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #11 on: January 29, 2012, 10:19:28 am »
Would resolve the problem, if I create a "ini/bublbob2.ini" with "modeline 0" (or with a fixed resolution)?
Earth could be the hell of another world

mazinger-z

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 47
Burning Rival (brival)
« Reply #12 on: January 30, 2012, 04:41:05 am »
Hello, there seems to be something going seriously wrong with this one. I can perfectly do without this game, but I'm reporting the issue here, in case some other game is affected. The problem doesn't happen with the latest official MAME build.

The game is "Burning Rival" (romset name: brival)

The problems are different, depending on how and where you run the emulator. On my arcade setup (Radeon 9200 AGP, 15KHz 25 inches arcade monitor, WinXP32 and CRT emudriver 6.5) I had 2 different behaviors.
1. I get the normal screen with the game's specs, then a message about the emulation driver not being 100% accurate. From now on it keeps switching resolutions forever.
2. If I force 416x224@60 by commandline, the game runs at about 50% speed without further problems.

On my everyday PC (integrated Nvidia 6150SE, VGA 17 inches CRT monitor, WinXP32), I get an even different behavior. The game starts normally, but there's a resolution switch at every screen change (i.e. from title screen to character selection screen). Then, when I insert a coin, I get a black screen, the emulator becomes unresponsive and I have to shut it down forcefully. I'm attaching the log from this setup.

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #13 on: January 30, 2012, 07:43:36 am »
Would resolve the problem, if I create a "ini/bublbob2.ini" with "modeline 0" (or with a fixed resolution)?

Well, just try and report back ;) bublbob2 issue is strange because the game runs normally, doesn't it? Try running it with modeline 0 in order to see if it Switchres-patch related.

As for the mslug issue, it is similar of some crashes we had before which ended up being related to the PLL divider routines. This code comes directly from ATI/AMD. By the time when GroovyArcade was developed Chris was in contact with the guy in AMD who deals with Linux drivers, and thanks to this, some fixes could be added to ATI core routines to improve the behaviour for lower dotclocks. Could it be that some other Linux distributions do not contain the same PLL routines?
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

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Burning Rival (brival)
« Reply #14 on: January 30, 2012, 07:54:25 am »
The problems are different, depending on how and where you run the emulator. On my arcade setup (Radeon 9200 AGP, 15KHz 25 inches arcade monitor, WinXP32 and CRT emudriver 6.5) I had 2 different behaviors.
1. I get the normal screen with the game's specs, then a message about the emulation driver not being 100% accurate. From now on it keeps switching resolutions forever.
2. If I force 416x224@60 by commandline, the game runs at about 50% speed without further problems.

There're still issues with games which change resolutions. I think I have a fix for that, it will go for next release.

By now, try disabling the -changeres and the -multithreading options for those games.
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

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #15 on: January 30, 2012, 08:17:41 am »
As for the mslug issue, it is similar of some crashes we had before which ended up being related to the PLL divider routines. This code comes directly from ATI/AMD. By the time when GroovyArcade was developed Chris was in contact with the guy in AMD who deals with Linux drivers, and thanks to this, some fixes could be added to ATI core routines to improve the behaviour for lower dotclocks. Could it be that some other Linux distributions do not contain the same PLL routines?
I think the PLL routines are into kernel mainline and they are patched with the "ati9200_pllfix.diff" file (which is part of "15KHz patch"), the questions could be
- does this fix work correctly with new ATI graphic cards?
- is this fix applied only to ATI 9200 cards, or it involves some wide-used routines?

For sure, the PLL routines change as change the kernel version (obviously only if developers change that part of kernel source, but this is the idea), so someone should check if something important has changed in new kernel releases.
Earth could be the hell of another world

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #16 on: January 30, 2012, 10:21:43 am »
As for the mslug issue, it is similar of some crashes we had before which ended up being related to the PLL divider routines. This code comes directly from ATI/AMD. By the time when GroovyArcade was developed Chris was in contact with the guy in AMD who deals with Linux drivers, and thanks to this, some fixes could be added to ATI core routines to improve the behaviour for lower dotclocks. Could it be that some other Linux distributions do not contain the same PLL routines?
I think the PLL routines are into kernel mainline and they are patched with the "ati9200_pllfix.diff" file (which is part of "15KHz patch"), the questions could be
- does this fix work correctly with new ATI graphic cards?
- is this fix applied only to ATI 9200 cards, or it involves some wide-used routines?

For sure, the PLL routines change as change the kernel version (obviously only if developers change that part of kernel source, but this is the idea), so someone should check if something important has changed in new kernel releases.

Well, that's not the patch I mean. That one was added to override the lower limits that were read from the card's bios (combios).

As you say, the pll routines are in the very kernel so there was no patch for them I believe, just the fix that came from AMD. But they might have change it again since then so that might be the issue. I remind the routine having two versions, one for newer cards and another for legacy cards and the issue was with the second one. However, the HD 5000 family was not tested thoroughly possibly.
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

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #17 on: February 03, 2012, 06:42:09 am »
After two days digging and searching for changed pll routines into kernel mainline, I give up.
The conclusion is that I have too limited knowledge for this (and at this point is only a waste of time).

I hope bitbytebit will come back with new magic patches (or something like that).
Earth could be the hell of another world

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #18 on: February 03, 2012, 07:10:03 am »
After two days digging and searching for changed pll routines into kernel mainline, I give up.
The conclusion is that I have too limited knowledge for this (and at this point is only a waste of time).

I hope bitbytebit will come back with new magic patches (or something like that).

Hi Ansa, sorry I can't be of much help. Is there a place to check source files for kernel of both the version in GroovyMAME cd and the one your using?
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

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #19 on: February 03, 2012, 07:25:56 am »
It should be enough to know the kernel version used by GroovyArcade, then you download that version from http://www.kernel.org and patch it with 15KHz patches.
Same process for my version (which is 3.2.2).
Now you have two directories like "linux-GA_VERSION" and "linux-3.2.2", and you can "diff -ruN linux-GA_VERSION/drivers/gpu/drm/radeon linux-3.2.2/drivers/gpu/drm/radeon" or (if you are really crazy/courageous) "diff -ruN linux-GA_VERSION linux-3.2.2".

If there is something not clear, just ask.


EDIT: if GroovyArcade kernel version is 3.0.2, then
- download this
- download this
- unpack the two files
- OPTIONAL apply 15KHz patches
- run "diff -ruN linux-3.0.2/drivers/gpu/drm/radeon linux-3.2.2/drivers/gpu/drm/radeon" (or whatever you need to see the differences)
« Last Edit: February 03, 2012, 12:14:38 pm by Ansa89 »
Earth could be the hell of another world

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #20 on: February 03, 2012, 07:36:35 am »
Yes, it's just that I don't know which is the kernel version in the last GroovyArcade CD :)
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

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #21 on: February 03, 2012, 08:00:38 am »
Oh, ok.
Do you mean latest official or unofficial release?
The kernel used by latest official release should be 3.0.2.
I never run the unofficial one ::) .
Earth could be the hell of another world

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #22 on: February 03, 2012, 11:56:50 am »
Oh, ok.
Do you mean latest official or unofficial release?
The kernel used by latest official release should be 3.0.2.
I never run the unofficial one ::) .

I bet both official and unoffial release use the same kernel, 3.0.2 then.

So it's a matter of comparing 3.0.2 vs 3.2.2. I assume I need to download the whole source, no way to browse it online, I'm I right?
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

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #23 on: February 03, 2012, 12:01:33 pm »
Yes, you right.
The steps are the same as I posted before.
Earth could be the hell of another world

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #24 on: February 06, 2012, 10:02:37 am »
Some news: I compiled kernel 3.2.4 and upgraded xf86-video-ati to 6.14.2 (from 6.14.1).
Now a lot of games (BubbleBoble, MetalSlug 1/2/3/X, and others) run at about 300% speed, so they are unplayable.
As I wrote before, now "mslug" works (3 times faster than original speed).
Log from "mslug":
Code: [Select]
Parsing mame.ini
Parsing mame.ini
SwitchRes: Found output connector 'VGA-0'
SwitchRes: Monitor: pal Orientation: horizontal Aspect 4:3
SwitchRes: MonitorLimits 15625.00-15800.00,49.50-61.00,2.000,4.700,8.000,0.064,0.160,1.056,0,0,288.0,448
SwitchRes: Raw limits (59.1856Hz)-> YresMin= 243p, YresMax= 246p(492i)
SwitchRes: Logical limit YresMin (448/2) = 224p
SwitchRes: Setup monitor limits min=184x224 max=0x492
SwitchRes: Starting with Horizontal freq of 14.344 and Vertical refresh of 59.19
SwitchRes: Increased horizontal frequency from 14.344 to 15.625
SwitchRes: Using 20 lines padding
SwitchRes: # 15.625Khz -> 15.800Khz: ( | Hfreq Change | Vpad +20 lines | )
SwitchRes: # mslug [4] 320x224@59.19 15.6250Khz
SwitchRes: ModeLine          "320x224x59.19" 6.625000 320 336 368 424 224 235 238 264 -HSync -VSync

SwitchRes v0.013: [mslug] (1) horizontal (320x224@59.19)->(320x224@59.19)->(320x224@59.19)
SwitchRes: # mslug 320x224@59.19 15.6250Khz
SwitchRes: ModeLine          "320x224x59.19" 6.625000 320 336 368 424 224 235 238 264 -HSync -VSync
SwitchRes: Setting Option -redraw 0
SwitchRes: Setting Option -rotate
SwitchRes: Setting Option -nothrottle
SwitchRes: Setting Option -refreshspeed
SwitchRes: Setting Option -waitvsync
SwitchRes: Xrandr ADD VGA-0: ModeLine          "320x224x59.19" 6.625000 320 336 368 424 224 235 238 264 -HSync -VSync
SwitchRes: Running 'xrandr  --newmode      "320x224x59.19" 6.625000 320 336 368 424 224 235 238 264 -HSync -VSync'
SwitchRes: Running 'xrandr  --addmode VGA-0 320x224x59.19'
SwitchRes: Setting Option -resolution 320x224x32@59.185606
Setting SDL audiodriver 'dsp' ...
Build version:      0.144u7 (Feb  6 2012)
Build architecure:  SDLMAME_ARCH=
Build defines 1:    SDLMAME_UNIX=1 SDLMAME_X11=1 SDLMAME_LINUX=1
Build defines 1:    LSB_FIRST=1 PTR64=1 DISTRO=generic SYNC_IMPLEMENTATION=tc
SDL/OpenGL defines: SDL_COMPILEDVERSION=1214 USE_OPENGL=1 USE_DISPATCH_GL=1
Compiler defines A: __GNUC__=4 __GNUC_MINOR__=5 __GNUC_PATCHLEVEL__=2 __VERSION__="4.5.2"
Compiler defines B: __amd64__=1 __x86_64__=1 __unix__=1
Compiler defines C: __USE_FORTIFY_LEVEL=0
SDL Device Driver     : x11
SDL Monitor Dimensions: 768 x 576
Enter sdlwindow_init
Using SDL single-window OpenGL driver (SDL 1.2)
Leave sdlwindow_init
 768x 576 -> 0.001248
 320x 224 -> 2.000000
Loaded opengl shared library: <default>
OpenGL: Advanced Micro Devices, Inc.
OpenGL: Mesa DRI R600 (CEDAR 68F9) 20090101  TCL DRI2
OpenGL: 2.1 Mesa 7.9.2
OpenGL: texture rectangle supported
OpenGL: non-power-of-2 textures supported (new method)
OpenGL: vertex buffer supported
OpenGL: pixel buffers supported
OpenGL: framebuffer object supported
OpenGL: GLSL supported, but disabled
OpenGL: max texture size 4096 x 4096
Keyboard: Start initialization
Input: Adding Kbd #0: System keyboard
Keyboard: Registered System keyboard
Keyboard: End initialization
Mouse: Start initialization
Input: Adding Mouse #0: System mouse
Mouse: Registered System mouse
Mouse: End initialization
Joystick: Start initialization
Joystick: End initialization
Audio: Start initialization
Audio: Driver is dsp
Audio: frequency: 48000, channels: 2, samples: 512
sdl_create_buffers: creating stream buffer of 114688 bytes
Audio: End initialization
ouput: unable to open output notifier file /tmp/sdlmame_out
ioport ':IN0' created
ioport ':IN1' created
ioport ':IN2' created
ioport ':IN3' created
ioport ':IN4' created
device ':' adding mapping for ':' => ':'
device ':' adding mapping for ':maincpu' => ':maincpu'
Region ':maincpu' created
Region ':fixed' created
Region ':fixedbios' created
Region ':zoomy' created
Region ':mainbios' created
Region ':audiobios' created
device ':' adding mapping for ':audiocpu' => ':audiocpu'
Region ':audiocpu' created
device ':' adding mapping for ':ymsnd' => ':ymsnd'
Region ':ymsnd' created
Region ':sprites' created
Searching font Liberation Sans in -fontpath
Matching font: /usr/share/fonts/TTF/LiberationSans-Regular.ttf
Starting Driver Device ':'
  (missing dependencies; rescheduling)
Starting 68000 ':maincpu'
Starting Z80 ':audiocpu'
Starting NVRAM ':saveram'
Starting Video Screen ':screen'
Starting Speaker ':lspeaker'
device ':' adding mapping for ':lspeaker' => ':lspeaker'
  (missing dependencies; rescheduling)
Starting Speaker ':rspeaker'
device ':' adding mapping for ':rspeaker' => ':rspeaker'
  (missing dependencies; rescheduling)
Starting YM2610 ':ymsnd'
Starting NEC uPD4990A ':upd4990a'
Starting Driver Device ':'
  (missing dependencies; rescheduling)
Starting Speaker ':lspeaker'
Starting Speaker ':rspeaker'
Starting Driver Device ':'
device ':' adding mapping for 'saveram' => ':saveram'
device ':' adding mapping for 'maincpu' => ':maincpu'
device ':' adding mapping for 'audiocpu' => ':audiocpu'
device ':' adding mapping for 'upd4990a' => ':upd4990a'
Loading cheats file from /home/roms/cheat/mslug.xml
Ignoring MAME exception: mslug.xml(5): error parsing cheat expression "maincpu.pb@106E93=3C" (invalid memory name)

mslug.xml(5): error parsing cheat expression "maincpu.pb@106E93=3C" (invalid memory name)

OpenGL: VBO supported
OpenGL: PBO supported
OpenGL: FBO supported
OpenGL: using vid filter: 0
GL texture: copy 0, shader 0, dynamic 0, 320x224 320x224 [RGB32, Equal: 1, Palette: 0,
            scale 1x1, border 0, pitch 384,320/4096], colors: 0, bytes/pix 4
GL texture: copy 0, shader 0, dynamic 0, 320x224 320x224 [RGB32, Equal: 1, Palette: 0,
            scale 1x1, border 0, pitch 384,320/4096], colors: 0, bytes/pix 4
Average speed: 365.30% (164 seconds)
sdl_kill: closing audio
Sound buffer: overflows=5973 underflows=0
Joystick: Start deinitialization
Joystick: End deinitialization
Enter sdlwindow_exit
Leave sdlwindow_exit
SwitchRes: Xrandr REMOVE VGA-0: ModeLine     320x224x59.19
SwitchRes: Running 'xrandr  --delmode VGA-0 "320x224x59.19"'
SwitchRes: Running 'xrandr  --rmmode "320x224x59.19"'
Log from "bublbobl":
Code: [Select]
Parsing mame.ini
Parsing mame.ini
SwitchRes: Found output connector 'VGA-0'
SwitchRes: Monitor: pal Orientation: horizontal Aspect 4:3
SwitchRes: MonitorLimits 15625.00-15800.00,49.50-61.00,2.000,4.700,8.000,0.064,0.160,1.056,0,0,288.0,448
SwitchRes: Raw limits (59.1856Hz)-> YresMin= 243p, YresMax= 246p(492i)
SwitchRes: Logical limit YresMin (448/2) = 224p
SwitchRes: Setup monitor limits min=184x224 max=0x492
SwitchRes: Starting with Horizontal freq of 14.344 and Vertical refresh of 59.19
SwitchRes: Increased horizontal frequency from 14.344 to 15.625
SwitchRes: Using 20 lines padding
SwitchRes: # 15.625Khz -> 15.800Khz: ( | Hfreq Change | Vpad +20 lines | )
SwitchRes: # bublbobl [4] 256x224@59.19 15.6250Khz
SwitchRes: ModeLine          "256x224x59.19" 5.500000 256 272 304 352 224 235 238 264 -HSync -VSync

SwitchRes v0.013: [bublbobl] (1) horizontal (256x224@59.19)->(256x224@59.19)->(256x224@59.19)
SwitchRes: # bublbobl 256x224@59.19 15.6250Khz
SwitchRes: ModeLine          "256x224x59.19" 5.500000 256 272 304 352 224 235 238 264 -HSync -VSync
SwitchRes: Setting Option -redraw 0
SwitchRes: Setting Option -rotate
SwitchRes: Setting Option -nothrottle
SwitchRes: Setting Option -refreshspeed
SwitchRes: Setting Option -waitvsync
SwitchRes: Xrandr ADD VGA-0: ModeLine          "256x224x59.19" 5.500000 256 272 304 352 224 235 238 264 -HSync -VSync
SwitchRes: Running 'xrandr  --newmode      "256x224x59.19" 5.500000 256 272 304 352 224 235 238 264 -HSync -VSync'
SwitchRes: Running 'xrandr  --addmode VGA-0 256x224x59.19'
SwitchRes: Setting Option -resolution 256x224x32@59.185606
Setting SDL audiodriver 'dsp' ...
Build version:      0.144u7 (Feb  6 2012)
Build architecure:  SDLMAME_ARCH=
Build defines 1:    SDLMAME_UNIX=1 SDLMAME_X11=1 SDLMAME_LINUX=1
Build defines 1:    LSB_FIRST=1 PTR64=1 DISTRO=generic SYNC_IMPLEMENTATION=tc
SDL/OpenGL defines: SDL_COMPILEDVERSION=1214 USE_OPENGL=1 USE_DISPATCH_GL=1
Compiler defines A: __GNUC__=4 __GNUC_MINOR__=5 __GNUC_PATCHLEVEL__=2 __VERSION__="4.5.2"
Compiler defines B: __amd64__=1 __x86_64__=1 __unix__=1
Compiler defines C: __USE_FORTIFY_LEVEL=0
SDL Device Driver     : x11
SDL Monitor Dimensions: 768 x 576
Enter sdlwindow_init
Using SDL single-window OpenGL driver (SDL 1.2)
Leave sdlwindow_init
 768x 576 -> 0.001156
 256x 224 -> 2.000000
Loaded opengl shared library: <default>
OpenGL: Advanced Micro Devices, Inc.
OpenGL: Mesa DRI R600 (CEDAR 68F9) 20090101  TCL DRI2
OpenGL: 2.1 Mesa 7.9.2
OpenGL: texture rectangle supported
OpenGL: non-power-of-2 textures supported (new method)
OpenGL: vertex buffer supported
OpenGL: pixel buffers supported
OpenGL: framebuffer object supported
OpenGL: GLSL supported, but disabled
OpenGL: max texture size 4096 x 4096
Keyboard: Start initialization
Input: Adding Kbd #0: System keyboard
Keyboard: Registered System keyboard
Keyboard: End initialization
Mouse: Start initialization
Input: Adding Mouse #0: System mouse
Mouse: Registered System mouse
Mouse: End initialization
Joystick: Start initialization
Joystick: End initialization
Audio: Start initialization
Audio: Driver is dsp
Audio: frequency: 48000, channels: 2, samples: 512
sdl_create_buffers: creating stream buffer of 114688 bytes
Audio: End initialization
ouput: unable to open output notifier file /tmp/sdlmame_out
ioport ':IN0' created
ioport ':DSW0' created
ioport ':DSW1' created
ioport ':IN1' created
ioport ':IN2' created
device ':' adding mapping for ':maincpu' => ':maincpu'
Region ':maincpu' created
device ':' adding mapping for ':slave' => ':slave'
Region ':slave' created
device ':' adding mapping for ':audiocpu' => ':audiocpu'
Region ':audiocpu' created
device ':' adding mapping for ':mcu' => ':mcu'
Region ':mcu' created
Region ':gfx1' created
Region ':proms' created
Region ':plds' created
pal16l8.bin NOT FOUND (NO GOOD DUMP KNOWN)
pal16l8.bin NOT FOUND (NO GOOD DUMP KNOWN)
pal16r4.bin NOT FOUND (NO GOOD DUMP KNOWN)
WARNING: the game might not run correctly.
device ':' adding mapping for ':ym2' => ':ym2'
device ':' adding mapping for ':ym1' => ':ym1'
Searching font Liberation Sans in -fontpath
Matching font: /usr/share/fonts/TTF/LiberationSans-Regular.ttf
Starting Driver Device ':'
  (missing dependencies; rescheduling)
Starting Z80 ':maincpu'
Starting Z80 ':slave'
Starting Z80 ':audiocpu'
Starting M6801 ':mcu'
Starting Video Screen ':screen'
Starting Speaker ':mono'
device ':' adding mapping for ':mono' => ':mono'
  (missing dependencies; rescheduling)
Starting YM2203 ':ym1'
Starting YM3526 ':ym2'
Starting Driver Device ':'
  (missing dependencies; rescheduling)
Starting Speaker ':mono'
Starting Driver Device ':'
device ':' adding mapping for 'maincpu' => ':maincpu'
device ':' adding mapping for 'mcu' => ':mcu'
device ':' adding mapping for 'audiocpu' => ':audiocpu'
device ':' adding mapping for 'slave' => ':slave'
Loading cheats file from /home/roms/cheat/bublbobl.xml
Ignoring MAME exception: bublbobl.xml(10): error parsing cheat expression "maincpu.pb@E366=63" (invalid memory name)

bublbobl.xml(10): error parsing cheat expression "maincpu.pb@E366=63" (invalid memory name)

device ':' adding mapping for 'screen' => ':screen'
OpenGL: VBO supported
OpenGL: PBO supported
OpenGL: FBO supported
OpenGL: using vid filter: 0
GL texture: copy 1, shader 0, dynamic 1, 256x224 256x224 [PALETTE16, Equal: 0, Palette: 1,
            scale 1x1, border 0, pitch 384,256/4096], colors: 256, bytes/pix 4
GL texture: copy 1, shader 0, dynamic 1, 256x224 256x224 [PALETTE16, Equal: 0, Palette: 1,
            scale 1x1, border 0, pitch 384,256/4096], colors: 256, bytes/pix 4
Average speed: 443.58% (247 seconds)
sdl_kill: closing audio
Sound buffer: overflows=9575 underflows=0
Joystick: Start deinitialization
Joystick: End deinitialization
Enter sdlwindow_exit
Leave sdlwindow_exit
SwitchRes: Xrandr REMOVE VGA-0: ModeLine     256x224x59.19
SwitchRes: Running 'xrandr  --delmode VGA-0 "256x224x59.19"'
SwitchRes: Running 'xrandr  --rmmode "256x224x59.19"'
Note that now there are a lot of "device ':' adding ..." strings.
This is strange and could be related to mame upgrade 7 (?), or is it only a trip?
Earth could be the hell of another world

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #25 on: February 06, 2012, 10:26:22 am »
Some news: I compiled kernel 3.2.4 and upgraded xf86-video-ati to 6.14.2 (from 6.14.1).
Now a lot of games (BubbleBoble, MetalSlug 1/2/3/X, and others) run at about 300% speed, so they are unplayable.
As I wrote before, now "mslug" works (3 times faster than original speed).

This happens when vsync hardware functionality fails or is not available. GroovyMAME relies on vsync enterely in order to keep the game throttle. Does this happen just to some games or is a general issue??
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

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #26 on: February 06, 2012, 10:38:44 am »
Galaga seems ok, so I think this happen only with some roms.
Earth could be the hell of another world

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #27 on: February 06, 2012, 10:45:15 am »
Galaga seems ok, so I think this happen only with some roms.

When GroovyMAME is able to create the game's native refresh (mslug, etc.) you get this kind of log:

Code: [Select]
SwitchRes: Setting Option -nothrottle
SwitchRes: Setting Option -refreshspeed
SwitchRes: Setting Option -waitvsync

However, when GroovyMAME is not able to generate the right refresh, which is the case of many vertical games rotated (galaga, etc.), then vsync is disable and -throttle is used instead. So these games cannot be considered.

A buggy v-sync only affects the first group of games (most).

Probably the combination of the new ATI driver, SDL, etc. is not working fine.
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

ves

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 210
Re: Games with ISSUES: report here!
« Reply #28 on: February 06, 2012, 11:02:56 am »
Some news: I compiled kernel 3.2.4 and upgraded xf86-video-ati to 6.14.2 (from 6.14.1).
Now a lot of games (BubbleBoble, MetalSlug 1/2/3/X, and others) run at about 300% speed, so they are unplayable.
As I wrote before, now "mslug" works (3 times faster than original speed).
Log from "mslug":
Code: [Select]
Parsing mame.ini
Parsing mame.ini
SwitchRes: Found output connector 'VGA-0'
SwitchRes: Monitor: pal Orientation: horizontal Aspect 4:3
SwitchRes: MonitorLimits 15625.00-15800.00,49.50-61.00,2.000,4.700,8.000,0.064,0.160,1.056,0,0,288.0,448
SwitchRes: Raw limits (59.1856Hz)-> YresMin= 243p, YresMax= 246p(492i)
SwitchRes: Logical limit YresMin (448/2) = 224p
SwitchRes: Setup monitor limits min=184x224 max=0x492
SwitchRes: Starting with Horizontal freq of 14.344 and Vertical refresh of 59.19
SwitchRes: Increased horizontal frequency from 14.344 to 15.625
SwitchRes: Using 20 lines padding
SwitchRes: # 15.625Khz -> 15.800Khz: ( | Hfreq Change | Vpad +20 lines | )
SwitchRes: # mslug [4] 320x224@59.19 15.6250Khz
SwitchRes: ModeLine          "320x224x59.19" 6.625000 320 336 368 424 224 235 238 264 -HSync -VSync

SwitchRes v0.013: [mslug] (1) horizontal (320x224@59.19)->(320x224@59.19)->(320x224@59.19)
SwitchRes: # mslug 320x224@59.19 15.6250Khz
SwitchRes: ModeLine          "320x224x59.19" 6.625000 320 336 368 424 224 235 238 264 -HSync -VSync
SwitchRes: Setting Option -redraw 0
SwitchRes: Setting Option -rotate
SwitchRes: Setting Option -nothrottle
SwitchRes: Setting Option -refreshspeed
SwitchRes: Setting Option -waitvsync
SwitchRes: Xrandr ADD VGA-0: ModeLine          "320x224x59.19" 6.625000 320 336 368 424 224 235 238 264 -HSync -VSync
SwitchRes: Running 'xrandr  --newmode      "320x224x59.19" 6.625000 320 336 368 424 224 235 238 264 -HSync -VSync'
SwitchRes: Running 'xrandr  --addmode VGA-0 320x224x59.19'
SwitchRes: Setting Option -resolution 320x224x32@59.185606
Setting SDL audiodriver 'dsp' ...
Build version:      0.144u7 (Feb  6 2012)
Build architecure:  SDLMAME_ARCH=
Build defines 1:    SDLMAME_UNIX=1 SDLMAME_X11=1 SDLMAME_LINUX=1
Build defines 1:    LSB_FIRST=1 PTR64=1 DISTRO=generic SYNC_IMPLEMENTATION=tc
SDL/OpenGL defines: SDL_COMPILEDVERSION=1214 USE_OPENGL=1 USE_DISPATCH_GL=1
Compiler defines A: __GNUC__=4 __GNUC_MINOR__=5 __GNUC_PATCHLEVEL__=2 __VERSION__="4.5.2"
Compiler defines B: __amd64__=1 __x86_64__=1 __unix__=1
Compiler defines C: __USE_FORTIFY_LEVEL=0
SDL Device Driver     : x11
SDL Monitor Dimensions: 768 x 576
Enter sdlwindow_init
Using SDL single-window OpenGL driver (SDL 1.2)
Leave sdlwindow_init
 768x 576 -> 0.001248
 320x 224 -> 2.000000
Loaded opengl shared library: <default>
OpenGL: Advanced Micro Devices, Inc.
OpenGL: Mesa DRI R600 (CEDAR 68F9) 20090101  TCL DRI2
OpenGL: 2.1 Mesa 7.9.2
OpenGL: texture rectangle supported
OpenGL: non-power-of-2 textures supported (new method)
OpenGL: vertex buffer supported
OpenGL: pixel buffers supported
OpenGL: framebuffer object supported
OpenGL: GLSL supported, but disabled
OpenGL: max texture size 4096 x 4096
Keyboard: Start initialization
Input: Adding Kbd #0: System keyboard
Keyboard: Registered System keyboard
Keyboard: End initialization
Mouse: Start initialization
Input: Adding Mouse #0: System mouse
Mouse: Registered System mouse
Mouse: End initialization
Joystick: Start initialization
Joystick: End initialization
Audio: Start initialization
Audio: Driver is dsp
Audio: frequency: 48000, channels: 2, samples: 512
sdl_create_buffers: creating stream buffer of 114688 bytes
Audio: End initialization
ouput: unable to open output notifier file /tmp/sdlmame_out
ioport ':IN0' created
ioport ':IN1' created
ioport ':IN2' created
ioport ':IN3' created
ioport ':IN4' created
device ':' adding mapping for ':' => ':'
device ':' adding mapping for ':maincpu' => ':maincpu'
Region ':maincpu' created
Region ':fixed' created
Region ':fixedbios' created
Region ':zoomy' created
Region ':mainbios' created
Region ':audiobios' created
device ':' adding mapping for ':audiocpu' => ':audiocpu'
Region ':audiocpu' created
device ':' adding mapping for ':ymsnd' => ':ymsnd'
Region ':ymsnd' created
Region ':sprites' created
Searching font Liberation Sans in -fontpath
Matching font: /usr/share/fonts/TTF/LiberationSans-Regular.ttf
Starting Driver Device ':'
  (missing dependencies; rescheduling)
Starting 68000 ':maincpu'
Starting Z80 ':audiocpu'
Starting NVRAM ':saveram'
Starting Video Screen ':screen'
Starting Speaker ':lspeaker'
device ':' adding mapping for ':lspeaker' => ':lspeaker'
  (missing dependencies; rescheduling)
Starting Speaker ':rspeaker'
device ':' adding mapping for ':rspeaker' => ':rspeaker'
  (missing dependencies; rescheduling)
Starting YM2610 ':ymsnd'
Starting NEC uPD4990A ':upd4990a'
Starting Driver Device ':'
  (missing dependencies; rescheduling)
Starting Speaker ':lspeaker'
Starting Speaker ':rspeaker'
Starting Driver Device ':'
device ':' adding mapping for 'saveram' => ':saveram'
device ':' adding mapping for 'maincpu' => ':maincpu'
device ':' adding mapping for 'audiocpu' => ':audiocpu'
device ':' adding mapping for 'upd4990a' => ':upd4990a'
Loading cheats file from /home/roms/cheat/mslug.xml
Ignoring MAME exception: mslug.xml(5): error parsing cheat expression "maincpu.pb@106E93=3C" (invalid memory name)

mslug.xml(5): error parsing cheat expression "maincpu.pb@106E93=3C" (invalid memory name)

OpenGL: VBO supported
OpenGL: PBO supported
OpenGL: FBO supported
OpenGL: using vid filter: 0
GL texture: copy 0, shader 0, dynamic 0, 320x224 320x224 [RGB32, Equal: 1, Palette: 0,
            scale 1x1, border 0, pitch 384,320/4096], colors: 0, bytes/pix 4
GL texture: copy 0, shader 0, dynamic 0, 320x224 320x224 [RGB32, Equal: 1, Palette: 0,
            scale 1x1, border 0, pitch 384,320/4096], colors: 0, bytes/pix 4
Average speed: 365.30% (164 seconds)
sdl_kill: closing audio
Sound buffer: overflows=5973 underflows=0
Joystick: Start deinitialization
Joystick: End deinitialization
Enter sdlwindow_exit
Leave sdlwindow_exit
SwitchRes: Xrandr REMOVE VGA-0: ModeLine     320x224x59.19
SwitchRes: Running 'xrandr  --delmode VGA-0 "320x224x59.19"'
SwitchRes: Running 'xrandr  --rmmode "320x224x59.19"'
Log from "bublbobl":
Code: [Select]
Parsing mame.ini
Parsing mame.ini
SwitchRes: Found output connector 'VGA-0'
SwitchRes: Monitor: pal Orientation: horizontal Aspect 4:3
SwitchRes: MonitorLimits 15625.00-15800.00,49.50-61.00,2.000,4.700,8.000,0.064,0.160,1.056,0,0,288.0,448
SwitchRes: Raw limits (59.1856Hz)-> YresMin= 243p, YresMax= 246p(492i)
SwitchRes: Logical limit YresMin (448/2) = 224p
SwitchRes: Setup monitor limits min=184x224 max=0x492
SwitchRes: Starting with Horizontal freq of 14.344 and Vertical refresh of 59.19
SwitchRes: Increased horizontal frequency from 14.344 to 15.625
SwitchRes: Using 20 lines padding
SwitchRes: # 15.625Khz -> 15.800Khz: ( | Hfreq Change | Vpad +20 lines | )
SwitchRes: # bublbobl [4] 256x224@59.19 15.6250Khz
SwitchRes: ModeLine          "256x224x59.19" 5.500000 256 272 304 352 224 235 238 264 -HSync -VSync

SwitchRes v0.013: [bublbobl] (1) horizontal (256x224@59.19)->(256x224@59.19)->(256x224@59.19)
SwitchRes: # bublbobl 256x224@59.19 15.6250Khz
SwitchRes: ModeLine          "256x224x59.19" 5.500000 256 272 304 352 224 235 238 264 -HSync -VSync
SwitchRes: Setting Option -redraw 0
SwitchRes: Setting Option -rotate
SwitchRes: Setting Option -nothrottle
SwitchRes: Setting Option -refreshspeed
SwitchRes: Setting Option -waitvsync
SwitchRes: Xrandr ADD VGA-0: ModeLine          "256x224x59.19" 5.500000 256 272 304 352 224 235 238 264 -HSync -VSync
SwitchRes: Running 'xrandr  --newmode      "256x224x59.19" 5.500000 256 272 304 352 224 235 238 264 -HSync -VSync'
SwitchRes: Running 'xrandr  --addmode VGA-0 256x224x59.19'
SwitchRes: Setting Option -resolution 256x224x32@59.185606
Setting SDL audiodriver 'dsp' ...
Build version:      0.144u7 (Feb  6 2012)
Build architecure:  SDLMAME_ARCH=
Build defines 1:    SDLMAME_UNIX=1 SDLMAME_X11=1 SDLMAME_LINUX=1
Build defines 1:    LSB_FIRST=1 PTR64=1 DISTRO=generic SYNC_IMPLEMENTATION=tc
SDL/OpenGL defines: SDL_COMPILEDVERSION=1214 USE_OPENGL=1 USE_DISPATCH_GL=1
Compiler defines A: __GNUC__=4 __GNUC_MINOR__=5 __GNUC_PATCHLEVEL__=2 __VERSION__="4.5.2"
Compiler defines B: __amd64__=1 __x86_64__=1 __unix__=1
Compiler defines C: __USE_FORTIFY_LEVEL=0
SDL Device Driver     : x11
SDL Monitor Dimensions: 768 x 576
Enter sdlwindow_init
Using SDL single-window OpenGL driver (SDL 1.2)
Leave sdlwindow_init
 768x 576 -> 0.001156
 256x 224 -> 2.000000
Loaded opengl shared library: <default>
OpenGL: Advanced Micro Devices, Inc.
OpenGL: Mesa DRI R600 (CEDAR 68F9) 20090101  TCL DRI2
OpenGL: 2.1 Mesa 7.9.2
OpenGL: texture rectangle supported
OpenGL: non-power-of-2 textures supported (new method)
OpenGL: vertex buffer supported
OpenGL: pixel buffers supported
OpenGL: framebuffer object supported
OpenGL: GLSL supported, but disabled
OpenGL: max texture size 4096 x 4096
Keyboard: Start initialization
Input: Adding Kbd #0: System keyboard
Keyboard: Registered System keyboard
Keyboard: End initialization
Mouse: Start initialization
Input: Adding Mouse #0: System mouse
Mouse: Registered System mouse
Mouse: End initialization
Joystick: Start initialization
Joystick: End initialization
Audio: Start initialization
Audio: Driver is dsp
Audio: frequency: 48000, channels: 2, samples: 512
sdl_create_buffers: creating stream buffer of 114688 bytes
Audio: End initialization
ouput: unable to open output notifier file /tmp/sdlmame_out
ioport ':IN0' created
ioport ':DSW0' created
ioport ':DSW1' created
ioport ':IN1' created
ioport ':IN2' created
device ':' adding mapping for ':maincpu' => ':maincpu'
Region ':maincpu' created
device ':' adding mapping for ':slave' => ':slave'
Region ':slave' created
device ':' adding mapping for ':audiocpu' => ':audiocpu'
Region ':audiocpu' created
device ':' adding mapping for ':mcu' => ':mcu'
Region ':mcu' created
Region ':gfx1' created
Region ':proms' created
Region ':plds' created
pal16l8.bin NOT FOUND (NO GOOD DUMP KNOWN)
pal16l8.bin NOT FOUND (NO GOOD DUMP KNOWN)
pal16r4.bin NOT FOUND (NO GOOD DUMP KNOWN)
WARNING: the game might not run correctly.
device ':' adding mapping for ':ym2' => ':ym2'
device ':' adding mapping for ':ym1' => ':ym1'
Searching font Liberation Sans in -fontpath
Matching font: /usr/share/fonts/TTF/LiberationSans-Regular.ttf
Starting Driver Device ':'
  (missing dependencies; rescheduling)
Starting Z80 ':maincpu'
Starting Z80 ':slave'
Starting Z80 ':audiocpu'
Starting M6801 ':mcu'
Starting Video Screen ':screen'
Starting Speaker ':mono'
device ':' adding mapping for ':mono' => ':mono'
  (missing dependencies; rescheduling)
Starting YM2203 ':ym1'
Starting YM3526 ':ym2'
Starting Driver Device ':'
  (missing dependencies; rescheduling)
Starting Speaker ':mono'
Starting Driver Device ':'
device ':' adding mapping for 'maincpu' => ':maincpu'
device ':' adding mapping for 'mcu' => ':mcu'
device ':' adding mapping for 'audiocpu' => ':audiocpu'
device ':' adding mapping for 'slave' => ':slave'
Loading cheats file from /home/roms/cheat/bublbobl.xml
Ignoring MAME exception: bublbobl.xml(10): error parsing cheat expression "maincpu.pb@E366=63" (invalid memory name)

bublbobl.xml(10): error parsing cheat expression "maincpu.pb@E366=63" (invalid memory name)

device ':' adding mapping for 'screen' => ':screen'
OpenGL: VBO supported
OpenGL: PBO supported
OpenGL: FBO supported
OpenGL: using vid filter: 0
GL texture: copy 1, shader 0, dynamic 1, 256x224 256x224 [PALETTE16, Equal: 0, Palette: 1,
            scale 1x1, border 0, pitch 384,256/4096], colors: 256, bytes/pix 4
GL texture: copy 1, shader 0, dynamic 1, 256x224 256x224 [PALETTE16, Equal: 0, Palette: 1,
            scale 1x1, border 0, pitch 384,256/4096], colors: 256, bytes/pix 4
Average speed: 443.58% (247 seconds)
sdl_kill: closing audio
Sound buffer: overflows=9575 underflows=0
Joystick: Start deinitialization
Joystick: End deinitialization
Enter sdlwindow_exit
Leave sdlwindow_exit
SwitchRes: Xrandr REMOVE VGA-0: ModeLine     256x224x59.19
SwitchRes: Running 'xrandr  --delmode VGA-0 "256x224x59.19"'
SwitchRes: Running 'xrandr  --rmmode "256x224x59.19"'
Note that now there are a lot of "device ':' adding ..." strings.
This is strange and could be related to mame upgrade 7 (?), or is it only a trip?

Hello I am doing a new live it bases in archlinux, and the problem on that you comment of the speed I pass, if you touch f10 the game it works to his correct, but this speed is not the solution, in archlinux had to install the package ati-dri, with this package already all the games returned to work correctly.
Verify that version of mesa/dri has in his system and updates, since the problem is not groovymame, it is the new driver.

 Regards.


« Last Edit: February 06, 2012, 11:05:44 am by ves »

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #29 on: February 06, 2012, 11:06:46 am »
I think we can exclude SDL.
IMHO the problematic software could be (one or more of):
- X server
- xf86-video-ati
- mesa
- linux kernel

I will downgrade xf86-video-ati to 6.14.1 and come back to old problems.
Earth could be the hell of another world

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #30 on: February 06, 2012, 11:23:01 am »
Hello I am doing a new live it bases in archlinux, and the problem on that you comment of the speed I pass, if you touch f10 the game it works to his correct, but this speed is not the solution, in archlinux had to install the package ati-dri, with this package already all the games returned to work correctly.
Verify that version of mesa/dri has in his system and updates, since the problem is not groovymame, it is the new driver.

Hi VeS, glad to see you back, please keep us informed of your archlinux live-CD progress.
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

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #31 on: February 06, 2012, 11:29:24 am »
Hello I am doing a new live it bases in archlinux, and the problem on that you comment of the speed I pass, if you touch f10 the game it works to his correct, but this speed is not the solution, in archlinux had to install the package ati-dri, with this package already all the games returned to work correctly.
Verify that version of mesa/dri has in his system and updates, since the problem is not groovymame, it is the new driver.

 Regards.
Mesa is at version 7.9.2.
Slackware hasn't any "ati-dri" package.
Earth could be the hell of another world

ves

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 210
Re: Games with ISSUES: report here!
« Reply #32 on: February 06, 2012, 11:54:41 am »
Packages and files in Archlinux

xf86-video-ati 6.14.3-1 (files theatre200_drv.so theatre_detect_drv.so theatre_drv.so radeon_drv.so ati_drv.so)
ati-dri 7.11.2-1 (files radeon_dri.so r600_dri.so r200_dri.so r300_dri.so)
mesa 7.11.2-1


Calamity looks at your mail.







Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #33 on: February 06, 2012, 12:14:09 pm »
In slackware there is only one (big) package called "mesa", so I need to update that.

[OT]
@ves: recently I've made some changes in openppjoy. If you are interested, I can send you the new tarball.
[/OT]
« Last Edit: February 06, 2012, 12:22:03 pm by Ansa89 »
Earth could be the hell of another world

ves

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 210
Re: Games with ISSUES: report here!
« Reply #34 on: February 06, 2012, 12:18:14 pm »
Does That you have donate changes in openppjoy? Send it please.

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #35 on: February 06, 2012, 12:54:01 pm »
Same version of xf86-video-ati and mesa, but still no luck.
Have you patched xf86-video-ati with the "low resolution" patch (from AGES)? (But this shouldn't be relevant).
Which version of Xorg are you using?

[OT]
@ves: you have mail.
[/OT]
Earth could be the hell of another world

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #36 on: February 06, 2012, 01:00:36 pm »
Same version of xf86-video-ati and mesa, but still no luck.
Have you patched xf86-video-ati with the "low resolution" patch (from AGES)? (But this shouldn't be relevant).
Which version of Xorg and libdrm are you using?

[OT]
@ves: you have mail.
[/OT]
Earth could be the hell of another world

ves

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 210
Re: Games with ISSUES: report here!
« Reply #37 on: February 06, 2012, 01:03:36 pm »
Thank you for the mail Ansa89, It will look at it afterwards coolly, but I have liked the renaming since this way it is very much an explicit

Xorg 1.11.4-1.

Your problem surely is for the driver radeon_dri, update it.


 I have the new live updated from yesterday, here you can see all the versions of the packages Xorg radeon etc..

http://www.archlinux.org/packages/


Regards.

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #38 on: February 06, 2012, 01:57:19 pm »
My Xorg is 1.9.5.
If I downgrade the xf86-video-ati all works well, so there should be something else involved (like libdrm or something close to it).

For now I will keep things as they are (because it seems all is working more or less).
Earth could be the hell of another world

mazinger-z

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 47
Mortal Kombat is perfect, Mortal Kombat 2 is unplayable
« Reply #39 on: February 08, 2012, 06:37:59 pm »
Dear Calamity, I've been a plague for you lately, I hope you will forgive me somehow.  :angel:

As the subject states, I'm having a problem with Mortal Kombat 2 (mk2): it stutters and runs slower and slower, whereas Mortal Kombat 1 (mk) runs perfectly smooth. NBA Hangtime (nbahangt) does a similar thing, too. With the official MAME build, the problem doesn't occur, but the final speed measurement says 100% for mk and 97% (or less) for mk2. Maybe the CPU isn't powerful enough?  :-[

My specs:

- Athlon XP 2400+ with 1.5 Gb RAM
- Windows XP 32 bit with CRT Emudriver 6.5
- Selti 25" arcade monitor
- ATi Radeon 9250 128Mb PCI

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #40 on: February 08, 2012, 06:50:33 pm »
Hi mazinger, try running it with -triplebuffer (to discard CPU power).
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

mazinger-z

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 47
Re: Games with ISSUES: report here!
« Reply #41 on: February 09, 2012, 07:27:59 am »
With triplebuffer enabled, the game stutters much less (once in a while) and is playable. Speed is 97.20%.
With triplebuffer enabled and sound disabled, it works more or less the same (maybe a tad better). Speed: 99.10%.
With triplebuffer disabled and sound disabled, it stutters and slows down like before. Speed: 84.00%.

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #42 on: February 09, 2012, 07:59:13 am »
The results with triplebuffer match the ones you're getting with official MAME, which means the issue is CPU related, I'm afraid. As a general rule, you shouldn't use syncrefresh for a game that can't reach a 100% speed when run without it (triplebuffer).

The fact that you're not getting a 100% speed with official MAME means that your CPU needs more than 1000/Vfreq ms (1000/54.81570 = 18.24 ms for mk2) in order to render some of the game's frames. In these circumstances, enabling syncrefresh will reduce performance dramatically, as much as 50% in some cases, because many of the vertical retraces will be missed and the CPU will need to wait for the next one.
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

JoeB

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 617
  • NES Fanatic
Re: Games with ISSUES: report here!
« Reply #43 on: February 12, 2012, 12:56:08 am »
Anyone noticed how many times switchres is called in "diehard" ?  For the start it gets called >10 times!!  It makes my arcade monitor go nuts with flickers.

And in all cases, it switches to same resolution!  Is this a bug in Diehard?  Tried in 0.145 ..

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #44 on: February 12, 2012, 01:43:11 pm »
Anyone noticed how many times switchres is called in "diehard" ?  For the start it gets called >10 times!!  It makes my arcade monitor go nuts with flickers.

And in all cases, it switches to same resolution!  Is this a bug in Diehard?  Tried in 0.145 ..

I've tried diehard and it switches resolutions a lot indeed, I'm not sure if the original game behaved like that or it's some kind of error in the routine which detects resolution switching. Actually the change is nearly not perceptible in my monitor but some other monitors shake a lot for mode switching so it can be nice to disable the -changeres option for that game.
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

jimmy2x2x

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1220
Re: Games with ISSUES: report here!
« Reply #45 on: February 19, 2012, 03:26:23 pm »
gm .145 (on 31khz monitor)

Green Beret is picking a strange resolution for me:

960x448

screengrab from VNC, imagine this compressed to a 4:3 screen - It looks like a vertical game



I work around this by picking a more appropriate res in gberet.ini

Is GM picking a wrong resolution or is GM not scaling the image correctly?

Thanks

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #46 on: February 19, 2012, 03:43:33 pm »
Is GM picking a wrong resolution or is GM not scaling the image correctly?

That's what the log will tell us :)
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

jimmy2x2x

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1220
Re: Games with ISSUES: report here!
« Reply #47 on: February 19, 2012, 03:48:39 pm »
Oops!

ROM: gberet
GM: .145 x64 build
OS: XP X64
VIDEO: PCIE 4890
DRIVERS: crt_emudriver_9.3_1.2a_x64_multisync.rar


« Last Edit: February 19, 2012, 03:52:04 pm by jimmy2x2x »

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #48 on: February 19, 2012, 04:10:30 pm »
Well, everything is right, it's MAME's fault  :D

GM is calculating the right 480x448 resolution, 240x224 scaled x 2. Unfortunately you don't have 480x448 available in your mode list, but instead you have 960x448 which happens to be an EXACT match: ( xres x 4, yres x 2 ). Most of the time MAME just does a great job autoscaling these things so the result is perfect, but in some special situations it can't resolve it for some reason and it does a partial scaling. I *think* it should be enough to enable -keepaspect for that particular game. If that doesn't help, I'd recommend you using magic resolutions, that would make sure GM always finds a perfect match (not just a perfect-after-scaling).


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

jimmy2x2x

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1220
Re: Games with ISSUES: report here!
« Reply #49 on: February 19, 2012, 04:16:07 pm »
My gberet.ini file now contains this:

keepaspect 1
##resolution 512x448

no change.

.ini is beig processed as I can comment in the res and that takes effect.


Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #50 on: February 19, 2012, 04:20:10 pm »
Try the -cleanstretch option too.
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

jimmy2x2x

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1220
Re: Games with ISSUES: report here!
« Reply #51 on: February 19, 2012, 04:22:12 pm »
its already enabled, but I have added the line and still no change.

Thanks for helping again, btw  :cheers:

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #52 on: February 19, 2012, 05:16:23 pm »
You're right, GM is enabling -cleanstretch there, I think it's a bad thing but I'm afraid we can't do anything as GM will override our option. Try -ddraw instead, though it shouldn't be different. This will 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

jimmy2x2x

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1220
Re: Games with ISSUES: report here!
« Reply #53 on: February 20, 2012, 04:19:43 am »
ddraw does not change anything either

I will just keep my forced resolution in there, not a problem

Thanks for looking into it Calamity

jimmy2x2x

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1220
Re: Games with ISSUES: report here!
« Reply #54 on: February 22, 2012, 11:18:38 pm »
Just a little more information on this scaling issue.

It is affecting a lot more games than I initially thought:

Bank Panic is another horizontal game (like green beret above)

Dodonpachi, Battle Garegga etc.. in fact most vertical games (on a horizontal monitor)



jimmy2x2x

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1220
Re: Games with ISSUES: report here!
« Reply #55 on: February 29, 2012, 10:47:02 am »
Zoo Keeper running too fast for me (about 126%)

Looks like GM is selecting 512x512 from the log?

its actually 512x480
« Last Edit: February 29, 2012, 10:48:56 am by jimmy2x2x »

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #56 on: February 29, 2012, 03:09:34 pm »
The problem with zookeeper is that it reports 256x256@76, but after that it internally switches to 256x240@60. The -changeres feature detects the resolution change but *not* the refresh change, so it still tries to refresh the game at 76 Hz, causing the wrong speed issue. This will need to be fixed, checking for refresh changes too.
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

jimmy2x2x

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1220
Re: Games with ISSUES: report here!
« Reply #57 on: February 29, 2012, 03:16:50 pm »
Thanks!

krick

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1806
  • Gotta have blue hair.
    • Tank + Paladin = Tankadin
Re: Games with ISSUES: report here!
« Reply #58 on: April 06, 2012, 04:04:34 pm »
Calamity,

I think that it might be useful if you created a companion sticky thread where the first post lists specific games in MAME that are useful for testing your setup and regression testing new GroovyMAME builds.

For example, you could list specific games that do weird stuff like resolution switches, or have odd resolutions, sizes, and/or refresh rates.  I would list games that are good for testing specific common situations like "low-res vertical game on a horizontal monitor", or "too-tall vertical game on horizontal monitor that requires an interlaced resolution".  I would also list problem games that are edge-cases that may require monitor or video mode tweaking, or special INI files.

If a game is known to work in certain GroovyMAME builds, and not others, that could be listed too, if known.

jimmy2x2x

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1220
Re: Games with ISSUES: report here!
« Reply #59 on: May 06, 2012, 06:13:36 pm »
Shienryu is solid 100% for the most part but keeps jumping to 103% now and then, this causes the sound to warp and wobble for a second or so

krick

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1806
  • Gotta have blue hair.
    • Tank + Paladin = Tankadin
Re: Games with ISSUES: report here!
« Reply #60 on: May 08, 2012, 12:50:59 am »
The problem with zookeeper is that it reports 256x256@76, but after that it internally switches to 256x240@60. The -changeres feature detects the resolution change but *not* the refresh change, so it still tries to refresh the game at 76 Hz, causing the wrong speed issue. This will need to be fixed, checking for refresh changes too.


Why in the world does the driver report the wrong resolution and refresh rate?  Is that the maximum the hardware is capable of or something?

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #61 on: May 09, 2012, 05:12:20 pm »
Why in the world does the driver report the wrong resolution and refresh rate?  Is that the maximum the hardware is capable of or something?

Well I wouldn't go as far as to say it's a wrong refresh rate, MAME reports it probably because the real hardware actually uses that mode "on boot". At some point the hardware will switch to the normal working mode, and MAME internally reflects this too. The problem is that MAME XML only reports the first video mode used by a game, this is a limitation indeed. On the other hand, the -changeres patch captures resolution switching by filtering changes in the frame buffer size, but refresh changes are not reflected here :(
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

krick

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1806
  • Gotta have blue hair.
    • Tank + Paladin = Tankadin
Re: Games with ISSUES: report here!
« Reply #62 on: May 09, 2012, 11:39:05 pm »
So for problem games like this, is the best option to force it to the final resolution and refresh rate using a game-specific ini file?

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #63 on: May 10, 2012, 12:53:13 pm »
So for problem games like this, is the best option to force it to the final resolution and refresh rate using a game-specific ini file?

Yes, I'm afraid. Games that change their refresh rate are very rare fortunately. Resolution changes are properly detected so they're not a problem.
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

jvlk

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 29
Re: Games with ISSUES: report here!
« Reply #64 on: July 06, 2012, 08:38:44 am »
Anyone noticed how many times switchres is called in "diehard" ?  For the start it gets called >10 times!!  It makes my arcade monitor go nuts with flickers.

And in all cases, it switches to same resolution!  Is this a bug in Diehard?  Tried in 0.145 ..

I've tried diehard and it switches resolutions a lot indeed, I'm not sure if the original game behaved like that or it's some kind of error in the routine which detects resolution switching. Actually the change is nearly not perceptible in my monitor but some other monitors shake a lot for mode switching so it can be nice to disable the -changeres option for that game.


Strider 2 also has this problem

krick

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1806
  • Gotta have blue hair.
    • Tank + Paladin = Tankadin
Re: Games with ISSUES: report here!
« Reply #65 on: July 09, 2012, 12:13:44 am »
I've been playing with GroovyMAME 146u2 and I've found a few things...

1) I'm don't think Zoo Keeper (zookeep) is running too fast.  After exiting the game, it says...
Average speed: 100.54% (173 seconds)

2) Space Fury (spacfury) is VERY difficult to get stable on my monitor.  I have to adjust one of the controls, I think it was vertical amplitude all the way as far as it will go to one end to get a good picture.  It's not rolling either, it's just... shaking.  If I adjust the control the other way, the image eventually turns into a double vision type thing where the text is repeated twice.  Additionally, it appears to be playing way fast...   Average speed: 123.90% (58 seconds)

3) Tempest (tempest) is cut off at the bottom of the screen.  I know this one's been mentioned before.  SwitchRes seems to think it's 640x480 horizontal for some reason instead of vertical.  Is this something that is goofy in MAME or is a SwitchRes bug?

Log files for all three games are attached.

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #66 on: July 25, 2012, 10:46:12 am »
Some issue with groovymame 0.146u3 and metal slug (mslug).
I repost my specs:
- slackware linux 64bit
- groovymame 0.146u3
- ATI hd5450 videocard
- pal tv as monitor (576x768)

In attach there is the log.
Earth could be the hell of another world

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #67 on: July 25, 2012, 01:33:23 pm »
Some issue with groovymame 0.146u3 and metal slug (mslug).

So what happens exactly with mslug? Bad video?
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

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #68 on: July 25, 2012, 02:24:21 pm »
Black screen (for few seconds), then groovymame exit.
Earth could be the hell of another world

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #69 on: July 25, 2012, 03:53:04 pm »
It seems to crash right after loading the cheats, have you tried disabling them? Also try disabling -multisync a compare the logs.
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

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #70 on: July 31, 2012, 02:19:45 am »
Disabling the cheat system fixed it.
Earth could be the hell of another world

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #71 on: October 22, 2012, 03:27:54 am »
A user of another forum can't get the "automatic resolution change" (the monitor stuck at 768x576 interlaced).
Technical info:
- romset: ssridersabd
- monitor: pal tv
- OS: windows xp sp3
- graphic card: ati radeon 9600
- crt-emudriver
- vga->scart cable
- groovymame-0.146u4 (32 bit)


The second log is what he get by adding "monitor_spec0 15625-15800,49.50-60.50,2.000,4.700,8.000,0.064,0.160,1.056,0,0,288,448" into "mame.ini".
Earth could be the hell of another world

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #72 on: October 22, 2012, 04:04:53 am »
Look at this:

Code: [Select]
DirectDraw: Warning - Device does not support hardware stretching
DirectDraw: Warning - Device may not perform well for DirectDraw rendering

He's got the ddraw's hardware acceleration disabled. If it can't get enabled from the dxdiag control panel then it's almost sure the drivers are not properly installed.
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

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #73 on: October 22, 2012, 04:09:19 am »
Ok, I will point this to him.
Earth could be the hell of another world

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #74 on: October 22, 2012, 06:04:18 am »
He said that he can't enable the hardware acceleration from dxdiag.
Which is the correct way to install the video driver, in order to enable the hardware acceleration?

EDIT: he said the problem was realvnc, which creates a "virtual graphic card" that screw up everything. After removing realvnc and reinstalling the driver, all works as expected.
« Last Edit: October 23, 2012, 12:44:04 pm by Ansa89 »
Earth could be the hell of another world

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #75 on: October 23, 2012, 12:40:13 pm »
EDIT: he said the problem was realvnc, which creates a "virtual graphic card" that screw up everything. After removing realvnc and reinstalling the driver, all work as expected.

Thank you very much for reporting this Ansa89, really good information.
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

krick

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1806
  • Gotta have blue hair.
    • Tank + Paladin = Tankadin
Re: Games with ISSUES: report here!
« Reply #76 on: October 23, 2012, 01:07:05 pm »
I had similar issues with my primary (not MAME) PC with a remote access product called LogMeIn that also installs a "mirror driver".

I ended up having to uninstall the mirror driver using some command-line mojo I found posted in the LogMeIn forums.

maxpontello

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 8
  • I want to build my own arcade controls!
Re: Games with ISSUES: report here!
« Reply #77 on: October 26, 2012, 08:14:39 am »
I've some problem with Pang. In the details the game starts with 640x480@60 instead of 384x240@57. It seems to me that the pang ini file is correct and that the modeline is present, but for some reason it uses a wrong resolution. I attach pang.txt log because is far too long.


Rom Name: Pang
Video Card: Ati Radeon 9250 Agp 128 Mb
Driver: Calamity Emu CRT 1.2
Monitor: Intervideo Dual Frequency
Os: Win Xp 32bit

Thanks for help :)


Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #78 on: October 31, 2012, 04:49:32 am »
I've some problem with Pang. In the details the game starts with 640x480@60 instead of 384x240@57. It seems to me that the pang ini file is correct and that the modeline is present, but for some reason it uses a wrong resolution. I attach pang.txt log because is far too long.

Hi maxpontello,

There's something odd going on there, probably the driver is not properly installed. If you look at your log, most fo the custom resolutions are not actually available in the mode list (the second one), just 41 custom modes are found. If can't fix this by running vmmaker again, this probably means that the wrong version of ati2mtag.sys file is in use.
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

maxpontello

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 8
  • I want to build my own arcade controls!
Re: Games with ISSUES: report here!
« Reply #79 on: October 31, 2012, 05:44:35 am »
Hi maxpontello,

There's something odd going on there, probably the driver is not properly installed. If you look at your log, most fo the custom resolutions are not actually available in the mode list (the second one), just 41 custom modes are found. If can't fix this by running vmmaker again, this probably means that the wrong version of ati2mtag.sys file is in use.

Hi Calamity, and thanks for your answer. You are right. In the meantime i've reinstalled crt drivers and realized that i was not using the most updated Vmmaker release. I've updated all and now things seem to wirk well. I've only one other concern. I've used the option 2 in modeline generation (automatic when the game start). When Pang (or other games) starts it seems that it uses the correct resolution but refresh is slightly different from original 384x240@57.42. Still i can't notice problems during the game, like stutters or audio problems (perhaps the pitch is different)? I've not seen great differences using mame.ini different options (vsync, syncrefresh, triplebuffer, etc) only i have to set throttle to 1 to avoid to execute the game at tremendous speed. Any suggestion for best results in emulation fidelity?

Thanks, Max

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #80 on: October 31, 2012, 05:48:26 am »
Hi maxpontello,

You can expect a slight difference in the actual refresh rate obtained, due to hardware limitations (pixel clock granularity), but that shouldn't be more than 0.1 Hz or so. Is that the case?
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

Beaps

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 98
Re: Games with ISSUES: report here!
« Reply #81 on: October 31, 2012, 06:39:29 am »
Hi guys

I made the leap over to Groovymame the other day and I have to say I am very impressed.

There are a few issues I have tho.

1. On Rolling Thunder when the screen is scrolling I get like a tear line ever few seconds

2. When I play a vertical game the screen is in the middle as you would expect. When I go in the option and change to rotate, the game is still in the middle of the screen as above but its the game rotates in the image? (hope that makes sense) games like bomb jack, donkey kong etc

3. In the Mame.ini I have bezels etc turned off, when I go into Groovymame they are always turn on so I have to go into each game and turn them off & exit, then they stay off

I am using a ms9 monitor, ati 4*** card, winxp 64

Thanks
« Last Edit: October 31, 2012, 06:45:11 am by Beaps »

maxpontello

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 8
  • I want to build my own arcade controls!
Re: Games with ISSUES: report here!
« Reply #82 on: October 31, 2012, 06:42:11 am »
Hi maxpontello,

You can expect a slight difference in the actual refresh rate obtained, due to hardware limitations (pixel clock granularity), but that shouldn't be more than 0.1 Hz or so. Is that the case?

I should control the log file generated from Pang. I'll tell you later. About mame.ini options, which are the best compromise for arcade fidelity? Is it normal that i have to set throttle to 1 when refreshsync is activated otherwise emulation is far too speedy? Thanks dude for your work ;)

Max

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #83 on: October 31, 2012, 06:54:25 am »
I should control the log file generated from Pang. I'll tell you later. About mame.ini options, which are the best compromise for arcade fidelity? Is it normal that i have to set throttle to 1 when refreshsync is activated otherwise emulation is far too speedy? Thanks dude for your work ;)

The best options in my opinion are the default ones when you create a fresh mame.ini by running groovymame -cc
Normally you only need to change your monitor type or add some custom monitor_specs.

Recent versions of GroovyMAME for Windows need throttle 1 so that -syncrefresh is effective, this is by design.
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

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #84 on: October 31, 2012, 06:56:56 am »
1. On Rolling Thunder when the screen is scrolling I get like a tear line ever few seconds

That's odd, try creating a fresh mame.ini as explained in my post above.

Quote
2. When I play a vertical game the screen is in the middle as you would expect. When I go in the option and change to rotate, the game is still in the middle of the screen as above but its the game rotates in the image? (hope that makes sense) games like bomb jack, donkey kong etc

Yeah that's an issue, fortunately I've fixed that for the new release that I'm working on.

Quote
3. In the Mame.ini I have bezels etc turned off, when I go into Groovymame they are always turn on so I have to go into each game and turn them off & exit, then they stay off

No idea, make sure you have -artworkcrop enabled and you create a fresh mame.ini. Also, delete all files inside the cfg folder.
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

maxpontello

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 8
  • I want to build my own arcade controls!
Re: Games with ISSUES: report here!
« Reply #85 on: October 31, 2012, 07:32:16 am »

The best options in my opinion are the default ones when you create a fresh mame.ini by running groovymame -cc
Normally you only need to change your monitor type or add some custom monitor_specs.

Recent versions of GroovyMAME for Windows need throttle 1 so that -syncrefresh is effective, this is by design.

Ok, thanks for your help ^^ I'll post the log file, so you can tell if it's all right ;)

Beaps

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 98
Re: Games with ISSUES: report here!
« Reply #86 on: October 31, 2012, 11:06:52 am »
1. On Rolling Thunder when the screen is scrolling I get like a tear line ever few seconds

That's odd, try creating a fresh mame.ini as explained in my post above.

Ok I will give it a shot & report back.

Quote
2. When I play a vertical game the screen is in the middle as you would expect. When I go in the option and change to rotate, the game is still in the middle of the screen as above but its the game rotates in the image? (hope that makes sense) games like bomb jack, donkey kong etc

Yeah that's an issue, fortunately I've fixed that for the new release that I'm working on.

Glad your aware of this & I'm not going mad. Ok I'll check out the next release. Thanks

Quote
3. In the Mame.ini I have bezels etc turned off, when I go into Groovymame they are always turn on so I have to go into each game and turn them off & exit, then they stay off

No idea, make sure you have -artworkcrop enabled and you create a fresh mame.ini. Also, delete all files inside the cfg folder.

Ok I will delete the defaught.cfg & report back

Beaps

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 98
Re: Games with ISSUES: report here!
« Reply #87 on: November 19, 2012, 06:56:47 pm »
Killer Instinct now working.

Diff CHD Error - mismatch CHD & Diff

15khz Monitor
ATI Radion 4550 HD running soft 15khz
Win64bit

yakk11

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 81
Re: Games with ISSUES: report here!
« Reply #88 on: November 20, 2012, 02:29:23 pm »
Getting random crashes with Tapper and Domino man.  Heres my txt from dominoman, when i try doing it for tapper, it crashes and doesn't create said txt. 

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #89 on: November 20, 2012, 05:39:20 pm »
Killer Instinct now working.

Diff CHD Error - mismatch CHD & Diff

15khz Monitor
ATI Radion 4550 HD running soft 15khz
Win64bit

http://www.mameworld.info/ubbthreads/showflat.php?Cat=&Number=287509&page=16&view=expanded&sb=5&o=&vc=1
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

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #90 on: November 20, 2012, 05:40:32 pm »
Getting random crashes with Tapper and Domino man.  Heres my txt from dominoman, when i try doing it for tapper, it crashes and doesn't create said txt.

Use -nomt for those games.

(it's because of the -redraw patch, this should be fixed in next version).
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

yakk11

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 81
Re: Games with ISSUES: report here!
« Reply #91 on: November 20, 2012, 06:28:03 pm »
Getting random crashes with Tapper and Domino man.  Heres my txt from dominoman, when i try doing it for tapper, it crashes and doesn't create said txt.

Use -nomt for those games.

(it's because of the -redraw patch, this should be fixed in next version).

thanks!  Do you know how would i do this via hyperspin?

Beaps

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 98
Re: Games with ISSUES: report here!
« Reply #92 on: November 29, 2012, 05:06:28 pm »
Does Ibara work with groovymame, I am not having much success.

Thanks
B

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #93 on: December 15, 2012, 11:47:00 am »
The bottom half of the screen is cut on NBA Hangtime (nbahangt); it seems an "image centering" problem.
The log:
Code: [Select]
Parsing mame.ini
Parsing mame.ini
SwitchRes: Monitor range 15625.00-15625.00,50.00-50.00,1.500,4.700,5.800,0.064,0.160,1.056,0,0,192,288,448,576
SwitchRes: Monitor: pal Orientation: horizontal
SwitchRes: Found output connector 'VGA-0'

SwitchRes: Entering switchres_modeline_setup
SwitchRes: v0.014:[nbahangt] Calculating best video mode for 399x253@54.815170 orientation: normal

SwitchRes: (   1)x(   1)_(60=0.0000Hz)
   rng(0):  400 x 253_50.000p 15.600 [integ] scale(1, 1, 1) diff(0.00, 0.00, -4.8152) ratio(1.000, 1.000)

SwitchRes: [nbahangt] (1) horizontal (399x253@54.82)->(400x253@50.00)
   rng(0):  400 x 253_50.000p 15.600 [integ] scale(1, 1, 1) diff(0.00, 0.00, -4.8152) ratio(1.000, 1.000)
SwitchRes: Modeline "400x253_60 15.60KHz 50.00Hz" 7.86 400 416 456 504 253 274 276 312   -hsync -vsync
SwitchRes: Running 'xrandr  --newmode "400x253_50.00" 7.86 400 416 456 504 253 274 276 312   -hsync -vsync'
SwitchRes: Running 'xrandr  --addmode VGA-0 "400x253_50.00"'
SwitchRes: Setting option -norotate
SwitchRes: Setting option -norol
SwitchRes: Setting option -noror
SwitchRes: Setting option -nosyncrefresh
SwitchRes: Setting option -nowaitvsync
SwitchRes: Setting option -nounevenstretch
SwitchRes: Setting option -nofilter
SwitchRes: Setting option -cleanstretch
SwitchRes: Setting option -keepaspect
SwitchRes: Setting option -prescale 1
Setting SDL audiodriver 'dsp' ...
Build version:      0.147u3 (Dec 11 2012)
Build architecure:  SDLMAME_ARCH=
Build defines 1:    SDLMAME_UNIX=1 SDLMAME_X11=1 SDLMAME_LINUX=1
Build defines 1:    LSB_FIRST=1 PTR64=1 DISTRO=generic SYNC_IMPLEMENTATION=tc
SDL/OpenGL defines: SDL_COMPILEDVERSION=1214 USE_OPENGL=1 USE_DISPATCH_GL=1
Compiler defines A: __GNUC__=4 __GNUC_MINOR__=5 __GNUC_PATCHLEVEL__=2 __VERSION__="4.5.2"
Compiler defines B: __amd64__=1 __x86_64__=1 __unix__=1
Compiler defines C: __USE_FORTIFY_LEVEL=0
SDL Device Driver     : x11
SDL Monitor Dimensions: 768 x 576
Enter sdlwindow_init
Using SDL single-window OpenGL driver (SDL 1.2)
Leave sdlwindow_init
Loaded opengl shared library: <default>
OpenGL: X.Org
OpenGL: Gallium 0.4 on AMD CEDAR
OpenGL: 2.1 Mesa 7.11.2
OpenGL: texture rectangle supported
OpenGL: non-power-of-2 textures supported (new method)
OpenGL: vertex buffer supported
OpenGL: pixel buffers supported
OpenGL: framebuffer object supported
OpenGL: GLSL supported, but disabled
OpenGL: max texture size 16384 x 16384
Keyboard: Start initialization
Input: Adding Kbd #0: System keyboard
Keyboard: Registered System keyboard
Keyboard: End initialization
Mouse: Start initialization
Input: Adding Mouse #0: System mouse
Mouse: Registered System mouse
Mouse: End initialization
Joystick: Start initialization
Input: Adding Joy #0: HORI CO.,LTD. HORI PAD 3 TURBO
Joystick: HORI CO.,LTD. HORI PAD 3 TURBO
Joystick:   ...  6 axes, 13 buttons 0 hats 0 balls
Joystick:   ...  Physical id 0 mapped to logical id 0
Input: Adding Joy #1: SZMY-POWER CO.,LTD. GAMEPAD 3 TURBO
Joystick: SZMY-POWER CO.,LTD. GAMEPAD 3 TURBO
Joystick:   ...  6 axes, 13 buttons 0 hats 0 balls
Joystick:   ...  Physical id 1 mapped to logical id 1
Joystick: End initialization
Audio: Start initialization
Audio: Driver is dsp
Audio: frequency: 48000, channels: 2, samples: 512
sdl_create_buffers: creating stream buffer of 114688 bytes
Audio: End initialization
ouput: unable to open output notifier file /tmp/sdlmame_out
Region ':dcs' created
Region ':maincpu' created
Region ':gfxrom' created
Searching font Liberation Sans in -fontpath
Matching font: /usr/share/fonts/TTF/LiberationSans-Regular.ttf
Starting NBA Hangtime (rev L1.1 04/16/96) ':'
Optional device 'adpcm' not found
Optional device 'cvsd' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
  (missing dependencies; rescheduling)
Starting TMS34010 ':maincpu'
Starting NVRAM ':nvram'
Starting Video Screen ':screen'
Starting ADSP-2105 ':dcs'
Starting Timer ':dcs_reg_timer'
Starting Timer ':dcs_int_timer'
Starting Speaker ':mono'
  (missing dependencies; rescheduling)
Starting DMA-driven DAC ':dac'
Starting NBA Hangtime (rev L1.1 04/16/96) ':'
Optional device 'adpcm' not found
Optional device 'cvsd' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
  (missing dependencies; rescheduling)
Starting Speaker ':mono'
Starting NBA Hangtime (rev L1.1 04/16/96) ':'
Optional device 'adpcm' not found
Optional device 'cvsd' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
OpenGL: VBO supported
OpenGL: PBO supported
OpenGL: FBO supported
OpenGL: using vid filter: 0
GL texture: copy 1, shader 0, dynamic 1, 399x253 399x253 [PALETTE16, Equal: 0, Palette: 1,
            scale 1x1, border 0, pitch 512,399/16384], colors: 32768, bytes/pix 4
SwitchRes: Resolution change from 399x253@54.815170 to 400x254@54.706841
GL texture: copy 1, shader 0, dynamic 1, 400x254 400x254 [PALETTE16, Equal: 0, Palette: 1,
            scale 1x1, border 0, pitch 512,400/16384], colors: 32768, bytes/pix 4
SwitchRes: Resolution change to 400x254@54.706841

SwitchRes: Entering switchres_modeline_setup
SwitchRes: v0.014:[nbahangt] Calculating best video mode for 400x254@54.706841 orientation: normal

SwitchRes: (   1)x(   1)_(60=0.0000Hz)
   rng(0):  400 x 254_50.000p 15.600 [integ] scale(1, 1, 1) diff(0.00, 0.00, -4.7068) ratio(1.000, 1.000)

SwitchRes: [nbahangt] (1) horizontal (400x254@54.71)->(400x254@50.00)
   rng(0):  400 x 254_50.000p 15.600 [integ] scale(1, 1, 1) diff(0.00, 0.00, -4.7068) ratio(1.000, 1.000)
SwitchRes: Modeline "400x254_60 15.60KHz 50.00Hz" 7.86 400 416 456 504 254 274 276 312   -hsync -vsync
SwitchRes: Running 'xrandr  --newmode "400x254_50.00" 7.86 400 416 456 504 254 274 276 312   -hsync -vsync'
SwitchRes: Running 'xrandr  --addmode VGA-0 "400x254_50.00"'
SwitchRes: Setting option -norotate
SwitchRes: Setting option -norol
SwitchRes: Setting option -noror
SwitchRes: Setting option -nosyncrefresh
SwitchRes: Setting option -nowaitvsync
SwitchRes: Setting option -nounevenstretch
SwitchRes: Setting option -nofilter
SwitchRes: Setting option -cleanstretch
SwitchRes: Setting option -keepaspect
SwitchRes: Setting option -prescale 1
GL texture: copy 1, shader 0, dynamic 1, 400x254 400x254 [PALETTE16, Equal: 0, Palette: 1,
            scale 1x1, border 0, pitch 512,400/16384], colors: 32768, bytes/pix 4
GL texture: copy 1, shader 0, dynamic 1, 400x254 400x254 [PALETTE16, Equal: 0, Palette: 1,
            scale 1x1, border 0, pitch 512,400/16384], colors: 32768, bytes/pix 4
Average speed: 100.00% (56 seconds)
sdl_kill: closing audio
Joystick: Start deinitialization
Joystick: End deinitialization
Enter sdlwindow_exit
Leave sdlwindow_exit
SwitchRes: Restoring desktop resolution: 768x576x50.00
SwitchRes: Running 'xrandr --output VGA-0 --mode 768x576x50.00'
SwitchRes: Running 'xrandr  --delmode VGA-0 "400x254_50.00"'
SwitchRes: Running 'xrandr  --rmmode "400x254_50.00"'
SwitchRes: Running 'xrandr  --delmode VGA-0 "400x253_50.00"'
SwitchRes: Running 'xrandr  --rmmode "400x253_50.00"'

I'm using groovymame 0.147u3 64 bit (compiled by myself).
Earth could be the hell of another world

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #94 on: December 15, 2012, 01:23:40 pm »
Hi Ansa89.

Your log looks ok. Are you having the same issue with mk?
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

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #95 on: December 15, 2012, 03:46:29 pm »
Yes, maybe it has something to do with midway games?
Earth could be the hell of another world

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #96 on: December 17, 2012, 10:48:36 am »
The problem persists even with groovymame 0.147u4.
Earth could be the hell of another world

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #97 on: December 17, 2012, 04:15:40 pm »
The problem persists even with groovymame 0.147u4.

Hi Ansa, just tested those games here with the new live (the unreleased beta) and they works just fine. Here I've attached a list of the component we're using, provided by VeS.
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

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #98 on: December 18, 2012, 05:19:54 am »
My software (libdrm, mesa, xf86-video-ati) is older: Slackware isn't a rolling distro; however it worked fine until groovymame 0.147u3.
I will try to upgrade to Slackware 14.0 (which has a bit newer software, but still older than the one on the live-cd).
Earth could be the hell of another world

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #99 on: December 18, 2012, 06:39:33 am »
My software (libdrm, mesa, xf86-video-ati) is older: Slackware isn't a rolling distro; however it worked fine until groovymame 0.147u3.
I will try to upgrade to Slackware 14.0 (which has a bit newer software, but still older than the one on the live-cd).

You may try disabling -changeres for Midway games, just to discard things.
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

Beaps

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 98
Re: Games with ISSUES: report here!
« Reply #100 on: December 18, 2012, 11:55:39 am »
Hummmmm I keep get this weird thing happen to me.

The default.cfg keeps resetting (which is similar in size to a new install). So I often I have to copy my saved default.cfg that I save on my desktop back over the one in the cfg folder to make the controls work again etc.

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #101 on: December 19, 2012, 05:23:28 pm »
Hummmmm I keep get this weird thing happen to me.

The default.cfg keeps resetting (which is similar in size to a new install). So I often I have to copy my saved default.cfg that I save on my desktop back over the one in the cfg folder to make the controls work again etc.

Do you mean the issue with the bezels, artwork, etc?
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

emuola

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 131
Re: Games with ISSUES: report here!
« Reply #102 on: December 21, 2012, 07:59:23 am »
I have some slight flicker with Up'n down  :dizzy: I've tested about 30 games and none other of those have this problem. The flicker is not bad, but it's there and I was wondering if there's a way to get it right (because it's just one game).

oliver

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 25
Re: Games with ISSUES: report here!
« Reply #103 on: December 22, 2012, 08:50:55 am »
Hi.

I experience sound slowdown issues on a few vertical games run on horizontal monitor.
I use the arcade_15 setting.
The system is running a E2160 cpu with 1gb and xp64.
crt_emudrivers and ati 4650 card.

extract from mame.ini (pretty standard):

Code: [Select]
syncrefresh             0
modeline                  1
#monitor                   generic_15
monitor                   arcade_15
orientation               horizontal
connector                 auto
interlace                 0
doublescan                1
cleanstretch           
changeres                 1
powerstrip                0
lock_system_modes         1
lock_unsupported_modes    1
refresh_dont_care         0
dotclock_min              0
sync_refresh_tolerance    2.0
frame_delay               0
lcd_range                 auto
crt_range0                auto
multithreading            1
video                     ddraw
numscreens                1
window                  0
maximize                1
keepaspect              0
prescale                  1
waitvsync               0
hwstretch               0
triplebuffer            0
switchres               1
audio_latency           2

extract from log file:

Code: [Select]
Parsing mame.ini
SwitchRes: Monitor range 15625.00-16200.00,49.50-65.00,2.000,4.700,8.000,0.064,0.192,1.024,0,0,192,288,448,576
SwitchRes: Monitor: arcade_15 Orientation: vertical
SwitchRes: DefaultVideo 'System\CurrentControlSet\Control\Video\{AE8AAAA8-8C03-4362-8646-700170C6597F}\0000'
Switchres: Searching for custom video modes...
...
SwitchRes: Found 108 custom of 119 active video modes

SwitchRes: Entering switchres_modeline_setup
SwitchRes: v0.014:[batsugun] Calculating best video mode for 240x320@60.000000 orientation: rotated
....
SwitchRes: [batsugun] (1) vertical (240x320@60.00)->(432x248@60.00)
   rng(0):  432 x 248_60.000p 16.140 [fract] scale(1, 1, 1) diff(0.00, 0.00, 0.0000) ratio(1.800, 0.775)
SwitchRes: Modeline "432x248_60 16.14KHz 60.00Hz" 9.17 432 456 496 568 248 250 253 269   -hsync -vsync
Switchres: saving    DALDTMCRTBCD432x248x0x60 - Modeline "432x248_60 16.15KHz 60.03Hz" 9.43 432 456 504 584 248 250 253 269   -hsync -vsync
Switchres: updating  DALDTMCRTBCD432x248x0x60 - Modeline "432x248_60 16.14KHz 60.00Hz" 9.17 432 456 496 568 248 250 253 269   -hsync -vsync
SwitchRes: Setting option -rotate
SwitchRes: Setting option -norol
SwitchRes: Setting option -noror
SwitchRes: Setting option -notriplebuffer
SwitchRes: Setting option -syncrefresh
SwitchRes: Setting option -waitvsync
SwitchRes: Setting option -hwstretch
SwitchRes: Setting option -nofilter
SwitchRes: Setting option -nocleanstretch
SwitchRes: Setting option -keepaspect
SwitchRes: Setting option -prescale 1
Video: Monitor 0000000000010001 = "\\.\DISPLAY1" (primary)
DirectDraw: Using DirectDraw 7
Blitting thread created
winwindow_video_window_create: blit_lock = TRUE
Blitting thread started
window_proc: WM_NCACTIVATE
DirectDraw: Configuring device ATI Radeon HD 4650
DirectDraw: primary surface created: 432x248x32 (R=00FF0000 G=0000FF00 B=000000FF)
DirectDraw: New blit size = 240x320
DirectDraw: blit surface created: 240x320x32 (R=00FF0000 G=0000FF00 B=000000FF)
blit_unlock = TRUE
window_proc: WM_PAINT
blit_lock = FALSE
window_proc: WM_PAINT:END
DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channels
RawInput: APIs detected
...
Starting Batsugun ':'
Optional shared pointer 'mainram16' not found
Optional shared pointer 'tx_gfxram16' not found
Optional shared pointer 'txscrollram16' not found
Optional shared pointer 'txvram_offs' not found
Optional shared pointer 'txvideoram16' not found
Optional shared pointer 'shared_ram16' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
  (missing dependencies; rescheduling)
Starting 68000 ':maincpu'
Starting V25 ':audiocpu'
Starting Video Screen ':screen'
Starting GP9001_VDP ':gp9001vdp0'
Starting GP9001_VDP ':gp9001vdp1'
Starting Speaker ':mono'
  (missing dependencies; rescheduling)
Starting YM2151 ':ymsnd'
Starting OKI6295 ':oki'
Starting Batsugun ':'
...
Average speed: 99.65% (90 seconds)
Sound: buffer overflows=9 underflows=3
window_proc: WM_NCACTIVATE
blit_lock = TRUE
window_proc: WM_DESTROY
blit_lock = TRUE
Blitting thread ended
Blitting thread destroyed
Switchres: restoring DALDTMCRTBCD432x248x0x60 - Modeline "432x248_60 16.15KHz 60.03Hz" 9.43 432 456 504 584 248 250 253 269   -hsync -vsync

Can the sound issue be fixed?
I have tried messing with the tripplebuffer / cleanstretch / hwstretch options but the screen then gets uncentered / too big / too narrow.
« Last Edit: December 23, 2012, 10:37:26 am by Calamity »

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #104 on: December 23, 2012, 11:04:57 am »
Quote
I experience sound slowdown issues on a few vertical games run on horizontal monitor.

Hi oliver, the sound slowdowns on batsugun are actually revealing your CPU is not fast enough to emulate this game when v-synced. I'm having issues with that game here too on a Core 2 Duo T5500. The right option for these specific games is -triplebuffer, that's the best you can get.

GroovyMAME's way of synchronizing sound with emulation reveals some slowdowns that do exist in main line MAME, although get somewhat hidden. To put it short, what MAME shows as a speed percent of 100% is an *average*, in fact some frames may take longer to emulate than the original hardware took to render them, although the final average speed may keep at 100%, giving you the impression that your CPU is fast enough. The problem here is, in order to emulate a game with v-sync enabled (the key here is v-sync), you need that every single frame can be emulated at its supposed speed.
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

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #105 on: December 23, 2012, 11:08:33 am »
I have some slight flicker with Up'n down  :dizzy: I've tested about 30 games and none other of those have this problem. The flicker is not bad, but it's there and I was wondering if there's a way to get it right (because it's just one game).

Hi emuola,

"Flicker" is not actually a game's issue, it's the supposed behaviour of an interlaced video mode. So first let's see why GM is picking an interlaced video mode for that specific game. As this is related to your particular monitor specs, please get a log of this game and post in your current monitor's thread so we can have a look.
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

oliver

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 25
Re: Games with ISSUES: report here!
« Reply #106 on: December 23, 2012, 01:30:45 pm »
Hi Calamity.
Thanks for the answer. I get it.
I will try to see if I can find some faster cpu for cheap to replace the e2160. Maybe I will look for a e6600.
I am very pleased with the result of this new build. It works very well indeed.

Edit:
actually, I turned on hwstretch and triplebuffer like you recommended and the game plays perfect and is properly centered and in lowres.
Maybe it is less accurate than with those settings off but it still looks very good to me.
« Last Edit: December 23, 2012, 01:59:12 pm by oliver »

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #107 on: December 23, 2012, 02:48:26 pm »
Hi oliver, I never said anything about hwstretch, that won't help at all, only triplebuffer makes sense for this.
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

oliver

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 25
Re: Games with ISSUES: report here!
« Reply #108 on: December 23, 2012, 04:23:07 pm »
if i keep hwstretch off, the game's boarders are off screen.

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #109 on: December 23, 2012, 04:39:15 pm »
if i keep hwstretch off, the game's boarders are off screen.

Nevermind, I didn't notice there's already an stretched resolution in use, so the -hwstretch is necessary indeed, I meant that the relevant option in terms of performance/synchronization is -triplebuffer.
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

oliver

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 25
Re: Games with ISSUES: report here!
« Reply #110 on: December 23, 2012, 04:45:58 pm »
yes, vertical game on horizontal screen is wrong anyway, so a little bit more or less wrong does not make much difference. The hwstretch does not have any impact on perf you are right. It is just needed to make the game fit.

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #111 on: January 15, 2013, 12:37:23 pm »
My software (libdrm, mesa, xf86-video-ati) is older: Slackware isn't a rolling distro; however it worked fine until groovymame 0.147u3.
I will try to upgrade to Slackware 14.0 (which has a bit newer software, but still older than the one on the live-cd).

You may try disabling -changeres for Midway games, just to discard things.
Upgraded to Slackware 14.0 and groovymame 0.148.
With "-changeres" enabled the problem persists, but if I disable that option, then all works as expected.
Earth could be the hell of another world

repetto74

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 84
Re: Games with ISSUES: report here!
« Reply #112 on: January 17, 2013, 12:33:50 pm »
Hi,

I am using GroovyUME 147 which I really like a lot as it gives me the opportunity to configure also some consoles emulation without playing with different emulators and configurations (and also picks the correct resolution!) :applaud:

I have installed the Atari 5200 emulation with a set of NoIntro roms but I have issues with some games. Most of the games play fine but Galaxian for example gives video troubles on screen. The aliens are displayed two times on screen and there are some color artifact displaying also when the spaceship is moved left and right. Frogger also gives a lot of image tearing. I have tried to replace the game roms with one of a different collection but no luck
I would like to know if someone has the same issue. The emulation of Atari5200 is reported to be good in MESS right?? ???

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #113 on: January 18, 2013, 05:09:34 am »
Upgraded to Slackware 14.0 and groovymame 0.148.
With "-changeres" enabled the problem persists, but if I disable that option, then all works as expected.

That's possibly opengl breaking due to resolution switching. Probably if you run GM with the '-video soft' option it will work, although terribly slow. At least setting -nochangeres for these games is not a problem because the resolution switch is not really needed (it's the same resolution all the time actually).
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

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #114 on: January 18, 2013, 05:25:35 am »
That's possibly opengl breaking due to resolution switching.
Ok, but why it happens only with these games and not wide in general?
If it's a opengl issue, then it should fail with all games that try to change the resolution or am I wrong?
Earth could be the hell of another world

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #115 on: January 18, 2013, 05:59:36 am »
Ok, but why it happens only with these games and not wide in general?
If it's a opengl issue, then it should fail with all games that try to change the resolution or am I wrong?

No idea. It does work fine with Arch, indeed.

BTW, both VeS and I have been testing Arch 64-bits lately trying to detect the sound issue with games like galaga, etc. but it just doesn't seem to exist in this system... was it a very noticeable noise or something subtle?
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

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #116 on: January 18, 2013, 06:25:48 am »
BTW, both VeS and I have been testing Arch 64-bits lately trying to detect the sound issue with games like galaga, etc. but it just doesn't seem to exist in this system... was it a very noticeable noise or something subtle?
I got the galaga crappy sound issue some release ago, but since version 0.147u3 it disappeared and now works as expected.
Earth could be the hell of another world

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #117 on: January 21, 2013, 07:38:02 am »
I got the galaga crappy sound issue some release ago, but since version 0.147u3 it disappeared and now works as expected.

That's a relief  ;)
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

Endprodukt

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 614
  • I want to build my own arcade controls!
Re: Games with ISSUES: report here!
« Reply #118 on: January 23, 2013, 01:13:46 pm »
Does anyone else have graphic bugs in Missile Command?

repetto74

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 84
Re: Games with ISSUES: report here!
« Reply #119 on: January 26, 2013, 08:52:46 am »
Yes I DO have a bug on Missile Command. Actually when playing the game some random dots colored artifacts will display on the background.

Endprodukt

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 614
  • I want to build my own arcade controls!
AW: Games with ISSUES: report here!
« Reply #120 on: January 27, 2013, 06:01:14 pm »
Exactly. Need to find out if this is Mame or groovymame related.

yakk11

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 81
Re: Games with ISSUES: report here!
« Reply #121 on: February 10, 2013, 09:43:10 pm »
The voices in shinobi don't appear to be working any more.  They work in MAMEUI, did I change something that I shouldn't have?

adder

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 611
  • Location: Easy St.
Re: Games with ISSUES: report here!
« Reply #122 on: February 10, 2013, 09:59:15 pm »
The voices in shinobi don't appear to be working any more.  They work in MAMEUI, did I change something that I shouldn't have?

did u try the System 16B version? try that instead of the 16A version
typed using my...

EvilDindon

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 47
Re: Games with ISSUES: report here!
« Reply #123 on: May 30, 2013, 07:00:13 am »
Tapper and roadrunner doesn't start for me (hd4350 + scart tv + groovymame32 0.148u5 under magic resolutions)

They both run on my desktop pc with standard mame 148.u5.
« Last Edit: May 31, 2013, 07:19:24 am by EvilDindon »

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #124 on: June 04, 2013, 01:38:59 pm »
Tapper and roadrunner doesn't start for me (hd4350 + scart tv + groovymame32 0.148u5 under magic resolutions)

They both run on my desktop pc with standard mame 148.u5.

tapper just works here.

roadrunr, bug confirmed, it's reported as mechanical, and not having a screen makes Switchres crash, we'll need to add a check for mechanical games.

Thanks!
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

EvilDindon

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 47
Re: Games with ISSUES: report here!
« Reply #125 on: June 05, 2013, 02:56:32 pm »
Heh, that's weird for Tapper !

Any tips ?

Isn't it this 30 Hz resolution's fault ?

What if I create a tapper.ini with "resolution 512X448" ?

Does groovymame reads the games ini files (in the ini folder of groovymame) ?

If no, how could i force groovy to pick a specific resolution for a game ?

Cheers,
« Last Edit: June 06, 2013, 02:14:26 am by EvilDindon »

ozfalcon

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 151
  • ZSystem
Re: Games with ISSUES: report here!
« Reply #126 on: June 07, 2013, 09:03:24 pm »
An order of magnitude incorrect.
Disregard this post.

This is relevant to my issue:
http://forum.arcadecontrols.com/index.php/topic,129585.msg1325567.html#msg1325567
« Last Edit: June 08, 2013, 07:21:58 am by ozfalcon »

ozfalcon

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 151
  • ZSystem
Re: Games with ISSUES: report here!
« Reply #127 on: June 07, 2013, 11:25:50 pm »
No longer relevant: Re Previous post   ???
« Last Edit: June 08, 2013, 07:23:51 am by ozfalcon »

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #128 on: June 09, 2013, 09:31:20 am »
Heh, that's weird for Tapper !

Any tips ?

Isn't it this 30 Hz resolution's fault ?

What if I create a tapper.ini with "resolution 512X448" ?

Does groovymame reads the games ini files (in the ini folder of groovymame) ?

If no, how could i force groovy to pick a specific resolution for a game ?

Cheers,

EvilDindon,

Posting about game issues without a log is a somewhat useless. Post a proper log so I can see what's going on there. You just say it doesn't start, but you're not saying if it crashes, or it just freezes, black screen, etc. Try disabling -multithreading, *sometimes* this is the issue with games that require refresh scaling.


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

EvilDindon

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 47
Re: Games with ISSUES: report here!
« Reply #129 on: June 10, 2013, 12:26:30 pm »
Yeah you're totally right !

Remind me how to create a log file ; is it the "debug 1" option in mame.ini ?

Gonna try "multithread 0" too.

What I'm sure is that the game doesn't lauch at all for the moment.

Thanks.

NightSprinter

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 171
Re: Games with ISSUES: report here!
« Reply #130 on: August 30, 2013, 01:58:30 pm »
Easy way to do so (as Calamity showed me this when I was testing things in Windows XP for him) is this example:

groovymame dkong -v >dkong.txt
It doesn't matter how bad things are, it'll work out in the end.

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #131 on: August 30, 2013, 02:22:16 pm »
First post of this topic:
SECOND: Get a proper log of your game by using the following command line:

             groovymame.exe romname -v >romname.txt
Earth could be the hell of another world

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
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

vindic8r

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 72
    • MOTUMAME: A Masters of the Universe Arcade Cabinet
Re: Games with ISSUES: report here!
« Reply #133 on: October 24, 2013, 12:37:58 am »
I've got an oddball. Arkanoid. It runs at 175%, even with throttle = 1. And playing with various -speed settings just made the sound...well they made it sound horrible. I confirmed that it runs just fine with MAME64 0.149. Also, turning SwitchRes on and off doesn't seem to make a difference.

Log files are attached.  Any suggestions or thoughts would be greatly appreciated.

vindic8r

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 72
    • MOTUMAME: A Masters of the Universe Arcade Cabinet
Re: Games with ISSUES: report here!
« Reply #134 on: October 24, 2013, 12:47:01 am »
Just saw the Carnevil thread and figured I'd try setting triplebuffer = 1. That worked like a charm, when set at the game level in arkanoid.ini.

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #135 on: April 11, 2014, 04:48:56 am »
I'm having some problems with galaga: when I try to launch the rom, the screen is upside-down and I can't even insert credits or start a game.
Code: [Select]
Parsing mame.ini
Parsing mame.ini
Optional device 'sub3' not found
Optional device 'samples' not found
Optional device 'sub3' not found
Optional device 'samples' not found
Optional device 'sub3' not found
Optional device 'samples' not found
Optional device 'sub3' not found
Optional device 'samples' not found
Optional device 'sub3' not found
Optional device 'samples' not found
Optional device 'sub3' not found
Optional device 'samples' not found
Optional device 'sub3' not found
Optional device 'samples' not found
SwitchRes: Monitor range 15625.00-15800.00,49.50-60.50,2.000,4.700,8.000,0.064,0.160,1.056,0,0,192,288,448,576
SwitchRes: Monitor: custom Orientation: vertical Modeline generation: enabled
SwitchRes: Found output connector 'VGA-0'

SwitchRes: Entering switchres_modeline_setup
SwitchRes: v0.015:[galaga] Calculating best video mode for 224x288@60.606060 orientation: rotated

SwitchRes: (   1)x(   1)_(60=0.0000Hz)
   rng(0):  400 x 288_51.299p 15.800 [integ] scale(1, 1, 1) diff(0.00, 0.00, -9.3074) ratio(1.786, 1.000)

SwitchRes: [galaga] (1) vertical (224x288@60.61)->(400x288@51.30)
   rng(0):  400 x 288_51.299p 15.800 [integ] scale(1, 1, 1) diff(0.00, 0.00, -9.3074) ratio(1.786, 1.000)
SwitchRes: Modeline "400x288_60 15.80KHz 51.30Hz" 8.22 400 416 456 520 288 289 292 308   -hsync -vsync
SwitchRes: Running 'xrandr  --newmode "400x288_51.30" 8.22 400 416 456 520 288 289 292 308   -hsync -vsync'
SwitchRes: Running 'xrandr  --addmode VGA-0 "400x288_51.30"'
SwitchRes: Setting option -rotate
SwitchRes: Setting option -noror
SwitchRes: Setting option -noautoror
SwitchRes: Setting option -norol
SwitchRes: Setting option -noautorol
SwitchRes: Setting option -noblack_frame_insertion
SwitchRes: Setting option -nomultithreading
SwitchRes: Setting option -nosyncrefresh
SwitchRes: Setting option -nowaitvsync
SwitchRes: Setting option -keepaspect
SwitchRes: Setting option -nounevenstretch
SwitchRes: Setting option -nofilter
SwitchRes: Setting option -prescale 1
Build version:      0.153 (Apr  9 2014)
Build architecure:  SDLMAME_ARCH=
Build defines 1:    SDLMAME_UNIX=1 SDLMAME_X11=1 SDLMAME_LINUX=1
Build defines 1:    LSB_FIRST=1 PTR64=1 DISTRO=generic SYNC_IMPLEMENTATION=tc
SDL/OpenGL defines: SDL_COMPILEDVERSION=1215 USE_OPENGL=1 USE_DISPATCH_GL=1
Compiler defines A: __GNUC__=4 __GNUC_MINOR__=8 __GNUC_PATCHLEVEL__=2 __VERSION__="4.8.2"
Compiler defines B: __amd64__=1 __x86_64__=1 __unix__=1
Compiler defines C: __USE_FORTIFY_LEVEL=0
SDL Device Driver     : x11
SDL Monitor Dimensions: 768 x 576
Enter sdlwindow_init
Using SDL single-window OpenGL driver (SDL 1.2)
Leave sdlwindow_init
Loaded opengl shared library: <default>
OpenGL: X.Org
OpenGL: Gallium 0.4 on AMD RS780
OpenGL: 2.1 Mesa 9.1.7
OpenGL: texture rectangle supported
OpenGL: non-power-of-2 textures supported (new method)
OpenGL: vertex buffer supported
OpenGL: pixel buffers supported
OpenGL: framebuffer object supported
OpenGL: GLSL supported, but disabled
OpenGL: max texture size 8192 x 8192
Keyboard: Start initialization
Input: Adding Kbd #0: System keyboard
Keyboard: Registered System keyboard
Keyboard: End initialization
Mouse: Start initialization
Input: Adding Mouse #0: System mouse
Mouse: Registered System mouse
Mouse: End initialization
Joystick: Start initialization
Joystick: End initialization
Audio: Start initialization
Audio: Driver is alsa
Audio: frequency: 48000, channels: 2, samples: 1024
sdl_create_buffers: creating stream buffer of 114688 bytes
Audio: End initialization
output: unable to open output notifier file /tmp/sdlmame_out
Region ':maincpu' created
Region ':sub' created
Region ':sub2' created
Region ':gfx1' created
Region ':gfx2' created
Region ':proms' created
Region ':namco' created
Region ':51xx:mcu' created
Region ':54xx:mcu' created
Searching font Liberation Sans in -fontpath
Matching font: /usr/share/fonts/TTF/LiberationSans-Regular.ttf
Starting Galaga (Namco rev. B) ':'
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
  (missing dependencies; rescheduling)
Starting Z80 ':maincpu'
Starting Z80 ':sub'
Starting Z80 ':sub2'
Starting Namco 51xx ':51xx'
Starting MB8843 ':51xx:mcu'
Starting Namco 54xx ':54xx'
Starting MB8844 ':54xx:mcu'
Starting Namco 06xx ':06xx'
Starting Video Screen ':screen'
  (missing dependencies; rescheduling)
Starting gfxdecode ':gfxdecode'
Starting palette ':palette'
Starting Speaker ':mono'
  (missing dependencies; rescheduling)
Starting Namco ':namco'
Starting DISCRETE ':discrete'
Starting Galaga (Namco rev. B) ':'
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
  (missing dependencies; rescheduling)
Starting Video Screen ':screen'
Starting Speaker ':mono'
Starting Galaga (Namco rev. B) ':'
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
OpenGL: VBO supported
OpenGL: PBO supported
OpenGL: FBO supported
OpenGL: using vid filter: 0
GL texture: copy 1, shader 0, dynamic 1, 288x224 288x224 [PALETTE16, Equal: 0, Palette: 1,
            scale 1x1, border 0, pitch 384,288/8192], bytes/pix 4
GL texture: copy 1, shader 0, dynamic 1, 288x224 288x224 [PALETTE16, Equal: 0, Palette: 1,
            scale 1x1, border 0, pitch 384,288/8192], bytes/pix 4
Average speed: 99.99% (22 seconds)
sdl_kill: closing audio
Joystick: Start deinitialization
Joystick: End deinitialization
Enter sdlwindow_exit
Leave sdlwindow_exit
SwitchRes: Restoring desktop resolution: 768x576x50.00
SwitchRes: Running 'xrandr --output VGA-0 --mode 768x576x50.00'
SwitchRes: Running 'xrandr  --delmode VGA-0 "400x288_51.30"'
SwitchRes: Running 'xrandr  --rmmode "400x288_51.30"'

The strange thing is "SwitchRes: Monitor: custom Orientation: vertical Modeline generation: enabled", since in "mame.ini" I explicitly set "orientation horizontal".
Earth could be the hell of another world

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #136 on: April 11, 2014, 05:17:25 am »
I'm having some problems with galaga: when I try to launch the rom, the screen is upside-down and I can't even insert credits or start a game.

Check this: http://www.mameworld.info/ubbthreads/showthreaded.php?Cat=&Number=324318&page=0&view=expanded&sb=5&o=&fpart=1&vc=1

Quote
The strange thing is "SwitchRes: Monitor: custom Orientation: vertical Modeline generation: enabled", since in "mame.ini" I explicitly set "orientation horizontal".

Yeah that text in the log is misleading. Instead of "vertical" it should say "rotated".

It doesn't reflect your current configuration but the combined effect of your -orientation option with the native orientation of the game. So, "-orientation vertical" with a vertical game would result in "orientation horizontal" in the log, which actually should express "not rotated".
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

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #137 on: April 11, 2014, 05:45:51 am »
Check this: http://www.mameworld.info/ubbthreads/showthreaded.php?Cat=&Number=324318&page=0&view=expanded&sb=5&o=&fpart=1&vc=1
Found this.
Thanks for pointing it out.


Yeah that text in the log is misleading. Instead of "vertical" it should say "rotated".

It doesn't reflect your current configuration but the combined effect of your -orientation option with the native orientation of the game. So, "-orientation vertical" with a vertical game would result in "orientation horizontal" in the log, which actually should express "not rotated".
A bit confusing, but ok.
Earth could be the hell of another world

ozfalcon

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 151
  • ZSystem
Re: Games with ISSUES: report here!
« Reply #138 on: April 18, 2014, 07:44:50 pm »
In other words, Galaga and DigDug are broken for Mame 0.153 and is fixed for next release.
« Last Edit: April 18, 2014, 07:49:26 pm by ozfalcon »

vindic8r

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 72
    • MOTUMAME: A Masters of the Universe Arcade Cabinet
Re: Games with ISSUES: report here!
« Reply #139 on: May 07, 2014, 11:59:29 pm »
I'm seeing audio skipping and freezing issues with Joust 2 (joust2) and Maximum Force (maxforce). The former just skips and stutters horribly, the latter does the same and also freezes just after loading into Level 1.

Log files are attached. Also attached is my mame.ini file, for context.

ArcadeVGA3000
WG U2000
Win 7 Pro 64

These games play just fine in MAME 0.152b proper.

Any ideas?

vindic8r

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 72
    • MOTUMAME: A Masters of the Universe Arcade Cabinet
Re: Games with ISSUES: report here!
« Reply #140 on: May 08, 2014, 12:29:51 am »
I should perhaps clarify that I'm using groovymame64 0.152.

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #141 on: May 08, 2014, 06:21:43 am »
Any ideas?

Try enabling -multithreading in mame.ini.

For maxforce, create a maxforce.ini file and put "resolution 320x240@60" in 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 or pasting it.

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

vindic8r

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 72
    • MOTUMAME: A Masters of the Universe Arcade Cabinet
Re: Games with ISSUES: report here!
« Reply #142 on: May 09, 2014, 07:48:27 am »
Try enabling -multithreading in mame.ini.

Thanks, that worked like a charm. I never caught that setting in there before. My second core was probably getting bored.

For maxforce, create a maxforce.ini file and put "resolution 320x240@60" in it.

That didn't work. I confirmed from Game Information that the resolution/refresh rate matched this setting (almost, the refresh rate was 59.79...), so the ini file is being read. Any other ideas?
I should perhaps clarify that I'm using groovymame64 0.152.

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #143 on: May 09, 2014, 08:01:27 am »
That didn't work. I confirmed from Game Information that the resolution/refresh rate matched this setting (almost, the refresh rate was 59.79...), so the ini file is being read. Any other ideas?

Please post a log of the game with the new setting added, maybe I can see something new now.
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

vindic8r

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 72
    • MOTUMAME: A Masters of the Universe Arcade Cabinet
Re: Games with ISSUES: report here!
« Reply #144 on: May 10, 2014, 12:19:01 am »
Please post a log of the game with the new setting added, maybe I can see something new now.
Here you are, sir.

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #145 on: May 10, 2014, 05:36:44 am »
Hi vindic8r,

Please use the latest version (with Switchres 0.015b), it has specific fixes for ArcadeVGA 3000, no one with this card should be running an older version.

That said, the log you show looks perfectly fine. It seems to exit normally too. What's the exact problem, sound stuttering? If so check the speed (F11), it probably won't be 100%.
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

ozfalcon

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 151
  • ZSystem
Re: Games with ISSUES: report here!
« Reply #146 on: May 19, 2014, 07:48:13 pm »
<Update>
Nevermind, wcbowl changes refresh on the fly.
« Last Edit: May 20, 2014, 12:39:45 am by ozfalcon »

cools

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 511
  • Arcade Otaku sysadmin...
    • Arcade Otaku
Re: Games with ISSUES: report here!
« Reply #147 on: June 18, 2014, 03:34:34 pm »
Xevious 3DG switches res in a way that leaves it taking up half the screen rather than filling it.

It's fine in normal MAME
Please don't PM me with support questions. Ask in public so everyone can learn!

NightSprinter

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 171
Re: Games with ISSUES: report here!
« Reply #148 on: July 05, 2014, 04:30:42 pm »
Posted that last bit in the wrong thread, but I can say that Twin Cobra (unlike other vertical games that display right on my monitor) looks completely wrong.  I'll go snap a pic real quick and provide a log.  Are the Toaplan games supposed to report a resolution of 320x240?  Something doesn't seem right.

[Edit] Ok, so took some pics.  Why in the bloody hell is my NEC reporting 48KHz horizontal scan and a refresh of over 80Hz?  My crt settings must be way off or something.
« Last Edit: July 06, 2014, 07:06:47 pm by NightSprinter »
It doesn't matter how bad things are, it'll work out in the end.

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #149 on: July 07, 2014, 07:33:52 am »
Are the Toaplan games supposed to report a resolution of 320x240?

Yes.

Quote
Why in the bloody hell is my NEC reporting 48KHz horizontal scan and a refresh of over 80Hz?  My crt settings must be way off or something.

Switchres is not able to apply its settings. The default refresh of that monitor is being used instead (85 Hz). This is probably caused because there is a mismatch between the output used by MAME and the connector selected by the kernel options.

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

NightSprinter

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 171
Re: Games with ISSUES: report here!
« Reply #150 on: July 07, 2014, 09:32:57 am »
Hmm, I'll have to go back to the GroovyArcade distro then for testing. I've been seeing how the packages cools uploaded to AUR worked in Manjaro.

[Update] I deleted all of the config files, and now it's displaying in 480i for Toaplan's games when not rotated to proper vertical mode.  I have my monitor set as "horizontal", as I physically can't rotate my NEC.
« Last Edit: July 07, 2014, 04:00:27 pm by NightSprinter »
It doesn't matter how bad things are, it'll work out in the end.

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #151 on: July 07, 2014, 06:11:18 pm »
[Update] I deleted all of the config files, and now it's displaying in 480i for Toaplan's games when not rotated to proper vertical mode.  I have my monitor set as "horizontal", as I physically can't rotate my NEC.

Which config files? The ones in /cfg?
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

NightSprinter

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 171
Re: Games with ISSUES: report here!
« Reply #152 on: July 08, 2014, 12:46:22 pm »
Yes.  If I set the games to be rotated 90 degrees either direction, the picture is full progressive scan.  Non-rotated results in the image being quite blurry (easily seen in how smudged the numbers for the score and the bomb icons are) and it goes to 480i.
It doesn't matter how bad things are, it'll work out in the end.

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #153 on: July 08, 2014, 05:32:31 pm »
Yes.  If I set the games to be rotated 90 degrees either direction, the picture is full progressive scan.

As expected.

Quote
Non-rotated results in the image being quite blurry (easily seen in how smudged the numbers for the score and the bomb icons are) and it goes to 480i.

It's blurry because it's using fractional scaling (320/480 lines). It's using 480i because of your current monitor config (15 kHz).
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

Andypc

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 104
Re: Games with ISSUES: report here!
« Reply #154 on: July 24, 2014, 09:49:48 am »
I am having problems with this command:-

groovymame.exe romname -v >romname.txt

Mine is:- c:\Groovymame153\Mame64.exe kungfum -v >kungfum.txt

This works c:\Groovymame153\Mame64.exe kungfum -v

but not when I add the output file?



Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #155 on: July 24, 2014, 09:56:08 am »
Hi Andypc,

Not sure how you're doing it... simply open a cmd box, cd into the MAME folder and run:

mame64 kungfum -v >kungfum.txt
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

Andypc

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 104
Re: Games with ISSUES: report here!
« Reply #156 on: July 24, 2014, 10:33:02 am »
Thanks. That just solved my problem. I ran the CMD box as administrator and it started at the right resolution. I went back and set Groovymame to run as administrator and the games are all starting in the right resolution :laugh: I also sorted the shift problem with the J-pac it was the coin switch stuck on which was the only thing I hadn't checked  :D Mega Happy. I can now play some games. Thanks for all your help.  :cheers:

joeblade2

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 61
  • Scanline Generation!
Re: Games with ISSUES: report here!
« Reply #157 on: August 07, 2014, 03:54:00 pm »
Ok so im sure there is an obvious answer for this one.....

Been happily playing away with GM for months now, various versions...now at win7 on an i7 3770.
Ok granted not the quickest out there but thought it would solve my radiant silvergun issue!!!

Firstly it changes resolution several times before the start screen, then when it gets to the start of the game as soon as I start firing it slows down to a crawl.

Posting the log file, hope I can resolve this issue, some of the other stv titles run a little off but nothing like this!!

Thanks guys
Joe

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #158 on: August 08, 2014, 11:53:32 am »
Hi joeblade2,

If you're using W7, make sure to get a GM version with Switchres 0.015b, it has several fixes specifically for W7. Besides, using "super" resolutions will make games that switch resolutions run way smoother.
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

joeblade2

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 61
  • Scanline Generation!
Re: Games with ISSUES: report here!
« Reply #159 on: August 08, 2014, 12:51:44 pm »
Hi joeblade2,

If you're using W7, make sure to get a GM version with Switchres 0.015b, it has several fixes specifically for W7. Besides, using "super" resolutions will make games that switch resolutions run way smoother.

Ok many thanks Calamity im on GM 0.153 so i'll see if upgrading to makes any difference, just out of interest, if cools happens upon this post could you let me know if super resolutions have made a difference in your setup..?

Im not talking about boot time for roms but performance wise on games.

Thanks

EDIT: Just patched GM 0.154 with diff & txt and replaced existing gm.exe....no difference!! Will have a look into super resolutions then.... :'(
« Last Edit: August 08, 2014, 01:25:45 pm by joeblade2 »

cools

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 511
  • Arcade Otaku sysadmin...
    • Arcade Otaku
Re: Games with ISSUES: report here!
« Reply #160 on: August 08, 2014, 01:47:27 pm »
Joe, that chip has no more power for MAME than my 4690, it's as good as it's going to get at the moment! You'll notice that Silvergun only crawls at certain parts - normally when it's scaling and rotating the background plane.

Super resolutions make no difference in this game for me, not with the resolution switching nor with speed.
Please don't PM me with support questions. Ask in public so everyone can learn!

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #161 on: August 08, 2014, 02:00:34 pm »
I thought it could be a problem with halved refresh rate & interlaced modes. If it's cpu related then there's not much we can do, apart from using -triplebuffer -multithreading (which may improve performance at the cost of breaking smooth video).
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

cools

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 511
  • Arcade Otaku sysadmin...
    • Arcade Otaku
Re: Games with ISSUES: report here!
« Reply #162 on: August 08, 2014, 02:06:39 pm »
In-game isn't interlaced, just the title screen is.
Please don't PM me with support questions. Ask in public so everyone can learn!

joeblade2

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 61
  • Scanline Generation!
Re: Games with ISSUES: report here!
« Reply #163 on: August 09, 2014, 02:07:36 am »
Joe, that chip has no more power for MAME than my 4690, it's as good as it's going to get at the moment! You'll notice that Silvergun only crawls at certain parts - normally when it's scaling and rotating the background plane.

Super resolutions make no difference in this game for me, not with the resolution switching nor with speed.

Thanks for the reply cools....yeah that's what I was thinking and why I didn't want to go down the super resolutions route until I heard from you....everything else is tickety boo so I'll leave it for the mo.

@calamity thanks again for the replies, as always, and I'll try changing triplebuffer/multithreading option just to be sure! ;)
« Last Edit: August 09, 2014, 02:10:58 am by joeblade2 »

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #164 on: August 30, 2014, 04:23:19 am »
I have some problems with groovymame 0.154 and some roms (for example Metal Slug (mslug) and Bubble Bobble (bublbobl)): the rom starts, but I only get a black screen.

Metal Slug log:
Code: [Select]
SwitchRes: Entering switchres_modeline_setup
SwitchRes: v0.015b:[mslug] Calculating best video mode for 320x224@59.185608 orientation: normal

SwitchRes: (   1)x(   1)_(60=0.0000Hz)
   rng(0):  320 x 224_59.186p 15.625 [integ] scale(1, 1, 1) diff(0.00, 0.00, 0.0000) ratio(1.000, 1.000)

SwitchRes: [mslug] (1) horizontal (320x224@59.19)->(320x224@59.19)
   rng(0):  320 x 224_59.186p 15.625 [integ] scale(1, 1, 1) diff(0.00, 0.00, 0.0000) ratio(1.000, 1.000)
SwitchRes: Modeline "320x224_60 15.63KHz 59.19Hz" 6.62 320 336 368 424 224 235 238 264   -hsync -vsync
SwitchRes: Running 'xrandr  --newmode "320x224_59.19" 6.62 320 336 368 424 224 235 238 264   -hsync -vsync'
SwitchRes: Running 'xrandr  --addmode VGA-0 "320x224_59.19"'
SwitchRes: Running 'xrandr  --output VGA-0 --mode "320x224_59.19"'
SwitchRes: Setting option -rotate
SwitchRes: Setting option -noror
SwitchRes: Setting option -autoror
SwitchRes: Setting option -norol
SwitchRes: Setting option -noautorol
SwitchRes: Setting option -noblack_frame_insertion
SwitchRes: Setting option -nomultithreading
SwitchRes: Setting option -syncrefresh
SwitchRes: Setting option -waitvsync
SwitchRes: Setting option -keepaspect
SwitchRes: Setting option -nounevenstretch
SwitchRes: Setting option -nofilter
SwitchRes: Setting option -prescale 1
Build version:      0.154 (Aug 22 2014)
Build architecure:  SDLMAME_ARCH=
Build defines 1:    SDLMAME_UNIX=1 SDLMAME_X11=1 SDLMAME_LINUX=1
Build defines 1:    LSB_FIRST=1 PTR64=1 DISTRO=generic SYNC_IMPLEMENTATION=tc
SDL/OpenGL defines: SDL_COMPILEDVERSION=1215 USE_OPENGL=1 USE_DISPATCH_GL=1
Compiler defines A: __GNUC__=4 __GNUC_MINOR__=8 __GNUC_PATCHLEVEL__=2 __VERSION__="4.8.2"
Compiler defines B: __amd64__=1 __x86_64__=1 __unix__=1
Compiler defines C: __USE_FORTIFY_LEVEL=0
SDL Device Driver     : x11
SDL Monitor Dimensions: 320 x 224
Enter sdlwindow_init
Using SDL single-window OpenGL driver (SDL 1.2)
Leave sdlwindow_init
Loaded opengl shared library: <default>
OpenGL: X.Org
OpenGL: Gallium 0.4 on AMD RS780
OpenGL: 2.1 Mesa 9.1.7
OpenGL: texture rectangle supported
OpenGL: non-power-of-2 textures supported (new method)
OpenGL: vertex buffer supported
OpenGL: pixel buffers supported
OpenGL: framebuffer object supported
OpenGL: GLSL supported, but disabled
OpenGL: max texture size 8192 x 8192
Audio: Start initialization
Audio: Driver is alsa
Audio: frequency: 48000, channels: 2, samples: 1024
sdl_create_buffers: creating stream buffer of 114688 bytes
Audio: End initialization
Keyboard: Start initialization
Input: Adding Kbd #0: System keyboard
Keyboard: Registered System keyboard
Keyboard: End initialization
Mouse: Start initialization
Input: Adding Mouse #0: System mouse
Mouse: Registered System mouse
Mouse: End initialization
Joystick: Start initialization
Joystick: End initialization
output: unable to open output notifier file /tmp/sdlmame_out
Region ':maincpu' created
Region ':fixed' created
Region ':fixedbios' created
Region ':zoomy' created
Region ':mainbios' created
Region ':audiobios' created
Region ':audiocpu' created
Region ':ymsnd' created
Region ':sprites' created
Searching font Liberation Sans in -fontpath
Matching font: /usr/share/fonts/TTF/LiberationSans-Regular.ttf
Starting Metal Slug - Super Vehicle-001 ':'
Optional device 'cartslot6' not found
Optional device 'cartslot5' not found
Optional device 'cartslot4' not found
Optional device 'cartslot3' not found
Optional device 'cartslot2' not found
Optional device 'cartslot1' not found
  (missing dependencies; rescheduling)
Starting M68000 ':maincpu'
Starting Z80 ':audiocpu'
Starting Video Screen ':screen'
Optional device 'finder_dummy_tag' not found
Starting palette ':palette'
Starting Neogeo Sprites ':spritegen'
Starting Speaker ':lspeaker'
  (missing dependencies; rescheduling)
Starting Speaker ':rspeaker'
  (missing dependencies; rescheduling)
Starting YM2610 ':ymsnd'
Starting NeoGeo Banked Cartridge ':banked_cart'
Starting uPD4990A RTC ':upd4990a'
Starting NVRAM ':saveram'
Starting NEOGEO Memory Card ':memcard'
Starting NeoGeo Metal Slug X Protection Device ':mslugx_prot'
Starting NeoGeo SMA Cartridge ':sma_prot'
Starting NeoGeo CMC Protection Device ':cmc_prot'
Starting NeoGeo NEOPCM2 Protection Device ':pcm2_prot'
Starting NeoGeo PVC Protection Device ':pvc_prot'
Starting NeoGeo Bootleg Protection Device ':bootleg_prot'
Starting NeoGeo KOF2002 Protection Device ':kof2002_prot'
Starting NeoGeo Fatal Fury 2 Protection Device ':fatfury2_prot'
Starting NeoGeo KOF98 Protection Device ':kof98_prot'
Starting NeoGeo Super Bubble Pop Protection Device ':sbp_prot'
Starting Metal Slug - Super Vehicle-001 ':'
Optional device 'cartslot6' not found
Optional device 'cartslot5' not found
Optional device 'cartslot4' not found
Optional device 'cartslot3' not found
Optional device 'cartslot2' not found
Optional device 'cartslot1' not found
  (missing dependencies; rescheduling)
Starting Speaker ':lspeaker'
Starting Speaker ':rspeaker'
Starting Metal Slug - Super Vehicle-001 ':'
Optional device 'cartslot6' not found
Optional device 'cartslot5' not found
Optional device 'cartslot4' not found
Optional device 'cartslot3' not found
Optional device 'cartslot2' not found
Optional device 'cartslot1' not found
OpenGL: VBO supported
OpenGL: PBO supported
OpenGL: FBO supported
OpenGL: using vid filter: 0
GL texture: copy 0, shader 0, dynamic 0, 320x224 320x224 [RGB32, Equal: 1, Palette: 0,
            scale 1x1, border 0, pitch 384,320/8192], bytes/pix 4
GL texture: copy 0, shader 0, dynamic 0, 320x224 320x224 [RGB32, Equal: 1, Palette: 0,
            scale 1x1, border 0, pitch 384,320/8192], bytes/pix 4
Average speed: 606.48% (261 seconds)
Enter sdlwindow_exit
Leave sdlwindow_exit
sdl_kill: closing audio
Sound buffer: overflows=10 underflows=0
Joystick: Start deinitialization
Joystick: End deinitialization
SwitchRes: Restoring desktop resolution: 768x576x50.00
SwitchRes: Running 'xrandr --output VGA-0 --mode 768x576x50.00'
SwitchRes: Running 'xrandr  --delmode VGA-0 "320x224_59.19"'
SwitchRes: Running 'xrandr  --rmmode "320x224_59.19"'

Bubble Bobble log:
Code: [Select]
SwitchRes: Entering switchres_modeline_setup
SwitchRes: v0.015b:[bublbobl] Calculating best video mode for 256x224@59.185608 orientation: normal

SwitchRes: (   1)x(   1)_(60=0.0000Hz)
   rng(0):  256 x 224_59.186p 15.625 [integ] scale(1, 1, 1) diff(0.00, 0.00, 0.0000) ratio(1.000, 1.000)

SwitchRes: [bublbobl] (1) horizontal (256x224@59.19)->(256x224@59.19)
   rng(0):  256 x 224_59.186p 15.625 [integ] scale(1, 1, 1) diff(0.00, 0.00, 0.0000) ratio(1.000, 1.000)
SwitchRes: Modeline "256x224_60 15.63KHz 59.19Hz" 5.25 256 272 296 336 224 235 238 264   -hsync -vsync
SwitchRes: Running 'xrandr  --newmode "256x224_59.19" 5.25 256 272 296 336 224 235 238 264   -hsync -vsync'
SwitchRes: Running 'xrandr  --addmode VGA-0 "256x224_59.19"'
SwitchRes: Running 'xrandr  --output VGA-0 --mode "256x224_59.19"'
SwitchRes: Setting option -rotate
SwitchRes: Setting option -noror
SwitchRes: Setting option -autoror
SwitchRes: Setting option -norol
SwitchRes: Setting option -noautorol
SwitchRes: Setting option -noblack_frame_insertion
SwitchRes: Setting option -nomultithreading
SwitchRes: Setting option -syncrefresh
SwitchRes: Setting option -waitvsync
SwitchRes: Setting option -keepaspect
SwitchRes: Setting option -nounevenstretch
SwitchRes: Setting option -nofilter
SwitchRes: Setting option -prescale 1
Build version:      0.154 (Aug 22 2014)
Build architecure:  SDLMAME_ARCH=
Build defines 1:    SDLMAME_UNIX=1 SDLMAME_X11=1 SDLMAME_LINUX=1
Build defines 1:    LSB_FIRST=1 PTR64=1 DISTRO=generic SYNC_IMPLEMENTATION=tc
SDL/OpenGL defines: SDL_COMPILEDVERSION=1215 USE_OPENGL=1 USE_DISPATCH_GL=1
Compiler defines A: __GNUC__=4 __GNUC_MINOR__=8 __GNUC_PATCHLEVEL__=2 __VERSION__="4.8.2"
Compiler defines B: __amd64__=1 __x86_64__=1 __unix__=1
Compiler defines C: __USE_FORTIFY_LEVEL=0
SDL Device Driver     : x11
SDL Monitor Dimensions: 256 x 224
Enter sdlwindow_init
Using SDL single-window OpenGL driver (SDL 1.2)
Leave sdlwindow_init
Loaded opengl shared library: <default>
OpenGL: X.Org
OpenGL: Gallium 0.4 on AMD RS780
OpenGL: 2.1 Mesa 9.1.7
OpenGL: texture rectangle supported
OpenGL: non-power-of-2 textures supported (new method)
OpenGL: vertex buffer supported
OpenGL: pixel buffers supported
OpenGL: framebuffer object supported
OpenGL: GLSL supported, but disabled
OpenGL: max texture size 8192 x 8192
Audio: Start initialization
Audio: Driver is alsa
Audio: frequency: 48000, channels: 2, samples: 1024
sdl_create_buffers: creating stream buffer of 114688 bytes
Audio: End initialization
Keyboard: Start initialization
Input: Adding Kbd #0: System keyboard
Keyboard: Registered System keyboard
Keyboard: End initialization
Mouse: Start initialization
Input: Adding Mouse #0: System mouse
Mouse: Registered System mouse
Mouse: End initialization
Joystick: Start initialization
Joystick: End initialization
output: unable to open output notifier file /tmp/sdlmame_out
Region ':maincpu' created
Region ':slave' created
Region ':audiocpu' created
Region ':mcu' created
Region ':gfx1' created
Region ':proms' created
Region ':plds' created
pal16l8.bin NOT FOUND (NO GOOD DUMP KNOWN) (tried in bublbobl bublbobl)
pal16l8.bin NOT FOUND (NO GOOD DUMP KNOWN) (tried in bublbobl bublbobl)
pal16r4.bin NOT FOUND (NO GOOD DUMP KNOWN) (tried in bublbobl bublbobl)
WARNING: the game might not run correctly.
Searching font Liberation Sans in -fontpath
Matching font: /usr/share/fonts/TTF/LiberationSans-Regular.ttf
Starting Bubble Bobble (Japan, Ver 0.1) ':'
  (missing dependencies; rescheduling)
Starting Z80 ':maincpu'
Starting Z80 ':slave'
Starting Z80 ':audiocpu'
Starting M6801 ':mcu'
Starting Video Screen ':screen'
  (missing dependencies; rescheduling)
Starting gfxdecode ':gfxdecode'
Starting palette ':palette'
Starting Speaker ':mono'
  (missing dependencies; rescheduling)
Starting YM2203 ':ym1'
Starting YM3526 ':ym2'
Starting Bubble Bobble (Japan, Ver 0.1) ':'
  (missing dependencies; rescheduling)
Starting Video Screen ':screen'
Starting Speaker ':mono'
Starting Bubble Bobble (Japan, Ver 0.1) ':'
OpenGL: VBO supported
OpenGL: PBO supported
OpenGL: FBO supported
OpenGL: using vid filter: 0
GL texture: copy 1, shader 0, dynamic 1, 256x224 256x224 [PALETTE16, Equal: 0, Palette: 1,
            scale 1x1, border 0, pitch 384,256/8192], bytes/pix 4
GL texture: copy 1, shader 0, dynamic 1, 256x224 256x224 [PALETTE16, Equal: 0, Palette: 1,
            scale 1x1, border 0, pitch 384,256/8192], bytes/pix 4
Average speed: 217.26% (187 seconds)
Enter sdlwindow_exit
Leave sdlwindow_exit
sdl_kill: closing audio
Joystick: Start deinitialization
Joystick: End deinitialization
SwitchRes: Restoring desktop resolution: 768x576x50.00
SwitchRes: Running 'xrandr --output VGA-0 --mode 768x576x50.00'
SwitchRes: Running 'xrandr  --delmode VGA-0 "256x224_59.19"'
SwitchRes: Running 'xrandr  --rmmode "256x224_59.19"'
Earth could be the hell of another world

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #165 on: September 03, 2014, 04:02:17 am »
Hi Ansa,

Have you noticed any pattern in which roms fail to work? I mean like both ones you posted use very low resolutions, 224p and 256 wide respectively.

I'm saying this because I know you update your kernel quite often and those low resolutions have always been problematic to get them working with stock drivers. Wondering if this has started happening after a kernel update... or if previous versions of GM do work with your current kernel.

Apart from that your logs seem fine. Do you get any error messages from xrandr in the console?


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

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #166 on: September 03, 2014, 04:18:33 am »
Have you noticed any pattern in which roms fail to work?
Not really, for example galaga works without problems.
The only pattern seems related to neogeo games, but bubble bobble isn't from neogeo, so not really sure.


I'm saying this because I know you update your kernel quite often and those low resolutions have always been problematic to get them working with stock drivers. Wondering if this has started happening after a kernel update... or if previous versions of GM do work with your current kernel.
Not yet tested, will test ASAP.


Do you get any error messages from xrandr in the console?
No errors (or messages) in console.
Earth could be the hell of another world

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #167 on: September 20, 2014, 10:29:25 am »
I'm saying this because I know you update your kernel quite often and those low resolutions have always been problematic to get them working with stock drivers. Wondering if this has started happening after a kernel update... or if previous versions of GM do work with your current kernel.
You were right: with kernel 3.16.x both groovymame 0.153 and 0.154 have issues.
Coming back to kernel 3.14.x everything is ok.


PS: is there anything I can do to have a working kernel 3.16.x?
Earth could be the hell of another world

vindic8r

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 72
    • MOTUMAME: A Masters of the Universe Arcade Cabinet
Re: Games with ISSUES: report here!
« Reply #168 on: January 06, 2015, 12:45:55 am »
I just realized that something is wrong with the audio in Xenophobe. It starts and stops oddly, and sometimes loops certain clips. In general, it's fubar. Perhaps its been like this for a while and I didn't notice it. Or perhaps its a new issue. Honestly, I can't say. I just got the urge to shoot some xenos tonight and discovered this. I'm also running an older version of GM - 0.153, with SwitchRes 0.015a.

As a first step, I tried messing with audio_latency, triple_buffering and multithreading. Turning each on and off, and changing the audio latency, didn't change anything.

Here's the log output:
Code: [Select]
Parsing xenophob.ini
Optional device 'tcs' not found
Optional device 'sg' not found
Optional device 'csd' not found
Optional device 'tcs' not found
Optional device 'sg' not found
Optional device 'csd' not found
Optional device 'tcs' not found
Optional device 'sg' not found
Optional device 'csd' not found
Optional device 'cvsd' not found
Optional device 'tcs' not found
Optional device 'csd' not found
Optional device 'cvsd' not found
Optional device 'tcs' not found
Optional device 'csd' not found
Optional device 'tcs' not found
Optional device 'sg' not found
Optional device 'csd' not found
Optional device 'tcs' not found
Optional device 'sg' not found
Optional device 'csd' not found
Optional device 'tcs' not found
Optional device 'sg' not found
Optional device 'csd' not found
Optional device 'cvsd' not found
Optional device 'csd' not found
Optional device 'cvsd' not found
Optional device 'csd' not found
Optional device 'tcs' not found
Optional device 'sg' not found
Optional device 'csd' not found
Optional device 'cvsd' not found
Optional device 'tcs' not found
Optional device 'csd' not found
Optional device 'cvsd' not found
Optional device 'tcs' not found
Optional device 'sg' not found
SwitchRes: Monitor range 15625.00-16200.00,49.50-65.00,2.000,4.700,8.000,0.064,0.192,1.024,0,0,192,288,448,576
SwitchRes: Monitor: arcade_15 Orientation: horizontal Modeline generation: enabled
SwitchRes: \\.\DISPLAY1: Ultimarc ArcadeVGA3000.
SwitchRes: DeviceKey: System\CurrentControlSet\Control\Video\{CED22CC3-F9AC-4D18-9214-5397F8623444}\0000
Switchres: Searching for custom video modes...
Switchres: [  1]  240x 240 @ 60: system mode
Switchres: [  2]  256x 240 @ 61: system mode
Switchres: [  3]  256x 256 @ 60: system mode
Switchres: [  4]  256x 264 @ 58: system mode
Switchres: [  5]  288x 240 @ 61: system mode
Switchres: [  6]  296x 240 @ 60: system mode
Switchres: [  7]  304x 240 @ 61: system mode
Switchres: [  8]  320x 200 @ 60: system mode
Switchres: [  9]  320x 240 @ 60: system mode
Switchres: [ 10]  320x 256 @ 60: system mode
Switchres: [ 11]  336x 240 @ 60: system mode
Switchres: [ 12]  352x 256 @ 60: system mode
Switchres: [ 13]  352x 264 @ 57: system mode
Switchres: [ 14]  352x 288 @ 51: system mode
Switchres: [ 15]  368x 240 @ 60: system mode
Switchres: [ 16]  384x 288 @ 51: system mode
Switchres: [ 17]  392x 240 @ 60: system mode
Switchres: [ 18]  400x 256 @ 52: system mode
Switchres: [ 19]  448x 240 @ 60: system mode
Switchres: [ 20]  512x 240 @ 60: system mode
Switchres: [ 21]  512x 288 @ 51: system mode
Switchres: [ 22]  512x 448 @ 60: system mode
Switchres: [ 23]  512x 512 @ 58: system mode
Switchres: [ 24]  632x 264 @ 57: system mode
Switchres: [ 25]  640x 240 @ 60: system mode
Switchres: [ 26]  640x 288 @ 51: system mode
Switchres: [ 27]  640x 480 @ 60: system mode
Switchres: [ 28]  648x 288 @ 51: system mode
Switchres: [ 29]  720x 480 @ 60*: system mode
Switchres: [ 30]  800x 600 @ 52: system mode
SwitchRes: Found 0 custom of 30 active video modes

SwitchRes: Entering switchres_modeline_setup
SwitchRes: v0.015a:[xenophob] Calculating best video mode for 512x480@30.000000 orientation: normal

SwitchRes: [ 240]x[ 240]_(60=60.0000Hz)
   rng(0):  240 x 240_60.000p 15.660 [fract] scale(1, 1, 2) diff(0.00, 0.00, 0.0000) ratio(0.469, 0.500)

SwitchRes: [ 256]x[ 240]_(61=61.0000Hz)
   rng(0):  256 x 240_60.000p 15.660 [fract] scale(1, 1, 2) diff(0.00, 0.00, 0.0000) ratio(0.500, 0.500)

SwitchRes: [ 256]x[ 256]_(60=60.0000Hz)
   rng(0):  256 x 256_58.484p 16.200 [fract] scale(1, 1, 2) diff(0.00, 0.00, -0.7581) ratio(0.500, 0.533)

SwitchRes: [ 256]x[ 264]_(58=58.0000Hz)
   rng(0):  256 x 264_56.842p 16.200 [fract] scale(1, 1, 2) diff(0.00, 0.00, -1.5789) ratio(0.500, 0.550)

SwitchRes: [ 288]x[ 240]_(61=61.0000Hz)
   rng(0):  288 x 240_60.000p 15.660 [fract] scale(1, 1, 2) diff(0.00, 0.00, 0.0000) ratio(0.563, 0.500)

SwitchRes: [ 296]x[ 240]_(60=60.0000Hz)
   rng(0):  296 x 240_60.000p 15.660 [fract] scale(1, 1, 2) diff(0.00, 0.00, 0.0000) ratio(0.578, 0.500)

SwitchRes: [ 304]x[ 240]_(61=61.0000Hz)
   rng(0):  304 x 240_60.000p 15.660 [fract] scale(1, 1, 2) diff(0.00, 0.00, 0.0000) ratio(0.594, 0.500)

SwitchRes: [ 320]x[ 200]_(60=60.0000Hz)
   rng(0):  320 x 200_60.000p 15.660 [fract] scale(1, 1, 2) diff(0.00, 0.00, 0.0000) ratio(0.625, 0.417)

SwitchRes: [ 320]x[ 240]_(60=60.0000Hz)
   rng(0):  320 x 240_60.000p 15.660 [fract] scale(1, 1, 2) diff(0.00, 0.00, 0.0000) ratio(0.625, 0.500)

SwitchRes: [ 320]x[ 256]_(60=60.0000Hz)
   rng(0):  320 x 256_58.484p 16.200 [fract] scale(1, 1, 2) diff(0.00, 0.00, -0.7581) ratio(0.625, 0.533)

SwitchRes: [ 336]x[ 240]_(60=60.0000Hz)
   rng(0):  336 x 240_60.000p 15.660 [fract] scale(1, 1, 2) diff(0.00, 0.00, 0.0000) ratio(0.656, 0.500)

SwitchRes: [ 352]x[ 256]_(60=60.0000Hz)
   rng(0):  352 x 256_58.484p 16.200 [fract] scale(1, 1, 2) diff(0.00, 0.00, -0.7581) ratio(0.688, 0.533)

SwitchRes: [ 352]x[ 264]_(57=57.0000Hz)
   rng(0):  352 x 264_56.842p 16.200 [fract] scale(1, 1, 2) diff(0.00, 0.00, -1.5789) ratio(0.688, 0.550)

SwitchRes: [ 352]x[ 288]_(51=51.0000Hz)
   rng(0):  352 x 288_52.427p 16.200 [fract] scale(1, 1, 2) diff(0.00, 0.00, -3.7864) ratio(0.688, 0.600)

SwitchRes: [ 368]x[ 240]_(60=60.0000Hz)
   rng(0):  368 x 240_60.000p 15.660 [fract] scale(1, 1, 2) diff(0.00, 0.00, 0.0000) ratio(0.719, 0.500)

SwitchRes: [ 384]x[ 288]_(51=51.0000Hz)
   rng(0):  384 x 288_52.427p 16.200 [fract] scale(1, 1, 2) diff(0.00, 0.00, -3.7864) ratio(0.750, 0.600)

SwitchRes: [ 392]x[ 240]_(60=60.0000Hz)
   rng(0):  392 x 240_60.000p 15.660 [fract] scale(1, 1, 2) diff(0.00, 0.00, 0.0000) ratio(0.766, 0.500)

SwitchRes: [ 400]x[ 256]_(52=52.0000Hz)
   rng(0):  400 x 256_58.484p 16.200 [fract] scale(1, 1, 2) diff(0.00, 0.00, -0.7581) ratio(0.781, 0.533)

SwitchRes: [ 448]x[ 240]_(60=60.0000Hz)
   rng(0):  448 x 240_60.000p 15.660 [fract] scale(1, 1, 2) diff(0.00, 0.00, 0.0000) ratio(0.875, 0.500)

SwitchRes: [ 512]x[ 240]_(60=60.0000Hz)
   rng(0):  512 x 240_60.000p 15.660 [fract] scale(1, 1, 2) diff(0.00, 0.00, 0.0000) ratio(1.000, 0.500)

SwitchRes: [ 512]x[ 288]_(51=51.0000Hz)
   rng(0):  512 x 288_52.427p 16.200 [fract] scale(1, 1, 2) diff(0.00, 0.00, -3.7864) ratio(1.000, 0.600)

SwitchRes: [ 512]x[ 448]_(60=60.0000Hz)
   rng(0):  512 x 448_60.000i 15.690 [fract] scale(1, 1, 2) diff(0.00, 0.00, 0.0000) ratio(1.000, 0.933)

SwitchRes: [ 512]x[ 512]_(58=58.0000Hz)
   rng(0):  512 x 512_58.484i 16.229 [integ] scale(1, 1, 2) diff(0.00, 3.25, -0.7581) ratio(1.000, 1.067)

SwitchRes: [ 632]x[ 264]_(57=57.0000Hz)
   rng(0):  632 x 264_56.842p 16.200 [fract] scale(1, 1, 2) diff(0.00, 0.00, -1.5789) ratio(1.234, 0.550)

SwitchRes: [ 640]x[ 240]_(60=60.0000Hz)
   rng(0):  640 x 240_60.000p 15.660 [fract] scale(1, 1, 2) diff(0.00, 0.00, 0.0000) ratio(1.250, 0.500)

SwitchRes: [ 640]x[ 288]_(51=51.0000Hz)
   rng(0):  640 x 288_52.427p 16.200 [fract] scale(1, 1, 2) diff(0.00, 0.00, -3.7864) ratio(1.250, 0.600)

SwitchRes: [ 640]x[ 480]_(60=60.0000Hz)
   rng(0):  640 x 480_60.000i 15.690 [fract] scale(1, 1, 2) diff(20.00, 0.00, 0.0000) ratio(1.250, 1.000)

SwitchRes: [ 648]x[ 288]_(51=51.0000Hz)
   rng(0):  648 x 288_52.427p 16.200 [fract] scale(1, 1, 2) diff(0.00, 0.00, -3.7864) ratio(1.266, 0.600)

SwitchRes: [ 720]x[ 480]_(60=60.0000Hz)
   rng(0):  720 x 480_60.000i 15.690 [fract] scale(1, 1, 2) diff(28.89, 0.00, 0.0000) ratio(1.406, 1.000)

SwitchRes: [ 800]x[ 600]_(52=52.0000Hz)
   rng(0):  out of range

SwitchRes: [xenophob] (1) horizontal (512x480@30.00)->(512x512@58.48)
   rng(0):  512 x 512_58.484i 16.229 [integ] scale(1, 1, 2) diff(0.00, 3.25, -0.7581) ratio(1.000, 1.067)
SwitchRes: Modeline "512x512_58 16.23KHz 58.48Hz" 10.91 512 536 584 672 512 515 521 555 interlace  -hsync -vsync
SwitchRes: Setting option -rotate
SwitchRes: Setting option -noror
SwitchRes: Setting option -autoror
SwitchRes: Setting option -norol
SwitchRes: Setting option -noautorol
SwitchRes: Setting option -video ddraw
SwitchRes: Setting option -noblack_frame_insertion
SwitchRes: Setting option -multithreading
SwitchRes: Setting option -notriplebuffer
SwitchRes: Setting option -syncrefresh
SwitchRes: Setting option -waitvsync
SwitchRes: Setting option -keepaspect
SwitchRes: Setting option -nohwstretch
SwitchRes: Setting option -nofilter
SwitchRes: Setting option -prescale 1
Video: Monitor 0000000000010001 = "\\.\DISPLAY1" (primary)
DirectDraw: Using DirectDraw 7
Blitting thread created
winwindow_video_window_create: blit_lock = TRUE
Blitting thread started
window_proc: WM_NCACTIVATE
DirectDraw: Configuring device Ultimarc ArcadeVGA3000.
DirectDraw: primary surface created: 512x512x32 (R=00FF0000 G=0000FF00 B=000000FF)
DirectDraw: New blit size = 512x480
DirectDraw: blit surface created: 512x480x32 (R=00FF0000 G=0000FF00 B=000000FF)
blit_unlock = TRUE
window_proc: WM_PAINT
blit_lock = FALSE
window_proc: WM_PAINT:END
stream_buffer_size = 76800
DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channels
RawInput: APIs detected
Input: Adding Mouse #0: HID-compliant mouse
Input: Adding Gun #0: HID-compliant mouse
Input: Adding Mouse #1: HID-compliant mouse
Input: Adding Gun #1: HID-compliant mouse
Input: Adding Mouse #2: HID-compliant mouse
Input: Adding Gun #2: HID-compliant mouse
Input: Adding Mouse #3: HID-compliant mouse
Input: Adding Gun #3: HID-compliant mouse
Input: Adding Mouse #4: HID-compliant mouse
Input: Adding Gun #4: HID-compliant mouse
Input: Adding Mouse #5: HID-compliant mouse
Input: Adding Gun #5: HID-compliant mouse
Input: Adding Kbd #0: Standard PS/2 Keyboard
DirectInput: Using DirectInput 7
Input: Adding Joy #0: Ultimarc Ultra-Stik Player 1
Input: Adding Joy #1: Ultimarc Ultra-Stik Player 2
Input: Adding Joy #2: ATRAK Device #1
Input: Adding Joy #3: ATRAK Device #2
Region ':maincpu' created
Region ':sg:cpu' created
Region ':gfx1' created
Region ':gfx2' created
Region ':cpu_plds' created
Region ':snd_pld' created
Starting Xenophobe ':'
Optional device 'cvsd' not found
Optional device 'tcs' not found
Optional device 'csd' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
  (missing dependencies; rescheduling)
Starting M68000 ':maincpu'
Starting Video Screen ':screen'
  (missing dependencies; rescheduling)
Starting gfxdecode ':gfxdecode'
Starting palette ':palette'
Starting Speaker ':mono'
  (missing dependencies; rescheduling)
Starting Midway Sounds Good Sound Board ':sg'
  (missing dependencies; rescheduling)
Starting M68000 ':sg:cpu'
Starting 6821 PIA ':sg:pia'
Starting DAC ':sg:dac'
Starting Xenophobe ':'
Optional device 'cvsd' not found
Optional device 'tcs' not found
Optional device 'csd' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
  (missing dependencies; rescheduling)
Starting Video Screen ':screen'
Starting Speaker ':mono'
  (missing dependencies; rescheduling)
Starting Midway Sounds Good Sound Board ':sg'
Starting Xenophobe ':'
Optional device 'cvsd' not found
Optional device 'tcs' not found
Optional device 'csd' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
  (missing dependencies; rescheduling)
Starting Speaker ':mono'
Starting Xenophobe ':'
Optional device 'cvsd' not found
Optional device 'tcs' not found
Optional device 'csd' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
Average speed: 194.24% (9 seconds)
Sound: buffer overflows=232 underflows=0
window_proc: WM_NCACTIVATE
blit_lock = TRUE
window_proc: WM_DESTROY
blit_lock = TRUE
Blitting thread destroyed

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #169 on: January 06, 2015, 06:22:12 am »
You need to enable -multithreading and leave the other options alone (-triplebuffer will be selected automatically). Anyway maybe forcing a 60 Hz mode will help. Try setting:

resolution 640x480
cleanstretch 2
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

vindic8r

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 72
    • MOTUMAME: A Masters of the Universe Arcade Cabinet
Re: Games with ISSUES: report here!
« Reply #170 on: January 09, 2015, 12:49:25 am »
Interesting. It now runs at 200% speed. I confirmed that frameskip is not on.

Log:
Code: [Select]
SwitchRes: Monitor range 15625.00-16200.00,49.50-65.00,2.000,4.700,8.000,0.064,0.192,1.024,0,0,192,288,448,576
SwitchRes: Monitor: arcade_15 Orientation: horizontal Modeline generation: enabled
SwitchRes: \\.\DISPLAY1: Ultimarc ArcadeVGA3000.
SwitchRes: DeviceKey: System\CurrentControlSet\Control\Video\{CED22CC3-F9AC-4D18-9214-5397F8623444}\0000
Switchres: Searching for custom video modes...
Switchres: [  1]  240x 240 @ 60: system mode
Switchres: [  2]  256x 240 @ 61: system mode
Switchres: [  3]  256x 256 @ 60: system mode
Switchres: [  4]  256x 264 @ 58: system mode
Switchres: [  5]  288x 240 @ 61: system mode
Switchres: [  6]  296x 240 @ 60: system mode
Switchres: [  7]  304x 240 @ 61: system mode
Switchres: [  8]  320x 200 @ 60: system mode
Switchres: [  9]  320x 240 @ 60: system mode
Switchres: [ 10]  320x 256 @ 60: system mode
Switchres: [ 11]  336x 240 @ 60: system mode
Switchres: [ 12]  352x 256 @ 60: system mode
Switchres: [ 13]  352x 264 @ 57: system mode
Switchres: [ 14]  352x 288 @ 51: system mode
Switchres: [ 15]  368x 240 @ 60: system mode
Switchres: [ 16]  384x 288 @ 51: system mode
Switchres: [ 17]  392x 240 @ 60: system mode
Switchres: [ 18]  400x 256 @ 52: system mode
Switchres: [ 19]  448x 240 @ 60: system mode
Switchres: [ 20]  512x 240 @ 60: system mode
Switchres: [ 21]  512x 288 @ 51: system mode
Switchres: [ 22]  512x 448 @ 60: system mode
Switchres: [ 23]  512x 512 @ 58: system mode
Switchres: [ 24]  632x 264 @ 57: system mode
Switchres: [ 25]  640x 240 @ 60: system mode
Switchres: [ 26]  640x 288 @ 51: system mode
Switchres: [ 27]  640x 480 @ 60: system mode
Switchres: [ 28]  648x 288 @ 51: system mode
Switchres: [ 29]  720x 480 @ 60*: system mode
Switchres: [ 30]  800x 600 @ 52: system mode
SwitchRes: Found 0 custom of 30 active video modes
SwitchRes: -resolution was forced as 640x480

SwitchRes: Entering switchres_modeline_setup
SwitchRes: v0.015a:[xenophob] Calculating best video mode for 512x480@30.000000 orientation: normal

SwitchRes: [ 240]x[ 240]_(60=60.0000Hz) - locked

SwitchRes: [ 256]x[ 240]_(61=61.0000Hz) - locked

SwitchRes: [ 256]x[ 256]_(60=60.0000Hz) - locked

SwitchRes: [ 256]x[ 264]_(58=58.0000Hz) - locked

SwitchRes: [ 288]x[ 240]_(61=61.0000Hz) - locked

SwitchRes: [ 296]x[ 240]_(60=60.0000Hz) - locked

SwitchRes: [ 304]x[ 240]_(61=61.0000Hz) - locked

SwitchRes: [ 320]x[ 200]_(60=60.0000Hz) - locked

SwitchRes: [ 320]x[ 240]_(60=60.0000Hz) - locked

SwitchRes: [ 320]x[ 256]_(60=60.0000Hz) - locked

SwitchRes: [ 336]x[ 240]_(60=60.0000Hz) - locked

SwitchRes: [ 352]x[ 256]_(60=60.0000Hz) - locked

SwitchRes: [ 352]x[ 264]_(57=57.0000Hz) - locked

SwitchRes: [ 352]x[ 288]_(51=51.0000Hz) - locked

SwitchRes: [ 368]x[ 240]_(60=60.0000Hz) - locked

SwitchRes: [ 384]x[ 288]_(51=51.0000Hz) - locked

SwitchRes: [ 392]x[ 240]_(60=60.0000Hz) - locked

SwitchRes: [ 400]x[ 256]_(52=52.0000Hz) - locked

SwitchRes: [ 448]x[ 240]_(60=60.0000Hz) - locked

SwitchRes: [ 512]x[ 240]_(60=60.0000Hz) - locked

SwitchRes: [ 512]x[ 288]_(51=51.0000Hz) - locked

SwitchRes: [ 512]x[ 448]_(60=60.0000Hz) - locked

SwitchRes: [ 512]x[ 512]_(58=58.0000Hz) - locked

SwitchRes: [ 632]x[ 264]_(57=57.0000Hz) - locked

SwitchRes: [ 640]x[ 240]_(60=60.0000Hz) - locked

SwitchRes: [ 640]x[ 288]_(51=51.0000Hz) - locked

SwitchRes: [ 640]x[ 480]_(60=60.0000Hz)
   rng(0):  640 x 480_60.000i 15.690 [fract] scale(1, 1, 2) diff(20.00, 0.00, 0.0000) ratio(1.250, 1.000)

SwitchRes: [ 648]x[ 288]_(51=51.0000Hz) - locked

SwitchRes: [ 720]x[ 480]_(60=60.0000Hz) - locked

SwitchRes: [ 800]x[ 600]_(52=52.0000Hz) - locked

SwitchRes: [xenophob] (1) horizontal (512x480@30.00)->(640x480@60.00)
   rng(0):  640 x 480_60.000i 15.690 [fract] scale(1, 1, 2) diff(20.00, 0.00, 0.0000) ratio(1.250, 1.000)
SwitchRes: Modeline "640x480_60 15.69KHz 60.00Hz" 13.05 640 664 728 832 480 483 489 523 interlace  -hsync -vsync
SwitchRes: Setting option -rotate
SwitchRes: Setting option -noror
SwitchRes: Setting option -autoror
SwitchRes: Setting option -norol
SwitchRes: Setting option -noautorol
SwitchRes: Setting option -video ddraw
SwitchRes: Setting option -noblack_frame_insertion
SwitchRes: Setting option -multithreading
SwitchRes: Setting option -notriplebuffer
SwitchRes: Setting option -syncrefresh
SwitchRes: Setting option -waitvsync
SwitchRes: Setting option -keepaspect
SwitchRes: Setting option -nohwstretch
SwitchRes: Setting option -nofilter
SwitchRes: Setting option -prescale 1
Video: Monitor 0000000000010001 = "\\.\DISPLAY1" (primary)
DirectDraw: Using DirectDraw 7
Blitting thread created
winwindow_video_window_create: blit_lock = TRUE
Blitting thread started
window_proc: WM_NCACTIVATE
DirectDraw: Configuring device Ultimarc ArcadeVGA3000.
DirectDraw: primary surface created: 640x480x32 (R=00FF0000 G=0000FF00 B=000000FF)
DirectDraw: New blit size = 512x480
DirectDraw: blit surface created: 512x480x32 (R=00FF0000 G=0000FF00 B=000000FF)
blit_unlock = TRUE
window_proc: WM_PAINT
blit_lock = FALSE
window_proc: WM_PAINT:END
stream_buffer_size = 18432
DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channels
RawInput: APIs detected
Input: Adding Mouse #0: HID-compliant mouse
Input: Adding Gun #0: HID-compliant mouse
Input: Adding Mouse #1: HID-compliant mouse
Input: Adding Gun #1: HID-compliant mouse
Input: Adding Mouse #2: HID-compliant mouse
Input: Adding Gun #2: HID-compliant mouse
Input: Adding Mouse #3: HID-compliant mouse
Input: Adding Gun #3: HID-compliant mouse
Input: Adding Mouse #4: HID-compliant mouse
Input: Adding Gun #4: HID-compliant mouse
Input: Adding Mouse #5: HID-compliant mouse
Input: Adding Gun #5: HID-compliant mouse
Input: Adding Kbd #0: Standard PS/2 Keyboard
DirectInput: Using DirectInput 7
Input: Adding Joy #0: Ultimarc Ultra-Stik Player 1
Input: Adding Joy #1: Ultimarc Ultra-Stik Player 2
Input: Adding Joy #2: ATRAK Device #1
Input: Adding Joy #3: ATRAK Device #2
Region ':maincpu' created
Region ':sg:cpu' created
Region ':gfx1' created
Region ':gfx2' created
Region ':cpu_plds' created
Region ':snd_pld' created
Starting Xenophobe ':'
Optional device 'cvsd' not found
Optional device 'tcs' not found
Optional device 'csd' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
  (missing dependencies; rescheduling)
Starting M68000 ':maincpu'
Starting Video Screen ':screen'
  (missing dependencies; rescheduling)
Starting gfxdecode ':gfxdecode'
Starting palette ':palette'
Starting Speaker ':mono'
  (missing dependencies; rescheduling)
Starting Midway Sounds Good Sound Board ':sg'
  (missing dependencies; rescheduling)
Starting M68000 ':sg:cpu'
Starting 6821 PIA ':sg:pia'
Starting DAC ':sg:dac'
Starting Xenophobe ':'
Optional device 'cvsd' not found
Optional device 'tcs' not found
Optional device 'csd' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
  (missing dependencies; rescheduling)
Starting Video Screen ':screen'
Starting Speaker ':mono'
  (missing dependencies; rescheduling)
Starting Midway Sounds Good Sound Board ':sg'
Starting Xenophobe ':'
Optional device 'cvsd' not found
Optional device 'tcs' not found
Optional device 'csd' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
  (missing dependencies; rescheduling)
Starting Speaker ':mono'
Starting Xenophobe ':'
Optional device 'cvsd' not found
Optional device 'tcs' not found
Optional device 'csd' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
Average speed: 200.51% (17 seconds)
Sound: buffer overflows=452 underflows=0
window_proc: WM_NCACTIVATE
blit_lock = TRUE
window_proc: WM_DESTROY
blit_lock = TRUE
Blitting thread destroyed

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #171 on: January 09, 2015, 07:12:32 am »
Interesting. It now runs at 200% speed. I confirmed that frameskip is not on.

You must have -syncrefresh enabled somewhere, probably in mame.ini. That is preventing -triplebuffer from being used.
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

vindic8r

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 72
    • MOTUMAME: A Masters of the Universe Arcade Cabinet
Re: Games with ISSUES: report here!
« Reply #172 on: January 10, 2015, 04:16:38 pm »
You must have -syncrefresh enabled somewhere, probably in mame.ini. That is preventing -triplebuffer from being used.

Nope. Checked mame.ini and syncrefresh = 0. Here's my mame.ini, for reference:
Code: [Select]
#
# CORE CONFIGURATION OPTIONS
#
readconfig                1
writeconfig               0

#
# CORE SEARCH PATH OPTIONS
#
rompath                   roms
hashpath                  hash
samplepath                samples
artpath                   artwork
ctrlrpath                 ctrlr
inipath                   ini
fontpath                  .
cheatpath                 cheat
crosshairpath             crosshair

#
# CORE OUTPUT DIRECTORY OPTIONS
#
cfg_directory             cfg
nvram_directory           nvram
memcard_directory         memcard
input_directory           inp
state_directory           sta
snapshot_directory        snap
diff_directory            diff
comment_directory         comments

#
# CORE OUTPUT DIRECTORY OPTIONS
#
hiscore_directory         hi

#
# CORE STATE/PLAYBACK OPTIONS
#
state                     
autosave                  1
playback                 
record                   
mngwrite                 
aviwrite                 
wavwrite                 
snapname                  %g/%i
snapsize                  auto
snapview                  internal
statename                 %g
burnin                    0

#
# CORE PERFORMANCE OPTIONS
#
autoframeskip             0
frameskip                 0
seconds_to_run            0
throttle                  1
syncrefresh               0
sleep                     1
speed                     1.0
refreshspeed              0

#
# CORE ROTATION OPTIONS
#
rotate                    1
ror                       0
rol                       0
autoror                   0
autorol                   0
flipx                     0
flipy                     0

#
# CORE ARTWORK OPTIONS
#
artwork_crop              1
use_backdrops             1
use_overlays              1
use_bezels                0
use_cpanels               1
use_marquees              1

#
# CORE SCREEN OPTIONS
#
brightness                1.0
contrast                  1.0
gamma                     1.0
pause_brightness          0.65
effect                    none

#
# CORE VECTOR OPTIONS
#
antialias                 1
beam                      1.0
flicker                   0

#
# CORE SOUND OPTIONS
#
sound                     1
samplerate                48000
samples                   1
volume                    0

#
# CORE INPUT OPTIONS
#
coin_lockout              1
ctrlr                     
mouse                     1
joystick                  1
lightgun                  1
multikeyboard             0
multimouse                1
steadykey                 0
ui_active                 0
offscreen_reload          1
joystick_map              auto
joystick_deadzone         0.3
joystick_saturation       0.85
natural                   0
joystick_contradictory    0
coin_impulse              0

#
# CORE INPUT AUTOMATIC ENABLE OPTIONS
#
paddle_device             mouse
adstick_device            keyboard
pedal_device              keyboard
dial_device               mouse
trackball_device          mouse
lightgun_device           none
positional_device         keyboard
mouse_device              mouse

#
# CORE DEBUGGING OPTIONS
#
log                       0
verbose                   0
update_in_pause           0
debug                     0
debugscript               
debug_internal            0

#
# CORE MISC OPTIONS
#
bios                     
cheat                     0
skip_gameinfo             0
uifont                      
ramsize                   
confirm_quit              0
ui_mouse                  0
autoboot_command         
autoboot_delay            2
autoboot_script           

#
# CORE MKChamp OPTIONS
#
disable_hiscore_patch     0
disable_nagscreen_patch   0
disable_loading_patch     0

#
# CORE SWITCHRES OPTIONS
#
modeline                  1
monitor                   arcade_15
orientation               horizontal
connector                 auto
interlace                 1
doublescan                0
cleanstretch              0
changeres                 1
powerstrip                0
lock_system_modes         0
lock_unsupported_modes    1
refresh_dont_care         1
dotclock_min              0
sync_refresh_tolerance    2.0
frame_delay               1
lcd_range                 auto
crt_range0                auto
crt_range1                auto
crt_range2                auto
crt_range3                auto
crt_range4                auto
crt_range5                auto
crt_range6                auto
crt_range7                auto
crt_range8                auto
crt_range9                auto

#
# WINDOWS DEBUGGING OPTIONS
#
oslog                     0
watchdog                  0
debugger_font             "Lucida Console"
debugger_font_size        9

#
# WINDOWS PERFORMANCE OPTIONS
#
priority                  0
multithreading            1
numprocessors             auto
profile                   0
bench                     0

#
# WINDOWS VIDEO OPTIONS
#
video                     d3d
numscreens                1
window                    0
maximize                  1
keepaspect                0
prescale                  1
waitvsync                 0
menu                      1


#
# DIRECTDRAW-SPECIFIC OPTIONS
#
hwstretch                 0

#
# DIRECT3D-SPECIFIC OPTIONS
#
filter                    1

#
# DIRECT3D POST-PROCESSING OPTIONS
#
hlsl_enable               0
hlslpath                  hlsl
hlsl_ini_read             0
hlsl_ini_write            0
hlslini                   %g
hlsl_prescale_x           0
hlsl_prescale_y           0
hlsl_preset               -1
hlsl_write               
hlsl_snap_width           2048
hlsl_snap_height          1536
shadow_mask_alpha         0.0
shadow_mask_texture       aperture.png
shadow_mask_x_count       320
shadow_mask_y_count       240
shadow_mask_usize         0.09375
shadow_mask_vsize         0.109375
curvature                 0.0
pincushion                0.0
scanline_alpha            0.0
scanline_size             1.0
scanline_height           0.7
scanline_bright_scale     1.0
scanline_bright_offset    0.0
scanline_jitter           0.0
defocus                   0.0,0.0
converge_x                0.0,0.0,0.0
converge_y                0.0,0.0,0.0
radial_converge_x         0.0,0.0,0.0
radial_converge_y         0.0,0.0,0.0
red_ratio                 1.0,0.0,0.0
grn_ratio                 0.0,1.0,0.0
blu_ratio                 0.0,0.0,1.0
saturation                1.0
offset                    0.0,0.0,0.0
scale                     1.0,1.0,1.0
power                     1.0,1.0,1.0
floor                     0.0,0.0,0.0
phosphor_life             0.0,0.0,0.0

#
# NTSC POST-PROCESSING OPTIONS
#
yiq_enable                0
yiq_cc                    3.59754545
yiq_a                     0.5
yiq_b                     0.5
yiq_o                     0.0
yiq_p                     1.0
yiq_n                     1.0
yiq_y                     6.0
yiq_i                     1.2
yiq_q                     0.6
yiq_scan_time             52.6
yiq_phase_count           2

#
# VECTOR POST-PROCESSING OPTIONS
#
vector_length_scale       0.8
vector_length_ratio       500.0

#
# BLOOM POST-PROCESSING OPTIONS
#
vector_bloom_scale        0.3
raster_bloom_scale        0.225
bloom_lvl0_weight         1.0
bloom_lvl1_weight         0.21
bloom_lvl2_weight         0.19
bloom_lvl3_weight         0.17
bloom_lvl4_weight         0.15
bloom_lvl5_weight         0.14
bloom_lvl6_weight         0.13
bloom_lvl7_weight         0.12
bloom_lvl8_weight         0.11
bloom_lvl9_weight         0.10
bloom_lvl10_weight        0.09

#
# PER-WINDOW VIDEO OPTIONS
#
screen                    auto
aspect                    auto
resolution                auto
view                      auto
screen0                   auto
aspect0                   auto
resolution0               auto
view0                     auto
screen1                   auto
aspect1                   auto
resolution1               auto
view1                     auto
screen2                   auto
aspect2                   auto
resolution2               auto
view2                     auto
screen3                   auto
aspect3                   auto
resolution3               auto
view3                     auto

#
# FULL SCREEN OPTIONS
#
triplebuffer              1
switchres                 1
full_screen_brightness    1.0
full_screen_contrast      1.0
full_screen_gamma         1.0

#
# WINDOWS SOUND OPTIONS
#
audio_latency             1

#
# INPUT DEVICE OPTIONS
#
dual_lightgun             0

I stupidly was forcing triplebuffer off in my xenophob.ini. I removed that line now, and the speed is correct now at 100%. However, the audio is still choppy. Just to cover bases, here's my latest log file:

Code: [Select]
Parsing xenophob.ini
Optional device 'tcs' not found
Optional device 'sg' not found
Optional device 'csd' not found
Optional device 'tcs' not found
Optional device 'sg' not found
Optional device 'csd' not found
Optional device 'tcs' not found
Optional device 'sg' not found
Optional device 'csd' not found
Optional device 'cvsd' not found
Optional device 'tcs' not found
Optional device 'csd' not found
Optional device 'cvsd' not found
Optional device 'tcs' not found
Optional device 'csd' not found
Optional device 'tcs' not found
Optional device 'sg' not found
Optional device 'csd' not found
Optional device 'tcs' not found
Optional device 'sg' not found
Optional device 'csd' not found
Optional device 'tcs' not found
Optional device 'sg' not found
Optional device 'csd' not found
Optional device 'cvsd' not found
Optional device 'csd' not found
Optional device 'cvsd' not found
Optional device 'csd' not found
Optional device 'tcs' not found
Optional device 'sg' not found
Optional device 'csd' not found
Optional device 'cvsd' not found
Optional device 'tcs' not found
Optional device 'csd' not found
Optional device 'cvsd' not found
Optional device 'tcs' not found
Optional device 'sg' not found
SwitchRes: Monitor range 15625.00-16200.00,49.50-65.00,2.000,4.700,8.000,0.064,0.192,1.024,0,0,192,288,448,576
SwitchRes: Monitor: arcade_15 Orientation: horizontal Modeline generation: enabled
SwitchRes: \\.\DISPLAY1: Ultimarc ArcadeVGA3000.
SwitchRes: DeviceKey: System\CurrentControlSet\Control\Video\{CED22CC3-F9AC-4D18-9214-5397F8623444}\0000
Switchres: Searching for custom video modes...
Switchres: [  1]  240x 240 @ 60: system mode
Switchres: [  2]  256x 240 @ 61: system mode
Switchres: [  3]  256x 256 @ 60: system mode
Switchres: [  4]  256x 264 @ 58: system mode
Switchres: [  5]  288x 240 @ 61: system mode
Switchres: [  6]  296x 240 @ 60: system mode
Switchres: [  7]  304x 240 @ 61: system mode
Switchres: [  8]  320x 200 @ 60: system mode
Switchres: [  9]  320x 240 @ 60: system mode
Switchres: [ 10]  320x 256 @ 60: system mode
Switchres: [ 11]  336x 240 @ 60: system mode
Switchres: [ 12]  352x 256 @ 60: system mode
Switchres: [ 13]  352x 264 @ 57: system mode
Switchres: [ 14]  352x 288 @ 51: system mode
Switchres: [ 15]  368x 240 @ 60: system mode
Switchres: [ 16]  384x 288 @ 51: system mode
Switchres: [ 17]  392x 240 @ 60: system mode
Switchres: [ 18]  400x 256 @ 52: system mode
Switchres: [ 19]  448x 240 @ 60: system mode
Switchres: [ 20]  512x 240 @ 60: system mode
Switchres: [ 21]  512x 288 @ 51: system mode
Switchres: [ 22]  512x 448 @ 60: system mode
Switchres: [ 23]  512x 512 @ 58: system mode
Switchres: [ 24]  632x 264 @ 57: system mode
Switchres: [ 25]  640x 240 @ 60: system mode
Switchres: [ 26]  640x 288 @ 51: system mode
Switchres: [ 27]  640x 480 @ 60: system mode
Switchres: [ 28]  648x 288 @ 51: system mode
Switchres: [ 29]  720x 480 @ 60*: system mode
Switchres: [ 30]  800x 600 @ 52: system mode
SwitchRes: Found 0 custom of 30 active video modes
SwitchRes: -resolution was forced as 640x480

SwitchRes: Entering switchres_modeline_setup
SwitchRes: v0.015a:[xenophob] Calculating best video mode for 512x480@30.000000 orientation: normal

SwitchRes: [ 240]x[ 240]_(60=60.0000Hz) - locked

SwitchRes: [ 256]x[ 240]_(61=61.0000Hz) - locked

SwitchRes: [ 256]x[ 256]_(60=60.0000Hz) - locked

SwitchRes: [ 256]x[ 264]_(58=58.0000Hz) - locked

SwitchRes: [ 288]x[ 240]_(61=61.0000Hz) - locked

SwitchRes: [ 296]x[ 240]_(60=60.0000Hz) - locked

SwitchRes: [ 304]x[ 240]_(61=61.0000Hz) - locked

SwitchRes: [ 320]x[ 200]_(60=60.0000Hz) - locked

SwitchRes: [ 320]x[ 240]_(60=60.0000Hz) - locked

SwitchRes: [ 320]x[ 256]_(60=60.0000Hz) - locked

SwitchRes: [ 336]x[ 240]_(60=60.0000Hz) - locked

SwitchRes: [ 352]x[ 256]_(60=60.0000Hz) - locked

SwitchRes: [ 352]x[ 264]_(57=57.0000Hz) - locked

SwitchRes: [ 352]x[ 288]_(51=51.0000Hz) - locked

SwitchRes: [ 368]x[ 240]_(60=60.0000Hz) - locked

SwitchRes: [ 384]x[ 288]_(51=51.0000Hz) - locked

SwitchRes: [ 392]x[ 240]_(60=60.0000Hz) - locked

SwitchRes: [ 400]x[ 256]_(52=52.0000Hz) - locked

SwitchRes: [ 448]x[ 240]_(60=60.0000Hz) - locked

SwitchRes: [ 512]x[ 240]_(60=60.0000Hz) - locked

SwitchRes: [ 512]x[ 288]_(51=51.0000Hz) - locked

SwitchRes: [ 512]x[ 448]_(60=60.0000Hz) - locked

SwitchRes: [ 512]x[ 512]_(58=58.0000Hz) - locked

SwitchRes: [ 632]x[ 264]_(57=57.0000Hz) - locked

SwitchRes: [ 640]x[ 240]_(60=60.0000Hz) - locked

SwitchRes: [ 640]x[ 288]_(51=51.0000Hz) - locked

SwitchRes: [ 640]x[ 480]_(60=60.0000Hz)
   rng(0):  640 x 480_60.000i 15.690 [fract] scale(1, 1, 2) diff(20.00, 0.00, 0.0000) ratio(1.250, 1.000)

SwitchRes: [ 648]x[ 288]_(51=51.0000Hz) - locked

SwitchRes: [ 720]x[ 480]_(60=60.0000Hz) - locked

SwitchRes: [ 800]x[ 600]_(52=52.0000Hz) - locked

SwitchRes: [xenophob] (1) horizontal (512x480@30.00)->(640x480@60.00)
   rng(0):  640 x 480_60.000i 15.690 [fract] scale(1, 1, 2) diff(20.00, 0.00, 0.0000) ratio(1.250, 1.000)
SwitchRes: Modeline "640x480_60 15.69KHz 60.00Hz" 13.05 640 664 728 832 480 483 489 523 interlace  -hsync -vsync
SwitchRes: Setting option -rotate
SwitchRes: Setting option -noror
SwitchRes: Setting option -autoror
SwitchRes: Setting option -norol
SwitchRes: Setting option -noautorol
SwitchRes: Setting option -video ddraw
SwitchRes: Setting option -noblack_frame_insertion
SwitchRes: Setting option -multithreading
SwitchRes: Setting option -triplebuffer
SwitchRes: Setting option -nosyncrefresh
SwitchRes: Setting option -nowaitvsync
SwitchRes: Setting option -keepaspect
SwitchRes: Setting option -nohwstretch
SwitchRes: Setting option -nofilter
SwitchRes: Setting option -prescale 1
Video: Monitor 0000000000010001 = "\\.\DISPLAY1" (primary)
DirectDraw: Using DirectDraw 7
Blitting thread created
winwindow_video_window_create: blit_lock = TRUE
Blitting thread started
window_proc: WM_NCACTIVATE
DirectDraw: Configuring device Ultimarc ArcadeVGA3000.
DirectDraw: primary surface created: 640x480x32 (R=00FF0000 G=0000FF00 B=000000FF)
DirectDraw: New blit size = 512x480
DirectDraw: blit surface created: 512x480x32 (R=00FF0000 G=0000FF00 B=000000FF)
blit_unlock = TRUE
window_proc: WM_PAINT
stream_buffer_size = 18432
DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channels
blit_lock = FALSE
window_proc: WM_PAINT:END
RawInput: APIs detected
Input: Adding Mouse #0: HID-compliant mouse
Input: Adding Gun #0: HID-compliant mouse
Input: Adding Mouse #1: HID-compliant mouse
Input: Adding Gun #1: HID-compliant mouse
Input: Adding Mouse #2: HID-compliant mouse
Input: Adding Gun #2: HID-compliant mouse
Input: Adding Kbd #0: Standard PS/2 Keyboard
Input: Adding Mouse #3: HID-compliant mouse
Input: Adding Gun #3: HID-compliant mouse
Input: Adding Mouse #4: HID-compliant mouse
Input: Adding Gun #4: HID-compliant mouse
Input: Adding Mouse #5: HID-compliant mouse
Input: Adding Gun #5: HID-compliant mouse
DirectInput: Using DirectInput 7
Input: Adding Joy #0: Ultimarc Ultra-Stik Player 1
Input: Adding Joy #1: Ultimarc Ultra-Stik Player 2
Input: Adding Joy #2: ATRAK Device #1
Input: Adding Joy #3: ATRAK Device #2
Region ':maincpu' created
Region ':sg:cpu' created
Region ':gfx1' created
Region ':gfx2' created
Region ':cpu_plds' created
Region ':snd_pld' created
Starting Xenophobe ':'
Optional device 'cvsd' not found
Optional device 'tcs' not found
Optional device 'csd' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
  (missing dependencies; rescheduling)
Starting M68000 ':maincpu'
Starting Video Screen ':screen'
  (missing dependencies; rescheduling)
Starting gfxdecode ':gfxdecode'
Starting palette ':palette'
Starting Speaker ':mono'
  (missing dependencies; rescheduling)
Starting Midway Sounds Good Sound Board ':sg'
  (missing dependencies; rescheduling)
Starting M68000 ':sg:cpu'
Starting 6821 PIA ':sg:pia'
Starting DAC ':sg:dac'
Starting Xenophobe ':'
Optional device 'cvsd' not found
Optional device 'tcs' not found
Optional device 'csd' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
  (missing dependencies; rescheduling)
Starting Video Screen ':screen'
Starting Speaker ':mono'
  (missing dependencies; rescheduling)
Starting Midway Sounds Good Sound Board ':sg'
Starting Xenophobe ':'
Optional device 'cvsd' not found
Optional device 'tcs' not found
Optional device 'csd' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
  (missing dependencies; rescheduling)
Starting Speaker ':mono'
Starting Xenophobe ':'
Optional device 'cvsd' not found
Optional device 'tcs' not found
Optional device 'csd' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram2' not found
Optional shared pointer 'paletteram' not found
Average speed: 100.00% (132 seconds)
Sound: buffer overflows=2 underflows=0
window_proc: WM_NCACTIVATE
blit_lock = TRUE
window_proc: WM_DESTROY
blit_lock = TRUE
Blitting thread destroyed

And xenophob.ini:
Code: [Select]
## xenophob ##

screen0 \\.\DISPLAY1
audio_latency 0
resolution 640x480
cleanstretch 2
hwstretch 0
bezel 0
backdrop 0

Any other ideas?

adder

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 611
  • Location: Easy St.
Re: Games with ISSUES: report here!
« Reply #173 on: January 10, 2015, 04:24:39 pm »
audio_latency 0         ?

shouldn't that be audio_latency 2       :)
typed using my...

vindic8r

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 72
    • MOTUMAME: A Masters of the Universe Arcade Cabinet
Re: Games with ISSUES: report here!
« Reply #174 on: January 10, 2015, 05:57:32 pm »
Good catch. Still no dice.

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #175 on: January 10, 2015, 06:10:58 pm »
Disable -frame_delay.
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

vindic8r

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 72
    • MOTUMAME: A Masters of the Universe Arcade Cabinet
Re: Games with ISSUES: report here!
« Reply #176 on: January 10, 2015, 09:09:30 pm »
Disable -frame_delay.

So this is odd. That didn't quite work. The audio got a bit better, but still clipped quite a bit. So then I loaded up up Xenophobe in mame64, (it worked just fine) played for a few minutes, then reloaded it in groovymame. This time, it was working flawlessly.  Why would that do anything? :dizzy:

Also, if I exit and reopen gmame, the game's audio is messed up again. But playing it again in mame64 and going back into gmame fixes it, but just for one load.
« Last Edit: January 10, 2015, 09:16:05 pm by vindic8r »

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #177 on: January 11, 2015, 05:59:26 am »
That's odd indeed. What's your system BTW? This is what I'd test:

- Try the latest version (GM 0.157).
- Now that you've found why -triplebuffer was not starting, try disabling -mt. I'm assuming you've kept -audio_latency 2.0.
- Always do your tests from command line.
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

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
Re: Games with ISSUES: report here!
« Reply #178 on: January 12, 2015, 04:02:27 am »
My guess: mame64 overwrites/modifies some configuration files (xenophob.ini?), so when you start it with groovymame it loads the modified configuration (and apparently these modified files work better than the previous ones).
However groovymame itself re-overwrites/modifies the same files, so the second time you launch the game, it comes back to audio problems.

Please note I'm not an expert, and this is only a guess.
Earth could be the hell of another world

vindic8r

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 72
    • MOTUMAME: A Masters of the Universe Arcade Cabinet
Re: Games with ISSUES: report here!
« Reply #179 on: January 13, 2015, 12:59:48 am »
 
My guess: mame64 overwrites/modifies some configuration files (xenophob.ini?), so when you start it with groovymame it loads the modified configuration (and apparently these modified files work better than the previous ones).
However groovymame itself re-overwrites/modifies the same files, so the second time you launch the game, it comes back to audio problems.

Please note I'm not an expert, and this is only a guess.

Good guess, Ansa. What appears to be happening is that the xenophob.cfg file is being overwritten by groovymame. This is what it looks like after I load the rom via groovymame once:
Code: [Select]
<?xml version="1.0"?>
<!-- This file is autogenerated; comments and unknown tags will be stripped -->
<mameconfig version="10">
    <system name="xenophob">
        <switchres>
            <switchres modeline=" 10.91 512 536 584 672 512 515 521 555 interlace  -hsync -vsync" />
        </switchres>
    </system>
</mameconfig>

And this is what it looks like after I load it with mame64:
Code: [Select]
<?xml version="1.0"?>
<!-- This file is autogenerated; comments and unknown tags will be stripped -->
<mameconfig version="10">
    <system name="xenophob" />
</mameconfig>

I did a test and if I delete the .cfg file and load the rom with GM, all is well.

Does this help, Calamity?

I'm a bit hesitant to upgrade to 1.57, on account of the fact that clrmamepro and I are on not so good terms. Anytime I have to upgrade my romset, it's a nightmarish exercise.  :banghead:

vindic8r

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 72
    • MOTUMAME: A Masters of the Universe Arcade Cabinet
Re: Games with ISSUES: report here!
« Reply #180 on: January 19, 2015, 01:02:43 am »
Ok, so I upgraded to 0.157.015e, keeping all existing settings the same, and the problems are nearly gone. The audio still stutters, but it only happens when the music is playing on load/exit of levels. So that is acceptable, if its as good as its going to get.

Latest log file:
Code: [Select]
SwitchRes: v0.015d, Monitor: arcade_15, Orientation: horizontal, Modeline generation: enabled
SwitchRes: Monitor range 15625.00-16200.00,49.50-65.00,2.000,4.700,8.000,0.064,0.192,1.024,0,0,192,288,448,576
SwitchRes: \\.\DISPLAY1: Ultimarc ArcadeVGA3000.
SwitchRes: DeviceKey: System\CurrentControlSet\Control\Video\{CED22CC3-F9AC-4D18-9214-5397F8623444}\0000
Switchres: Searching for custom video modes...
Switchres: [  1]  240x 240 @ 60 : system mode
Switchres: [  2]  256x 240 @ 61 : system mode
Switchres: [  3]  256x 256 @ 60 : system mode
Switchres: [  4]  256x 264 @ 58 : system mode
Switchres: [  5]  288x 240 @ 61 : system mode
Switchres: [  6]  296x 240 @ 60 : system mode
Switchres: [  7]  304x 240 @ 61 : system mode
Switchres: [  8]  320x 200 @ 60 : system mode
Switchres: [  9]  320x 240 @ 60 : system mode
Switchres: [ 10]  320x 256 @ 60 : system mode
Switchres: [ 11]  336x 240 @ 60 : system mode
Switchres: [ 12]  352x 256 @ 60 : system mode
Switchres: [ 13]  352x 264 @ 57 : system mode
Switchres: [ 14]  352x 288 @ 51 : system mode
Switchres: [ 15]  368x 240 @ 60 : system mode
Switchres: [ 16]  384x 288 @ 51 : system mode
Switchres: [ 17]  392x 240 @ 60 : system mode
Switchres: [ 18]  400x 256 @ 52 : system mode
Switchres: [ 19]  448x 240 @ 60 : system mode
Switchres: [ 20]  512x 240 @ 60 : system mode
Switchres: [ 21]  512x 288 @ 51 : system mode
Switchres: [ 22]  512x 448 @ 60 : system mode
Switchres: [ 23]  512x 512 @ 58 : system mode
Switchres: [ 24]  632x 264 @ 57 : system mode
Switchres: [ 25]  640x 240 @ 60 : system mode
Switchres: [ 26]  640x 288 @ 51 : system mode
Switchres: [ 27]  640x 480 @ 60 : system mode
Switchres: [ 28]  648x 288 @ 51 : system mode
Switchres: [ 29]  720x 480 @ 60* : system mode
Switchres: [ 30]  800x 600 @ 52 : system mode
SwitchRes: Found 0 custom of 30 active video modes

SwitchRes: Entering switchres_modeline_setup
SwitchRes: v0.015d:[xenophob] Calculating best video mode for 512x480@30.000000 orientation: normal

SwitchRes: [ 240]x[ 240]_(60=60.0000Hz)
   rng(0):  240 x 240_60.000p 15.660 [fract] scale(1, 1, 2) diff(0.00, 0.00, 0.0000) ratio(0.469, 0.500)

SwitchRes: [ 256]x[ 240]_(61=61.0000Hz)
   rng(0):  256 x 240_60.000p 15.660 [fract] scale(1, 1, 2) diff(0.00, 0.00, 0.0000) ratio(0.500, 0.500)

SwitchRes: [ 256]x[ 256]_(60=60.0000Hz)
   rng(0):  256 x 256_58.484p 16.200 [fract] scale(1, 1, 2) diff(0.00, 0.00, -0.7581) ratio(0.500, 0.533)

SwitchRes: [ 256]x[ 264]_(58=58.0000Hz)
   rng(0):  256 x 264_56.842p 16.200 [fract] scale(1, 1, 2) diff(0.00, 0.00, -1.5789) ratio(0.500, 0.550)

SwitchRes: [ 288]x[ 240]_(61=61.0000Hz)
   rng(0):  288 x 240_60.000p 15.660 [fract] scale(1, 1, 2) diff(0.00, 0.00, 0.0000) ratio(0.563, 0.500)

SwitchRes: [ 296]x[ 240]_(60=60.0000Hz)
   rng(0):  296 x 240_60.000p 15.660 [fract] scale(1, 1, 2) diff(0.00, 0.00, 0.0000) ratio(0.578, 0.500)

SwitchRes: [ 304]x[ 240]_(61=61.0000Hz)
   rng(0):  304 x 240_60.000p 15.660 [fract] scale(1, 1, 2) diff(0.00, 0.00, 0.0000) ratio(0.594, 0.500)

SwitchRes: [ 320]x[ 200]_(60=60.0000Hz)
   rng(0):  320 x 200_60.000p 15.660 [fract] scale(1, 1, 2) diff(0.00, 0.00, 0.0000) ratio(0.625, 0.417)

SwitchRes: [ 320]x[ 240]_(60=60.0000Hz)
   rng(0):  320 x 240_60.000p 15.660 [fract] scale(1, 1, 2) diff(0.00, 0.00, 0.0000) ratio(0.625, 0.500)

SwitchRes: [ 320]x[ 256]_(60=60.0000Hz)
   rng(0):  320 x 256_58.484p 16.200 [fract] scale(1, 1, 2) diff(0.00, 0.00, -0.7581) ratio(0.625, 0.533)

SwitchRes: [ 336]x[ 240]_(60=60.0000Hz)
   rng(0):  336 x 240_60.000p 15.660 [fract] scale(1, 1, 2) diff(0.00, 0.00, 0.0000) ratio(0.656, 0.500)

SwitchRes: [ 352]x[ 256]_(60=60.0000Hz)
   rng(0):  352 x 256_58.484p 16.200 [fract] scale(1, 1, 2) diff(0.00, 0.00, -0.7581) ratio(0.688, 0.533)

SwitchRes: [ 352]x[ 264]_(57=57.0000Hz)
   rng(0):  352 x 264_56.842p 16.200 [fract] scale(1, 1, 2) diff(0.00, 0.00, -1.5789) ratio(0.688, 0.550)

SwitchRes: [ 352]x[ 288]_(51=51.0000Hz)
   rng(0):  352 x 288_52.427p 16.200 [fract] scale(1, 1, 2) diff(0.00, 0.00, -3.7864) ratio(0.688, 0.600)

SwitchRes: [ 368]x[ 240]_(60=60.0000Hz)
   rng(0):  368 x 240_60.000p 15.660 [fract] scale(1, 1, 2) diff(0.00, 0.00, 0.0000) ratio(0.719, 0.500)

SwitchRes: [ 384]x[ 288]_(51=51.0000Hz)
   rng(0):  384 x 288_52.427p 16.200 [fract] scale(1, 1, 2) diff(0.00, 0.00, -3.7864) ratio(0.750, 0.600)

SwitchRes: [ 392]x[ 240]_(60=60.0000Hz)
   rng(0):  392 x 240_60.000p 15.660 [fract] scale(1, 1, 2) diff(0.00, 0.00, 0.0000) ratio(0.766, 0.500)

SwitchRes: [ 400]x[ 256]_(52=52.0000Hz)
   rng(0):  400 x 256_58.484p 16.200 [fract] scale(1, 1, 2) diff(0.00, 0.00, -0.7581) ratio(0.781, 0.533)

SwitchRes: [ 448]x[ 240]_(60=60.0000Hz)
   rng(0):  448 x 240_60.000p 15.660 [fract] scale(1, 1, 2) diff(0.00, 0.00, 0.0000) ratio(0.875, 0.500)

SwitchRes: [ 512]x[ 240]_(60=60.0000Hz)
   rng(0):  512 x 240_60.000p 15.660 [fract] scale(1, 1, 2) diff(0.00, 0.00, 0.0000) ratio(1.000, 0.500)

SwitchRes: [ 512]x[ 288]_(51=51.0000Hz)
   rng(0):  512 x 288_52.427p 16.200 [fract] scale(1, 1, 2) diff(0.00, 0.00, -3.7864) ratio(1.000, 0.600)

SwitchRes: [ 512]x[ 448]_(60=60.0000Hz)
   rng(0):  512 x 448_60.000i 15.690 [fract] scale(1, 1, 2) diff(0.00, 0.00, 0.0000) ratio(1.000, 0.933)

SwitchRes: [ 512]x[ 512]_(58=58.0000Hz)
   rng(0):  512 x 512_58.484i 16.229 [integ] scale(1, 1, 2) diff(0.00, 3.25, -0.7581) ratio(1.000, 1.067)

SwitchRes: [ 632]x[ 264]_(57=57.0000Hz)
   rng(0):  632 x 264_56.842p 16.200 [fract] scale(1, 1, 2) diff(18.99, 0.00, -1.5789) ratio(1.234, 0.550)

SwitchRes: [ 640]x[ 240]_(60=60.0000Hz)
   rng(0):  640 x 240_60.000p 15.660 [fract] scale(1, 1, 2) diff(20.00, 0.00, 0.0000) ratio(1.250, 0.500)

SwitchRes: [ 640]x[ 288]_(51=51.0000Hz)
   rng(0):  640 x 288_52.427p 16.200 [fract] scale(1, 1, 2) diff(20.00, 0.00, -3.7864) ratio(1.250, 0.600)

SwitchRes: [ 640]x[ 480]_(60=60.0000Hz)
   rng(0):  640 x 480_60.000i 15.690 [integ] scale(1, 1, 2) diff(20.00, 0.00, 0.0000) ratio(1.250, 1.000)

SwitchRes: [ 648]x[ 288]_(51=51.0000Hz)
   rng(0):  648 x 288_52.427p 16.200 [fract] scale(1, 1, 2) diff(20.99, 0.00, -3.7864) ratio(1.266, 0.600)

SwitchRes: [ 720]x[ 480]_(60=60.0000Hz)
   rng(0):  720 x 480_60.000i 15.690 [integ] scale(1, 1, 2) diff(28.89, 0.00, 0.0000) ratio(1.406, 1.000)

SwitchRes: [ 800]x[ 600]_(52=52.0000Hz)
   rng(0):  out of range

SwitchRes: [xenophob] (1) horizontal (512x480@30.00)->(512x512@58.48)
   rng(0):  512 x 512_58.484i 16.229 [integ] scale(1, 1, 2) diff(0.00, 3.25, -0.7581) ratio(1.000, 1.067)
SwitchRes: Modeline "512x512_58 16.23KHz 58.48Hz" 10.91 512 536 584 672 512 515 521 555 interlace  -hsync -vsync
SwitchRes: Setting option -rotate
SwitchRes: Setting option -noror
SwitchRes: Setting option -autoror
SwitchRes: Setting option -norol
SwitchRes: Setting option -noautorol
SwitchRes: Setting option -video ddraw
SwitchRes: Setting option -noblack_frame_insertion
SwitchRes: Setting option -nomultithreading
SwitchRes: Setting option -triplebuffer
SwitchRes: Setting option -nosyncrefresh
SwitchRes: Setting option -nowaitvsync
SwitchRes: Setting option -nohwstretch
SwitchRes: Setting option -keepaspect
SwitchRes: Setting option -nofilter
SwitchRes: Setting option -prescale 1
Video: Monitor 0000000000010001 = "\\.\DISPLAY1" (primary)
DirectDraw: Using DirectDraw 7
window_proc: WM_NCACTIVATE
blit_lock = TRUE
DirectDraw: Configuring device Ultimarc ArcadeVGA3000.
DirectDraw: primary surface created: 512x512x32 (R=00FF0000 G=0000FF00 B=000000FF)
DirectDraw: New blit size = 512x480
DirectDraw: blit surface created: 512x480x32 (R=00FF0000 G=0000FF00 B=000000FF)
blit_unlock = TRUE
stream_buffer_size = 37888
DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channels
RawInput: APIs detected
Input: Adding Mouse #0: HID-compliant mouse
Input: Adding Gun #0: HID-compliant mouse
Input: Adding Mouse #1: HID-compliant mouse
Input: Adding Gun #1: HID-compliant mouse
Input: Adding Mouse #2: HID-compliant mouse
Input: Adding Gun #2: HID-compliant mouse
Input: Adding Mouse #3: HID-compliant mouse
Input: Adding Gun #3: HID-compliant mouse
Input: Adding Mouse #4: HID-compliant mouse
Input: Adding Gun #4: HID-compliant mouse
Input: Adding Kbd #0: Standard PS/2 Keyboard
Input: Adding Mouse #5: HID-compliant mouse
Input: Adding Gun #5: HID-compliant mouse
DirectInput: Using DirectInput 7
Input: Adding Joy #0: Ultimarc Ultra-Stik Player 1
Input: Adding Joy #1: Ultimarc Ultra-Stik Player 2
Input: Adding Joy #2: ATRAK Device #1
Input: Adding Joy #3: ATRAK Device #2
window_proc: WM_PAINT
blit_lock = FALSE
window_proc: WM_PAINT:END
Unable to load winpcap: 7e
Region ':maincpu' created
Region ':sg:cpu' created
Region ':gfx1' created
Region ':gfx2' created
Region ':cpu_plds' created
Region ':snd_pld' created
Starting Xenophobe ':'
Optional device 'cvsd' not found
Optional device 'tcs' not found
Optional device 'csd' not found
  (missing dependencies; rescheduling)
Starting M68000 ':maincpu'
Starting Video Screen ':screen'
  (missing dependencies; rescheduling)
Starting gfxdecode ':gfxdecode'
Starting palette ':palette'
Starting Speaker ':mono'
  (missing dependencies; rescheduling)
Starting Midway Sounds Good Sound Board ':sg'
  (missing dependencies; rescheduling)
Starting M68000 ':sg:cpu'
Starting 6821 PIA ':sg:pia'
Starting DAC ':sg:dac'
Starting Xenophobe ':'
Optional device 'cvsd' not found
Optional device 'tcs' not found
Optional device 'csd' not found
  (missing dependencies; rescheduling)
Starting Video Screen ':screen'
Starting Speaker ':mono'
  (missing dependencies; rescheduling)
Starting Midway Sounds Good Sound Board ':sg'
Starting Xenophobe ':'
Optional device 'cvsd' not found
Optional device 'tcs' not found
Optional device 'csd' not found
  (missing dependencies; rescheduling)
Starting Speaker ':mono'
Starting Xenophobe ':'
Optional device 'cvsd' not found
Optional device 'tcs' not found
Optional device 'csd' not found
Average speed: 97.12% (573 seconds)
window_proc: WM_NCACTIVATE
blit_lock = TRUE
window_proc: WM_DESTROY
blit_lock = TRUE
Sound: buffer overflows=576 underflows=4

I should note that I always test via custom batch files that I make, which execute a simple command line, like this:
Code: [Select]
groovymame.exe xenophob -ctrlr MOTUMAME -v >xenophob.txt -log
I'm assuming this is acceptable?

Also, I didn't bother upgrading my romsets. It's just too much of a pain. Hopefully, that won't introduce issues with other games. Does anyone know what that might do?

haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 986
  • retro maniac
Re: Games with ISSUES: report here!
« Reply #181 on: January 19, 2015, 02:46:25 pm »
I've found two games that works but:

Nato Defense - game constantly switching resolutions when tank is destroyed. Better to force one resolution (does not happen in 179)

Sky Fox - for unknown reason game always choosing 320x248@60,223 instead 320x240@62,069 with arcade_15
« Last Edit: November 10, 2016, 03:54:58 pm by haynor666 »

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #182 on: January 25, 2015, 05:10:24 pm »
Quote
Ok, so I upgraded to 0.157.015e, keeping all existing settings the same, and the problems are nearly gone. The audio still stutters, but it only happens when the music is playing on load/exit of levels.

I can see -triplebuffering is in use (GM picks it automatically), but it needs that you manually enable -multithreading in order to work.
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

vindic8r

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 72
    • MOTUMAME: A Masters of the Universe Arcade Cabinet
Re: Games with ISSUES: report here!
« Reply #183 on: January 29, 2015, 12:21:52 am »
I can see -triplebuffering is in use (GM picks it automatically), but it needs that you manually enable -multithreading in order to work.

Multithreading did it. Xenophobe works perfectly now. Thanks!

haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 986
  • retro maniac
Re: Games with ISSUES: report here!
« Reply #184 on: January 29, 2015, 03:45:42 am »
It seems vector games on windows 7 had the same problem. mt has to been forces in order to get 100% speed.

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #185 on: January 29, 2015, 04:56:57 am »
As I explained -mt enabled should be the default setting for GroovyMAME, it's only I had to disable it so Hyperspin didn't make GroovyMAME crash.
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

xga

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 56
  • I want to build my own arcade controls!
Re: Games with ISSUES: report here!
« Reply #186 on: January 29, 2015, 09:05:24 am »
When I launch S.T.U.N. Runner, the MAME info window displays the video as 512 x 228 (H) 60.201796 Hz and Switchres as 512 x 232p 60.202 Hz 15.472 kHz.  Once the game has started, if I bring up the MAME menu and go into the Game Information menu, it displays video as 512 x 240 (H) 60.201796 Hz and Switchres as 512 x 240p 60.202 Hz 15.953 kHz.

Does this seem like correct behavior?  Is the first resolution (512 x 228) kind of like the BIOS of the game as it is starting and once the actual game commences it forces the later resolution (512 x 240)?

Thanks in advance.

xga

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 56
  • I want to build my own arcade controls!
Re: Games with ISSUES: report here!
« Reply #187 on: January 29, 2015, 10:05:12 am »
Hard Drivin' game play speed is locked at 97%.  Any way to fix this?

Code: [Select]
SwitchRes: v0.015d, Monitor: ms2930, Orientation: horizontal, Modeline generation: enabled
SwitchRes: Monitor range 15450.00-16050.00,50.00-65.00,3.190,4.750,6.450,0.191,0.191,1.164,0,0,192,288,448,576
SwitchRes: Monitor range 23900.00-24900.00,50.00-65.00,2.870,3.000,4.440,0.451,0.164,1.148,0,0,384,400,0,0
SwitchRes: Monitor range 31000.00-32000.00,50.00-65.00,0.330,3.580,1.750,0.316,0.063,1.137,0,0,480,512,0,0
SwitchRes: \\.\DISPLAY1: ATI Radeon HD 4300/4500 Series
SwitchRes: DeviceKey: System\CurrentControlSet\Control\Video\{4D259452-608C-4C70-9F0E-A84376F70671}\0000
Switchres: Searching for custom video modes...
Switchres: [  1]  640x 480 @ 60* : DALDTMCRTBCD640x480x0x60 - Modeline "640x480_60 31.61KHz 59.87Hz" 24.53 640 648 736 776 480 490 492 528   -hsync -vsync
Switchres: [  2] 1392x1040 @ 52 : DALDTMCRTBCD1392x1040x0x53 - Modeline "1392x1040_52 31.03KHz 52.55Hz" 52.13 1392 1408 1592 1680 1040 1083 1087 1181 interlace  -hsync -vsync
Switchres: [  3] 1392x1040 @ 54 : DALDTMCRTBCD1392x1040x0x54 - Modeline "1392x1040_54 31.00KHz 53.96Hz" 52.08 1392 1408 1592 1680 1040 1068 1072 1149 interlace  -hsync -vsync
Switchres: [  4] 2560x 224 @ 60 : DALDTMCRTBCD2560x224x0x60 - Modeline "2560x224_60 15.45KHz 59.64Hz" 50.79 2560 2720 2960 3288 224 233 236 259   -hsync -vsync
Switchres: [  5] 2560x 240 @ 60 : DALDTMCRTBCD2560x240x0x60 - Modeline "2560x240_60 15.90KHz 60.00Hz" 52.66 2560 2728 2976 3312 240 244 247 265   -hsync -vsync
Switchres: [  6] 2560x 248 @ 60 : DALDTMCRTBCD2560x248x0x60 - Modeline "2560x248_60 23.94KHz 59.99Hz" 81.20 2560 2792 3032 3392 248 313 317 399   -hsync -vsync
Switchres: [  7] 2560x 256 @ 60 : DALDTMCRTBCD2560x256x0x60 - Modeline "2560x256_60 23.94KHz 59.99Hz" 81.20 2560 2792 3032 3392 256 317 321 399   -hsync -vsync
Switchres: [  8] 2560x 264 @ 60 : DALDTMCRTBCD2560x264x0x60 - Modeline "2560x264_60 23.94KHz 59.99Hz" 81.20 2560 2792 3032 3392 264 321 325 399   -hsync -vsync
Switchres: [  9] 2560x 272 @ 60 : DALDTMCRTBCD2560x272x0x60 - Modeline "2560x272_60 23.94KHz 59.99Hz" 81.20 2560 2792 3032 3392 272 325 329 399   -hsync -vsync
Switchres: [ 10] 2560x 280 @ 60 : DALDTMCRTBCD2560x280x0x60 - Modeline "2560x280_60 23.94KHz 59.99Hz" 81.20 2560 2792 3032 3392 280 329 333 399   -hsync -vsync
Switchres: [ 11] 2560x 288 @ 60 : DALDTMCRTBCD2560x288x0x60 - Modeline "2560x288_60 23.94KHz 59.99Hz" 81.20 2560 2792 3032 3392 288 333 337 399   -hsync -vsync
Switchres: [ 12] 2560x 296 @ 60 : DALDTMCRTBCD2560x296x0x60 - Modeline "2560x296_60 23.94KHz 59.99Hz" 81.20 2560 2792 3032 3392 296 337 341 399   -hsync -vsync
Switchres: [ 13] 2560x 304 @ 60 : DALDTMCRTBCD2560x304x0x60 - Modeline "2560x304_60 23.94KHz 59.99Hz" 81.20 2560 2792 3032 3392 304 341 345 399   -hsync -vsync
Switchres: [ 14] 2560x 320 @ 60 : DALDTMCRTBCD2560x320x0x60 - Modeline "2560x320_60 23.94KHz 59.99Hz" 81.20 2560 2792 3032 3392 320 349 353 399   -hsync -vsync
Switchres: [ 15] 2560x 336 @ 60 : DALDTMCRTBCD2560x336x0x60 - Modeline "2560x336_60 23.94KHz 59.99Hz" 81.20 2560 2792 3032 3392 336 357 361 399   -hsync -vsync
Switchres: [ 16] 2560x 344 @ 60 : DALDTMCRTBCD2560x344x0x60 - Modeline "2560x344_60 23.94KHz 59.99Hz" 81.20 2560 2792 3032 3392 344 361 365 399   -hsync -vsync
Switchres: [ 17] 2560x 352 @ 60 : DALDTMCRTBCD2560x352x0x60 - Modeline "2560x352_60 23.94KHz 59.99Hz" 81.20 2560 2792 3032 3392 352 365 369 399   -hsync -vsync
Switchres: [ 18] 2560x 360 @ 60 : DALDTMCRTBCD2560x360x0x60 - Modeline "2560x360_60 24.18KHz 60.00Hz" 82.60 2560 2800 3048 3416 360 371 375 403   -hsync -vsync
Switchres: [ 19] 2560x 368 @ 60 : DALDTMCRTBCD2560x368x0x60 - Modeline "2560x368_60 24.72KHz 60.00Hz" 84.84 2560 2800 3056 3432 368 380 384 412   -hsync -vsync
Switchres: [ 20] 2560x 376 @ 60 : DALDTMCRTBCD2560x376x0x60 - Modeline "2560x376_60 31.02KHz 60.00Hz" 96.29 2560 2592 2936 3104 376 433 435 517   -hsync -vsync
Switchres: [ 21] 2560x 384 @ 60 : DALDTMCRTBCD2560x384x0x60 - Modeline "2560x384_60 31.02KHz 60.00Hz" 96.29 2560 2592 2936 3104 384 437 439 517   -hsync -vsync
Switchres: [ 22] 2560x 392 @ 60 : DALDTMCRTBCD2560x392x0x60 - Modeline "2560x392_60 31.02KHz 60.00Hz" 96.29 2560 2592 2936 3104 392 441 443 517   -hsync -vsync
Switchres: [ 23] 2560x 400 @ 60 : DALDTMCRTBCD2560x400x0x60 - Modeline "2560x400_60 31.02KHz 60.00Hz" 96.29 2560 2592 2936 3104 400 445 447 517   -hsync -vsync
Switchres: [ 24] 2560x 416 @ 60 : DALDTMCRTBCD2560x416x0x60 - Modeline "2560x416_60 31.02KHz 60.00Hz" 96.29 2560 2592 2936 3104 416 453 455 517   -hsync -vsync
Switchres: [ 25] 2560x 432 @ 60 : DALDTMCRTBCD2560x432x0x60 - Modeline "2560x432_60 31.02KHz 60.00Hz" 96.29 2560 2592 2936 3104 432 461 463 517   -hsync -vsync
Switchres: [ 26] 2560x 448 @ 60 : DALDTMCRTBCD2560x448x0x60 - Modeline "2560x448_60 31.02KHz 60.00Hz" 96.29 2560 2592 2936 3104 448 469 471 517   -hsync -vsync
Switchres: [ 27] 2560x 464 @ 60 : DALDTMCRTBCD2560x464x0x60 - Modeline "2560x464_60 31.02KHz 60.00Hz" 96.29 2560 2592 2936 3104 464 477 479 517   -hsync -vsync
Switchres: [ 28] 2560x 480 @ 60 : DALDTMCRTBCD2560x480x0x60 - Modeline "2560x480_60 31.68KHz 60.00Hz" 98.84 2560 2592 2944 3120 480 490 492 528   -hsync -vsync
Switchres: [ 29] 2560x 496 @ 59 : DALDTMCRTBCD2560x496x0x59 - Modeline "2560x496_59 32.00KHz 58.72Hz" 100.10 2560 2592 2952 3128 496 507 509 545   -hsync -vsync
Switchres: [ 30] 2560x 512 @ 57 : DALDTMCRTBCD2560x512x0x57 - Modeline "2560x512_57 32.00KHz 57.04Hz" 100.10 2560 2592 2952 3128 512 523 525 561   -hsync -vsync
Switchres: [ 31] 2560x 768 @ 60 : DALDTMCRTBCD2560x768x0x60 - Modeline "2560x768_60 31.05KHz 60.00Hz" 96.38 2560 2592 2936 3104 768 874 878 1035 interlace  -hsync -vsync
Switchres: [ 32] 2560x 800 @ 60 : DALDTMCRTBCD2560x800x0x60 - Modeline "2560x800_60 31.05KHz 60.00Hz" 96.38 2560 2592 2936 3104 800 890 894 1035 interlace  -hsync -vsync
SwitchRes: Found 32 custom of 32 active video modes
SwitchRes: -resolution was forced as 2560x0

SwitchRes: Entering switchres_modeline_setup
SwitchRes: v0.015d:[roms\harddriv.zip] Calculating best video mode for 508x384@59.952038 orientation: normal

SwitchRes: [ 640]x[ 480]_[60=59.8674Hz] - locked

SwitchRes: [1392]x[1040]_(52=52.5470Hz) - locked

SwitchRes: [1392]x[1040]_(54=53.9600Hz) - locked

SwitchRes: [2560]x[ 224]_(60=59.6409Hz)
   rng(0): 2560 x 224_59.952p 15.468 [fract] scale(5, 1, 1) diff(0.00, 0.00, 0.0000) ratio(5.000, 0.583)
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 240]_(60=59.9962Hz)
   rng(0): 2560 x 240_59.952p 15.887 [fract] scale(5, 1, 1) diff(0.00, 0.00, 0.0000) ratio(5.000, 0.625)
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 248]_(60=59.9950Hz)
   rng(0): 2560 x 248_58.791p 16.050 [fract] scale(5, 1, 1) diff(0.00, 0.00, -1.1608) ratio(5.000, 0.646)
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 256]_(60=59.9950Hz)
   rng(0): 2560 x 256_57.117p 16.050 [fract] scale(5, 1, 1) diff(0.00, 0.00, -2.8346) ratio(5.000, 0.667)
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 264]_(60=59.9950Hz)
   rng(0): 2560 x 264_55.536p 16.050 [fract] scale(5, 1, 1) diff(0.00, 0.00, -4.4157) ratio(5.000, 0.688)
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 272]_(60=59.9950Hz)
   rng(0): 2560 x 272_54.040p 16.050 [fract] scale(5, 1, 1) diff(0.00, 0.00, -5.9116) ratio(5.000, 0.708)
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 280]_(60=59.9950Hz)
   rng(0): 2560 x 280_52.623p 16.050 [fract] scale(5, 1, 1) diff(0.00, 0.00, -7.3291) ratio(5.000, 0.729)
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 288]_(60=59.9950Hz)
   rng(0): 2560 x 288_51.278p 16.050 [fract] scale(5, 1, 1) diff(0.00, 0.00, -8.6741) ratio(5.000, 0.750)
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 296]_(60=59.9950Hz)
   rng(0):  out of range
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 304]_(60=59.9950Hz)
   rng(0):  out of range
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 320]_(60=59.9950Hz)
   rng(0):  out of range
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 336]_(60=59.9950Hz)
   rng(0):  out of range
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 344]_(60=59.9950Hz)
   rng(0):  out of range
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 352]_(60=59.9950Hz)
   rng(0):  out of range
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 360]_(60=60.0000Hz)
   rng(0):  out of range
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 368]_(60=60.0000Hz)
   rng(0):  out of range
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 376]_(60=60.0019Hz)
   rng(0):  out of range
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 384]_(60=60.0019Hz)
   rng(0):  out of range
   rng(1): 2560 x 384_58.178p 24.900 [integ] scale(5, 1, 1) diff(0.00, 0.00, -1.7745) ratio(5.000, 1.000)
   rng(2):  out of range

SwitchRes: [2560]x[ 392]_(60=60.0019Hz)
   rng(0):  out of range
   rng(1): 2560 x 392_57.110p 24.900 [integ] scale(5, 1, 1) diff(0.00, 2.06, -2.8419) ratio(5.000, 1.021)
   rng(2):  out of range

SwitchRes: [2560]x[ 400]_(60=60.0019Hz)
   rng(0):  out of range
   rng(1): 2560 x 400_56.081p 24.900 [integ] scale(5, 1, 1) diff(0.00, 3.83, -3.8710) ratio(5.000, 1.042)
   rng(2):  out of range

SwitchRes: [2560]x[ 416]_(60=60.0019Hz)
   rng(0):  out of range
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 432]_(60=60.0019Hz)
   rng(0):  out of range
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 448]_(60=60.0019Hz)
   rng(0): 2560 x 448_59.952i 15.498 [fract] scale(5, 1, 1) diff(0.00, 24.81, 0.0000) ratio(5.000, 1.167)
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 464]_(60=60.0019Hz)
   rng(0): 2560 x 464_59.952i 15.498 [fract] scale(5, 1, 1) diff(0.00, 24.81, 0.0000) ratio(5.000, 1.208)
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 480]_(60=59.9981Hz)
   rng(0): 2560 x 480_59.952i 15.917 [fract] scale(5, 1, 1) diff(0.00, 26.79, 0.0000) ratio(5.000, 1.250)
   rng(1):  out of range
   rng(2): 2560 x 480_59.952p 31.655 [fract] scale(5, 1, 1) diff(0.00, 20.08, 0.0000) ratio(5.000, 1.250)

SwitchRes: [2560]x[ 496]_(59=58.7174Hz)
   rng(0): 2560 x 496_58.791i 16.079 [fract] scale(5, 1, 1) diff(0.00, 27.11, -1.1608) ratio(5.000, 1.292)
   rng(1):  out of range
   rng(2): 2560 x 496_58.716p 31.941 [fract] scale(5, 1, 1) diff(0.00, 20.59, -1.2364) ratio(5.000, 1.292)

SwitchRes: [2560]x[ 512]_(57=57.0428Hz)
   rng(0): 2560 x 512_57.117i 16.079 [fract] scale(5, 1, 1) diff(0.00, 26.33, -2.8346) ratio(5.000, 1.333)
   rng(1):  out of range
   rng(2): 2560 x 512_57.041p 31.943 [fract] scale(5, 1, 1) diff(0.00, 20.00, -2.9110) ratio(5.000, 1.333)

SwitchRes: [2560]x[ 768]_(60=60.0000Hz)
   rng(0):  out of range
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [2560]x[ 800]_(60=60.0000Hz)
   rng(0):  out of range
   rng(1):  out of range
   rng(2):  out of range

SwitchRes: [roms\harddriv.zip] (1) horizontal (508x384@59.95)->(2560x384@58.18)
   rng(1): 2560 x 384_58.178p 24.900 [integ] scale(5, 1, 1) diff(0.00, 0.00, -1.7745) ratio(5.000, 1.000)
SwitchRes: Modeline "2560x384_60 24.90KHz 58.18Hz" 85.86 2560 2808 3064 3448 384 396 400 428   -hsync -vsync
Switchres: saving    DALDTMCRTBCD2560x384x0x60 - Modeline "2560x384_60 31.02KHz 60.00Hz" 96.29 2560 2592 2936 3104 384 437 439 517   -hsync -vsync
Switchres: updating  DALDTMCRTBCD2560x384x0x60 - Modeline "2560x384_60 24.90KHz 58.18Hz" 85.86 2560 2808 3064 3448 384 396 400 428   -hsync -vsync
SwitchRes: Setting option -rotate
SwitchRes: Setting option -noror
SwitchRes: Setting option -autoror
SwitchRes: Setting option -norol
SwitchRes: Setting option -noautorol
SwitchRes: Setting option -noblack_frame_insertion
SwitchRes: Setting option -multithreading
SwitchRes: Setting option -notriplebuffer
SwitchRes: Setting option -syncrefresh
SwitchRes: Setting option -waitvsync
SwitchRes: Setting option -nohwstretch
SwitchRes: Setting option -keepaspect
SwitchRes: Setting option -nofilter
SwitchRes: Setting option -prescale 1
Video: Monitor 0000000000010001 = "\\.\DISPLAY1" (primary)
Direct3D: Using Direct3D 9
Blitting thread created
winwindow_video_window_create: blit_lock = TRUE
Blitting thread started
window_proc: WM_NCACTIVATE
Direct3D: Configuring adapter #0 = ATI Radeon HD 4300/4500 Series
Direct3D: Using dynamic textures
Direct3D: YUV format = RGB
Direct3D: Max texture size = 8192x8192
Direct3D: Device created at 2560x384
blit_unlock = TRUE
window_proc: WM_PAINT
stream_buffer_size = 37888
DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channels
blit_lock = FALSE
window_proc: WM_PAINT:END
RawInput: APIs detected
Input: Adding Mouse #0: Microsoft USB Basic Optical Mouse v2.0 (Mouse and Keyboard Center)
Input: Adding Gun #0: Microsoft USB Basic Optical Mouse v2.0 (Mouse and Keyboard Center)
Input: Adding Kbd #0: HID Keyboard Device
DirectInput: Using DirectInput 7
Unable to load winpcap: 7e
Region ':mainpcb:maincpu' created
Region ':mainpcb:soundcpu' created
Region ':mainpcb:user1' created
Region ':mainpcb:serialroms' created
Region ':mainpcb:200e' created
Region ':mainpcb:210e' created
Starting Hard Drivin' (cockpit, rev 7) ':'
  (missing dependencies; rescheduling)
Starting Hard Drivin' PCB Family ':mainpcb'
Optional device 'asic65' not found
Optional device 'ds3xdsp_timer' not found
Optional device 'ds3sdsp_timer' not found
Optional shared pointer 'ds3xdsp_pgm' not found
Optional shared pointer 'ds3sdsp_pgm' not found
Optional shared pointer 'ds3sdsp_data' not found
Optional device 'dsk_30c' not found
Optional device 'dsk_10c' not found
Optional device 'jsa' not found
Optional device 'ds3dac2' not found
Optional device 'ds3dac1' not found
Optional device 'ds3xdsp' not found
Optional device 'ds3sdsp' not found
Optional device 'dsp32' not found
Optional device 'jsacpu' not found
Starting M68010 ':mainpcb:maincpu'
Starting Atari Slapstic ':mainpcb:slapstic'
Starting TMS34010 ':mainpcb:gsp'
  (missing dependencies; rescheduling)
Starting M48T02 Timekeeper ':mainpcb:200e'
Starting Parallel EEPROM 2816 (2048x8) ':mainpcb:210e'
Starting MC68681 DUART ':mainpcb:duartn68681'
Starting MC68681 DUART CHANNEL ':mainpcb:duartn68681:cha'
Starting MC68681 DUART CHANNEL ':mainpcb:duartn68681:chb'
Starting palette ':mainpcb:palette'
Starting Video Screen ':mainpcb:screen'
Starting TMS34010 ':mainpcb:msp'
Starting ADSP-2100 ':mainpcb:adsp'
Starting M68000 ':mainpcb:soundcpu'
Starting TMS32010 ':mainpcb:sounddsp'
Starting Speaker ':mainpcb:mono'
  (missing dependencies; rescheduling)
Starting DAC ':mainpcb:dac'
Starting Hard Drivin' (cockpit, rev 7) ':'
  (missing dependencies; rescheduling)
Starting TMS34010 ':mainpcb:gsp'
Starting Speaker ':mainpcb:mono'
Starting Hard Drivin' (cockpit, rev 7) ':'
Average speed: 97.07% (91 seconds)
Switchres: restoring DALDTMCRTBCD2560x384x0x60 - Modeline "2560x384_60 31.02KHz 60.00Hz" 96.29 2560 2592 2936 3104 384 437 439 517   -hsync -vsync
window_proc: WM_NCACTIVATE
blit_lock = TRUE
window_proc: WM_DESTROY
blit_lock = TRUE
Blitting thread destroyed
Sound: buffer overflows=1 underflows=0



haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 986
  • retro maniac
Re: Games with ISSUES: report here!
« Reply #188 on: January 29, 2015, 10:45:54 am »
Games in hardriv.c are changing resolutions. S.T.U.N Runner - 512x240 is used during game.
« Last Edit: January 29, 2015, 10:48:57 am by haynor666 »

xga

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 56
  • I want to build my own arcade controls!
Re: Games with ISSUES: report here!
« Reply #189 on: January 29, 2015, 09:02:24 pm »
Games in hardriv.c are changing resolutions.

Thanks for your reply, haynor666.  Are you able to elaborate on your comment, please?  When I bring up the game information in the MAME menu, the game says it is running at it's native resolution (508 x 384).

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #190 on: January 30, 2015, 05:10:34 pm »
Hi xga,

Try with the 'arcade_15_25_31' preset. The ms2930 one is defined with a too long vertical back porch/too low Hfreqmax to reach 384p@60Hz.

STUN runner behaviour is normal. Vertical resolutions below 240p can be rendered inside a 240p container resolution without artifacts, leaving black borders as needed.

 
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

vindic8r

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 72
    • MOTUMAME: A Masters of the Universe Arcade Cabinet
Re: Games with ISSUES: report here!
« Reply #191 on: February 15, 2015, 01:13:16 am »
Here's an odd one. It's been happening for quite a while now, but I didn't report it since I've been unable to pin down specific repro steps. Every once in a while when I start up a game, I get a black screen. This can be fixed by opening up the in-game menu, going to Video Options, and changing the aspect ratio to Standard (4:3).

I've thought about forcing aspect 4:3 in my mame.ini, but was worried that might somehow prevent switchres from working properly.

For reference, here's my mame.ini, as it stands:
Code: [Select]
#
# CORE CONFIGURATION OPTIONS
#
readconfig                1
writeconfig               0

#
# CORE SEARCH PATH OPTIONS
#
rompath                   roms
hashpath                  hash
samplepath                samples
artpath                   artwork
ctrlrpath                 ctrlr
inipath                   ini
fontpath                  .
cheatpath                 cheat
crosshairpath             crosshair

#
# CORE OUTPUT DIRECTORY OPTIONS
#
cfg_directory             cfg
nvram_directory           nvram
memcard_directory         memcard
input_directory           inp
state_directory           sta
snapshot_directory        snap
diff_directory            diff
comment_directory         comments

#
# CORE OUTPUT DIRECTORY OPTIONS
#
hiscore_directory         hi

#
# CORE STATE/PLAYBACK OPTIONS
#
state                     
autosave                  1
playback                 
record                   
mngwrite                 
aviwrite                 
wavwrite                 
snapname                  %g/%i
snapsize                  auto
snapview                  internal
statename                 %g
burnin                    0

#
# CORE PERFORMANCE OPTIONS
#
autoframeskip             0
frameskip                 0
seconds_to_run            0
throttle                  1
syncrefresh               0
sleep                     1
speed                     1.0
refreshspeed              0

#
# CORE ROTATION OPTIONS
#
rotate                    1
ror                       0
rol                       0
autoror                   0
autorol                   0
flipx                     0
flipy                     0

#
# CORE ARTWORK OPTIONS
#
artwork_crop              1
use_backdrops             1
use_overlays              1
use_bezels                0
use_cpanels               1
use_marquees              1

#
# CORE SCREEN OPTIONS
#
brightness                1.0
contrast                  1.0
gamma                     1.0
pause_brightness          0.65
effect                    none

#
# CORE VECTOR OPTIONS
#
antialias                 1
beam                      1.0
flicker                   0

#
# CORE SOUND OPTIONS
#
sound                     1
samplerate                48000
samples                   1
volume                    0

#
# CORE INPUT OPTIONS
#
coin_lockout              1
ctrlr                     
mouse                     1
joystick                  1
lightgun                  1
multikeyboard             0
multimouse                1
steadykey                 0
ui_active                 0
offscreen_reload          1
joystick_map              auto
joystick_deadzone         0.3
joystick_saturation       0.85
natural                   0
joystick_contradictory    0
coin_impulse              0

#
# CORE INPUT AUTOMATIC ENABLE OPTIONS
#
paddle_device             mouse
adstick_device            keyboard
pedal_device              keyboard
dial_device               mouse
trackball_device          mouse
lightgun_device           none
positional_device         keyboard
mouse_device              mouse

#
# CORE DEBUGGING OPTIONS
#
log                       0
verbose                   0
update_in_pause           0
debug                     0
debugscript               
debug_internal            0

#
# CORE MISC OPTIONS
#
bios                     
cheat                     0
skip_gameinfo             0
uifont                      
ramsize                   
confirm_quit              0
ui_mouse                  0
autoboot_command         
autoboot_delay            2
autoboot_script           

#
# CORE MKChamp OPTIONS
#
disable_hiscore_patch     0
disable_nagscreen_patch   0
disable_loading_patch     0

#
# CORE SWITCHRES OPTIONS
#
modeline                  1
monitor                   arcade_15
orientation               horizontal
connector                 auto
interlace                 1
doublescan                0
cleanstretch              0
changeres                 1
powerstrip                0
lock_system_modes         0
lock_unsupported_modes    1
refresh_dont_care         1
dotclock_min              0
sync_refresh_tolerance    2.0
frame_delay               1
lcd_range                 auto
crt_range0                auto
crt_range1                auto
crt_range2                auto
crt_range3                auto
crt_range4                auto
crt_range5                auto
crt_range6                auto
crt_range7                auto
crt_range8                auto
crt_range9                auto

#
# WINDOWS DEBUGGING OPTIONS
#
oslog                     0
watchdog                  0
debugger_font             "Lucida Console"
debugger_font_size        9

#
# WINDOWS PERFORMANCE OPTIONS
#
priority                  0
multithreading            1
numprocessors             auto
profile                   0
bench                     0

#
# WINDOWS VIDEO OPTIONS
#
video                     d3d
numscreens                1
window                    0
maximize                  1
keepaspect                0
prescale                  1
waitvsync                 0
menu                      1


#
# DIRECTDRAW-SPECIFIC OPTIONS
#
hwstretch                 0

#
# DIRECT3D-SPECIFIC OPTIONS
#
filter                    1

#
# DIRECT3D POST-PROCESSING OPTIONS
#
hlsl_enable               0
hlslpath                  hlsl
hlsl_ini_read             0
hlsl_ini_write            0
hlslini                   %g
hlsl_prescale_x           0
hlsl_prescale_y           0
hlsl_preset               -1
hlsl_write               
hlsl_snap_width           2048
hlsl_snap_height          1536
shadow_mask_alpha         0.0
shadow_mask_texture       aperture.png
shadow_mask_x_count       320
shadow_mask_y_count       240
shadow_mask_usize         0.09375
shadow_mask_vsize         0.109375
curvature                 0.0
pincushion                0.0
scanline_alpha            0.0
scanline_size             1.0
scanline_height           0.7
scanline_bright_scale     1.0
scanline_bright_offset    0.0
scanline_jitter           0.0
defocus                   0.0,0.0
converge_x                0.0,0.0,0.0
converge_y                0.0,0.0,0.0
radial_converge_x         0.0,0.0,0.0
radial_converge_y         0.0,0.0,0.0
red_ratio                 1.0,0.0,0.0
grn_ratio                 0.0,1.0,0.0
blu_ratio                 0.0,0.0,1.0
saturation                1.0
offset                    0.0,0.0,0.0
scale                     1.0,1.0,1.0
power                     1.0,1.0,1.0
floor                     0.0,0.0,0.0
phosphor_life             0.0,0.0,0.0

#
# NTSC POST-PROCESSING OPTIONS
#
yiq_enable                0
yiq_cc                    3.59754545
yiq_a                     0.5
yiq_b                     0.5
yiq_o                     0.0
yiq_p                     1.0
yiq_n                     1.0
yiq_y                     6.0
yiq_i                     1.2
yiq_q                     0.6
yiq_scan_time             52.6
yiq_phase_count           2

#
# VECTOR POST-PROCESSING OPTIONS
#
vector_length_scale       0.8
vector_length_ratio       500.0

#
# BLOOM POST-PROCESSING OPTIONS
#
vector_bloom_scale        0.3
raster_bloom_scale        0.225
bloom_lvl0_weight         1.0
bloom_lvl1_weight         0.21
bloom_lvl2_weight         0.19
bloom_lvl3_weight         0.17
bloom_lvl4_weight         0.15
bloom_lvl5_weight         0.14
bloom_lvl6_weight         0.13
bloom_lvl7_weight         0.12
bloom_lvl8_weight         0.11
bloom_lvl9_weight         0.10
bloom_lvl10_weight        0.09

#
# PER-WINDOW VIDEO OPTIONS
#
screen                    auto
aspect                    auto
resolution                auto
view                      auto
screen0                   auto
aspect0                   auto
resolution0               auto
view0                     auto
screen1                   auto
aspect1                   auto
resolution1               auto
view1                     auto
screen2                   auto
aspect2                   auto
resolution2               auto
view2                     auto
screen3                   auto
aspect3                   auto
resolution3               auto
view3                     auto

#
# FULL SCREEN OPTIONS
#
triplebuffer              1
switchres                 1
full_screen_brightness    1.0
full_screen_contrast      1.0
full_screen_gamma         1.0

#
# WINDOWS SOUND OPTIONS
#
audio_latency             1

#
# INPUT DEVICE OPTIONS
#
dual_lightgun             0

Thoughts?

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #192 on: February 15, 2015, 09:12:38 am »
I've thought about forcing aspect 4:3 in my mame.ini, but was worried that might somehow prevent switchres from working properly.

You can force aspect 4:3 in mame.ini, no problem with that. Check if this fixes your problem. I've never seen what you describe but I've neither tested this with an ArcadeVGA.
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

cyb

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 43
Re: Games with ISSUES: report here!
« Reply #193 on: June 25, 2015, 03:00:44 am »
Mace: The Dark Age is running way too fast. Over 200%. I've attached a log. Using latest version of groovyMAME with win7


haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 986
  • retro maniac
Re: Games with ISSUES: report here!
« Reply #194 on: June 25, 2015, 07:12:44 am »
I already mentioned problems with some 3D games mostly Atari and Midway here - http://forum.arcadecontrols.com/index.php/topic,143528.0.html

big10p

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 555
  • Mmmm, arcade classics!
Re: Games with ISSUES: report here!
« Reply #195 on: July 02, 2015, 01:15:58 pm »
This isn't a big deal, just something I've noticed about GroovyMAME when compared to regular MAME and am curious about:

In GM, games with a scrolling background star field (Galaxian, Moon Cresta etc.) - the stars are a single pixel in regular MAME (and the original game, I think), but are 2 pixels in GM, making them look like short vertical lines. This also happens with the bullet fired from the player ship in Scramble. This isn't a scaling issue as I'm running the games at native res.

Just wondered why the difference?

haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 986
  • retro maniac
Re: Games with ISSUES: report here!
« Reply #196 on: July 02, 2015, 01:40:36 pm »

big10p

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 555
  • Mmmm, arcade classics!
Re: Games with ISSUES: report here!
« Reply #197 on: July 02, 2015, 04:11:05 pm »
Here you can find explanation ;) - http://forum.arcadecontrols.com/index.php/topic,142786.0.html
Thanks. I don't quite understand why there's a hack, though. I use a horizontal monitor and run Galaxian at 256 vert res. Isn't that the res of the original game, or something?

haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 986
  • retro maniac
Re: Games with ISSUES: report here!
« Reply #198 on: July 02, 2015, 04:20:12 pm »
Indeed but to emulate properly starfield has to be set 3 times higher.

big10p

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 555
  • Mmmm, arcade classics!
Re: Games with ISSUES: report here!
« Reply #199 on: July 02, 2015, 05:03:00 pm »
Ah, OK - weird. Thanks.

haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 986
  • retro maniac
Re: Games with ISSUES: report here!
« Reply #200 on: July 03, 2015, 01:40:34 am »
I didn't like it at the beginning but since every TV/ arcade monitor is cabable of displaying 768x224 it's not a problem.
« Last Edit: July 19, 2015, 04:53:28 am by haynor666 »

donluca

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 94
  • I want to build my own arcade controls!
Re: Games with ISSUES: report here!
« Reply #201 on: November 20, 2015, 03:38:45 pm »
Another issue found: Soul Calibur runs either at half speed when in Interlace mode or twice the speed when in non-interlace mode.

Not sure if this happens in regular MAME as well.

EDIT: the strange thing is that while in attract mode or at the beginning of a round, the speed is correct, only when the round starts the speed goes twice as fast or half.

EDIT 2: ok, it's a bug in MAME, found the bug ticket in their tracker. Nevermind.
« Last Edit: November 20, 2015, 03:56:48 pm by donluca »

stiegi

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 31
  • We learn from experience.
Re: Games with ISSUES: report here!
« Reply #202 on: November 21, 2015, 05:24:09 am »
Hello!

I would like to report an issue about the game pac-man. I am using groovymame .149 with an ati radeon x600. All in all the scrolling is very smooth

but I noticed that in the game pac-man - the character sprites and also the main character sprite which you move in the game has got some kind

of "microstutter" i.e. the movement is not smooth. Does anyone know if the original pac-man has got the same issue? From videos on the internet

I can tell that the characters have got smooth movement. I also noticed this issue in Donkey Kong when you move the main character. It is hard to

describe - the movement of the character is not "sharp and spot on" but in a way blurry and not precise. I can tell the difference in the game pac-

man because there is a pac-man speed up hack - and in this version when pac-man moves faster it is spot on and there is no micro stutter in it.

You can also see this issue in Bagman and SuperBagman - where the motion of the character is not precise.

Does anyone know why this happens - is it caused by input lag that groovy mame cannot exactly sync to the motion of the character?

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #203 on: November 21, 2015, 05:32:23 am »
If a game runs at its native refresh and syncrefresh is enabled it will be as smooth as the pcb was. Please read the first post in this thread and always attach a log to your posts reporting issues.
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

inv

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 15
  • I want to build my own arcade controls!
Re: Games with ISSUES: report here!
« Reply #204 on: February 24, 2016, 07:40:14 am »
Hi!

New to here.

I want to report a save/load state error of GM.

To reproduce this error, start a game, e.g. mslug, save state A in the start point, then advance till encounter a helicopter, beat it.

Then, load state from A, and advance to meet the helicopter, beat it again, and advance a bit, GM will eventually crush.

Other games will suffer from the same error, e.g. kov2 I tested.

I use mame64.exe -cc to create a mame.ini, and not modify it except lcd. I tested on two computers of mine, one had a AMD 7850 and one had a GTX 960, both crushed.


I have no idea why this error will produce, it's not in official mame. Guess it's a save/load route error.

inv

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 15
  • I want to build my own arcade controls!
Re: Games with ISSUES: report here!
« Reply #205 on: February 24, 2016, 08:57:22 pm »
Ok, there is my log file.

monitor: Benq lcd bl2410pt, system: win7 64-bit, video card: MicroStar Nvidia GTX 960, GM version: 0.171

Code: [Select]
SwitchRes: v0.015m, Monitor: lcd, Orientation: horizontal, Modeline generation: enabled
SwitchRes: Using default vfreq range for LCD 59.000000-61.000000
SwitchRes: \\.\DISPLAY1: NVIDIA GeForce GTX 960 (PCI\VEN_10DE&DEV_1401&SUBSYS_32021462&REV_A1)
SwitchRes: Device key: System\CurrentControlSet\Control\Video\{88E3986A-3E01-450B-BF23-C5AA20220357}\0000
Video chipset is not compatible.
Switchres: Searching for custom video modes...
Switchres: [  1]  640x 480 @ 60 : system mode
Switchres: [  2]  640x 480 @ 75 : system mode
Switchres: [  3]  720x 480 @ 60 : system mode
Switchres: [  4]  720x 480 @ 75 : system mode
Switchres: [  5]  720x 576 @ 60 : system mode
Switchres: [  6]  720x 576 @ 75 : system mode
Switchres: [  7]  800x 600 @ 60 : system mode
Switchres: [  8]  800x 600 @ 75 : system mode
Switchres: [  9] 1024x 768 @ 60 : system mode
Switchres: [ 10] 1024x 768 @ 75 : system mode
Switchres: [ 11] 1152x 864 @ 60 : system mode
Switchres: [ 12] 1152x 864 @ 75 : system mode
Switchres: [ 13] 1280x 720 @ 60 : system mode
Switchres: [ 14] 1280x 768 @ 60 : system mode
Switchres: [ 15] 1280x 800 @ 60 : system mode
Switchres: [ 16] 1280x 960 @ 60 : system mode
Switchres: [ 17] 1280x 960 @ 75 : system mode
Switchres: [ 18] 1280x1024 @ 60 : system mode
Switchres: [ 19] 1280x1024 @ 75 : system mode
Switchres: [ 20] 1360x 768 @ 60 : system mode
Switchres: [ 21] 1366x 768 @ 60 : system mode
Switchres: [ 22] 1600x 900 @ 60 : system mode
Switchres: [ 23] 1600x1024 @ 59 : system mode
Switchres: [ 24] 1600x1024 @ 60 : system mode
Switchres: [ 25] 1680x1050 @ 59 : system mode
Switchres: [ 26] 1680x1050 @ 60 : system mode
Switchres: [ 27] 1920x1080 @ 60* : system mode
SwitchRes: Found 0 custom of 27 active video modes
SwitchRes: Creating automatic specs for LCD based on VESA GTF
SwitchRes: Monitor range 65962.00-68198.00,59.00-61.00,0.741,1.157,1.898,0.015,0.045,0.507,0,1,1080,1080,0,0
SwitchRes: -resolution was forced as 1920x1080@60

SwitchRes: Entering switchres_modeline_setup
SwitchRes: v0.015m:[mslug] Calculating best video mode for 320x224@59.185608 orientation: normal

SwitchRes: [ 640]x[ 480]_[60=60.000000Hz] - locked

SwitchRes: [ 640]x[ 480]_[75=75.000000Hz] - locked

SwitchRes: [ 720]x[ 480]_[60=60.000000Hz] - locked

SwitchRes: [ 720]x[ 480]_[75=75.000000Hz] - locked

SwitchRes: [ 720]x[ 576]_[60=60.000000Hz] - locked

SwitchRes: [ 720]x[ 576]_[75=75.000000Hz] - locked

SwitchRes: [ 800]x[ 600]_[60=60.000000Hz] - locked

SwitchRes: [ 800]x[ 600]_[75=75.000000Hz] - locked

SwitchRes: [1024]x[ 768]_[60=60.000000Hz] - locked

SwitchRes: [1024]x[ 768]_[75=75.000000Hz] - locked

SwitchRes: [1152]x[ 864]_[60=60.000000Hz] - locked

SwitchRes: [1152]x[ 864]_[75=75.000000Hz] - locked

SwitchRes: [1280]x[ 720]_[60=60.000000Hz] - locked

SwitchRes: [1280]x[ 768]_[60=60.000000Hz] - locked

SwitchRes: [1280]x[ 800]_[60=60.000000Hz] - locked

SwitchRes: [1280]x[ 960]_[60=60.000000Hz] - locked

SwitchRes: [1280]x[ 960]_[75=75.000000Hz] - locked

SwitchRes: [1280]x[1024]_[60=60.000000Hz] - locked

SwitchRes: [1280]x[1024]_[75=75.000000Hz] - locked

SwitchRes: [1360]x[ 768]_[60=60.000000Hz] - locked

SwitchRes: [1366]x[ 768]_[60=60.000000Hz] - locked

SwitchRes: [1600]x[ 900]_[60=60.000000Hz] - locked

SwitchRes: [1600]x[1024]_[59=59.000000Hz] - locked

SwitchRes: [1600]x[1024]_[60=60.000000Hz] - locked

SwitchRes: [1680]x[1050]_[59=59.000000Hz] - locked

SwitchRes: [1680]x[1050]_[60=60.000000Hz] - locked

SwitchRes: [1920]x[1080]_[60=60.000000Hz]
   rng(0): 1920 x1080_60.000000p 0.000000 [fract] scale(6, 4, 1) diff(0.00, 18.07, 0.8144) ratio(6.000, 4.821)

SwitchRes: [mslug] (1) horizontal (320x224@59.185608)->(1920x1080@60.000000)
   rng(0): 1920 x1080_60.000000p 0.000000 [fract] scale(6, 4, 1) diff(0.00, 18.07, 0.8144) ratio(6.000, 4.821)
SwitchRes: Modeline "1920x1080_60 0.000000KHz 60.000000Hz" 0.000000 1920 0 0 0 1080 0 0 0   -hsync -vsync
SwitchRes: Setting option -rotate
SwitchRes: Setting option -noror
SwitchRes: Setting option -autoror
SwitchRes: Setting option -norol
SwitchRes: Setting option -noautorol
SwitchRes: Setting option -noblack_frame_insertion
SwitchRes: Setting option -nomultithreading
SwitchRes: Setting option -notriplebuffer
SwitchRes: Setting option -syncrefresh
SwitchRes: Setting option -waitvsync
SwitchRes: Setting option -keepaspect
SwitchRes: Setting option -filter
SwitchRes: Setting option -prescale 3
Video: Monitor 000000000864C398 = "\\.\DISPLAY1" (primary)
Direct3D: Using Direct3D 9
window_proc: WM_NCACTIVATE
blit_lock = TRUE
Physical width 1920, height 1080
Direct3D: Configuring adapter #0 = NVIDIA GeForce GTX 960
Direct3D: Adapter has Vendor ID: 10DE and Device ID: 1401
Direct3D: Using dynamic textures
Direct3D: Using StretchRect for prescaling
Direct3D: YUV format = RGB
Direct3D: Max texture size = 16384x16384
Direct3D: Device created at 1920x1080
Direct3D: First scanline: 0, Last scanline: 1079, Break scanline: 1079, Delay scanline: -108
blit_unlock = TRUE
RawInput: APIs detected
Input: Adding Mouse #0: HID-compliant mouse
Input: Adding Gun #0: HID-compliant mouse
Input: Adding Kbd #0: HID Keyboard Device
DirectInput: Using DirectInput 8
window_proc: WM_PAINT
blit_lock = FALSE
window_proc: WM_PAINT:END
stream_buffer_size = 37888
DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channels
Region ':maincpu' created
Region ':fixed' created
Region ':fixedbios' created
Region ':zoomy' created
Region ':mainbios' created
Region ':audiobios' created
Region ':audiocpu' created
Region ':ymsnd' created
Region ':sprites' created
Starting Metal Slug - Super Vehicle-001 ':'
Optional device 'cartslot6' not found
Optional device 'cartslot5' not found
Optional device 'cartslot4' not found
Optional device 'cartslot3' not found
Optional device 'cartslot2' not found
Optional device 'cartslot1' not found
  (missing dependencies; rescheduling)
Starting M68000 ':maincpu'
Starting Z80 ':audiocpu'
Starting Video Screen ':screen'
Optional device 'finder_dummy_tag' not found
Starting palette ':palette'
Starting Neogeo Sprites ':spritegen'
Starting Speaker ':lspeaker'
  (missing dependencies; rescheduling)
Starting Speaker ':rspeaker'
  (missing dependencies; rescheduling)
Starting YM2610 ':ymsnd'
Starting NeoGeo Banked Cartridge ':banked_cart'
Starting uPD4990A RTC ':upd4990a'
Starting NVRAM ':saveram'
Starting NeoGeo Memory Card ':memcard'
Starting NeoGeo Protection (Metal Slug X) ':mslugx_prot'
Starting NeoGeo SMA Cartridge ':sma_prot'
Starting NeoGeo Protection (CMC) ':cmc_prot'
Starting NeoGeo Protection (NEOPCM2) ':pcm2_prot'
Starting NeoGeo Protection (PVC) ':pvc_prot'
Starting NeoGeo Protection (Bootleg) ':bootleg_prot'
Starting NeoGeo Protection (KOF2002) ':kof2002_prot'
Starting NeoGeo Protection (Fatal Fury 2) ':fatfury2_prot'
Starting NeoGeo Protection (KOF98) ':kof98_prot'
Starting NeoGeo Protection (Super Bubble Pop) ':sbp_prot'
Starting Metal Slug - Super Vehicle-001 ':'
Optional device 'cartslot6' not found
Optional device 'cartslot5' not found
Optional device 'cartslot4' not found
Optional device 'cartslot3' not found
Optional device 'cartslot2' not found
Optional device 'cartslot1' not found
  (missing dependencies; rescheduling)
Starting Speaker ':lspeaker'
Starting Speaker ':rspeaker'
Starting Metal Slug - Super Vehicle-001 ':'
Optional device 'cartslot6' not found
Optional device 'cartslot5' not found
Optional device 'cartslot4' not found
Optional device 'cartslot3' not found
Optional device 'cartslot2' not found
Optional device 'cartslot1' not found
Average speed: 101.35% (12 seconds)
window_proc: WM_NCACTIVATE
blit_lock = TRUE
window_proc: WM_DESTROY
blit_lock = TRUE

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #206 on: February 25, 2016, 11:26:25 am »
Ok, there is my log file.

Confirmed here, thanks for reporting.
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

funkycochise

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 39
  • I want to build my own arcade controls!
Re: Games with ISSUES: report here!
« Reply #207 on: July 18, 2016, 02:48:32 pm »
Hi there,
First I'd like to thank Calamity for his huge work to make groovymame a reality.

I'm posting here because I noticed a strange behavior when running kungfum or spartanx (basically the same game).
Regarding groovymame's job, resolutions/frequency seems to work as it should.
Issues are on the audio part. Sound samples seems to be very low in volume and the music seems to crackle.

Same game, ran on regular mame have a much clear volume/sound track.

I don't believe that the log dump will give any advice. I made it anyway. I've seen lines concerning the audio driver but nothing like any error or so.
If someone could confirm this issue...

Thanks a lot.
FKY

haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 986
  • retro maniac
Re: Games with ISSUES: report here!
« Reply #208 on: July 20, 2016, 09:16:52 am »
You are comparing groovymame 171 vs mame 171 ?

Some time ago discrete sound has been added and cause a serious performance drop that's why on some configurations sound is choppy.

funkycochise

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 39
  • I want to build my own arcade controls!
Re: Games with ISSUES: report here!
« Reply #209 on: July 20, 2016, 02:44:38 pm »
You are comparing groovymame 171 vs mame 171 ?

Some time ago discrete sound has been added and cause a serious performance drop that's why on some configurations sound is choppy.
Sound issue has nothing to do with performance drop making that caracteristic warped record sound, if it's what you are talking about.
And yes I used 171 version of groovymame and regular mame.
 

haynor666

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 986
  • retro maniac
Re: Games with ISSUES: report here!
« Reply #210 on: July 21, 2016, 05:10:22 am »
That might be problem with syncrefresh. A slightly more power is required to run groovymame that regular mame especially when You are using frame_delay option. From time to time I can hear it also on my arcade PC with G3258 4,2 GHz.

Dicrete emulation is really demanding for processor power.

Andypc

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 104
Re: Games with ISSUES: report here!
« Reply #211 on: September 11, 2016, 07:51:35 pm »
I'm having a problem with Golden Tee Fore running to fast in groovymame as if it's not throttled. Everything else is running fine. Any Suggestions. I am using Groovymame 0.171

ArcadeAction

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 37
  • I have built my own arcade controls!
    • ArcadeMade.com
Re: Games with ISSUES: report here!
« Reply #212 on: December 15, 2016, 02:10:36 pm »
When running through Hyperspin, Zookeeper starts and then gets distorted and seemingly errors out and doesn't play. CPS2 also failed to launch.

I was using:
-GroovyMAME versions .172 through .178 I believe with the same result
-CRTEmu_driver 2.0

***Update***
Using GroovyMAME .180 fixes the Zookeeper issue with Hyperspin. CPS2 games are still canceling out after the nag screen. Elevator Action is not launching.
« Last Edit: December 18, 2016, 10:20:07 am by ArcadeAction »

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #213 on: December 19, 2016, 07:02:56 am »
As you see I no longer bother asking for logs. I explored the path of moving posts to a purgatory thread but it involves even more time from my part.
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

ArcadeAction

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 37
  • I have built my own arcade controls!
    • ArcadeMade.com
Re: Games with ISSUES: report here!
« Reply #214 on: December 20, 2016, 06:36:11 pm »
As you see I no longer bother asking for logs. I explored the path of moving posts to a purgatory thread but it involves even more time from my part.

I recently noticed the requirement to post logs along with issues, and will do so with any similar future posts. Thanks

beaches

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 9
  • I want to build my own arcade controls!
Re: Games with ISSUES: report here!
« Reply #215 on: January 20, 2017, 08:21:47 am »
Hello everybody, well I can´t play tetris the grandmaster 2 by groovymame. It appears a blue screen. I can hear the sounds but only a blue screen on my CRT.
¿what´s the problem?
Here it´s the log.  Thanks.

Rom name: tgm2
Videocard: ati radeon X1300
Monitor: pal tv
OS: XP
Groovymame 0.161


Code: [Select]
SwitchRes: v0.015g, Monitor: generic_15, Orientation: horizontal, Modeline generation: enabled
SwitchRes: Monitor range 15625.00-15750.00,49.50-65.00,2.000,4.700,8.000,0.064,0.192,1.024,0,0,192,288,448,576
SwitchRes: \\.\DISPLAY1: Radeon X1300 Series
SwitchRes: DeviceKey: System\CurrentControlSet\Control\Video\{6E5AF182-A75A-4EE8-B9C8-B6E393D0BA61}\0000
Switchres: Searching for custom video modes...
Switchres: [  1]  480x 192 @ 60 : DALDTMCRTBCD480x192x0x60 - Modeline "480x192_60 15.66KHz 60.02Hz" 9.90 480 504 552 632 192 218 221 261   -hsync -vsync
Switchres: [  2]  480x 200 @ 60 : DALDTMCRTBCD480x200x0x60 - Modeline "480x200_60 15.66KHz 60.02Hz" 9.90 480 504 552 632 200 222 225 261   -hsync -vsync
Switchres: [  3]  496x 192 @ 60 : DALDTMCRTBCD496x192x0x60 - Modeline "496x192_60 15.66KHz 60.01Hz" 10.15 496 520 568 648 192 218 221 261   -hsync -vsync
Switchres: [  4]  512x 192 @ 60 : DALDTMCRTBCD512x192x0x60 - Modeline "512x192_60 15.66KHz 60.01Hz" 10.40 512 536 584 664 192 218 221 261   -hsync -vsync
Switchres: [  5]  512x 224 @ 60 : DALDTMCRTBCD512x224x0x60 - Modeline "512x224_60 15.66KHz 59.55Hz" 10.40 512 536 584 664 224 235 238 263   -hsync -vsync
Switchres: [  6]  512x 239 @ 60 : DALDTMCRTBCD512x239x0x60 - Modeline "512x239_60 15.66KHz 60.01Hz" 10.40 512 536 584 664 239 241 244 261   -hsync -vsync
Switchres: [  7]  512x 240 @ 60 : DALDTMCRTBCD512x240x0x60 - Modeline "512x240_60 15.66KHz 60.01Hz" 10.40 512 536 584 664 240 242 245 261   -hsync -vsync
Switchres: [  8]  512x 244 @ 60 : DALDTMCRTBCD512x244x0x60 - Modeline "512x244_60 15.83KHz 59.97Hz" 10.64 512 536 584 672 244 245 248 264   -hsync -vsync
Switchres: [  9]  512x 256 @ 58 : DALDTMCRTBCD512x256x0x58 - Modeline "512x256_58 16.20KHz 58.50Hz" 10.89 512 536 584 672 256 258 261 277   -hsync -vsync
Switchres: [ 10]  512x 448 @ 60 : DALDTMCRTBCD512x448x0x60 - Modeline "512x448_60 15.69KHz 60.01Hz" 10.42 512 536 584 664 448 467 473 523 interlace  -hsync -vsync
Switchres: [ 11]  512x 478 @ 60 : DALDTMCRTBCD512x478x0x60 - Modeline "512x478_60 15.69KHz 60.01Hz" 10.42 512 536 584 664 478 482 488 523 interlace  -hsync -vsync
Switchres: [ 12]  512x 480 @ 60 : DALDTMCRTBCD512x480x0x60 - Modeline "512x480_60 15.68KHz 57.53Hz" 10.41 512 536 584 664 480 494 500 545 interlace  -hsync -vsync
Switchres: [ 13]  512x 512 @ 58 : DALDTMCRTBCD512x512x0x58 - Modeline "512x512_58 16.23KHz 58.50Hz" 10.91 512 536 584 672 512 515 521 555 interlace  -hsync -vsync
Switchres: [ 14]  544x 242 @ 60 : DALDTMCRTBCD544x242x0x60 - Modeline "544x242_60 15.72KHz 59.98Hz" 11.19 544 568 624 712 242 243 246 262   -hsync -vsync
Switchres: [ 15]  640x 200 @ 60 : DALDTMCRTBCD640x200x0x60 - Modeline "640x200_60 15.66KHz 60.00Hz" 13.03 640 664 728 832 200 222 225 261   -hsync -vsync
Switchres: [ 16]  640x 224 @ 60 : DALDTMCRTBCD640x224x0x60 - Modeline "640x224_60 15.65KHz 59.96Hz" 13.02 640 664 728 832 224 234 237 261   -hsync -vsync
Switchres: [ 17]  640x 240 @ 60 : DALDTMCRTBCD640x240x0x60 - Modeline "640x240_60 15.65KHz 59.96Hz" 13.02 640 664 728 832 240 242 245 261   -hsync -vsync
Switchres: [ 18]  640x 244 @ 60 : DALDTMCRTBCD640x244x0x60 - Modeline "640x244_60 15.84KHz 60.00Hz" 13.18 640 664 728 832 244 245 248 264   -hsync -vsync
Switchres: [ 19]  640x 256 @ 58 : DALDTMCRTBCD640x256x0x58 - Modeline "640x256_58 16.20KHz 58.49Hz" 13.74 640 672 736 848 256 258 261 277   -hsync -vsync
Switchres: [ 20]  640x 480 @ 60* : DALDTMCRTBCD640x480x0x60 - Modeline "640x480_60 15.69KHz 59.98Hz" 13.05 640 664 728 832 480 483 489 523 interlace  -hsync -vsync
Switchres: [ 21]  640x 960 @ 60 : system mode
mode_locked
Switchres: [ 22]  664x 496 @ 60 : DALDTMCRTBCD664x496x0x60 - Modeline "664x496_60 16.17KHz 60.00Hz" 14.10 664 696 760 872 496 499 505 539 interlace  -hsync -vsync
Switchres: [ 23]  672x 224 @ 60 : DALDTMCRTBCD672x224x0x60 - Modeline "672x224_60 15.66KHz 60.00Hz" 13.78 672 704 768 880 224 234 237 261   -hsync -vsync
Switchres: [ 24]  720x 480 @ 60 : system mode
mode_locked
Switchres: [ 25]  768x 240 @ 60 : DALDTMCRTBCD768x240x0x60 - Modeline "768x240_60 15.63KHz 59.89Hz" 15.63 768 800 872 1000 240 242 245 261   -hsync -vsync
Switchres: [ 26]  768x 512 @ 58 : DALDTMCRTBCD768x512x0x58 - Modeline "768x512_58 16.23KHz 58.49Hz" 16.36 768 800 880 1008 512 515 521 555 interlace  -hsync -vsync
Switchres: [ 27] 1280x 480 @ 60 : system mode
mode_locked
Switchres: [ 28] 1280x 720 @ 60 : system mode
mode_locked
Switchres: [ 29] 1920x1200 @ 60 : system mode
mode_locked
Switchres: [ 30] 1920x1200 @ 75 : system mode
mode_locked
Switchres: [ 31] 1920x1200 @ 85 : system mode
mode_locked
Switchres: [ 32] 1920x1200 @100 : system mode
mode_locked
Switchres: [ 33] 1920x1440 @ 60 : system mode
mode_locked
Switchres: [ 34] 1920x1440 @ 75 : system mode
mode_locked
Switchres: [ 35] 1920x1440 @ 85 : system mode
mode_locked
Switchres: [ 36] 1920x1440 @ 90 : system mode
mode_locked
Switchres: [ 37] 2048x1536 @ 60 : system mode
mode_locked
Switchres: [ 38] 2048x1536 @ 66 : system mode
mode_locked
Switchres: [ 39] 2048x1536 @ 70 : system mode
mode_locked
Switchres: [ 40] 2048x1536 @ 75 : system mode
mode_locked
Switchres: [ 41] 2048x1536 @ 85 : system mode
mode_locked
SwitchRes: Found 24 custom of 41 active video modes

SwitchRes: Entering switchres_modeline_setup
SwitchRes: v0.015g:[tgm2] Calculating best video mode for 320x240@61.681171 orientation: normal

SwitchRes: [ 480]x[ 192]_(60=60.0153Hz)
   rng(0):  480 x 192_61.681p 15.667 [fract] scale(1, 1, 1) diff(33.33, 0.00, 0.0000) ratio(1.500, 0.800)

SwitchRes: [ 480]x[ 200]_(60=60.0153Hz)
   rng(0):  480 x 200_61.681p 15.667 [fract] scale(1, 1, 1) diff(33.33, 0.00, 0.0000) ratio(1.500, 0.833)

SwitchRes: [ 496]x[ 192]_(60=60.0115Hz)
   rng(0):  496 x 192_61.681p 15.667 [fract] scale(1, 1, 1) diff(35.48, 0.00, 0.0000) ratio(1.550, 0.800)

SwitchRes: [ 512]x[ 192]_(60=60.0077Hz)
   rng(0):  512 x 192_61.681p 15.667 [fract] scale(1, 1, 1) diff(37.50, 0.00, 0.0000) ratio(1.600, 0.800)

SwitchRes: [ 512]x[ 224]_(60=59.5513Hz)
   rng(0):  512 x 224_61.681p 15.667 [fract] scale(1, 1, 1) diff(37.50, 0.00, 0.0000) ratio(1.600, 0.933)

SwitchRes: [ 512]x[ 239]_(60=60.0077Hz)
   rng(0):  512 x 239_60.811p 15.750 [fract] scale(1, 1, 1) diff(37.50, 0.00, -0.8704) ratio(1.600, 0.996)

SwitchRes: [ 512]x[ 240]_(60=60.0077Hz)
   rng(0):  512 x 240_60.577p 15.750 [fract] scale(1, 1, 1) diff(37.50, 0.00, -1.1042) ratio(1.600, 1.000)

SwitchRes: [ 512]x[ 244]_(60=59.9735Hz)
   rng(0):  512 x 244_59.659p 15.750 [fract] scale(1, 1, 1) diff(37.50, 1.14, -2.0221) ratio(1.600, 1.017)

SwitchRes: [ 512]x[ 256]_(58=58.5018Hz)
   rng(0):  512 x 256_57.065p 15.750 [fract] scale(1, 1, 1) diff(37.50, 5.43, -4.6160) ratio(1.600, 1.067)

SwitchRes: [ 512]x[ 448]_(60=60.0076Hz)
   rng(0):  512 x 448_61.681i 15.698 [fract] scale(1, 1, 1) diff(37.50, 81.89, 0.0000) ratio(1.600, 1.867)

SwitchRes: [ 512]x[ 478]_(60=60.0076Hz)
   rng(0):  512 x 478_60.811i 15.780 [fract] scale(1, 1, 1) diff(37.50, 82.24, -0.8704) ratio(1.600, 1.992)

SwitchRes: [ 512]x[ 480]_(60=57.5303Hz)
   rng(0):  512 x 480_60.577i 15.780 [fract] scale(1, 2, 1) diff(37.50, 0.00, -1.1042) ratio(1.600, 2.000)

SwitchRes: [ 512]x[ 512]_(58=58.5045Hz)
   rng(0):  512 x 512_57.065i 15.779 [fract] scale(1, 2, 1) diff(37.50, 5.43, -4.6160) ratio(1.600, 2.133)

SwitchRes: [ 544]x[ 242]_(60=59.9847Hz)
   rng(0):  544 x 242_60.115p 15.750 [fract] scale(1, 1, 1) diff(41.18, 0.38, -1.5667) ratio(1.700, 1.008)

SwitchRes: [ 640]x[ 200]_(60=60.0038Hz)
   rng(0):  640 x 200_61.681p 15.667 [fract] scale(2, 1, 1) diff(0.00, 0.00, 0.0000) ratio(2.000, 0.833)

SwitchRes: [ 640]x[ 224]_(60=59.9579Hz)
   rng(0):  640 x 224_61.681p 15.667 [fract] scale(2, 1, 1) diff(0.00, 0.00, 0.0000) ratio(2.000, 0.933)

SwitchRes: [ 640]x[ 240]_(60=59.9579Hz)
   rng(0):  640 x 240_60.577p 15.750 [integ] scale(2, 1, 1) diff(0.00, 0.00, -1.1042) ratio(2.000, 1.000)

SwitchRes: [ 640]x[ 244]_(60=60.0038Hz)
   rng(0):  640 x 244_59.659p 15.750 [integ] scale(2, 1, 1) diff(0.00, 1.14, -2.0221) ratio(2.000, 1.017)

SwitchRes: [ 640]x[ 256]_(58=58.4910Hz)
   rng(0):  640 x 256_57.065p 15.750 [integ] scale(2, 1, 1) diff(0.00, 5.43, -4.6160) ratio(2.000, 1.067)

SwitchRes: [ 640]x[ 480]_[60=59.9809Hz]
   rng(0):  640 x 480_59.981i 15.685 [integ] scale(2, 2, 1) diff(0.00, 0.00, -1.7003) ratio(2.000, 2.000)

SwitchRes: [ 640]x[ 960]_[60=60.0000Hz] - locked

SwitchRes: [ 664]x[ 496]_(60=59.9963Hz)
   rng(0):  664 x 496_58.769i 15.779 [integ] scale(2, 2, 1) diff(3.61, 2.61, -2.9125) ratio(2.075, 2.067)

SwitchRes: [ 672]x[ 224]_(60=59.9962Hz)
   rng(0):  672 x 224_61.681p 15.667 [fract] scale(2, 1, 1) diff(4.76, 0.00, 0.0000) ratio(2.100, 0.933)

SwitchRes: [ 720]x[ 480]_[60=60.0000Hz] - locked

SwitchRes: [ 768]x[ 240]_(60=59.8851Hz)
   rng(0):  768 x 240_60.577p 15.750 [fract] scale(2, 1, 1) diff(16.67, 0.00, -1.1042) ratio(2.400, 1.000)

SwitchRes: [ 768]x[ 512]_(58=58.4865Hz)
   rng(0):  768 x 512_57.065i 15.779 [fract] scale(2, 2, 1) diff(16.67, 5.43, -4.6160) ratio(2.400, 2.133)

SwitchRes: [1280]x[ 480]_[60=60.0000Hz] - locked

SwitchRes: [1280]x[ 720]_[60=60.0000Hz] - locked

SwitchRes: [1920]x[1200]_[60=60.0000Hz] - locked

SwitchRes: [1920]x[1200]_[75=75.0000Hz] - locked

SwitchRes: [1920]x[1200]_[85=85.0000Hz] - locked

SwitchRes: [1920]x[1200]_[100=100.0000Hz] - locked

SwitchRes: [1920]x[1440]_[60=60.0000Hz] - locked

SwitchRes: [1920]x[1440]_[75=75.0000Hz] - locked

SwitchRes: [1920]x[1440]_[85=85.0000Hz] - locked

SwitchRes: [1920]x[1440]_[90=90.0000Hz] - locked

SwitchRes: [2048]x[1536]_[60=60.0000Hz] - locked

SwitchRes: [2048]x[1536]_[66=66.0000Hz] - locked

SwitchRes: [2048]x[1536]_[70=70.0000Hz] - locked

SwitchRes: [2048]x[1536]_[75=75.0000Hz] - locked

SwitchRes: [2048]x[1536]_[85=85.0000Hz] - locked

SwitchRes: [tgm2] (1) horizontal (320x240@61.68)->(640x240@60.58)
   rng(0):  640 x 240_60.577p 15.750 [integ] scale(2, 1, 1) diff(0.00, 0.00, -1.1042) ratio(2.000, 1.000)
SwitchRes: Modeline "640x240_60 15.75KHz 60.58Hz" 13.10 640 664 728 832 240 241 244 260   -hsync -vsync
Switchres: saving    DALDTMCRTBCD640x240x0x60 - Modeline "640x240_60 15.65KHz 59.96Hz" 13.02 640 664 728 832 240 242 245 261   -hsync -vsync
Switchres: updating  DALDTMCRTBCD640x240x0x60 - Modeline "640x240_60 15.75KHz 60.58Hz" 13.10 640 664 728 832 240 241 244 260   -hsync -vsync
SwitchRes: Setting option -rotate
SwitchRes: Setting option -noror
SwitchRes: Setting option -autoror
SwitchRes: Setting option -norol
SwitchRes: Setting option -noautorol
SwitchRes: Setting option -noblack_frame_insertion
SwitchRes: Setting option -nomultithreading
SwitchRes: Setting option -notriplebuffer
SwitchRes: Setting option -syncrefresh
SwitchRes: Setting option -waitvsync
SwitchRes: Setting option -nohwstretch
SwitchRes: Setting option -keepaspect
SwitchRes: Setting option -nofilter
SwitchRes: Setting option -prescale 1
Video: Monitor 002581E4 = "\\.\DISPLAY1" (primary)
Direct3D: Using Direct3D 9
window_proc: WM_NCACTIVATE
blit_lock = TRUE
Direct3D: Configuring adapter #0 = Radeon X1300 Series
Direct3D: Using dynamic textures
Direct3D: YUV format = UYVY
Direct3D: Max texture size = 4096x4096
Direct3D: Device created at 640x240
blit_unlock = TRUE
RawInput: APIs detected
Input: Adding Mouse #0: Mouse compatible con HID
Input: Adding Gun #0: Mouse compatible con HID
Input: Adding Mouse #1: Mouse compatible con HID
Input: Adding Gun #1: Mouse compatible con HID
Input: Adding Kbd #0: Teclado estándar de 101/102 teclas o Microsoft Natural PS/2 Keyboard
Input: Adding Kbd #1: Dispositivo de teclado HID
Input: Adding Kbd #2: Dispositivo de teclado HID
Input: Adding Kbd #3: Dispositivo de teclado HID
DirectInput: Using DirectInput 8
window_proc: WM_PAINT
blit_lock = FALSE
window_proc: WM_PAINT:END
stream_buffer_size = 37888
DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channels
Region ':maincpu' created
Region ':gfx1' created
Region ':ymf' created
Region ':eeprom' created
Starting Tetris the Absolute The Grand Master 2 ':'
  (missing dependencies; rescheduling)
Starting SH-2 ':maincpu'
Starting Serial EEPROM 93C56 (256x8) ':eeprom'
Starting Buffered Sprite RAM ':spriteram'
Starting Video Screen ':screen'
Optional device 'finder_dummy_tag' not found
Starting gfxdecode ':gfxdecode'
Starting palette ':palette'
Starting Speaker ':lspeaker'
  (missing dependencies; rescheduling)
Starting Speaker ':rspeaker'
  (missing dependencies; rescheduling)
Starting YMF278B ':ymf'
Starting Tetris the Absolute The Grand Master 2 ':'
  (missing dependencies; rescheduling)
Starting Speaker ':lspeaker'
Starting Speaker ':rspeaker'
Starting Tetris the Absolute The Grand Master 2 ':'
Loading data from EEPROM region ':eeprom'
Average speed: 98.33% (170 seconds)
Switchres: restoring DALDTMCRTBCD640x240x0x60 - Modeline "640x240_60 15.65KHz 59.96Hz" 13.02 640 664 728 832 240 242 245 261   -hsync -vsync
Sound: buffer overflows=6 underflows=0
window_proc: WM_NCACTIVATE
blit_lock = TRUE
window_proc: WM_DESTROY
blit_lock = TRUE
.
« Last Edit: January 20, 2017, 11:32:41 am by beaches »

beaches

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 9
  • I want to build my own arcade controls!
Re: Games with ISSUES: report here!
« Reply #216 on: January 22, 2017, 05:42:27 pm »
Done : I have made a tgm2.ini file with resolution 320x240 and now works properly. Thanks

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 5540
Re: Games with ISSUES: report here!
« Reply #217 on: January 23, 2017, 03:42:51 pm »
Done : I have made a tgm2.ini file with resolution 320x240 and now works properly. Thanks

The blue screen on your TV probably means it doesn't accept the input frequency. This would make sense because tmg2 is outputting 61 Hz (beyond NTSC). However, if forcing 320x240 fixes the issue, then I must be missing something.

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

SpaceGod

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 39
  • I want to build my own arcade controls!
Re: Games with ISSUES: report here!
« Reply #218 on: February 26, 2017, 05:47:08 pm »
im having problems with win10 crtemudriver 12.6.1(hd6970) with tekken 3 with 15khz pvm. the game runs super slow and it doesn't run slow on linux using my lcd.

donluca

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 94
  • I want to build my own arcade controls!
Re: Games with ISSUES: report here!
« Reply #219 on: March 21, 2017, 01:34:30 pm »
Albeit not an issue specifically with GroovyMAME, does anyone know what's the state of emulation for wait states on CPS1 and CPS2 hardware?

big10p

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 555
  • Mmmm, arcade classics!
Re: Games with ISSUES: report here!
« Reply #220 on: May 07, 2017, 09:58:49 am »
I'm getting a weird error with GM 0.183 and Salamander 2. The game works OK with mainline MAME 0.183 on my PC, but with GM in my cab, one of the ROMs fails the boot test as BAD, and the machine reboots and repeats. I copied the romset from PC to cab, so they are identical.

EDIT: It's sorted now. I had an NVRAM save that was from an older version of GM. Deleteted it, and now it's working.
« Last Edit: May 07, 2017, 03:32:34 pm by big10p »