Software Support > GroovyMAME
Games with ISSUES: report here!
Ansa89:
--- Quote from: Calamity 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.
--- End quote ---
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.
--- Quote from: Calamity on January 26, 2012, 11:53:23 am ---Definitely don't have a clue with the other issue. Is the resolution actually set before mslug exits?
--- End quote ---
The monitor become black and I don't see nothing, so I don't know if the resolution change before groovymame gives up :-\ .
Ansa89:
Would resolve the problem, if I create a "ini/bublbob2.ini" with "modeline 0" (or with a fixed resolution)?
mazinger-z:
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:
--- Quote from: Ansa89 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)?
--- End quote ---
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?
Calamity:
--- Quote from: mazinger-z on January 30, 2012, 04:41:05 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.
--- End quote ---
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.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version