Yoshi
- YoshiHack56
- yoshihack56
- Europe/Amsterdam
- Yes
- No
Still not fixed in 15w38a unfortunately...
Actual maximum FPSis always one lower than Max FPS settingFPS in F3 menu is always one lower than Max FPS setting
When messing around with 1.13, I noticed that
myFPS would always be 59 at most although the Max FPS setting is set to 60. If I set it to 61 in options.txt, the FPS will be at most 60. If I set it to 70 with the slider in video settings, the FPS will be at most 69.I don't think this is intended, having the actual max FPS always be one lower than the max FPS setting.
When messing around with 1.13, I noticed that the FPS in the F3 menu would always be 59 at most although the Max FPS setting is set to 60. If I set it to 61 in options.txt, the FPS will be at most 60. If I set it to 70 with the slider in video settings, the FPS will be at most 69.
I don't think this is intended, having the actual max FPS always be one lower than the max FPS setting.
FPS in F3menuis always one lower than Max FPS settingFPS in F3 screen is always one lower than Max FPS setting
When messing around with 1.13, I noticed that the FPS in the F3
menuwould always be 59 at most although the Max FPS setting is set to 60. If I set it to 61 in options.txt, the FPS will be at most 60. If I set it to 70 with the slider in video settings, the FPS will be at most 69.I don't think this is intended, having the
actual max FPSalways be one lower than the max FPS setting.
When messing around with 1.13, I noticed that the FPS in the F3 screen would always be 59 at most although the Max FPS setting is set to 60. If I set it to 61 in options.txt, the FPS will be at most 60. If I set it to 70 with the slider in video settings, the FPS will be at most 69.
I don't think this is intended, having the FPS in the F3 screen always be one lower than the max FPS setting.
When messing around with 1.13, I noticed that the FPS in the F3 screen would always be 59 at most although the Max FPS setting is set to 60. I
f I set itto 61 in options.txt, the FPS will be at most 60. If I set it to 70 with the slider in video settings, the FPS will be at most 69.I don't think this is intended, having the FPS in the F3 screen always be one lower than the max FPS setting.
When messing around with 1.13, I noticed that the FPS in the F3 screen would always be 59 at most although the Max FPS setting is set to 60. In 1.12.2 it would reach 60 like normal. If I set the max FPS to 61 in options.txt, the FPS will be at most 60. If I set it to 70 with the slider in video settings, the FPS will be at most 69.
I don't think this is intended, having the FPS in the F3 screen always be one lower than the max FPS setting.
When you want to scroll through your recent chat messages or commands that you executed recently, you use the up arrow key. However, if you change the
upkey under controls, youbstill need to press the up key to scroll through your recent chats/commands. In 1.12.2 you could just use the key you set forupunder controls. This bug is especially annoying if you have a broken up arrow key on your keyboard.When you want to scroll through your recent chat messages or commands that you executed recently, you use the up arrow key. However, if you change the move forwards key under controls, you still need to press the up key to scroll through your recent chats/commands. In 1.12.2 you could just use the key you set for move forwards under controls. This bug is especially annoying if you have a broken up arrow key on your keyboard.
When you want to scroll through your recent chat messages or commands that you executed recently, you use the up arrow key. However, if you change the move forwards key under controls, you still need to press the up key to scroll through your recent chats/commands.
In 1.12.2 you could just use the key you set for move forwards under controls.This bug is especially annoying if you have a broken up arrow key on your keyboard.When you want to scroll through your recent chat messages or commands that you executed recently, you use the up arrow key. However, if you change the move forwards key under controls, you still need to press the up key to scroll through your recent chats/commands. This bug is especially annoying if you have a broken up arrow key on your keyboard. In my opinion, there needs to be another setting in the control settings called something like "recent chat key" where you can change this key
Recent chats button is always the up arrow keyinstead of the control set under controls
When you want to scroll through your recent chat messages or commands that you executed recently, you use the up arrow key. However, if you change the move forwards key under controls, you still need to
pressthe up key to scroll through your recent chats/commands. Thisbugis especially annoying if you have a broken up arrow key on your keyboard. In my opinion, there needs to be another setting in the control settings called something like "recent chat key" where you can change this keyWhen you want to scroll through your recent chat messages or commands that you executed recently, you use the up arrow key. However, if you change the move forwards key under controls, you still need to use the up key to scroll through your recent chats/commands. This is especially annoying if you have a broken up arrow key on your keyboard. In my opinion, there needs to be another setting in the control settings called something like "recent chat key" where you can change this key apart from the walk forwards key.

Confirmed on 15w36d.
Still not fixed in 15w38a unfortunately... See attachement above in the discription.
Confirmed in 15w40a, generated a new world, but the issue is still present unfortunately.
Confirmed as fixed in 15w42a.
Confirmed. When you want to move villagers and you send them off in the minecart, they return back because they can control the minecart. Once one is back from travelling a bit, he will be frozen. You can still move the minecart, but the villager will act like he is still in the minecart nd is impossible to move. Sometimes these frozen villagers disappear too.
Can confirm too.
Confirmed for 16w33a.
So you're saying that they intend the have the game running at 59.9 FPS now? I never knew that got changed... In 1.12.2 and lower this wasn't the case...
EDIT: But this doesn't explain the others like 70 to 69 FPS, does it? That only has to do with 60, this bug affects more than only 60?
I don't think this is working as intended. If you have the Max FPS set to 70, the maximum FPS in the F3 screen should be 70, not 69.
Interesting. Thank you for adding this information to the report. I hope that somebody can clarify whether or not this is intended behavior...
Whoops. I meant the move forwards button. Default key is w. You would set it to up arrow key if you want to use the arrow keys to move, rather than the wasd keys.