Main > Software Forum
My official MAME output wip thread.
Howard_Casto:
OK I went through all my changes and I'll make them into one big old diff tonight.
For the curious this is what I've done so far, not including my previous run that is already in the u2 build of mame:
==========================================================================================================
Output Cleanup/Hookup (Part 2) [Howard Casto]
-----------------------------------------------------
segas32.c: Hooked up all digital outputs for all games (radm, alien3, radr, f1en, arescue, f1lap, jpark, slipstrm, orunners, harddunk, scross, titlef)
Emulation needs to progress more on the analog output data before those outputs can be hooked up.
audio\mw8080bw.c: Changed output name for desertgn to something more descriptive (Player1_Gun_Recoil)
bbusters.c: Added new output handling functions and hooked up outputs for bbusters and mechatt
opwolf3.c: Added gun outputs for opwolf3 (man that game is terrible)
machine\willaims.c: Fixed existing outputs in tshoot (they needed inverted) and hooked up the rest, including the feather blower. :-D
gunbustr.c: Hooked up all outputs for gunbstr
namcos12.c: Hooked up outputs for all system 11 gun games. (ptblank2, ghlpanic, tenkomor)
segaybd.c: Hooked up all digital outputs (gloc, glocr360, gforce2, pdrift, rchase, strkfghtr), also hooked up motor/analog outputs for Power Drift and G-Loc/ Strike Fighter
The remaining games with motors could be hooked up as well assuming emulation can progress enough to get past the error messages.
namcos2.c: Hooked up gun recoils for golly ghost. Also noted that the outputs for the remaining gun games are also in that area. Someone who can find the offsets should be able to hook them up.
segas18.c: Hooked up gun recoils for lghost.
taito_z.c: Hooked up outputs for spacegun and made a few prototype functions to help in hooking up the remaining games. Someone familiar with the driver should take a look.
I hooked up a few, but they don't work like they should according to the comments.
==========================================================================================================
I don't think I'm done this build cycle though... I'm just done with the analog gun outputs for a while. There are around 20 or so hooked up now, so that should be enough to get people interested in adding recoil to their mame cabs ;)
I want to work on the remaining sega drivers next.
Now that I've done a few, I'm beginning to understand the strangeness that is sega hardware design and all the "segas" boards work similarly.
I would also like to finally hook up afterburner and friends assuming the emulation has the output data doing something. Those games use a similar drive system to gloc, so if we are lucky we'll still get output data despite the fact that the motor test screens give error messages.
Howard_Casto:
Ok... I cleaned everything up and sent it along to the mamedevs.
I'll update the first page accordingly.
Howard_Casto:
I'm currently looking at the sega x board driver. (Afterburner and friends)
Now that I'm strating to understnad how the mame source works it becomes apparent to me why my previous attempts at getting the remaining outputs connected have failed. Aaron installed a custom memory write handler for afterburner2 during it's startup. This is a much cleaner way to do things. (I wish I had thought of it when I was doing these other games... oh well). The problem is it only parses the single 16 bit line where the lamp data is held, and thus I will NEVER find the motor data in there. Fortunately the generic io function is still in place, and I can install outputs there to snoop around. I can make more custom io handlers once I find the data though.
I'm probably not going to attempt this atm.... I want to dig up some info on how the deluxe aburner cab worked.... pretty sure it's just a single motor on a worm gear for up/down movement and then the standard joystick feedback you see on the upright.
Howard_Casto:
I couldn't resist so I took a look at the xboard....
all-in-all a lot more has been figured out on this board than the y board.
I've already found all the digital outputs, including the vibration motor for super monaco gp. Can't figure out the air brake motors thought (for the deluxe cabinet) basically they error out in the service menu, meaning I don't have an easy way of figuring it out.
I haven't found the motor outputs for afterburner yet, but I have figured out why the output lamps don't work right for afterburner but they do for part 2... basically the outputs are shifted down a byte for the original, so it should be an easy fix.
Howard_Casto:
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??
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version