Main > Driving & Racing Cabinets
Outrun on MAME0151 and mamehooker: a first attempt
BadMouth:
--- Quote from: baritonomarchetto on November 21, 2013, 03:15:21 pm ---racermame151
--- End quote ---
;D Thanks for making that available. :cheers:
Hunk_4TH:
--- Quote from: baritonomarchetto on November 21, 2013, 03:15:21 pm ---You need both mamehoker and racermame151
--- End quote ---
Thanks, though I never really had luck with getting 360 controller working with this. Under "show supported devices" it doesn't list my 360 controller under force feedback devices.
Howard_Casto:
If you are talking about mamehooker, it won't show up as a force feedback device, it'll show up as a 360 controller because 360 controllers do NOT support FF! They support xinput rumble, which is an entirely different protocol that I support.
Xiaou2:
Technically speaking... any controller that creates a vibration is often thought of as being Force Feedback. Its logical its description of what it does. Its a device that creates forces, as feedback to whats happening in game.
Generally, people do not tend to think & speak about devices by their protocols, and even many companies may have advertised them as such, before the lawyers piped up.
http://www.amazon.com/ISHOCK-GAMEPAD-IMAC-FORCE-FEEDBACK/dp/B000YL9A1A/ref=sr_1_2?s=electronics&ie=UTF8&qid=1385136450&sr=1-2&keywords=gamepad+force
So, when people are using software, trying to get their controllers to be seen for what they Do... they are expecting it to show up as some sort of force feedback device. Even if thats not the exacting protocol.
For such a case, a simple User friendly statement such as: (Rumble Feedback Support) would be enough to clear up any confusion.
However, the program should and would have to lump all protocols into a single programs.. else nobody would think to fire up various other programs to detect other protocols. This is very basic user friendly interfacing, thats used on pretty much everything and anything out there for the masses. As not everyone is an OCD hardware / software nerd.
Howard_Casto:
If someone else wants to build an all inclusive hardware solution that I've put as many man hours into and release it for free they are welcome to label things however they like.
I segregate these devices purposefully because they don't use the same protocol and require different settings by the user to achieve the same effect. This is also all spelled out in the readme.txt... all one would have to is actually read the documentation provided.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version