Aaron Franke
- aaronfranke
- aaronfranke
- America/Chicago
- Yes
- No
MC-5368![[Mojang] Jeb (Jens Bergensten)](../../../data/assets/gravatar/jeb.jpeg){kind=small}
While mining using a tool (ex: a pickaxe), data gets sent over to the server saying what block was broken, and then the server updates the data values to make the pick more damaged, and this also gets updated on the client. Because of the new feature where the cracking restarts when the tool is swapped, this causes the block you started to break right after you broke the previous one to reset and consume about 1.5x as much time as it should take (with a diamond pick). A solution to this I thought up was to have the crack only reset after the normal block ID is changed, instead of the metadata value changing.
Windows 7, Java 7 Update 25
Basically, as you can see, the title screen background flashes when exiting out to it.
Occurs from snapshots 13w23b to 1.6.1. I cannot get the launcher to run any snapshots before 13w23b. Does not occur on 1.5.2.
Windows 7, Java 7 Update 25, 64-bit architecture
Basically, as you can see, the title screen background flashes when exiting out to it.
Occurs from snapshots 13w23b to 1.6.
1. I cannot get the launcher to run any snapshots before 13w23b. Does not occur on 1.5.2.Basically, as you can see, the title screen background flashes when exiting out to it.
Occurs from snapshots 13w23b to 1.6.2. I cannot get the launcher to run any snapshots before 13w23b. Does not occur on 1.5.2.
How to reproduce: Add Minecraft as a non-Steam game (via "java -jar C:\path\to\minecraft\launcher.jar") and login. Change the settings of the Steam controller to make one of the buttons F11. If you press it, the game will crash. The game also crashes if you go into Options and enable the Fullscreen setting there.
Minecraft crashes when theF11 key is pressed using the Steam controllerMinecraft crashes when the game is fullscreened using the Steam controller
EDIT: Fixed in 1.10.2
How to reproduce: Add Minecraft as a non-Steam game (via "java -jar C:\path\to\minecraft\launcher.jar") and login. Change the settings of the Steam controller to make one of the buttons F11. If you press it, the game will crash. The game also crashes if you go into Options and enable the Fullscreen setting there.
Windows 10 Pro 64-bit
t, GTX 770, 8 GB RAM, i5-4690k
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
Aaron Franke, see MC-2548.
@Aaron Franke: 1.10.2 is already marked as affected. Please check the affected versions before confirming an issue.
Yay, I give good descriptions according to tails
Yes, but first of all 1) I provide better information apparently 2) It is SUPPOSED to reset while changing blocks 3) The only BUG happens with tools
Is anyone making any progress to solving this??? All I've gotten is 'Confirmed.' from Tails...
To test this on the current snapshot, I'd need to have a remote server, and the network needs to be a bit latent. This issue is primarily caused by the values updating, but they simply would update way too fast on singleplayer (About <1ms). To see this fully happening, I'd need to log onto a server using 13w03a. Does anyone have an IP for a snapshot server?
As soon as 1.5 is released and all the multiplayer servers get updated, I will test this bug on there. I will furthermore be unable to test this bug on snapshots because I'd need someone else to host a snapshot server.
Mojang really needs to fix as many bugs as possible, especially major ones like this, before ANY major release. A buggy game = a blob of inefficient code to me.
PS: This discussion has filled my email inbox
Of course the FPS behaves differently on different computers, but this doesn't change the fact that this bug is causing drops in the framerate. Also, smooth lighting min/max doesn't matter, the fact that it is on impacts the preformance the same for both min and max.
If anyone wants to get accurate FPS measures, I highly recommend using external software (I use Fraps), because the in-game FPS rate only updates once a second.
@Joey, you said you had average 1 fps. That is a problem which extends to not only MC but your computer, you must be running it on your calculator or something. If you want me to help me tune up your PC for an attempt at better fps, PM me on steam: aaronfranke0 or skype: aaronfranke1.
Sorry people, there are no ways to PM through Jira.
This discussion has nothing left to discuss other than confirms - _ - FIX DA BUG MOJANG!
Ok then, sorry Joey, you just said 1 fps and that's extreme.
Anyway, you gave a pretty good report, and Mojang should probably check out how it affects different GPU's, they said they could not reproduce it, and since this is a GPU problem, maybe they have some weird setup with their GPU?
http://www.minecraftforum.net/topic/1720059-15-fps-fixer-01/page__st__40#entry21399548
I asked the person on the Minecraft Forums topic who was not getting lag from 1.5 to post his specs - maybe we will have better luck then.
@John, I have a very nice desktop computer, on a test I conducted with 1.5, I have 155 fps with smooth lighting off and 89 with smooth lighting on.
You can find my specs here: http://www.sevenforums.com/members/aaronfranke.html
HD packs obviously would lag more than default packs, as there are less pixels to render when you go down resolutions. Only use HD packs if you know your computer can handle them, your performance on the default texturepack tells me you do not have the best setup out there.
This is now fixed in 13w22a.
What do you mean update affected versions? Is Minecraft 1.6.2 not the latest version? I am unable to find any version released beyond 1.6.2.
@Matt Enloe
Problem exists in both a normal server and in Bukkit/Craftbukkit. However, Spigot has fixed this problem.
Soniji said he tested this in 13w39b.
This bug is not present in 1.7.2. Where is the close issue button?
Can we get some tests comparing 1.5.2 (or whatever version was before this bug) and the latest snapshot? From what I hear, this problem keeps getting better, so I want to see results between now and before the bug, to see if it is at least close to the same, in which case this bug should be marked as solved.
redstonehelper, what are your computer's specifications?
If I were to make a suggestion to Mojang, you may as well drop Java 6 support anyway when you drop OpenGL 1.0. Java 8 is right around the corner, its first releases are already out, and most machines capable of Java 6 and Minecraft can use 7.
It is disappointing that the migration away from IDs did not fix this, I wpuld have figured that they'd have checked the code then, but oh well.
Confirmed for 1.8.1 release.
This is NOT a duplicate of 5520. This has nothing to do with multiple monitors, this computer only has 1 monitor. I'm also using Windows, not Mac.
Partially confirmed for Minecraft 1.10.2. I can't reproduce the tool metadata issue (I may just be having really good ping) but adding items to the stack you're holding still causes the cracking action to reset.
I tried to reproduce this in 1.10.2 and the bug no longer exists. The bug has been fixed, and this ticket should be closed.
Fixed in 1.10.2
I have the same issue in 1.10.2.
I can confirm that this bug happens in 1.10.2.
I've attached two from the 1.12 crashes and one from the 1.8.2 crashes.
Despite this being a LWJGL issue, shouldn't the confirmation status still be marked as "Confirmed" rather than "Unconfirmed"? There are 11 duplicates.
Can no longer reproduce in 17w47b but I am able to reproduce in 1.12.2.
I experienced this bug today, mending pickaxe in hand, picking up XP doesn't repair the pickaxe.
I fixed it by restarting my game, and now it works fine.