Raw input in MAME

[dov_EL]

Is possible configure Raw input in MAME ? 

[DOS76]

These are where you would change the input I believe but don't have any experience in doing so.

-keyboardprovider

Chooses how MAME will get keyboard input.

On Windows, you can choose from: auto, rawinput, dinput, win32, or none On SDL, you can choose from: auto, sdl, none

The default is auto. On Windows, auto will try rawinput with fallback to dinput. On SDL, auto will default to sdl.

-mouseprovider

Chooses how MAME will get mouse input.

On Windows, you can choose from: auto, rawinput, dinput, win32, or none On SDL, you can choose from: auto, sdl, none

The default is auto. On Windows, auto will try rawinput with fallback to dinput. On SDL, auto will default to sdl.

-lightgunprovider

Chooses how MAME will get light gun input.

On Windows, you can choose from: auto, rawinput, win32, or none On SDL, you can choose from: auto, x11 or none

The default is auto. On Windows, auto will try rawinput with fallback to win32, or none if it doesn’t find any. On SDL/Linux, auto will default to x11, or none if it doesn’t find any. On other SDL, auto will default to none.

-joystickprovider

Chooses how MAME will get joystick input.

On Windows, you can choose from: auto, winhybrid, dinput, xinput, or none On SDL, you can choose from: auto, sdl, none

Edited June 4, 2017 by DOS76

[dov_EL]

But but .... 
In MAME 0.185 for for Joystick too . 
TRY !!! 

[DOS76]

Yeah I didn't notice there wasn't a raw input option for Joystickprovider so I don't know that the documentation is from 0.174 so it may be an option unless it was added since then

Edited June 4, 2017 by DOS76

[dov_EL]

I do not see any documentation, but I assure you it works fine.
I would like to have a way to perform a precision test to calculate the differences

[DOS76]

http://docs.mamedev.org/commandline/commandline-all.html

This is where I got the info I pasted. So you are saying setting it to rawinput it does work?

[dov_EL]

2 minutes ago, DOS76 said:

http://docs.mamedev.org/commandline/commandline-all.html

This is where I got the info I pasted. So you are saying setting it to rawinput it does work?

I do not know, I just tried it and it seems to work fine. I do not think it is my mental conditioning: D

[Lordmonkus]

I've been using this guys custom compiled version of Mame 186 where he has D3D9ex built into it which has lower input latency than the normal Mame and normal D3D. This custom compiled version has the nag screens disabled as well as really killer looking HLSL settings. If you decide to try it out generate your mame.ini file with the command mame64.exe -cc and then set your video to d3d and hlsl_enable to 1.

Watch this guys videos at your own peril, he comes off as a total prick but he knows his stuff.

[dov_EL]

11 hours ago, lordmonkus said:

I've been using this guys custom compiled version of Mame 186 where he has D3D9ex built into it which has lower input latency than the normal Mame and normal D3D. This custom compiled version has the nag screens disabled as well as really killer looking HLSL settings. If you decide to try it out generate your mame.ini file with the command mame64.exe -cc and then set your video to d3d and hlsl_enable to 1.

Watch this guys videos at your own peril, he comes off as a total prick but he knows his stuff.

On Bartop I use 0.185, and I assure you that if we write rawinput in the filename, we get the same result that we have in RAW backward.
It is not possible that it is just my impression: D
I want to see if I also find the Big Blue 0.185.
Thanks for the info !!

[Lordmonkus]

There is a difference in that custom compiled version I linked. It has d3dex support which reduces input lag but atleast 1 extra frame (16.67ms @ 60Hz) compared to the standard Mame build which doesn't have d3dex support built in.

And judging by the docs that @DOS76 linked Mame defaults to rawinput if it's available when set to auto.

Input lag is one of those things that isn't just one single thing that removes it or reduces it to its minimum, it's a combination of several different things that gets it to its lowest possible amount.

Edit:
You do get to a point though where you are shaving tiny amounts off where it can be imperceptible. The largest source of input lag is in the display you are using or it can be depending on what you are using. 

[dov_EL]

This is d3dex too ? 

 

[Lordmonkus]

That's from the same game so if you are using one of his custom compiled builds then you could very well be using a build that has d3dex in it. As far as I am aware of default Mame does not.

[dov_EL]

or this 

 

[Lordmonkus]

Skip in to 2:00 where he talks about d3dex.

I have no idea if his other custom builds have d3dex built in or not, I only know his 186 build does.

[dov_EL]

2 minutes ago, lordmonkus said:

Skip in to 2:00 where he talks about d3dex.

I have no idea if his other custom builds have d3dex built in or not, I only know his 186 build does.

Damn , is only 64 bit . My Bartop have Windows 10 Cu X86

PS http://forum.arcadeotaku.com/viewtopic.php?t=24216&start=600

[dov_EL]

Here http://forum.arcadeotaku.com/viewtopic.php?p=467305&sid=499887271aee80e554d3078fa0620864#p467305

[Lordmonkus]

Yeah, I have used GroovyMame in the past.

It got a little messed up back when Mame went full open source because some of the stuff in it wasn't open source. It may have gotten back up to speed though, I haven't looked at it in a while.

You could always just use Retroarch Mame as well with rawinput and its other input lag reduction.

[dov_EL]

No , groovy mame is for CRT

[Lordmonkus]

It was designed for CRT use but you aren't confined to CRT use only, it can be used with LCD displays.

[dov_EL]

4 minutes ago, lordmonkus said:

It was designed for CRT use but you aren't confined to CRT use only, it can be used with LCD displays.

I have real coin op too , , but i used (bad) Pandoras Box 4 , One day, inside I put a mini PC with launchbox, but I have to convert everything from Jamma