Hello all,
I said I had two separate issues I thought best to post as different threads, here is the second one.
Ever since I got to 3.0-4xx I have encounter a very annoying problem that nobody else appears to have. I have searched the forums and Google and come up with nothing.
I usally notice it in FPS games where you can iron sight/zoom in. When the L trigger is being pressed and you press the R trigger at the same time, it's like the L trigger is let go of and r is never pressed. Does that make sense? Haha, it's kind of confusing when I type it out.
Basically I go to use iron sights, and when I want to fire, it quite iron sights and doesn't even fire.
This is not just in FPS titles. It's any game that needs you to do this. Does anyone know what could cause this? All my computers have this problem, and all my controllers do. (Three separate ones) It has to be the emulator, I don't see how it could be everything else.
Thanks for any suggestions! Looking forward to hearing what you guys have to say.
- Angelus
It's probably your controller config. Check to make sure that the two triggers are set to only the "+" direction (for my gamecube controller on the Magic Joybox it is Slider 1+ and Slider 0+). I think your L config is messed up (like it says slider 1+ & !slider 0+ or something like that).
If that isn't it, then just try the official 3.0 build (or redownload it if you have already tried it).
Hey Axxer,
Thanks for the reply. That was a good suggestion. I gave it a try and it didn't seem to help though. what's odd is the two triggers work fine individually and in the little config menu both highlight in red when pressed. I don't get what's up. I just downloaded and did a fresh config of the latest x64 win build too. I can't go back to the official 3.0 as I've gained about 25FPS in total going to the current revision. I'm only at like 28-40 FPS on playable titles, so losing that much would kill it.
Thankfully this has not made a game unplayable, but it would be nice to have it.
Side note, and I'm sure this has been answered somewhere, but can you get trigger sensitivity in L and R? Like in Mario Sunshine, for the water pack? So you can run and squirt water?
Thanks for the help!
Post up a screenshot of your GCPad config window (on Windows use Snippet tool, on Mac keyboard shortcuts, and I don't know on Linux).
1. For your first problem: if you press and hold your left trigger while hitting your right trigger, does it stop working in the test area of GCPad config?
2. Trigger sensitivity is done by using the sliders, which you have to do by right click the "L-Analog" choice and selecting your left analog's "axis" or "slider" (just choose a slider that looks right and test; if it isn't it try a different one). The GC controller's triggers are weird in that they are analog at first and end in a button, so unless you use a third party program (such as GlovePIE which I believe does this) to first take your controller's triggers and say, for example that any value > 70% pushed in would be considered a button press and anything less than that analog, I don't think you will be able to get both the button press and the analog trigger to work in-game.
Hey,
First off thanks for the info on sensitivity. And you are right! Something is wonky here. In the GC Pad setup wizard thing it has the same problem. I press L and while holding L press R, nothing is pressed, even when I'm actually pressing them. I took a screenshot of my config though. this is how I've been setting up for YEARS. I don't know why it suddenly doesn't work.
I have also noticed this problem, it has to do with dolphin not allowing the emulated controller to accept 3 inputs simultaneously although it dosent happen all the time e.g performing a roll in skyward sword which involves move+dash+shake nunchuck, most of the time the shake nunchuck command is not accepted by dolphin.
That Axis 2+/- thing is kinda weird, but if that is what the PS3 controller does then ok.
I've never noticed this issue with Dolphin before, but I guess maybe it really does exist.
Interesting you have noticed this too Zee530. Thanks for letting me know I'm not the only one haha.
Axxer the controller is actually a MadCatz mini 360 (wired) controller. I don't know if that makes a difference. Also, would it be helpful to provide a text log of when playing a game so that someone can see what is going on when I get this error? If so how would I go about doing that?
Just submit a report at google code pages and hopefully one of the devs will look into it.
this isn't a bug
you are assigning the 360 pad via dinput. (technically, since SDL is layered over DX on windows)
the controller via this api treats the triggers as a single Axis and pressing both at once cancels them out
Switch the controller to xinput in the list at the top left