Main > Software Forum
.117u1 and What it means to control viewers...
Howard_Casto:
Ok the time is finally here.... as of .117u1 the new input system is finally out. I haven't really ran it through it's paces yet, but from what I can tell it's really good.
Ok I'll just post the quotes and explain what this means to our community (in terms of changes and improvments)
-----------------
Added two new options: -multikeyboard and -multimouse. By default,
both options are OFF. When OFF, the core will combine all keyboard
or mouse input into a single keyboard or mouse device. When ON,
these options instruct the core to keep inputs for each keyboard
and/or mouse independent.
------------------
Ok first off, you know a few months back how the new "improved" mouse system came out and totally ruined it for those of us with a single trackball/spinner/whatever? Well this fixes it. Just as I suggested way back then, the raw-mouse code is finally optional! The new multi-keyboard is fairly useless from my point of view (who needs more than 256 inputs?) but since it's optional it won't hurt anything. Viewer devs will have to add support for multiple keybaords eventually, but as-is, things should work with the current setups.
-------------------
* Added new option: -joystick_map. This option allows for a 9x9 grid
to be specified which controls analog-to-digital mapping of
joystick inputs.
-------------------
Now I haven't played with this yet, but this is frikkin awesome! For those of you who don't get it... Now you can use an analog joystick for a shifter, make custom plates, and map a DIGITAL shift button to each position! Bascially it means one shifter to rule them all.
I have no clue how it's implemented, I'll have to really look at it. No clue how this could be addded to controls viewers.
Judging by the replies, this is more of an analog-to-digital converter, al-la the "sticky" option, but more advanced. In theory it could still be used for such a thing, but not exactly in the way I described.
It's more for blocking out directions for 4-ways and 45 degree 4-ways and what-not.
------------------------
* Changed the Windows implementation of input handling to fully
support the raw input interfaces for keyboard and mouse.
DirectInput is still used for all joystick inputs, as well as for
keyboard and mouse inputs on pre-Windows XP systems. This allows
for multiple keyboards and mice to be supported. Also changed
keyboard and mouse behavior to use non-exclusive mode in
DirectInput, and to keep the devices alive during pause for more
consistent input handling.
------------------------
This one is very specific to devs... basically it means you can send input to mame in a more reliable manner, which is a good thing. Again, I haven't tested it yet, so it might end up making things worse, but from what I get, it's a good thing.....
So good news all around... I'm no expert on any of this, but post your questions and I'll try to answer them or get them answered.
Angry_Radish:
Sounds VERY interesting!
Thanks for filtering it so it makes sense to me :cheers:
headkaze:
--- Quote ---This one is very specific to devs... basically it means you can send input to mame in a more reliable manner, which is a good thing. Again, I haven't tested it yet, so it might end up making things worse, but from what I get, it's a good thing.....
--- End quote ---
Actually it's the opposite AFAIK. You can send input to Mame in current versions but you can't send input to the RAW input interface. I believe it was the GetAsyncKeyState() code in wininput_poll() that made it possible previously. Mame not being in exclusive mode doesn't really mean much for sending keys either, it just means you can use DirectInput to READ input at the same time (non-exclusive). But sending input through the DirectInput interface is as hard as it ever was. CoinDrop is the only app that ever did it and it used APIHook to inject keycodes into the IDirectInputDevice_GetDeviceState() function.
Oh btw I have started work on the Mame Input Bible, just finding it hard to get time to work on it. I'm going to put as much info as I know into it then send it to you. These latest additions will obviously add another level of information to cover, but it shouldn't be too hard to figure out eventually.
Thanks for the update.
MKChamp:
Not sure if this is an issue for anyone using Johnny5...maybe I am running an old version...but anyways...
With the new 'mame' browser, just running mame.exe no longer gives the verison info...it now launches the browser. The easy fix (for me anyways) was to blank out the getVersion.bat file (which is generated dynamically by Johnny5) and then set the attributes of it to read only.
Hope that helps anyone that may be in the same situation I was in.
headkaze:
It will probably have to change to "Mame.exe -help"
Navigation
[0] Message Index
[#] Next page
Go to full version