Aifer Gettisnem
Assigned
Reported
Comments
When you die, any thrown enderpearls that have your player name in the ownerName tag of the enderpearl are deleted. That's my assumption based on what I saw when I tested this fix.
Enabling Vsync still crashes the game for me as of 14w30c.
I think I've found the problem. Messing around with my video settings to see if I could get a better frame rate and after turning off VSync it actually makes it pretty stable. No sudden drops in frame rate every second and no screen tearing which is stupid since VSync's job is to prevent screen tearing not cause it...
I'll upload a crash report and a copy of my development console just for the heck of it, but if anyone else is having this problem try turning your VSync off and see if that makes a difference.
I'm not calling this Issue resolved just yet since I don't know if the problem with VSync is bad on my end or if it's the jar handling it wrong. I will update the Issue with this information.
Try recording your gameplay with Fraps or whatever you have if possible. For some reason running Fraps for me clears up any of the lag I'm getting and I want to know if it's the same with others.
Updated my Environment with my Renderer and some other stuff. It should all be up to date unless windows is lying to me.
Another crash report for the latest snapshot. Still getting the weird framerate lag. Windows says my Graphics card is up to date. Is there something I'm missing? I would think it would be poor implementation that the developers would make the game unplayable on a system it once could play on.
As of the latest snapshot I've also noticed that my shift key and scroll wheel stop working at points. May have something to do with the new gamemode.
Java Realtime Environment has been updated to 7u51 x64. Ram Allocation was set to 256m-512m by default when I created a new profile; changed it back to 1g. Screen freezing has been noticeably reduced but is still present especially while in F3 mode, and client often becomes unresponsive on world selection menu. I'll try upload another crash report.
I'll keep adding a crash report for every version still effected by this. It's bizarre how only some computers are effected by this.
Attached a crash report from version 14w04a as well.
A crash report has been added.
Updated affected versions list. Behavior is still present in 1.7.2 and 14w03b.
The issue is stacking Night Vision and Blindness creates a super blindness that makes it impossible to see anything. Not even the floor! Just pure darkness! Whereas before, it would give you the visual limitations of blindness but change the appearance of the block light level for what you could still see(i.e. the floor) to 15.
Now I don't see anything wrong with this, as much as I like how the two effects stacked previously I can certainly use this new behavior for other things as well, but I want you to understand what the community here is pointing out.
In short...this is what we've come to expect:
http://www.youtube.com/watch?v=FlKK9k5g7zw&t=1m56s
This is what we're getting now:
http://www.youtube.com/watch?v=6ANrnQlcPc8&t=3m20s
Is this really working "as intended"?
Knockback has always been on these forms of damage. Fall damage, fire, poison, wither, etc. This bug merely intensified the problem. These should really be removed. Actually, they should have been removed back when knockback from drowning became a problem as this method of applying knockback to any kind of damage was always bound to cause problems for future applications in the game. Knockback. Player on Player/Monster/Projectile contact only. External forces only. No status effects. No internal elements should have a say in how my external physical form behaves other than how fast I lose hearts/hunger/other stats.