Software Support > GroovyMAME

GroovyMAME 0.227 - Switchres v0.017t

<< < (240/241) > >>

schmerzkaufen:
Legacy obviously as I wrote twice, even used italics, and specified for Windows. It's still the main official release.

I haven't had time to try the 'new' one yet (you guys would maybe think about updating the build's name since as far as I understand it's quite different from the old design; GroovyMAME-X ? GroovyMAME-2X ? SuperGroovyMAME ?)
By the time 'new' is ready enough that Legacy can be discontinued for good, that'd be cool !

Also I'm kind of waiting to read Calamity's writeup before trying the 'new' Groovy, so I can maybe finally understand what it's about, as I could never read anything that actually explains it for ppl who aren't engineers, programmers, technicians or such IRL (so an explanation mainly for me since I'm practically the only member around who isn't one lol ;D)

schmerzkaufen:

--- Quote from: Calamity on January 11, 2021, 08:11:28 am ---- Slider enhancements (as requested by schmerzkaufen):
--- End quote ---

BTW note there are slider quirks that can be considered issues, though quite minor.

As I've observed before there's really two cases of wrong behaviour;

- When you first set a game's vsync_offset, exit and then select a different game to adjust settings on, the previous game's value will carry over and be assumed as the default (in place of 0), although nothing's written in the second game's config file vsync_offset line yet.
Somehow the value sticks temporarily within the UI's memory ? dunno how to call that, anyway that reminds me of the relatively recent fixed problem with the specific .ini files,  when settings were carried over the next selected game.
Restart MAME to get rid of the sticking values.

- When there's an additional file selected in between the games list and the launch of the game proper; like NeoGeo, if you select a different BIOS before starting a game another time, your previously set slider values will be gone.

Anyway those are minor annoyances, more like quirks that don't break using the sliders, I just thought they were worth mentioning in case ppl ask questions.

Substring:
The "new" GM uses a partly externalized switchres code. As you may have heard, Calamity made a library (understand some portions of code that can be used in other emulators) of the CRT resolution and computation part, so other emulators can enjoy this too (we've added it to Final Burn Neo, work is being done on mednafen). That library also has some little improvements here and there.

All in all, this also eases the maintenance of the core switchres code. This was a necessary change for the future.

There are still some cide parts that are specific to mame and that stay in mame (UI, vsync, command line switches, etc ...)

schmerzkaufen:
Sorry I don't understand most of your post. Porting CRT compatibility to other emulators, ok that I get is nice indeed!

Code news might be exciting for developers, but as an end user not knowing anything about that, all I can read is the same echo I got this past year and even before every time something about Groovy's development seemed to happen and ppl here got excited, yet every time I asked what was up all I got was the same kind of answers; vague, unrelatable.

In the past there was talk about things like beam racing, or making the frame_delay+vsync_offset relationship 'automatic', or even kill the remaining BGFX lag (eventually switching to BGFX as a whole with the same features and performance we get from 9ex now) etc

So I don't know, if you tell me it's more or less related to one of these I'll share the excitement, but as you guys present it now it's still too occult for me.

Understand that from an end user perspective the exciting recent (Groovy)MAME news were the vsync_slider, and update to CPU% one, both game-changing features I've been waiting to happen as the final touches that make Groovy definitely easily and useable in full without hassle (and for anyone down to complete noobs)

It's arrived kind of too late if you think community-wise and the aging crowd that lost interest in arcades emulation and even games period, for the remaining demographics still playing with emulators which is like 95% of end users if not more, RA finished establishing itself as the standard like 2 years ago and today it's not even worth arguing with them that there is something better out there they can use without needing to learn 5 pages of training, nor buy expensive FPGA setups, but still I'm glad it finally happened anyway.
(ps: that's not a criticism, calamity & helpers is only a semi-handful of ppl, can't be helped if neither MAME nor anything else can beat the RA train in popularity and activity speed. plus them, don't have much actual dev work to do in comparison)

Anyway for me it's full circle - as far as MAME and old designs go - from about 2005 when I started being annoyed with MAME's lackings, to Groovy 0.227, all the important boxes that needed to be ticked, have been by Calamity & Co.
(I'll write a summary of these soon)

Substring:

--- Quote from: schmerzkaufen on January 17, 2021, 09:52:07 am ---Sorry I don't understand most of your post. Porting CRT compatibility to other emulators, ok that I get is nice indeed!

--- End quote ---
At my level, can't tell more, because there is no other magic you may think of, as of today


--- Quote ---Code news might be exciting for developers, but as an end user not knowing anything about that, all I can read is the same echo I got this past year and even before every time something about Groovy's development seemed to happen and ppl here got excited, yet every time I asked what was up all I got was the same kind of answers; vague, unrelatable.

--- End quote ---
I really made a non developer explanation. If there were some new uber feature, I would have said it ;)

--- Quote ---
In the past there was talk about things like beam racing, or making the frame_delay+vsync_offset relationship 'automatic', or even kill the remaining BGFX lag (eventually switching to BGFX as a whole with the same features and performance we get from 9ex now) etc

So I don't know, if you tell me it's more or less related to one of these I'll share the excitement, but as you guys present it now it's still too occult for me.

--- End quote ---
If that's what you expected, still not done. Although we have internally discussed wuite much about it, it's still not there.


--- Quote ---
Understand that from an end user perspective the exciting recent (Groovy)MAME news were the vsync_slider, and update to CPU% one, both game-changing features I've been waiting to happen as the final touches that make Groovy definitely easily and useable in full without hassle (and for anyone down to complete noobs)

--- End quote ---
I'm on Linux, and not a hardcore tweaker at all. So these new features do not even concern me :) But Calamity has answered your call, enjoy!


--- Quote ---
It's arrived kind of too late if you think community-wise and the aging crowd that lost interest in arcades emulation and even games period, for the remaining demographics still playing with emulators which is like 95% of end users if not more, RA finished establishing itself as the standard like 2 years ago and today it's not even worth arguing with them that there is something better out there they can use without needing to learn 5 pages of training, nor buy expensive FPGA setups, but still I'm glad it finally happened anyway.
(ps: that's not a criticism, calamity & helpers is only a semi-handful of ppl, can't be helped if neither MAME nor anything else can beat the RA train in popularity and activity speed. plus them, don't have much actual dev work to do in comparison)

Anyway for me it's full circle - as far as MAME and old designs go - from about 2005 when I started being annoyed with MAME's lackings, to Groovy 0.227, all the important boxes that needed to be ticked, have been by Calamity & Co.
(I'll write a summary of these soon)

--- End quote ---
Things come when people have time. There is RA on one side (with a bunch of developers, nonnestly), MAME on the other (still quite a number of them). It's pretty easy for them to launch new versions with a bunch of astonishing features. And in the middle of nowhere in the emulation scene, CRT addicts. There is hardly any coder left for that, we're doing our best for new features, testing but ... Its some kind of knowledge that is extremly accurate and no one cares about it in 2020 but a few reluctant people who still think that CRT rocks for retro gaming.

So if it arrives too late, honnestly, why should we care ? That's our hobby, a way we spend our free time. We really don't care about that "mainstream emulation scene", so to speak. We play on CRTs dude, it's retro gaming on retro hardware almost :) We're dinosaurs ! So what ? Be happy we're still trying to improve GM, or CRT gaming in general. When I submitted the CRT port of Finab Burn Neo, devs were like "Yeah that's so cool ! Let me find the twitter password account we haven't used for years" (I'm not lying). There will be an alternative to RA for CRT, I do wish it, and it will happen.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version