Software Support > GroovyMAME
GroovyMAME 0.287 - Switchres 2.22b
digitalwacker:
Hoping someone can let me know if I'm EOL with .227? Trying to use .229 with no luck. I'm using a 6530D. Works great up to .227. I tried updating the driver to 16.2.1, but not recognized. I wasn't sure if the drivers will be updated at some point for more cards? Any information is appreciated and thank you for everything!
--- Quote from: Calamity on February 05, 2021, 12:38:27 pm ---
--- Quote from: reeone on February 05, 2021, 01:58:18 am ---ATI/AMD ADL init
ERROR: ADL Initialization error!
--- End quote ---
Hi reeone,
Yes, in fact your card is using ADL. But now GM uses ADL2, and 12.6 is only compatible with ADL(1). This means 12.6 will now just work for legacy (pre-HD5000) cards (non-ADL). HD 5000+ cards will be forced to use 16.2.1. So we'll need to modify 16.2.1 files so it recognizes your card. It should support it already, but for some stupid reason Mobility models have usually been removed from the generic driver package. I only realise when someone with a Mobility card complains.
Well, to be honest I didn't anticipate this incompatibility with 12.6, but at least now people will move forward to 16.2.1 which works definitely better in general.
--- End quote ---
beernut:
--- Quote from: fred92 on March 22, 2021, 05:14:42 pm ---i wonder why we can't find the groovymame.diff on the new https://github.com/antonioginer/GroovyMAME/releases
--- End quote ---
Fred,
If you want diffs from github you just need to add .diff to the end of the compare url. Here are the diffs for GM 0.229 as compared to baseline 0.229
Here is the compare page on github:
https://github.com/mamedev/mame/compare/mame0229...antonioginer:groovymame0229
And here it is as a diff:
https://github.com/mamedev/mame/compare/mame0229...antonioginer:groovymame0229.diff
fred92:
thanks :applaud:
Calamity:
Just a note about v0.230: it will be delayed because at the moment I'm working on modifications to the sync options and settings are all over the place. I've found a way to re-implement "triplebuffer" without multithreading, based on D3D9ex only. There's another change in Linux to remove tearing on amdgpu. I want to have everything working correctly before the release.
schmerzkaufen:
You're the best. Maybe in a few years from now something like this triplebuffer (actually double? I still wonder) won't be needed at all anymore (thanks to a better software alternative from you guys or whomever, or a broader generalization of VRR hardware+soft)
But in the meantime it's still very useful.
Just yesterday I was fine-adjusting sync_refresh_tolerance to see how fast an acceleration is acceptable in general, and found that over 105% starts being too much, so I set 2.771 so syncrefresh at least covers Sega's classic system18 games @57.23
Beyond that limit which is close to halfway the 6Hz spanning from 60 to 54, there's really a lot of games for which Groovy's 9ex triplebuffer is the preferable solution, better than speed up or tearing.
NMK & UPL games, Raiden II & DX, most of the IREM catalog, Mortal Kombat series and many Williams & Midway games, Xexex, Raiden Fighters series a the bottom, and many more.
It's choppy and gives about 2 frames of delay (still unconfirmed yet this is what it feels like), but that's still better than dealing with 110% speed, or tearing, or the 3 frames of the 'normal' triplebuffer in other MAMEs.
Anyway great news.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version