Main > Software Forum
My official MAME output wip thread.
Xiaou2:
With your Hook program, there could be a checkbox option to auto-calibrate
motors... which would then have to go thru game specific procedures that
you have stored as some sort of .ini data text file...?
In reality, if one were to build an actual simulator, they would most likely want to
hook up all the limit switches, so that the thing didnt over-grind when it reached
end-of-travel.
But for a rumble-pad or test situation, it would be different, and thus a false
calibration would work fine.
Haze:
--- Quote from: Howard_Casto on April 19, 2010, 12:41:42 am ---Well I've got good news and bad news. The good news is I fully figured out the outputs for afterburner. The bad news is it doesn't matter because we can't use them.
Ever noticed where all the limit switches for afterburner are forced on? They are that way to keep the game from erroring on boot. If you turn them all off you also get an error.
The only proper way to pass the motor test on boot is to hook all four switches up to inputs and rapidly toggle the left and right limits until left and right show "good" on the screen and then do the same thing for up/down. This simulates the motors running to their full limits.
This will give us positional data as an output. But not speed.
The only way to get speed is to hook up the positional reads for both motors. This really isn't the correct way to do it. This is, however how gloc is hooked up... I might look at it to figure out how to get this working.
That motor test on boot is the problem though. With all the limits off you error out.. with them all on you don't get any data.
Any ideas??
--- End quote ---
I imagine you'll run into similar problems with things like GTI Club. I believe the 'wheel error' you get on startup is because the game is using the force feedback control to move the wheel, then expecting data read back from the wheel position to show that the wheel has moved and reached it's limits (within a defined range). There is no way this can be hooked up using MAME's current systems, and it will be even harder to map to anything except the original device if you want FF to work (because every non-original device will have very different behavior)
For simple cases, as you've found, it can be pretty simple to hook up lights and outputs, but for others the solution isn't really obvious.
Sorry, I don't really have any good solutions for you, but there is no generic 'right' answer here from what I can see.
Howard_Casto:
I'm less worried about making a generic solution than I am breaking the game. MAME is primarially a documention project as you know and by that path all the limit switches I've found should be hooked up. But that would "break" the game. Is that really a good idea? I mean it isn't like afterburner would be unplayable.... changing the cabinet type dip to "upright" will disable the motor check and allow the game to play normally I can imagine the backlash of hooking it up though and the unending questions of "Why isn't afterburner working?" ect... ect...
I didn't bother to hook up the limit switches on the yboard for this reason and because most of the games worked anyway. I figured that would be the way to keep it because anyone attempting to hook it up to a simulator rig would have hard-wired limit switches that have nothing to do with the game's feedback anyway.
Generally the game is still playable even if the motor test errors out though, it's just the motor test takes MUCH longer than it normally would. So I don't know, I just need advice on how to proceed.
bdam:
Would this be a situation where a default NVRAM would help?
Howard_Casto:
Not really...... a savestate might work though that starts the game after the motor check has already passed.
See like I said, a generic solution isn't that much of an issue, I just don't want people getting up in arms on how I "broke" afterburner.
I'm going to hook up the motor read values tonight and map them to the joystick to see what kind of data I can get. That'll let me know if it's even worth pursuing.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version