Grave

I forgot to mention that this seems to only affect certain systems and certain world types. Some people only have it with amplified terrain, others with every world type, and others with normal terrain gen.

Could be a driver issue with NVidia. Possibly only Windows 7 systems. Haven't heard anything about W8/8.1 or recent Catalyst drivers from AMD being affected.

So it's intended for FPS to be severely limited, even when close to nothing is being rendered?

I made a new report for my FPS issues, go check it out if you like.

I recommend you retake both pictures with your F3 menu up in the exact/nearly exact same camera and foot position for accuracy. It's really hard to tell how far you moved, or if you moved.

Edit: F3 menu will do 3 things for you:

-Add legitimacy to your position in coordinates
-More clearly show your render distance
-Show what versions of Minecraft each picture was taken in

Another tip for you would be to take 4 pictures. 1.7.2, any snapshot/version of 1.7 before 1.7.2, 1.6.4, and 1.5.2. That'll also help show any inconsistencies in the 1.7 snapshots.

That has to do with mipmapping and not having anisotropic filtering set up high enough, I believe. They wouldn't look nearly as blurry, if at all, if you maxed out anisotropic filtering on your video settings. It's not a bug.

I don't believe this is a bug. It's considered a vehicle (like a horse or mine cart) but has no health, which would replace the hunger bar. On top of that, you don't lose hunger in a boat so it's not a problem.

Instead, maybe Mojang should implement a hunger bar into vehicle GUI so that people aren't blind if they take damage when in a vehicle.

Do you want picture proof with all my settings, pc info, etc?

Nothing fixes it except maybe a full client reboot, but even then it's not a guaranteed fix.

I can confirm this has happened to myself.

Can anyone confirm a hotfix that was applied to 13w38c in the last 4 hours? My fps in 38c has gone up considerably (haven't tested it everywhere), and Minecraft seems to be performing well. I still get about 25% drop in my FPS because of the tools/weapons (improved), but my memory usage is less than 40%+ of what it was before.

I'll update with a new post if anything changes. I think it was just being kind to me on this morning's 3rd launch of Minecraft.

Still no change on the server, but I think they changed the entity ID if that's possible. If they used the same one from 37a/b in 38a-c, it may fix itself. Otherwise, I don't know. I just know that no new arrows are stacking up. All old ones are still all over the world.

I checked on the server, and the arrow count didn't go down at all when waiting for the arrows to despawn.. That sucks.

It seems to be fixed in 13w38a. Arrows seem to despawn within 30-60 seconds after being shot by skeletons now. I threw up about 1500 of them from skeletons for testing's sake, and it took far less than 5 minutes for them to despawn if no updates occur to them (break the block they're stuck to, etc will reset the despawn timer). That was done in singleplayer, I'll have to see if it's any different on the server I'll be playing snapshots on.

Still an issue as of this post.

Still exists in the most recent 1.6.2 and launcher.

Still an issue as of this post date.

Still an issue as of this post.

I've yet to encounter this issue. If anything, they despawn.

Still does not show bonus damage in the most recent 1.6.2 patch and 1.2.1 launcher.
Is it really supposed to, though? I'd like it to, don't get me wrong.

I'm also having major major memory leaks in 1.6.2. I've had this since 1.6.1, and it happened more when I had lots of mobs in water/severe amounts of particles. Now in 1.6.2 and launcher version 1.2.1, I'm having severe memory leaks of 200mb in seconds. Minecraft wasn't like this until 2-3 weeks ago, max (hadn't been playing due to massive lag regardless of memory leak).

I'm running Windows 7 64bit, Java 7 Update 25 for both 32 and 64-bit versions. Doesn't matter what settings I have in-game.