Sensitivity and using latest dev builds

[Bradleyw801]

noob: "WTF?! Why won't (insert difficult to emulate game here) run on my (insert weak phone with unsupported drivers here) PLZ FIX!!!!!"

dev: "Because dolphin for android sucks, always will suck, and always has sucked, and this will never change"

I have noticed that pretty much every new thread starts and ends that way, so I figured I better get that out of the way before posting my actual question.

My hardware is the Nvidia Shield TV, using the original Shield controller.

Now, my real question, I find that dolphin has been great for most of the gamecube games I run on it. But one issue for me is analog sensitivity. I have searched for a while, and maybe I am just dumb, but I can't seem to find a way to adjust that? My second question is, do you see any issue with me just periodically grabbing the latest autobuild and upgrading dolphin? I don't use savestates, so that's not a problem. It hasn't been an issue so far, but maybe I am better off checking in to see what the most stable recent build is?

Any help is appreciated. Thanks!

[JosJuice]

(10-03-2017, 04:48 AM)Bradleyw801 Wrote: But one issue for me is analog sensitivity. I have searched for a while, and maybe I am just dumb, but I can't seem to find a way to adjust that?

I'm not completely sure about this, but I think the sensitivity for physical controllers is adjustable in the INI files but not in the GUI, and the sensitivity of the on-screen controls isn't adjustable.

(10-03-2017, 04:48 AM)Bradleyw801 Wrote: My second question is, do you see any issue with me just periodically grabbing the latest autobuild and upgrading dolphin? I don't use savestates, so that's not a problem.

That's fine. The only real other problem with that is that each update will invalidate the shader cache, so you'll get some extra shader compilation stuttering the first time or so you play each game after updating, but it might not be that big of a deal. (Maybe the Nvidia Shield TV even supports ubershaders well? I can't recall)

[Bradleyw801]

(10-03-2017, 05:00 AM)JosJuice Wrote: I'm not completely sure about this, but I think the sensitivity for physical controllers is adjustable in the INI files but not in the GUI, and the sensitivity of the on-screen controls isn't adjustable.

I appreciate the quick reply! I found the setting in the ini file that I believe it is, it looks like it should be "Main Stick/Radius" under GCPad. Do you have any guess what I should change that number to? Right now it's " = 100 , 000000"

[JosJuice]

You can set it to any value between 0 and 100, but you shouldn't go close to 0 if you want to have playable controls. Try 70 or something like that if you want the stick to be more sensitive.

[Bradleyw801]

(10-03-2017, 06:22 AM)JosJuice Wrote: You can set it to any value between 0 and 100, but you shouldn't go close to 0 if you want to have playable controls. Try 70 or something like that if you want the stick to be more sensitive.

So if I want to turn down the sensitivity, do I go higher?

[Helios]

josjuice, I do believe the Shield TV supports ubers. It's just kind of useless because of GL/Vulkan stuttering and takes 7 years to compile.

[degasus]

(10-03-2017, 07:03 AM)Helios Wrote: josjuice, I do believe the Shield TV supports ubers. It's just kind of useless because of GL/Vulkan stuttering and takes 7 years to compile.

It just takes 2 minutes to compile, but without any visual progress report...

[Helios]

2 minutes is 7 years in 2017 technology

[mstreurman]

(10-04-2017, 06:31 AM)Helios Wrote: 2 minutes is 7 years in 2017 technology

My Pentium G4560 + GTX780 non-ti + 16GB + Samsung EVO 940 nVME also takes about 2 minutes to compile the ubershaders...