Software Support > GroovyMAME
Games with ISSUES: report here!
Calamity:
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.
retrorepair:
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:
BubbleBobble fail start:
--- Code: ---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
--- End code ---
Rom name: bublbobl
Videocard: ati radeon hd5450
Monitor: pal tv
OS: slackware64 13.37
Calamity:
--- Quote from: retrorepair 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
--- End quote ---
Hi retrorepair,
Do you mean a blue screen type crash, where the ati2mtag.sys file is mentioned as guilty or something different?
Calamity:
--- Quote from: Ansa89 on January 20, 2012, 09:20:16 am ---Rom name: bublbobl
Videocard: ati radeon hd5450
Monitor: pal tv
OS: slackware64 13.37
--- End quote ---
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.
Navigation
[0] Message Index
[#] Next page
Go to full version