Mouse Sensitivity Reverts to Default Each Time Game is Run
The in-game sensitivity appears to revert to default each time the game is run. This, however, is not reflected by the in-game sensitivity option, and subsequent changes to the in-game sensitivity do not appear to do much. Fiddling with the sensitivity and window size seem to eventually resolve the issue for the running game instance, but I have been unable to create a reproducible method of fixing it.
This appears to only affect KB/M controls, as controller input is very consistent.
Created Issue:
Mouse Sensitivity Reverts to Default Each Time Game is Run
The in-game sensitivity appears to revert to default each time the game is run. This, however, is not reflected by the in-game sensitivity option, and subsequent changes to the in-game sensitivity do not appear to do much. Fiddling with the sensitivity and window size seem to eventually resolve the issue for the running game instance, but I have been unable to create a reproducible method of fixing it.
This appears to only affect KB/M controls, as controller input is very consistent.
is duplicated by
relates to
relates to
relates to
is duplicated by
Thank you for your report!
However, this issue has been closed as a Duplicate of MCPE-22135.
It has been linked to this report. If you have additional information, please add it to that report.
If you have not, please search before reporting, as it's likely that one exists already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Feedback – 📖 Game Wiki
Thank you for your report!
However, this issue has been closed as a Duplicate of MCPE-22135.
Your additional information and observations are very useful, so if you can add them to the comments section of the parent issue it would be appreciated.
If you have not, you might like to make use of the search feature before making a new ticket, as it's likely that the issue has been reported already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Feedback – 📖 Game Wiki
This appears to be fixed in version 1.1. I will continue to test to see if the issue creeps up again.
Appears to be fixed.
Occurs in 1.1.3, albeit rarely. Attempting to find a way to reproduce.
Persists in 1.1.5.0. Will test in 1.2.0.31.
Is this still an issue in the latest version?
The bug was fixed in early 1.2, but I forgot to mark this as resolved. My bad!