[MCPE-9357] Invert Y-Axis cannot be turned on when using touch controls on any platform, but works as expected with controllers Created: 30/Jul/15  Updated: 10/May/17  Resolved: 25/Jan/16

Status: Resolved
Project: Minecraft (Bedrock codebase)
Component/s: None
Affects Version/s: 0.12.1, 0.12.2, 0.12.3, 0.13.0 Beta 1, 0.13.0 Beta 2, 0.13.0 Beta 3, 0.13.0 Beta 4, 0.13.0 Beta 5, 0.13.0
Fix Version/s: 0.14.0 Beta 1

Type: Bug
Reporter: TheOnePEGamers
Resolution: Fixed Votes: 21
Labels: None

Issue Links:
Cloners
is cloned by MCPE-11612 Invert Y-axis option is not working c... Resolved
Duplicate
is duplicated by MCPE-10515 Y-axis will not invert Resolved
is duplicated by MCPE-10519 Invert Y Axis not working. Resolved
is duplicated by MCPE-11071 Invert Look Function Not Functional Resolved
is duplicated by MCPE-11129 Not a duplicate. Invert look function... Resolved
is duplicated by MCPE-11949 Invert y still not working? Resolved
is duplicated by MCPE-12125 invert y axis stillnot working Resolved
is duplicated by MCPE-13295 Invert y STILL broken. Resolved
Relates
relates to MCPE-9378 Auto-jump cannot be turned off when u... Resolved
Confirmation Status: Confirmed
Platform: Phone - Android - LG Nexus 5
CHK:

 Description   

Invert Y-axis cannot be turned on when using touch controls on any platform. It works as expected when you have a mouse and keyboard or controller. Same problem for Invert Y-Axis option.

Original report:
there is a bug in 0.12 build 1 where Invert Y-Axis doesn't work nobody reported this yet, when turned on it has the same effect as it turned off

UPDATE by MissMarzenia
This issue has been reported as fixed for 0.14.0 beta. However players are still reporting it is not working as desired. We are looking into the issue. Please, try not to spam the comment section if you do not have bug related information.

Players who can't seem to play the game because of this issue can ALWAYS request a refund from the store they bought the game at (Amazon, Play or App Store).
Thanks for your patience.



 Comments   
Comment by [Mojang] MissMarzenia (Aleksandra Zajac) [ 23/Feb/16 ]

I am sorry to hear that this fix is not letting you enjoy the game. As previously noted this was already reported with high priority and the only thing we can do is just waiting for a more suitable fix. I am afraid I can not provide any more information.

Comment by Sergey Zakharov [ 19/Feb/16 ]

I will add that this same "rubber-banding" issue described with v0.14.0 with "invert Y-axis enabled" also affects iOS (all devices: iPad mini 4, iPhone 5s, iPad Air 2, all under iOS 9.2.1), and not just Android. While the invert-Y axis issue has in fact been corrected, there is now this rubber-band snap for a split second as if invert-Y has NOT been enabled, then snaps and inverts it. Yes, the game is now much more playable...but at the same time, this rubber-band snapping should not be occurring; it didn't occur before invert-Y was broken...it doesn't occur with invert-Y disabled.

Comment by Ian Ward [ 19/Feb/16 ]

I'm seeing the same thing. The bounce effect in v0.14.0 is very disorienting for me.

With invert-Y enabled the Y-direction is non-inverted for the beginning of the swipe before switching to inverted. For example if I make small quick view adjustments, swiping up looks upwards (non-inverted) but longer upward swipes twitch up then look down. The effect is to have my player's view end in a seemingly random place depending on how much of the movement was treated as non-inverted and how much inverted.

Is it possible to remove the delay from the beginning of the swipe until when the invert-y setting takes effect?

Comment by Alan Fasick [ 19/Feb/16 ]

New information: The version that was released this morning in the Google Play Store, v0.14.0 (not the beta that's been previously tested and noted here on this thread) has been confirmed to fix it on my SGH-T999 running Android version 4.1.2 which I confirmed earlier in the thread was not working on v0.13.1 alpha on SGH-T999 Android version 4.1.2. In my experience troubleshooting IT issues, I find it helpful to know that something that was confirmed NOT working is later confirmed WORKING with all other variables remaining the same (hardware, user and OS), if you do not find this useful I will not take the time to provide you this feedback in the future.

As far as why I could not play the game, have this broken for someone who is used to it is like using a computer with the mouse turned upside down. Yes, I could do it, but it is extremely difficult. Have you attempted to use the invert-Y option set opposite of how you normally play the game? If so, how long were you able to enjoyably play the game without getting frustrated? Maybe you adjust to doing everything upside-down from what you're used to than I am, but based on the feedback I've seen given to Mojang regarding this bug I don't think I'm in the minority.

Comment by [Mojang] MissMarzenia (Aleksandra Zajac) [ 19/Feb/16 ]

alan_f I don't understand how this is stopping you from playing the game. Please read previous comments before posting and consider not posting if there is no new information that have been reported and replied to previously.

Comment by Alan Fasick [ 19/Feb/16 ]

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!

Comment by [Mojang] MissMarzenia (Aleksandra Zajac) [ 15/Feb/16 ]

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.

Comment by Kevin Anderson [ 15/Feb/16 ]

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!

Comment by [Mojang] MissMarzenia (Aleksandra Zajac) [ 15/Feb/16 ]

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.

Comment by Kevin Anderson [ 12/Feb/16 ]

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

Comment by [Mojang] MissMarzenia (Aleksandra Zajac) [ 10/Feb/16 ]

Catweizle 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.

Comment by Kevin Anderson [ 09/Feb/16 ]

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.

Comment by Alex Good [ 09/Feb/16 ]

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

Comment by [Mojang] MissMarzenia (Aleksandra Zajac) [ 28/Jan/16 ]

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

Comment by Jayson Gallardo [ 27/Jan/16 ]

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.

Comment by [Mojang] MissMarzenia (Aleksandra Zajac) [ 26/Jan/16 ]

kevinreichart6@gmail.com you should read the comments before posting.

Comment by rplatham [ 26/Jan/16 ]

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.

Comment by Kevin Reichart (Inactive) [ 25/Jan/16 ]

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

Comment by Luis Robles [ 25/Jan/16 ]

Fixed in an upcoming version

Comment by [Mojang] MissMarzenia (Aleksandra Zajac) [ 25/Jan/16 ]

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.

Comment by Ian Ward [ 21/Jan/16 ]

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.

Comment by Senna Star [ 19/Jan/16 ]

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

Comment by Rayan Mufti [ 19/Jan/16 ]

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.

Comment by Sean Walker [ 02/Jan/16 ]

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.

Comment by Senna Star [ 21/Dec/15 ]

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.

Comment by Darren Woloshyn [ 21/Dec/15 ]

Confirmed on iPad Air 2 iOS 9.2 Version 0.13.1

Comment by Jorgen [ 20/Dec/15 ]

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

Comment by Rich Gudmunsen [ 20/Dec/15 ]

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.

Comment by Jorgen [ 19/Dec/15 ]

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 !!!

Comment by Alan Fasick [ 16/Dec/15 ]

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 mobile@mojang.com to request a refund? That is the contact information listed in the Google Play store for Minecraft : Pocket Edition.

Comment by Jason Levine [ 16/Dec/15 ]

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

Comment by Fox_McCloud45 [ 19/Nov/15 ]

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.

Comment by [Mojang] MissMarzenia (Aleksandra Zajac) [ 17/Nov/15 ]

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.

Comment by Tyrone Howe [ 17/Nov/15 ]

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.

Comment by Kevin Anderson [ 17/Nov/15 ]

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.

Comment by [Mojang] MissMarzenia (Aleksandra Zajac) [ 17/Nov/15 ]

Please read the UPDATE before posting here.

Comment by [Mojang] MissMarzenia (Aleksandra Zajac) [ 17/Nov/15 ]

zeh 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.

Comment by Tyrone Howe [ 17/Nov/15 ]

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.

Comment by Ian Ward [ 17/Nov/15 ]

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

Comment by jason zeh [ 15/Nov/15 ]

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?

Comment by Kevin Anderson [ 12/Nov/15 ]

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.

Comment by Fox_McCloud45 [ 12/Nov/15 ]

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.

Comment by Kathy Walker [ 09/Nov/15 ]

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.

Comment by Kevin Anderson [ 08/Nov/15 ]

Still not fixed as of 0.13 build 3.

Comment by Jason Levine [ 05/Nov/15 ]

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.

Comment by Tyrone Howe [ 05/Nov/15 ]

Confirmed - version 0.12.3 still NOT working on iOS

Comment by Kevin Anderson [ 05/Nov/15 ]

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.

Comment by Mark Krueger [ 04/Nov/15 ]

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.

Comment by rplatham [ 30/Oct/15 ]

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.

Comment by Kevin Anderson [ 29/Oct/15 ]

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?

Comment by rplatham [ 29/Oct/15 ]

levinej98 and wardi, 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.

Comment by Ian Ward [ 29/Oct/15 ]

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

Comment by Jason Levine [ 29/Oct/15 ]

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.

Comment by Darren Woloshyn [ 23/Oct/15 ]

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

Comment by Kevin Anderson [ 23/Oct/15 ]

Still not fixed on 0.12.3 on Android with touch controls.

Comment by Kevin Anderson [ 15/Oct/15 ]

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.

Comment by Jason Levine [ 15/Oct/15 ]

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.

Comment by rplatham [ 14/Oct/15 ]

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.

Comment by Gary Hasbrook [ 27/Sep/15 ]

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?

Comment by Kevin Anderson [ 25/Sep/15 ]

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.

Comment by Leon Geyser [ 24/Sep/15 ]

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.

Comment by Kathy Walker [ 22/Sep/15 ]

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.

Comment by Kevin Anderson [ 22/Sep/15 ]

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?

Comment by Leon Geyser [ 12/Sep/15 ]

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.

Comment by Jeremy Kidd [ 11/Sep/15 ]

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

Comment by Kevin Anderson [ 10/Sep/15 ]

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?

Comment by Kevin Anderson [ 09/Sep/15 ]

Confirmed on Nexus 5 on 12.1 release on Android 5.1.1

Comment by JG in NC [ 09/Sep/15 ]

I am experiencing the same issue in the 0.12.1 update for iOS that just went live.

Comment by Kevin Anderson [ 02/Sep/15 ]

Confirmed in build 13 as well. The affected versions of this bug need to be updated.

For reference this is at the least for touch devices like the Nexus 5

Comment by Kevin Anderson [ 22/Aug/15 ]

Still present in build 11. This is unplayable to me.

Comment by Fox_McCloud45 [ 12/Aug/15 ]

Not fixed in 0.12.1 build 8.

Comment by Fox_McCloud45 [ 08/Aug/15 ]

Confirmed in 0.12.1 build 7.

Generated at Sat Jan 11 14:44:03 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.