N64 controller Analog stick problems
 

Hi, i ordered a Mayflash USB N64 adaptor, a popularly used one as far as i can tell, a few days ago and just started using it with my snazzy clear purple controller (the stick is barely even loose after years of use). I came on here looking around to see how to configure it, and if i need to update the plug ins for what pj64 1.6 comes with. Which ive done, upgrading nrage to 1.83. Anyways, after setting the controls up i went to play Banjo-Kazooie to test it out.. Every button works as it should, except that the buttons seem to feel like they are being mashed repeatedly (ex: Banjo would jump when i pressed A, but instantly turned into the hover jump [double A]. The only solution i found was press lightly and fast, a hard task to master for playing a game... I also have another problem that might be connected to this, my control stick doesnt respond the way it should. Up is up, down is down, ect. but it only lasts for a second (Banjo will turn the desired direction, but not walk or run).

Any ideas??:confused: I can't be the only person who has ever had this problem. At least i hope not... And I am dreadfully sorry if this is a frequently asked question.

Oh, forgot to mention, im running this on WINE, if that matters.

WINE being a windows emulator, yes? We don't really support that, but the only reason that would stop us from being able to help is if that was the problem (which it most likely is.)

1.83 is the latest version that was created by the original designer AFAIK. A dood named Rabiddeity and our very own Squall_leonhart created a newer version, which you can download here.

Go ahead and install that, and make sure that the controller is calibrated.

Yea, well WINE doesnt "emulate", but thats basically the idea. Idt WINE is the problem, just thought I should say just to be sure. Thanks for the nrage download though! I hope that I just calibrated it wrong.

the mayflash adapters are sometimes unpredictable though

How so? Because it appears in the pj64 config settings, it just doesn't work 100% correctly in the actual games.

WINE IS AN EMULATOR
regardless of what those faggot winerdevs say.

I suppose it is, but not in the way others are. Converts most stuff to unix, at least as far as I understand it. I think that technically doesn't make it an emu, but it does the same thing so for most people its interchangeable, unless you are doing something like really complicated on it.

Well there are different devices an emulator uses; for example it doesn't always have to act as a virtual machine for a completely different system.

Semantically though, we get to exclude a most common context and use that to say it's not an emulator.

Don't know the details though quite honestly since I haven't used it.

Its been a while since i posted this so idk if anyone will notice, but in hoping that someone does...

I am no longer using Linux on my computer, and so I wanted to try at this emulator business again. You guys said that WINE was most likely the problem, so I assumed it would work this time. Thing is, I have the same problem that I did before. Anything else I could try?

I just started with MayFlash adapter and a real N64 controller myself, and I have the exact same issue. Every movement, even the joystick, is treated like a rapid button press, not like holding the button down or holding the joystick in a direction. This makes it impossible to use. For example, in Goldeneye, if I hold R to use the aiming reticle, it flashes constantly instead of remaining solid. Also, if I try to turn, it might jerk a couple inches to the side, but then doesn't move any more. I am running this on a brand new Alienware M14x with Windows 7, so I know that's not the issue.

The turn-only and no walking issue you were describing is either a hardware issue with whatever exotic controller you may be using (keyboard ftw), or maybe you just have N64 range turned down. In either case try turning it way up, and it may be a bit more playable.

The button auto-mashing is definitely unusual; I would have to say that must be a device/driver issue.

Mayflash sucks.

Sorry, but I read Mayflash problems like that a lot.