Screen Refresh slider: Groovy cake and eat it w/out custom modes/Emudriver ?

[Mike A]

You don't owe him any explanation.

When, how, and if you share information is completely up to you.

That guy is out of his mind.

[donluca]

Hopefully I'll not come out sounding like a ---meecrob---, but what baffles me most is why are we even discussing such things in first place.

This is the GM subforum and its threads should be about GM, not about how the developer should interact with the end user or whatever.

Do you want to let your opinions be heard on how you'd like communication between software developers and users to be handled?

That's great and an interesting topic (and pretty hot topic, especially regarding how dev teams like MAME communicate with the users and even other devs), but it has no place here, open it elsewhere.

You opened this thread providing information on using the Screen Refresh slider. You've done, as far as I can see, your research and various tests and the issues/limitations revolving around using this option has been discussed.

I respect any and all contributions, but really, we should make an extra effort to stay in topic and not waste the developer's (little) time in discussing topics outside of GM.

[schmerzkaufen]

I don't know what you're talking about mate. I didn't change my attitude to you

Shall I refresh your memory? from that post to bottom of the page.
http://forum.arcadecontrols.com/index.php/topic,157909.msg1677379.html#msg1677379
I just couldn't believe what I read, basically you see me as a guy playing an act to gain support from real geeks. When you're in my place reading that you gave all the reasons to feel unwelcome.

That's how the '2019 year in Groovy' started for me and yes indeed you blanked a couple PM's and many questions after that, all year long, even simple stuff or the rare times you did react sounded like it annoyed you to death to reply to me.
Many if those occurences where at times you were around the forum and still managed to speak with/reply others but mine even very mundane questions were ignored.

Sorry but, you know even I as a user have a life (people always make it sound like only developers have one) and often I can't do much in several months as well, but I can at least always answer "sorry no time to reply, very busy times", or "I don't know but no time to look into it probably later this year just remind me", things like that.

I actually did what I could to contribute and help even at my low level, I dedicated time and actually quite a bit of money (not just the donation but more hardware to test and verify things), I helped other users here and elsewhere, many hours dedicated to that just like you did for me, which I considered sharing what you did for me with other to be a just return of things, and I promoted the qualities of GroovyMAME everywhere and time I could.

Also as I said giving maybe a couple times a year an indication of where Groovy's going to even just to inform the users like me who aren't geeks but only enthusiasts, doesn't hurt, here you did it in one line.

For me, having a feature planned for a couple of years in the future means "not-too-distant future". So, if that's good to you as an answer, then yes, that's my plan.

Is it unreasonable and abusing a developer to ask such short general project information update, like every 6-8 months maybe so that users can know the project's not dead? I said it even if it's to tell its slow bc dev and contributors are busy, no one would blame you guys for that, on the contrary you'd get encouragements.

---

@Mike, and it's because of ass*les like you, proudly being ignorant do*chebags to people, that communities, and society in general, make people feel so unwelcome and the mood the shittiest it can be. Be useful to humanity; kindly fall off a cliff, pathetic entitled as*wipe, who the f do you think you are?


--


I get that, flats panels side of groovy is an annoyance, a petty unskilled user like me is seen as an ungrateful leech, that's how this dusty nerds community sees things. my enthusiasm: murdered, congratulations boys.

Well, f*ck BYOAC.

[Mike A]

@Mike, and it's because of ass*les like you, proudly being ignorant do*chebags to people, that communities, and society in general, make people feel so unwelcome and the mood the shittiest it can be. Be useful to humanity; kindly fall off a cliff, pathetic entitled as*wipe, who the f do you think you are?

So does that mean you are not going to ass ram me with a cactus?

[schmerzkaufen]

No to begin I offered you to f yourself with it. * should have made that clear, don't want to get near your filth. I can mail the tabasco tho.

Welp. If one last useful thing I've learned about this 'community', is what the 'A' in 'Mike A' stands for.

Bye.

[Mike A]

Well it is about time you figured out the A stands for "awesome".

I will be expecting that Tabasco sauce before Christmas.

[Calamity]

I don't know what you're talking about mate. I didn't change my attitude to you

Shall I refresh your memory? from that post to bottom of the page.
http://forum.arcadecontrols.com/index.php/topic,157909.msg1677379.html#msg1677379
I just couldn't believe what I read, basically you see me as a guy playing an act to gain support from real geeks. When you're in my place reading that you gave all the reasons to feel unwelcome.

All I see there is a friendly exchange. I just attempted a joke so all, you included, could laugh. It didn't work.

I leave it here.

[Trnzaddict]

Calamity -

So as a Gsync user is there absolutely anything I could benefit from GM anymore as far as input lag? Frame delay does not apply to vrr users correct?

I’d love to start using mameui again.

[Recapnation]

Try this:

https://emulationrealm.net/downloads/file/1221-m-gui

[Calamity]

Calamity -

So as a Gsync user is there absolutely anything I could benefit from GM anymore as far as input lag? Frame delay does not apply to vrr users correct?

I’d love to start using mameui again.

Frame delay does not apply to VRR users. Now as of 0.216 baseline MAME with the -lowlatency setting should be on par with GM in terms of latency, but *only* for VRR monitors. So your MAMEUI must be based on 0.216 or later.