Invert Y-Axis cannot be turned on when using touch controls on any platform, but works as expected with controllers

Confirmed on Nexus 5 on 12.1 release on Android 5.1.1

Notable that this option works correctly on the Windows 10 versions (I can specifically confirm that), but does NOT work on Android, back to build 1 according to the original filing of this bug.

I have no idea if it works/doesn't with controllers or anything else hooked up to an Android phone/tablet, but I can confirm it does not work with a Nexus 5 touchscreen. And since the poster above me there says it doesn't work on iOS, it's definitely something cross-platform, not Android-specific. Weird that it WORKS on Win10.

Some fragment of code that's exercised from input devices, but not from touchscreens?

I can confirm this is an issue on v 0.12.1 alpha on iOS.

This did work correctly on previous IOS pocket editions. I can't remember what version.
I can confirm that this is an issue on 'v0.12.1 alpha' on IOS and 'v0.12.1' on Windows 10.

It's interesting to me Leon Geyser that this bug doesn't exist for me with Windows 10 with a mouse, by which I mean the feature works both ways. Can you clarify in your comment if this exists with touch or mouse for you with windows 10?

I reported this issue for the iPhone version and told my case was a duplicate of this one. So I'm not sure if other people are having the issue with just the mobile versions or if it's windows 10 too. I haven't seen a response from anyone yet so I don't know if Mojang is even aware or if they knew and decided to patch it later.

On my Windows 10 tablet I only use touch input for Minecraft. I haven't tried connecting a mouse to see if the Y axis is correctly inverted for the mouse.

Leon, you've basically isolated it. I know the Invert Y-axis switch works for mouse on win 10, you say it doesn't work for touch for win10, and everybody else (including myself) know that it doesn't work for touch for mobile platforms either. The problem is that the code path for input devices checks the switch, but the touch path doesn't. And it also means that the problem is in the cross-platform code, not in platform-specific code (that's also important).

If I had the source I'd fix it right now. Sadly, not a Mojang employee.

When I updated to v0.12.1 alpha I had the same problem in which the "Invert Y-Axis" no longer works. This happened on both my ipad and iphone. In addition to that problem the "Split Controls" toggle doesn't work either. Can anyone help with this issue?

I am checking with Mojang to see if this (as well as autojump) are options that should apply to all input methods or if they are options that only apply when using external inputs like controller/keyboard & mouse. In previous versions (0.11, 0.10) these options applied to all input methods, but they certainly don't work now for touch input.

Having the same issue with v0.12.2 alpha running on Android 5.0.1, samsung note 4. Update came through the Google play store. Regardless of how the option is set, the y-axis will not invert.

Well in response to rplatham's comment, obviously this option existed before "alternate" methods were available at all. I guess gamepads existed on android/iOS (and should work with them), but still, it was predominantly touch, and it definitely worked before. I'm GLAD it works with the mouse on PC, but obviously still a rather bad bug that it no longer works with touch.

Still not fixed on 0.12.3 on Android with touch controls.

I think it only works with controllers. The auto jump toggle and the invert y-axis don't work with touch for some reason.

I also confirm it's not working on v0.12.3 on Android 5.0.1. This makes the game unplayable for me. Is this going to get assigned? Bug has been around since August.

This bug has made the game unplayable for me as well. Please assign the issue.

@unknown and @unknown, I am sorry, but assigning tickets in MoJira has no significance any more. I believe that voting for tickets still has some significance in terms of how quickly a ticket may be addressed.

How about changing the label above from "awaiting confirmation" to something else, since the Confirmation Status right below it is "confirmed"? Maybe to "affecting large swaths of players" or "makes game unplayable to many" or something else equally dire, as that's true?

Hey Kevin, thanks for the suggestion, but "awaiting_confirmation" is used internally and doesn't have anything to do with the confirmation status of the bug.

Confirmed to still be there on MCPE beta 0.13.0 alpha build 1 as tested on SONY SGP712.

Just to reiterate: This bug is a HUGE problem for those of us that play inverted. It makes the game almost unplayable. It's screwing up my gameplay on console now as I try (badly) to play without invert on MCPE, and then get confused when I switch back for all my other games.

To reproduce: Go to Options -> Controls -> Invert Y-Axis. Switch to On. Nothing changes. Switch to Off. Nothing changes.

Invert DOES work if you connect a controller. But 99.9% of MCPE users do not use a controller.

Confirmed still present in 0.13.0 alpha build 2 as well.

And I'll keep echoing others' comments as to just HOW critical this bug is. If anybody doubts it, imagine if it worked backwards for YOU, and they didn't fix it for 3+ months (this was introduced in the beta for 0.12). Now imagine our pain.

I am actively playing less because of this bug, and would NOT recommend the game in its current state because of it. I'm really only logging in to see if it's fixed. It isn't, so I stop playing immediately.

Confirmed - version 0.12.3 still NOT working on iOS 😞

I will reiterate Kevin's comments. I have stopped playing the game because of this bug. I pretty much only check on it when I get an email update to this forum post.

Still not fixed as of 0.13 build 3.

I'd also like to reiterate that this has broken the game for me. It shouldn't matter how many "votes" this has, it's a broken mechanic. If you have an invert axis option, it should work. I don't mean to be snarky but we've had an update or two now and it remains broken. I'd gladly give up the "crouch" button, bats that don't spawn, and boats just to have the controls back to where they were.

Confirmed in Alpha 0.13.0 build 5. They better gotta fix this bug for the release or else spamming via email will be the only way for them to notice, maybe.

Fox, look at the filing date on this bug: July 30th. It's been broken at least that long and they haven't noticed. If you have some way to get them to notice, DO IT. They're not going to on their own obviously.

And they don't even know they're losing players, which is the really weird part here.

They aren't worried about fixing this issue because they all ready have our money. My daughters and I haven't played the game since this has happened. Is there any way to get a refund?

Same here, my kids and I haven't played in months. Is downgrading to an earlier version possible?

The trouble with MCPE on iOS is that you cannot roll back to a previous version. Had I known that invert Y-axis was broken, I would never have updated to version 0.12.

I would rather have fewer features and invert Y-axis working so that I (and my daughter) can actually play the game.

@unknown You can get a refund from your store. Since we do not sell Pocket Edition directly - like Java version - we can't make a refund, but your store (depending on your device) will. As far as I know you have to contact App Store for a refund, and if this was Android purchase go to Play Store and request a refund within the app.

Please read the UPDATE before posting here.

Please install an earlier version on an android phone (I'm sure you have an earlier APK you can try). Invert the controls. Proceed to struggle. Now you will see why this bug will "make the game unplayable" as you say. For bonus points, play survival, wait until nighttime, and THEN do it. When the creeper/skeleton/whatever GETS you, and you are stuck looking at the floor/sky, you will REALLY understand.

That it's been ignored for 4 months makes it even worse.

And FYI, changing the state to "assigned" and showing us it actually is might help restore a bit of faith.

Thank you for the update, Aleksandra.

It's good to know that it's finally recognised as a bug. But, unfortunately, sounds like still quite a while until it's fixed 😞

I would disagree about this feature not breaking the game for some users. I have played with inverted Y-axis for many years (on all games) and find it unplayable without this feature. To me, the playing of the game is broken.

Guys, this is not a forum, please do not comment irrelevant information. As noted multiple times before: we do NOT assign bugs to developers anymore.

Still, come on, this feature worked in the past. This bug occurs because when the controller controls were implemented, they moved the Invert Axis code there and it is no longer executed on touch mode.

This bug is probably freaking easy to fix, I guess it can be made without any effort, and it is, as you wrote, REALLY frustrating. If the developers would just consider this, it would be fixed in a couple of seconds, but it looks like they are too lazy for this.

If only one of the developers would be playing with this option on, it would have been fixed since the start for sure. It REALLY BETTER GOTTA BE FIXED for the upcoming patch, because if you implement an option in a STABLE release as simple as that, it REALLY gotta be WORKING without problems.

The invert Y-Axis option is still not working for v0.13.1 alpha. Platform is Android 5.0.1 on Samsung Note 4 Verizon (SM-N910V).

Is there a way to become a beta tester?

Thanks,
Jason

Game is still unplayable: Bug confirmed in latest update, v0.13.1 alpha on SGH-T999 Android version 4.1.2 – I have not found a way to install a previous version of the game before the bug was introduced – is there a way to do this as a work-around until it is resolved? Several updates have been released since this bug was discovered but this problem has not been addressed.

I have looked into requesting a refund from Google, they state: "If Google Play's 2-hour return period has passed, the developer is responsible for deciding if you are eligible for a refund. Contact the app developer directly and ask for a refund. You can find an app developer's contact information listed on an app or game's detail page on Google Play."

Should we e-mail [email protected] to request a refund? That is the contact information listed in the Google Play store for Minecraft : Pocket Edition.

Still not fixed in new update, I can not understand why this does not get high prio as it frustrates a lot of fans en renders the game unplayable if you play like this for years !!!

The bad: Still broken in PE 13.1 alpha:

• IOS 9.2 ipad air

• Nexus 6 Android 6.0.1

The good: Premium skin packs are still being added! We all know how critical they are to game play.

Indeed, really embarrassing if you look at it this way.

Confirmed on iPad Air 2 iOS 9.2 Version 0.13.1

I have tried to retrain myself using the controls and can play to a point. This is bad from Mojang and leads to the question, why is it not possible to roll back to a previous version.

Hi, my name is Sean, and I've not played pocket edition in over three months. Please, please, PLEASE fix the Y axis, already! Sheesh.

Aleksandra Zajac, Thanks for the update but please reconsider the stance on prioritizing bug. A refund is an option, but better customer service would be to fix the bug. We don't want a refund, we want to play the game we like. We stopped playing because it's confusing. It's how we perceive and react whether it's touch, mouse or joystick. Thanks for your consideration.

Nice Comment by Rayan Mufti, it is actually really poor customer service to guide someone to seeking a refund.Deal with the Issue as a priority and in context. Dogs with white collars means nothing to many players, sort it out

Hello Aleksandra,

I understand how software issues get set aside sometimes, but please reconsider the priority of this issue. Many of us have been unable to play for months now.

This issue HAD a high priority and I am happy to say that I am testing new update and it seems to be working correctly.
I am testing 0.14 update INTERNALLY - please do no ask when it will be implemented because we honestly can not tell you.

Fixed in an upcoming version

when will the update come 0.14.0? is only ne question. The developer should please react.

Sorry Kevin, not even the developers know when the beta testing will be done. From experience helping with these beta tests, a very rough estimate is 3 weeks, but there's no guarantees.

@unknown you should read the comments before posting.

Now that it's fixed, can we have a separate invert y-axis setting for touch and controllers? I actually play with controllers and y-inverted, but when on touch, not so much.

@unknown Bug tracker is not a feature request forum, please refrain from comments like this.

It's not fixed, it's not resolved! It's STILL broken!

It's partially fixed in 0.14b6 on android. Well, fixed in an earlier beta, but there's still an issue: it's a cheat. If you swipe up (or down) quickly with the option enabled, the screen actually goes OPPOSITE of what you want (it moves like the option isn't enabled) for a fraction of a second, then "rubberbands" back, and functions "correctly" for the rest of your swipe, no matter how long you are pressing on the screen.

Try it. Not completely fixed. That "rubberband" is a symptom of their fix I think. Doesn't work as well/smoothly as it did prior to them breaking this back in 0.12 beta.

@unknown Can you explain how is it still broken for you, what phone are you using, what version of OS and which build? Please not that it was fixed for the current BETA version for Android. If you are not participating in beta tests for Android and you are using 0.13.2 it might not be fixed for you.

As per my previous comment two up (link) the "rubberband" problem still exists in beta 7 on android.

I have reported the rubberband issue - however it is not critical to fix. Thanks for your comments and I hope it will go back to the previously bug free state.

Is there another bug under which rubberbanding is being tracked? I would classify it as related to this bug (this fix introduced it) but I would also say it's not the same issue. Basically I'd like a public place to discuss it if necessary, as well as a clear place to point others who might want to file it. If they can't find it, they will keep filing new bugs!

There is no need to create another issue in the tracker, since it is not hard to reproduce, and it is not really considered a bug. I can only recommend creating a thread on Reddit and discuss it there - we do not allow discussions, suggestions and other off topics on Jira.
It was reported to the internal bug tracker and will be continued there.

I just downloaded and tested v0.14.0 on my SGH-T999, Android version 4.1.2:

• When Invert Y-Axis is turned off, it behaves as expected (not inverted)

• When Invert Y-Axis is turned on, when first moving up or down it behaves briefly like Invert Y-Axis is turned off, then reverses direction and moves inverted – this is as described by the beta testers in previous comments. I noticed that as long as I hold my thumb on the screen moving up and down continues to move in the correct direction (inverted). If I pick up my thumb and put it back down the first time I move up or down it briefly moves the wrong way at first, then corrects itself.

While not completely fixed, it does behave well enough that I can play the game, which I haven't been able to for over 6 months.

Thank you!