Main > Main Forum
720 Real/Joystick/Spinner Test
<< < (18/30) > >>
Derrick Renaud:
To further the technical discussion:

The latest idea to use the -joy & -mouse options to select between options in the driver code would be refused.

Options should not be used in this way.  They are used to tell the MAME core how to operate, not game code.  Not one file in the src\mame directory accesses options using options_get_string()  The -joy & -mouse options tell MAME that these devices are hooked up to the computer.  Not how a game is to behave.

Doing so limits the user.  If it was done with the -joy options, then you are forcing the user to use the joystick simulation, when maybe they are using -joy just to use the inc/dec buttons on their joystick.

As for fixing the sprite flicker, submit the code as everyone has told you.  I do not make the MAME decisions.  The submissions are sent to everyone on the team for discussion.
Haze:

--- Quote from: Xiaou2 on January 25, 2011, 02:18:16 pm ---5) Neither Haze nor Derrick are in charge of the Driver Inclusion.  A good submission will be handled by the project leader.

--- End quote ---

Decisions tend to be delegated to those who have actively worked on an area of the code.  Derrick, being an actual developer has direct access to SVN, and can check changes in directly.  Aaron handles very little directly, there are many areas of MAME, he can't possible make decisions regarding every single one because he doesn't have the knowledge to do so (I doubt ANYBODY knows the entire MAME code-base inside out)

As a developer Derricks decisions are trusted.


--- Quote from: Xiaou2 on January 25, 2011, 02:18:16 pm ---6) Derrick is much more willing and flexible to adding things and helping out than Haze.
While you and him might not completely agree... you might be able to learn and share from each other ... IF... you can calm your attitude down.

--- End quote ---

It's Derrick's area of the code, had you come to me with problems more related to my areas of the code I'm sure you'd find me to be just as helpful at getting them sorted out.  I've worked with plenty of people in the past doing just that.  IOW you found the right guy, the one who knows and understands that code well, and can make + approve appropriate changes as well as reject ones that seem inappropriate whereas I could only give you the overall policy.  This is what has happened.

Derrick came here of his own accord.
Derrick Renaud:
Let's throw this thread sightly off topic.

MAME - the conspiracy.

I know everyone thinks that MAMEdev is some huge corporation that holds closed meetings and mainly discusses how we can torment the public.  We revel in keeping all the good drivers to ourselves, etc.

But truth be told, it is just a mailing list that loosely keeps things together.  Prove that you are a useful contributor and won't run amok with the code and you are in, if you want.  Then you too will get all the hidden drivers, ROMz, Babez, etc.

Actually, sorry to disappoint.  Being a DEV gets you nothing special.  No Babes, no hidden ROMz, etc.  You just get to help out more by giving your say on code in your area of interest.  Even then, the team leader has final say.  For this you get some public thanks and some public scorn, all while collecting a salary of $0,000.00.

Come join the team.

I started out just figuring out unknown DIPs.  I did not even know how to contact MAME and could not compile the code myself.  That DJGPP compiler kept crashing and I never once got it to work.  I believe Tiger-Heli or Triggerfin submitted my first attempts.  Then MAME switched from DOS to Windows.  While I'm never a big fan of the necessary evil that is Windows, at least with the new compile tools  I could now compile and test my own code.

From there I looked into how the sound system worked and figured out how do get sounds in the old games I was/am interested in.  I've played around with the input system due to my desire to make the controls better and easier to use.

All along the way I have received no money and nothing special from being on the MAME team that every other MAME user does not have access to.  Other then access to the mailing list, which needs to be private so we don't have to deal with stuff like what you have read recently on the forums.

So it really is just as simple as "Submit your code."  And yes we don't have the time to bother to respond to all submissions.  No one kept me up to date on anything I submitted.  If it was accepted, I would see it eventually in the MAME code.  Then look to see what they changed in it.  The changes gave me a better idea of how the team at the time liked things done.  I did not hate them for it.  I learned from it.
Derrick Renaud:
Now, sort of back on topic.

I did a quick patch to make Return of the Jedi easier to play with a mouse.  This will not be in the official MAME, but I am interested in other games that use that kind of throttle control for movement.  Speed increases only while moving stick forward.  Centering keeps at that speed.  Moving stick back reduces speed.

I'm thinking Paperboy speed axis, but don't know of any other games.

See the patch here:
http://forum.arcadecontrols.com/index.php?topic=108813.msg1155368#msg1155368
Gray_Area:
Is this thread still viable for driver/performance feedback? If so, I'd like to say that the 'joystick' option in current MAME doesn't seem to work very well, and works differently than the original analogue stick implementation.

In the new format, I had trouble getting very far in the game, because I had to hug the periphery of the stick's range. If I did not, there was a snapping movement of the skater toward the direction that my joystick next registered.

In the old analogue stick feature, I was able to get my highest score ever (50k+) using a digital stick.
Navigation
Message Index
Next page
Previous page

Go to full version