Main > Main Forum
Ultimarc rotary encoder issues
<< < (2/6) > >>
Ed_McCarron:

--- Quote from: Derrick Renaud on April 06, 2007, 12:41:22 pm ---So I only get a chance to work on the code when the time and motivation is right.

--- End quote ---

And, the majority of us realize this and applaud you (and the others) for it.

Thanks!
Derrick Renaud:

--- Quote from: Ed_McCarron on April 06, 2007, 12:56:19 pm ---
--- Quote from: Derrick Renaud on April 06, 2007, 12:41:22 pm ---So I only get a chance to work on the code when the time and motivation is right.

--- End quote ---

And, the majority of us realize this and applaud you (and the others) for it.

Thanks!

--- End quote ---

You are welcome.  :)

Just some further clarification.

I never took anything in this thread as a personal attack against me or any of my code.

I was just trying to clarify why there are inconstancy's in MAME.  Every forum on the internet that mentions MAME, always attacks MAME for being inconstant in their policies.  While forgetting that they are pointing out 1 small thing in 6000+ games.  And not realizing how easy it is to miss something in MAME's huge multi-megabyte source code.

So when people mention that X has been done, so that means MAME should allow Y.  Talk like that usually means that X is removed too.  It's just easier to fix that way.

FWIW, I want to see the analog menu completely removed.  The name is confusing.  In it's place would be a control X setup menu.  That means when you go to the player controls menu, instead of seeing Player 1 Trackball X analog, inc, dec items, you would see a Player 1 Trackball X setup item, that would bring up another menu that would group the analog input with the inc/dec buttons and the items from the analog menu (Digital Speed, Sensitivity, etc).

D.
MaximRecoil:

--- Quote from: Derrick Renaud on April 06, 2007, 02:36:10 pm ---I was just trying to clarify why there are inconstancy's in MAME.  Every forum on the internet that mentions MAME, always attacks MAME for being inconstant in their policies.  While forgetting that they are pointing out 1 small thing in 6000+ games.  And not realizing how easy it is to miss something in MAME's huge multi-megabyte source code.

--- End quote ---

Those inconsistencies in policy would probably not be brought up all that often if it were not for all the disciples who preach with fervor the "For Preservation, Not For Gameplay!" gospel. For example:


--- Quote from: Extreme8 on April 04, 2007, 12:06:31 am ---Mamedev wouldn't care if NONE of the games run on current hardware. Their stated mission is to preserve these classics in as close to original form as possible.
The fact that hardware has progressed to the point that many of them are usable is just a bonus.
Those that don't contribute to the cause (and I consider myself among that number) should just be grateful that we are reaping the benefits of their work.

"Boo-hoo-hoo, Pacman is only 3 times faster than it needs to be. If those know nothing devs didn't mess with the code it could be 5 times faster than required, then the world would be all rainbows and lollipops."

Gimme a break.
--- End quote ---
ahofle:

--- Quote from: Derrick Renaud on April 06, 2007, 12:41:22 pm ---There are all sorts of features I want to add to MAME.  If anyone wants to pay my yearly wage so I can quit my job and solely work on MAME, then these features will get added quicker.  Until then, just like anyone who has added code to MAME, I have real life issues to attend to.  So I only get a chance to work on the code when the time and motivation is right.

--- End quote ---

If I were rich I would do just that.  Seriously.
Your work is much appreciated.  In addition, you are very civil to users despite owing them nothing.  I can only imagine how hard that must be given that I write software in the real world for users I can't stand.  Thanks for all your work.
 :cheers:
Rip:

--- Quote from: 2600 on April 06, 2007, 11:50:54 am ---Are you actually using MAME > 113?  If not, you will not get a 1 to 1 click setting.

If you think it is the Encoder, then try a keyboard to prove that it is either the encoder or joystick.

--- End quote ---

Yes.  I am using 113u2 (MAME32) and using the positional setting games.  Here is how it behaves.

In Guerrilla War (gwar):

Regular keyboard gives a 1 for 1 click (using the [ and ] keys)
Ultimarc encoder (USB) misses clicks consistently (but not always the same place)

In notepad:

Regular keyboard seems to generate a 1 for 1 click (using the [ and ] keys)
Ultimarc encoder (USB) gives a perfect 1 for 1 click

So I am stumped.  It can't be the encoder because it works flawlessly outside MAME.  It can't be MAME because the regular keyboard seems to work.  ???

Could it be a USB conflict within MAME?  Does MAME recognize one USB HID (my regular kb) over the Ultimarc HID (the encoder)?  Maybe a DirectInput issue?

p.s. - I am not dumping on the devs...just curious and looking for any tips.  This may force me to crack open the once and for all.
Navigation
Message Index
Next page
Previous page

Go to full version