Main > Driving & Racing Cabinets
Universal Gear Shifter support in MAME discussion
BadMouth:
First step of the spreadsheet I've been talking about making is attached.
No controls are listed yet, but all the driving games supported by MAME (according to MAWS).
They are sorted by manufacturer and year. The drivers loosely follow that for the most part..
They are separated into 3 sheets based on their emulation status; good, imperfect, & preliminary.
I apologize for it being done with Excel XP, it's what I have and what I'm familiar with.
When it's more complete, I'll try to convert it to google docs or something.
It will give you an idea of how many different drivers there are.
I'm still pondering exactly how much information to include about the controls. It needs to be kept somewhat simple.
Right now I'm thinking-
Wheel: 360, 270, 900 or other
Pedals: Number of pedals, pot or switch based
Shifter: Number of gears, number of switches
Outputs: Lights, FFB, etc. This will probably be a fairly long description that you'll have to click on the cell to see.
I'll enter the controls haphazardly, starting with the most popular and the games that interest me.
jennifer:
Concern: Any colaborative efforts would be impeded by crossing OS"s.... I mean do we need to sync to one platform?
In another thread it was said 99% of dev"s use windows,.... Well considering the "bloat" maybe Lin\xp would be a better option.
Paul Olson:
I don't quite understand the bloat argument anymore. 1TB hard drives are less than $70, and computers in general are dirt cheap. A $200 computer will run > 90% of the games in MAME and it will come with Windows 7.
Accurate emulation is always going to be slower than the hacks. I would never consider accuracy as bloat. XP is almost 10 years old. There is no reason to write software with XP as a target, and Linux is covered in SDLMAME.
BadMouth - controls.dat and Howard's output project should help with your list. The official controls.dat required verification from the manuals, so should be pretty accurate.
For the optical controls, I think tooth count and encoder wheel diameter would be good to list.
For Analog, the travel range in hex would be nice. Most of that info can be found in the manuals.
Converting to Google Docs might be best. If I edit it with word 2010, it might mess it up for you. I think it is just one click to convert it. The more people that see it will allow for better error checking. MAWS will be wrong in a few cases most likely, but it is a great place to start.
BadMouth:
--- Quote from: Paul Olson on January 16, 2011, 02:57:42 pm ---BadMouth - controls.dat and Howard's output project should help with your list. The official controls.dat required verification from the manuals, so should be pretty accurate.
--- End quote ---
Thanks. I forgot about controls.dat
It's going friggin' slow using KLOV & barely readable manuals.
Most of the manuals aren't as comprehensive as I thought they'd be.
All I have so far is most of the old atari games. (atarisy2 & sprint2,4,8 drivers)
The sprint games are cases where we have a 4 speed shifter with only 3 switches in it.
4th is the default gear this time when nothing else is pressed.
The current mame UI shows 4 gears to map.
Thought I'd mention it if you want to look at the driver and get a feel for how it was handled.
--- Quote from: Paul Olson on January 16, 2011, 02:57:42 pm ---For the optical controls, I think tooth count and encoder wheel diameter would be good to list.
For Analog, the travel range in hex would be nice. Most of that info can be found in the manuals.
--- End quote ---
:angry: you for making sense & making more work.
I wanted to do the tooth count, but had forgotten about it.
Not sure how much I'll accomplish this evening.
I'll convert it to google docs & post a link later tonight when I've had enough.
EDIT:Not going to bother uploading anything tonight because I didn't get much more done. No sense in posting it in 1/8th increments.
huygens:
Tooth count for some of them is on the wiki.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version