• 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 ... 45 46 47 48 49 ... 316 Next »

iPega Extendible - Analogue Sensitivity problems
View New Posts | View Today's Posts

Thread Closed 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Thread Modes
iPega Extendible - Analogue Sensitivity problems
02-27-2019, 12:45 AM
#1
dlads Offline
Junior Member
**
Posts: 45
Threads: 6
Joined: Apr 2010
hi all,

have my android phone set up pretty much perfect for every game i play, but one thing i've noticed is the analogues, both left and right are not exactly the most sensitive and do not replicate the actual feeling of a normal pad, other games and applications which allow me to test the pad, does indeed show that the analogues are both acting normally and do have a full range on each stick, but dolphin simply does not utilise it. 

They are definitely seen as axis and not digital buttons in dolphin but they are certainly not right, so you are either dead center or with a little movement at around 70 - 80% movement, moving all the way on any stick does go to 100% but the subtle movement which should register do not.

Is there a way to alter this range? or it's sensitivity? 

This is apparent in both the official and none official versions of the dolphin application. 

Phone: Huawei P20 Pro - rooted running AOSIP
Controller: iPega Extending pad - bluetooth
Dolphin version: 5.0-10172-mmj (this is Zhang Wei's custom version, which is brilliant btw)

I have the pad connected via bluetooth and it is seen as a control pad, android testing applications do see the full range on either stick, they see all the buttons and everything else works as expected.

I can use the on screen controls for a greater degree of control when required, ie: windwaker when aiming mirror reflections in the 1st sage temple, but i would like this to be functional with the pad.


Does anyone know if there is anything that can be edited or any values that can be added? 

According to the config files in /dolphin/config/gcpadnew.ini there is a max range which is set at default of 100.000000, no deadzone is listed and no range provided.

Any help would be greatly appreciated.

Many thanks.
Find
02-27-2019, 09:15 AM (This post was last modified: 03-01-2019, 07:30 AM by Billiard26.)
#2
Billiard26 Offline
Developer
**********
Developers (Some Administrators and Super Moderators)
Posts: 2,660
Threads: 8
Joined: Feb 2010
I'm looking through the Android related input code and I think I've noticed an issue but I lack the proper hardware to test.

Can you please try the following settings in your GCPadNew.ini and let me know the results?

Main Stick/Calibration = 200
C-Stick/Calibration = 200

Edit: The issue should be fixed by this change https://github.com/dolphin-emu/dolphin/pull/7829 (not yet merged into master)
Find
03-05-2019, 04:42 AM (This post was last modified: 03-05-2019, 05:02 AM by dlads.)
#3
dlads Offline
Junior Member
**
Posts: 45
Threads: 6
Joined: Apr 2010
(02-27-2019, 09:15 AM)Billiard26 Wrote: I'm looking through the Android related input code and I think I've noticed an issue but I lack the proper hardware to test.

Can you please try the following settings in your GCPadNew.ini and let me know the results?

Main Stick/Calibration = 200
C-Stick/Calibration = 200

Edit: The issue should be fixed by this change https://github.com/dolphin-emu/dolphin/pull/7829 (not yet merged into master)


Cheers mate, looks like that could be it, I've looked into all options possible from my end, will try what you suggested anyway, fingers crossed. 

Ok so I don't have calibration listed, as I said I'm using Zhang Wei's Dolphin version which offers superior performance.

He's the read out soon the file for pad one
[GCPad1]
Device = Android/0/Touchscreen
Buttons/A = `Button 0`
Buttons/B = `Button 1`
Buttons/Start = `Button 2`
Buttons/X = `Button 3`
Buttons/Y = `Button 4`
Buttons/Z = `Button 5`
D-Pad/Up = `Button 6`
D-Pad/Down = `Button 7`
D-Pad/Left = `Button 8`
D-Pad/Right = `Button 9`
Main Stick/Up = `Axis 11`
Main Stick/Down = `Axis 12`
Main Stick/Left = `Axis 13`
Main Stick/Right = `Axis 14`
Main Stick/Radius = 100,000000
C-Stick/Up = `Axis 16`
C-Stick/Down = `Axis 17`
C-Stick/Left = `Axis 18`
C-Stick/Right = `Axis 19`
C-Stick/Radius = 100,000000
Triggers/L = `Axis 20`
Triggers/R = `Axis 21`
Triggers/L-Analog = `Axis 20`
Triggers/R-Analog = `Axis 21`
Triggers/Threshold = 90,000000
Rumble/Motor = `Rumble 700`

I could only assume that radius is the variable which I could alter.

Will test and report.

PS shall I add these values? I'll try.

Update: nah mate, didn't change anything, I can still play just I am missing analogue accuracy so I use the touchscreen for certain things where needed, not too up to speed with the inner workings of dolphin, but I'm assuming commits are made and added to a base (master) then to be used for Devs and enthusiasts to make their own versions.

Perhaps then Zhang had already added it? I'll have a nose.

Appreciate you checking by the way.

Also the lines that I added "C-Stick/Calibration = 200" were removed on launch of the emulator, could try to make it read only but may cause issues.
Find
03-05-2019, 07:09 AM (This post was last modified: 03-05-2019, 07:11 AM by Billiard26.)
#4
Billiard26 Offline
Developer
**********
Developers (Some Administrators and Super Moderators)
Posts: 2,660
Threads: 8
Joined: Feb 2010
I've confirmed with another developer that this is the source of the problem.
The "Calibration" setting was added in 5.0-9599.
It seems whatever version of Not-Dolphin you are using does not support "Calibration" if it is being removed on launch.

Calibration at 200 is of course a workaround though. The proper fix will be by the merge of: https://github.com/dolphin-emu/dolphin/pull/7829
Find
03-05-2019, 09:03 AM (This post was last modified: 03-05-2019, 09:04 AM by mbc07.)
#5
mbc07 Offline
Wiki Caretaker
*******
Content Creators (Moderators)
Posts: 3,520
Threads: 46
Joined: Dec 2010
I'm a bit late but you're not using an official build. Anything related to forked versions should go into their forum threads instead, so I'm closing this one.

Ask this in weihuoya thread if you need any further help...
Avell A70 MOB: Core i7-11800H, GeForce RTX 3060, 16 GB DDR4-3200, Windows 11 (Insider Preview)
ASRock Z97M OC Formula: Pentium G3258, GeForce GT 440, 16 GB DDR3-1600, Windows 10 (21H2)
Find
« Next Oldest | Next Newest »
Thread Closed 


  • 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