GroovyMAME 0.227 - Switchres v0.017t

[Sociopathos]

THANKS!!!! 

[Doozer]

GM unified branch ? Can you elaborate ?

The idea would be, instead of different GM approach under Windows and Linux, to have a single switchres library with OS wrapper to expose internal API. Development is still in early phase. Don't expect something soon.

[Substring]

The idea would be, instead of different GM approach under Windows and Linux, to have a single switchres library with OS wrapper to expose internal API. Development is still in early phase. Don't expect something soon.

Ah yeah, Calamity told me once about that. I gave it the libswitchres name rather
Not my that C skills are worth it, but if I can help in any way ...

[b4nd1t0]

nonag versions win/linux ready https://b4nd1t0.blogspot.com/2019/06/mame-0210.html

[Calamity]

GroovyMAME 0.211 is out!

[lettuce]

So been a good while since i have used GroovyMame, what the latest version what settings do i need to change in the ini file to get the best results with an LCD screen (1440p 144hz) and getting the best possible reduced input lag?

Also what is the bgfx mod exe file do/for?

[Substring]

MAME 0.212 is out ^^

[b4nd1t0]

hI @Calamity, are you planning to release a new patch or we can compile the 0.212 with the 017n? Thanks 

[haynor666]

Did it patch 211 work for 212? I have many errors diff.

[Calamity]

I'm releasing a new patch, 0.017o, it'll be ready in a while.

[b4nd1t0]

Great, thanks.

[Doozer]

I'm releasing a new patch, 0.017o, it'll be ready in a while.

I nothing has changed for Linux, I can upload the 0.17n version. I saw 0.17o but did not checked the diff.

[Calamity]

I'm releasing a new patch, 0.017o, it'll be ready in a while.

I nothing has changed for Linux, I can upload the 0.17n version. I saw 0.17o but did not checked the diff.

The new patch changes the bgfx backend which also applies to Linux.

[Calamity]

GroovyMAME 0.212 is out!

What's new in Switchres v0.017o (August 2019)

- Reduced input latency for the BGFX video backend with vsync enabled. Measured latency is now 2 frames lower on Windows (not tested on Linux yet). Using DwmFlush() on Windows for vsync. [oomek/Calamity]

[lettuce]

Can you explain whats the difference between using BGFX or D3D, does one have an advantage over the other?

[oomek]

BGFX backend has more advanced and multiplatform shaders. D3D has HLSL shaders and works only on Windows.

[ph111hud0]

Question !
GroovyMAME 0.212   for windows 10 anywhere??

[schmerzkaufen]

Download link is on page 1.

[ph111hud0]

I have seen the download link, but the file is for windows XP not windows 10 ?

[schmerzkaufen]

Did you grab the right one ? (win-7-8-10)

[ph111hud0]

got it thank you

[Trnzaddict]

hI @Calamity, are you planning to release a new patch or we can compile the 0.212 with the 017n? Thanks 

Hey - I always download your builds to use on my cab, but on your latest 212 windows build the nonag patch doesn't seem to be working. Still nags about "There are known problems with this game. blah blah blah"

[b4nd1t0]

Sorry, i have uploaded, the wrong version, now is ok, thanks.

[Recapnation]

I'm about to update Eiusdemmodi's GM guide (for real!) and I'm including a Port Audio section. What's the final word on the -priority setting, 1 or 0? Seems low audio latency configurations are better with it (1) but it also could even mess with your input? I never noticed control or threading issues myself with it, but thought I'd better ask here.

[schmerzkaufen]

FYI as per 0.212 there's a new setting for Portaudio which I believe is 0 (? to confirm)

a special low latency mode has been added for the PortAudio sound module.

Code: [Select]

-Added an ultra-low-latency mode for PortAudio sound output module.
Couldn't find more explanation.

EDIT: also here compiled all (afaik) notes by intealls on settings http://forum.arcadecontrols.com/index.php/topic,160094.msg1684615.html#msg1684615

[Recapnation]

0.212's ini options seem to be the same, though?

Code: [Select]

# PORTAUDIO OPTIONS
#
pa_api                    none
pa_device                 none
pa_latency                0

[schmerzkaufen]

Maybe in 'mode' they mean 'setting' and 0 is that new one. Not sure just assuming. ¯\_(ツ)_/¯

EDIT: found more in the mame info:

Suggestion for very-low-latency mode on PortAudio. Needed to keep audio in sync when playing rhythm game machines such as Konami System 573. This is because the lowest audio_latency currently supported (audio_latency 1) introduces at least 10 ms of variable latency. I am unsure how to go about this without breaking backward compatibility so I set it to work only when audio_latency is 0 (which was previously ignored by mame itself and was treated equivalent to audio_latency 1). I am aware that setting audio_latency to 0 is not supported by many mame frontends, but this change seems natural. Otherwise, would it be better to add a new mame.ini option, or to automatically enable this low-latency mode when pa_latency is set lower than, say, 0.01 (10ms), which would break people's configurations if they already rely on the old behavior? (sound\pa_sound.cpp).

[Recapnation]

audio_latency 0, then.

https://github.com/mamedev/mame/commit/1ccdfb873a480c0306ac0553cf9298036f79d2d7#diff-1366df4e746fbede41c717eaa3aa00fe


I guess it was finally added in 0.212, but it could change later on? Though if '0' worked as '1' before this, nothing is lost by suggesting this.


Thank you.


(The question about -priority still applies.)

[schmerzkaufen]

Yeah sounds like it could change later.

(The question about -priority still applies.)

If you check the link I edit-posted up there, intealls only said the following afaik:

- One thing to keep in mind with low-latency audio is that it is important to have as few other applications running when using it. For instance, only have MAME running, and if problems are encountered, try using -nosleep and -priority 1.

[Recapnation]

Yeah, thanks; that was my understanding, enabling it only if there're "problems" since everybody suggests to leave it disabled. I was wondering if somebody has ever noticed issues by enabling it with GM (and no frontends, if possible).

[Rupert H]

GroovyMAME 0.212 is out!

What's new in Switchres v0.017o (August 2019)

- Reduced input latency for the BGFX video backend with vsync enabled. Measured latency is now 2 frames lower on Windows (not tested on Linux yet). Using DwmFlush() on Windows for vsync. [oomek/Calamity]

Hi Calamity,

Assuming complete ignorance on my part, can you explain what this BGFX change means? I have GM64 d3dex 2.06 running on Windows 7 on CRT on a cab. Will 2.12 give me minus two frames of lag compared to my current set-up? How do I implement this? Do I just download the latest build and I’m good to go or do I need to make new changes to the .ini file?

Thanks for all your hard work as always.

Rupert.

[schmerzkaufen]

Today I went back to trying Groovy on my laptop (W8.1, i3-4030u 1.9GHz 2core+HT, nVidia Optimus), and with 0.212 I've noticed frame_delay is completely unuseable as even 1 makes all games crawl at a fixed 50% speed.

I've tried older builds to verify and the last one where frame_delay is useable is 0.205 (which would make it the last 'lighweight' frame_delay version)

Is this related to the changes started back then ?

GroovyMAME 0.205 is out!

What's new in Switchres v0.017m (December 2018)

- Added feature to autosave UI sliders to make frame delay in-game adjustments non-volatile.

- (Windows) Added capability to toggle frame delay from the UI.

- (Windows) Preliminar work on modifications to the frame delay implementation to improve its accuracy.

- (Windows) Temporarily dropped BFGX support due to upstream overhaul.

[cools]

Frame delay works fine for me in 211, W7 x64 4690k 6450.

[schmerzkaufen]

Yeah works fine for me too on my 'real' PC.

It's just that at some point he said frame_delay was going to weigh a heavier load, which might be imperceptible to powerful-enough CPUs, but could explain that sudden change bewteen 205 and 206~212 for weaker ones.

Maybe it's that, maybe not, I'm simply curious.

[Substring]

Mame 0.213 is out !

[Doozer]

Just for fun. It is the first time I am experiencing several segfaults due to ASM opcode not being executed correctly in a kvm. Even after reboot of the host, result was the same. Now switching to another machine.

Code: [Select]

[ 2819.252872] RIP: 0010:kvm_arch_vcpu_ioctl_run+0x19b1/0x1b00 [kvm]
[ 2819.252883] Call Trace:
[ 2819.252901]  ? kvm_vm_ioctl+0x80a/0x980 [kvm]
[ 2819.252904]  ? __switch_to_asm+0x34/0x70
[ 2819.252905]  ? __switch_to_asm+0x40/0x70
[ 2819.252917]  kvm_vcpu_ioctl+0x22f/0x5e0 [kvm]
[ 2819.252919]  ? __switch_to_asm+0x34/0x70
[ 2819.252920]  ? __switch_to_asm+0x34/0x70
[ 2819.252921]  ? __switch_to_asm+0x40/0x70
[ 2819.252922]  ? __switch_to_asm+0x34/0x70
[ 2819.252923]  ? __switch_to_asm+0x40/0x70
[ 2819.252924]  ? common_interrupt+0xa/0xf
[ 2819.252926]  do_vfs_ioctl+0xa4/0x630
[ 2819.252930]  ? security_file_ioctl+0x12/0x50
[ 2819.252931]  ksys_ioctl+0x60/0x90
[ 2819.252933]  __x64_sys_ioctl+0x16/0x20
[ 2819.252935]  do_syscall_64+0x5f/0x1a0
[ 2819.252937]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 2819.252939] RIP: 0033:0x7f9b8bcac0fb


[Calamity]

GroovyMAME 0.213 is out!

[Calamity]

Just for fun. It is the first time I am experiencing several segfaults due to ASM opcode not being executed correctly in a kvm. Even after reboot of the host, result was the same. Now switching to another machine.

Do you mean with version 0.213?

[Doozer]

Yep, that's what happen when using old host (Core2 duo) with new kernel (5.2) ;-) No worries, I managed to do it differently.

[Doozer]

GroovyMAME 0.213 is out!

The Linux binary is uploaded as well.