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

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

  

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

0 Members and 1 Guest are viewing this topic.

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 7411
  • Last login:March 14, 2024, 05:26:05 am
  • Quote me with care
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 of pasting it.

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

retrorepair

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 252
  • Last login:April 14, 2023, 04:49:58 pm
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
My arcade racing setup:
My Youtube Channel: http://www.youtube.com/user/RetroRepair
My Twitter: http://twitter.com/retrorepair

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
  • Last login:December 09, 2016, 10:40:11 am
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: 7411
  • Last login:March 14, 2024, 05:26:05 am
  • Quote me with care
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 of pasting it.

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

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 7411
  • Last login:March 14, 2024, 05:26:05 am
  • Quote me with care
Re: 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 of pasting it.

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

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
  • Last login:December 09, 2016, 10:40:11 am
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
  • Last login:December 09, 2016, 10:40:11 am
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: 7411
  • Last login:March 14, 2024, 05:26:05 am
  • Quote me with care
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 of pasting it.

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

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
  • Last login:December 09, 2016, 10:40:11 am
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: 7411
  • Last login:March 14, 2024, 05:26:05 am
  • Quote me with care
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 of pasting it.

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

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
  • Last login:December 09, 2016, 10:40:11 am
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
  • Last login:December 09, 2016, 10:40:11 am
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
  • Last login:January 03, 2016, 12:50:47 pm
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: 7411
  • Last login:March 14, 2024, 05:26:05 am
  • Quote me with care
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 of pasting it.

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

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 7411
  • Last login:March 14, 2024, 05:26:05 am
  • Quote me with care
Re: 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 of pasting it.

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

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
  • Last login:December 09, 2016, 10:40:11 am
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: 7411
  • Last login:March 14, 2024, 05:26:05 am
  • Quote me with care
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 of pasting it.

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

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
  • Last login:December 09, 2016, 10:40:11 am
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: 7411
  • Last login:March 14, 2024, 05:26:05 am
  • Quote me with care
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 of pasting it.

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

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
  • Last login:December 09, 2016, 10:40:11 am
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: 7411
  • Last login:March 14, 2024, 05:26:05 am
  • Quote me with care
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 of pasting it.

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

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
  • Last login:December 09, 2016, 10:40:11 am
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: 7411
  • Last login:March 14, 2024, 05:26:05 am
  • Quote me with care
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 of pasting it.

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

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
  • Last login:December 09, 2016, 10:40:11 am
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
  • Last login:December 09, 2016, 10:40:11 am
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: 7411
  • Last login:March 14, 2024, 05:26:05 am
  • Quote me with care
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 of pasting it.

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

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
  • Last login:December 09, 2016, 10:40:11 am
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: 7411
  • Last login:March 14, 2024, 05:26:05 am
  • Quote me with care
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 of pasting it.

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

ves

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 225
  • Last login:April 11, 2020, 02:57:49 am
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
  • Last login:December 09, 2016, 10:40:11 am
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: 7411
  • Last login:March 14, 2024, 05:26:05 am
  • Quote me with care
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 of pasting it.

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

Ansa89

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 377
  • Last login:December 09, 2016, 10:40:11 am
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: 225
  • Last login:April 11, 2020, 02:57:49 am
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
  • Last login:December 09, 2016, 10:40:11 am
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: 225
  • Last login:April 11, 2020, 02:57:49 am
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
  • Last login:December 09, 2016, 10:40:11 am
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
  • Last login:December 09, 2016, 10:40:11 am
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: 225
  • Last login:April 11, 2020, 02:57:49 am
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
  • Last login:December 09, 2016, 10:40:11 am
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
  • Last login:January 03, 2016, 12:50:47 pm
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