Dolphin, the GameCube and Wii emulator - Forums

Full Version: Why the flying heck can't you guys fix the on-screen controls?
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3
Like compared to all driver workarounds, speed optimizations, etc, making playable on-screen controls isn't just a piece of cake, it's 100 times less complicated.

Jesus Mohammed. All you need is to give some options for the player, most notably:

1- Allow us to reduce the sensitivity of the analog sticks! Why is that so damn hard? That's all it takes to allow us to walk instead of running all the time.

2- Allow the analog sticks to be centered wherever our finger land! That would make a 1000 tons of difference. Just copy the style of every android game on the playstore, i.e. right half of screen is for looking around and left half is for movement.

3- Allow us to change the visibility of the controls. Does that need a reason?

4- Why the heck are on-screen controls shaped identically to physical buttons of the gamecube controller? What purpose does that serve other than being annoying and unergonomic?

5- And this is most important thing to make on-screen controls playable, allow us to join the R button to the right analog stick. Just check how any shooting game on android works. You have the right half of the screen for looking around, and you have a shooting button which when you press you also get to look around when firing. Thus you're able to aim and fire at the same time! If you don't know what I mean try playing Dead Effect (it's free on the playstore).

I can't believe the amount of apathy and indifference you people have towards the android port. Such a thing would make dolphin infinitely more playable for us who don't want the input lag of a bluetooth controller or don't have one to begin with.

And inb4, "If it bothers you so much fix it yourself". I only know how to print Hello World.
Pretty sure there is a way to ask for this without being rude...

Also, the project is open source. You can learn a thing or two about coding and then contribute by doing that.
I only know primitive C programming stuff like sorting arrays, files, and linked lists etc. I don't know anything about games, APIs, or how they work. But I'm pretty damn sure they're 100 times more complicated than fixing the controls. There are very expert programmers on here, and it would only take them a couple of hours to fix these controls if they really tried. But they don't give a damn about android so they won't.
(02-20-2018, 01:46 AM)biomedical1010 Wrote: [ -> ]Like compared to all driver workarounds, speed optimizations, etc, making playable on-screen controls isn't just a piece of cake, it's 100 times less complicated.

Jesus Mohammed. All you need is to give some options for the player, most notably:

1- Allow us to reduce the sensitivity of the analog sticks!  Why is that so damn hard? That's all it takes to allow us to walk instead of running all the time.

2- Allow the analog sticks to be centered wherever our finger land! That would make a 1000 tons of difference. Just copy the style of every android game on the playstore, i.e. right half of screen is for looking around and left half is for movement.

3- Allow us to change the visibility of the controls. Does that need a reason?

4- Why the heck are on-screen controls shaped identically to physical buttons of the gamecube controller? What purpose does that serve other than being annoying and unergonomic?

5- And this is most important thing to make on-screen controls playable, allow us to join the R button to the right analog stick. Just check how any shooting game on android works. You have the right half of the screen for looking around, and you have a shooting button which when you press you also get to look around when firing. Thus you're able to aim and fire at the same time! If you don't know what I mean try playing Dead Effect (it's free on the playstore).

I can't believe the amount of apathy and indefference you people have towards the android port. Such a thing would make dolphin infinitely more playable for us who don't want the input lag of a bluetooth controller or don't have one to begin with.

And inb4, "If it bothers you so much fix it yourself". I only know how to print Hello World.

Then it is time to delve more into developing and actually learn how to program, since according to you it is so fucking easy, instead of bitching about things that bother you.

Just to repeat what has said a 100 times before, and it seems like you know it has been said before:
1. There are only a few people working on the Android port
2. All of them are volunteers and thus do not get paid
3. Being a developer doesn't mean you understand all different platforms
4. All developers are doing this because they love programming and are allowed to select themselves what they work on and when they work on it. This keeps it fun for them too, setting deadlines or making them work on things they do not feel like working on will only drop even more developers.
5. In general Android drivers suck and no one feels like doing workarounds inside Dolphin for shitty drivers and devices
6. In general Android devices are still too slow to run anything reliably.
7. Developers just aren't interested in developing for Android
8. Harassing developers has never made them care more, if anything it will make them care even less.
So you saying that trying to make games run at acceptable framerates is fun for programmers but fixing broken controls is not fun, and this is why they will never fix them?

So how do we make fixing controls fun?
By not being a ridiculously obnoxious user, for starters.

In a more serious answer - stop trying to think you need to trick developers into fixing things you care about. You're not doing yourself any favors
(02-20-2018, 02:05 AM)Abiomedical1010 Wrote: [ -> ]So you saying that trying to make games run at acceptable framerates if fun for programmers but fixing broken controls is not fun, and this is why they will never fix them?

In my opinion, yes. So I used my time to improve the JIT and the execution speed on ARM64 devices. And I think the current state of the JIT is quite well. But I neither care about driver workarounds or the Android UI.

But two other people care about the Android UI, and they made a *great* progress in the last months. I agree on your suggestions, so I've forwarded it to one of those devs. We'll see if they want to work on the OSD controlls. IIRC one of them uses dolphin on his mobile, the other one on Android TV. So there is a chance they are motivated Wink

If you want to learn about how to program, just ask for support on our IRC channel. The Android UI is about 11k lines of java code, well isolated from all kind of emulation code. And you just have to download Android Studio and hit the compile button. And "it's 100 times less complicated" than the emulation part, so a nice task for beginner Tongue
(02-20-2018, 03:57 AM)degasus Wrote: [ -> ]In my opinion, yes. So I used my time to improve the JIT and the execution speed on ARM64 devices. And I think the current state of the JIT is quite well. But I neither care about driver workarounds or the Android UI.

But two other people care about the Android UI, and they made a *great* progress in the last months. I agree on your suggestions, so I've forwarded it to one of those devs. We'll see if they want to work on the OSD controlls. IIRC one of them uses dolphin on his mobile, the other one on Android TV. So there is a chance they are motivated Wink

If you want to learn about how to program, just ask for support on our IRC channel. The Android UI is about 11k lines of java code, well isolated from all kind of emulation code. And you just have to download Android Studio and hit the compile button. And "it's 100 times less complicated" than the emulation part, so a nice task for beginner Tongue
11 thousand lines of code?

Holy sh why would controls need that many?


Btw thanks for asking them. Tell me if they reply back.
(02-20-2018, 04:43 AM)biomedical1010 Wrote: [ -> ]11 thousand lines of code?

Holy sh why would controls need that many?

That isn't only for controls. That is *everything* for the Android UI.
(02-20-2018, 05:01 AM)degasus Wrote: [ -> ]That isn't only for controls. That is *everything* for the Android UI.

Where do I find the code for the controls? Give them to me. I don't. Care if it takes me 10 months I'll fix them.
Pages: 1 2 3