• Login
  • Register
  • Dolphin Forums
  • Home
  • FAQ
  • Download
  • Wiki
  • Code


Dolphin, the GameCube and Wii emulator - Forums › Dolphin Emulator Discussion and Support › Controllers v
« Previous 1 ... 215 216 217 218 219 ... 320 Next »

Metroid Prime - 360 Controller issue (Onza)
View New Posts | View Today's Posts

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Thread Modes
Metroid Prime - 360 Controller issue (Onza)
07-04-2013, 05:25 AM
#1
mgysgthath
Unregistered
 
The controller is a Razer Onza BF3 Tournament Edition (X360 Controller drivers/equivalent).

I've configured Metroid Prime (Gamecube) and it runs well, sound and all.
I have set up the controller and it works well, except for one thing.

When in Scan Visor mode, and holding Right Trigger to aim up at a scan point higher than yourself (pushing on the left analog stick to aim), then trying to press and hold the Left Trigger to scan the object, the view pans back down rather than scanning -- as if you let go of the left analog stick. This means I cannot scan items higher than head level.

It has been a while since I've played Metroid Prime on the Gamecube, but unless I'm forgetting something; That shouldn't happen.

Any advice?


Attached Files Thumbnail(s)
   
Reply
07-04-2013, 05:09 PM (This post was last modified: 07-04-2013, 05:11 PM by pauldacheez.)
#2
pauldacheez Offline
hot take: fascism is bad
*******
Posts: 1,527
Threads: 1
Joined: Apr 2012
Ah, good ol' analog/digital shoulder button issues...

The GameCube controller's shoulder buttons have two parts, an analog part that measures how hard you're pressing the button and a digital part that's triggered when you press all the way down until it clicks. Dolphin lists the digital parts as "L" and "R", while the analog parts are obviously labeled as such.

Now, the game (from my experimentation) doesn't enjoy it if you press the digital parts separately from the analog parts or if you press the analog part and the digital part at the exact same time. Your controller seems to be configured so that either a) the latter happens, or b) pressing one of the shoulder buttons unpresses the other (because they're on the same axis). Right-click on the buttons for some ridiculous advanced options, and after poking around a bit it should be pretty obvious what you have to do: in case A, make it so that the digital buttons are only activated once you've pressed the buttons down far enough, or in case B, find separate axes for the two buttons or find out how to make Dolphin read the + and - separately without mashing them together.

Of course, you could also just get lazy and map the digital parts to LB/RB and map Z to the Back button, but then you'll have to remember to press down LT/RT before pressing LB/RB to avoid stupid bugs.

Oh, and I forgot to mention – you're using an old build of Dolphin from an old, decrepit website. You can get much newer builds here: http://dolphin-emu.org/download/
<@skid_au> fishing resort is still broken: http://i.imgur.com/dvPiQKg.png
<@neobrain> dafuq
<+JMC47> no dude, you're just holding the postcard upside down
----------------------------------------
<@Lioncash> pauldachz in charge of shitposting :^)
Website Find
Reply
07-04-2013, 11:11 PM (This post was last modified: 07-04-2013, 11:16 PM by MayImilae.)
#3
MayImilae Online
Chronically Distracted
**********
Administrators
Posts: 4,604
Threads: 120
Joined: Mar 2011
Actually, pauldacheez is wrong.

Quote:The controller is a Razer Onza BF3 Tournament Edition (X360 Controller drivers/equivalent).

This is a classic problem with X360 controllers (and those that use the drivers, like my SCP driver running PS3 controller). Basically, on Dinput (and SDL apparently), the shoulder buttons share an axis. An axis is -255 to 255, so it splits it down the middle, one is -255 to 0, and the other is 0 to 255. Press both triggers down, and the shared axis reads as 0, as if neither were being pressed. Yea, it's stupid. Notice how, in your GCpad config image, L uses "Axis 2+" and R uses "Axis 2-"? That's it exactly. They are both Axis 2.

Use Xinput instead of Dinput or SDL. If your controller properly supports 360 controller drivers, then Xinput will have triggers that are individual axis, and you can set it up properly.
[Image: RPvlSEt.png]
AMD Threadripper Pro 5975WX PBO+200 | Asrock WRX80 Creator | NVIDIA GeForce RTX 4090 FE | 64GB DDR4-3600 Octo-Channel | Windows 11 22H2 | (details)
MacBook Pro 14in | M1 Max (32 GPU Cores) | 64GB LPDDR5 6400 | macOS 12
Find
Reply
07-05-2013, 12:20 AM
#4
mgysgthath
Unregistered
 
Success. Thank you Smile Xinput worked, once I remapped the controls.
(07-04-2013, 11:11 PM)MaJoR Wrote: Actually, pauldacheez is wrong.

Quote:The controller is a Razer Onza BF3 Tournament Edition (X360 Controller drivers/equivalent).

This is a classic problem with X360 controllers (and those that use the drivers, like my SCP driver running PS3 controller). Basically, on Dinput (and SDL apparently), the shoulder buttons share an axis. An axis is -255 to 255, so it splits it down the middle, one is -255 to 0, and the other is 0 to 255. Press both triggers down, and the shared axis reads as 0, as if neither were being pressed. Yea, it's stupid. Notice how, in your GCpad config image, L uses "Axis 2+" and R uses "Axis 2-"? That's it exactly. They are both Axis 2.

Use Xinput instead of Dinput or SDL. If your controller properly supports 360 controller drivers, then Xinput will have triggers that are individual axis, and you can set it up properly.
Reply
« Next Oldest | Next Newest »


  • View a Printable Version
  • Subscribe to this thread
Forum Jump:


Users browsing this thread: 1 Guest(s)



Powered By MyBB | Theme by Fragma

Linear Mode
Threaded Mode