Anthoni Wiese
Assigned
Reported
Comments
Why was this marked duplicate of 87041? They're similar errors but not identical. This one states a Execution Exception w/ a OOB, while the one marked for the duplicate states the player receives a Decoder Exception and OOB. It's probably related, but without having seen the full error message the players get in the other one I see no particular reason that these two errors stem from the same core classes thus duplicating one another. As for the driver being out of date, well aware, held off on it initially due to nvidia drivers being potentially buggy in the past and waiting to see if they would immediately release another update.
Can also confirm for 15w39c as well as the observed disconnects happening on major block update counts (such as trees) and newly created chunks
Can confirm for 15w39a, 15w39b, 15w39c. Attached my manually caused crash from 15w39c for reference (crash-2015-09-23_23.19.24-client.txt)
Can confirm for 1.8.2-pre3
Can confirm for 1.8.1
Can confirm in 14w34d.
I understand the reasoning behind why the minecarts shouldnt move, since players cannot push other entities (sheep, etc) around when they have the NoAI set to 1, but the reasoning of not having rotation/motion tags is completely wrong.
This said, the NoAI tag removes an entities AI, it being pushed around by outside forces really isnt an AI thing imo. But we'll see what Searge has to say (or anyone else) since Searge has marked a lot of NoAI issues as "won't fix"
Can confirm still in 14w34d.
Cannot replicate at all in 14w34d. Running with a GTX 660 (seemed relevant since its a visual thing)
Similar to Jay Blunt, cannot reproduce either in 14w34d.
Can confirm, during my testing my average FPS was ~325 without the lava attempting to flow into barriers. Once it was released and the flowing lava hit the barriers, FPS dropped to ~190
Can confirm on Win 7 in 14w34d as well, as well as on RHEL, Ubuntu, and OS X Mavericks on same snapshot.
An image would be helpful to explain the exact setup, but from what I understand, this method wouldn't work at all unless the redstone didn't go into the side of the comparator with the comparator in subtraction mode.
In the claimed duplicated report, we can actually see the full stack trace of the error, in this one we cannot. As a programmer I would never claim this error to be identical to the other one without being able to trace where this error comes up from. There are plenty of ways to cause an individual error to appear without being the same culprit. I will agree to it possibly stemming from the same core issue (major block updates), but cannot agree to it being duplicates based on the presented error information. For all I know this error could stem from (hypothetical) class baz whereas the one claiming to be a duplicate of this one, stems from class bab.