mojira.dev

Chris Koehler

Assigned

No issues.

Reported

MC-37398 Clicking super secret settings in the main menu throws an exception (but does not crash) Fixed MC-36388 NPE when attempting to connect to MC realms world Invalid MC-16847 Horse jump bar becomes stuck if player is kicked off / dismounts while charging a jump Fixed MC-15807 Nether Portal block in inventory renders as a cube if no portal blocks exist in the world. Invalid MC-11526 Light does not update correctly if source is 100 blocks away vertically Duplicate

Comments

Confirmed. I believe they are lit up both stuck into a block and while in flight.

Confirmed, and also related is that items cannot be shift-clicked into the slot even if some of that type of item are already there.

Confirmed as well.

I can confirm, also there is no stack trace or console message.

@Galaxy_2Alex

This effects all versions through 14w03b

@Ezekiel

This is still an issue with those versions, and in 14w02c it is even more of an issue. (I have not tested the other two snapshots)

@Ezekiel
This has not happened to me in any of the post-1.7.2 snapshots.

@Talven81

This has not happened to me in 1.7.2.

@Talven81

This still happens with the latest MC and Launcher.

This has not happened in 1.7.2, so I assume it is fixed. I can not test the newer snapshots as I lost access to Minecraft Realms.

I can confirm that this happens in 1.7 / 1.7.1. The snapshot before that was not NEARLY so bad. The frame-drop in 1.7.1 is bad enough to negate all the performance improvements that have been added since 1.6.4.

@Talven81

I just tested on 13w38c, and even with a horde of 300 zombies the lag was no more than with 300 of any other entity. Looks pretty much fixed to me.

This happens to me as well.

I have encountered this many times in 1.6.2. Confirmed.

@ Branden
Technical blocks were not removed, they were just made to be impossible to keep in the inventory.

I can confirm, although the block was off by 2 in both X and Z.

@Mahamatan
Actually I'm on a laptop with 1GB graphics. That is why I was so surprised at the FPS! On 1.6.2 with all settings on fancy I get around 30 FPS with vanilla, and 120 with optifine. Here on the same render distance I got 130 with vanilla! Also attaching a crash report. I can also confirm the bug where the launcher thinks the game is modded even though the crash report says it is not.

@ Mahamatan

I will test this as soon as I am done updating my graphics drivers. They keep reverting to using my integrated graphics in stead of dedicated, which may be related.

EDIT: Finally done with an absolutely HORRIBLE round of update-uninstall-reinstall between factory default drivers, AMD drivers, and Intel drivers so I was able to test this. In my case max FPS on normal render distance gave about 175 FPS at normal window size, 110 at nearly maximized, 85 at maximized, and 110 fullscreen. Maximized definitely had a serious impact on FPS. I am going to go test at far render distance and I will update with the numbers there.

EDIT2: Here it is with far: 130 normal window size, 120 somewhat enlarged, 100 nearly maximized, and 90 both maximized and fullscreen. It seems far render distance does not have the bug the same way. I will test with short/tiny and see what happens there.

EDIT3: On short the change was even more dramatic. 330 FPS normal size, 240 somewhat expanded, 170 nearly maximized, and 160 both fullscreen and maximized.

EDIT4: Tiny even more so: normal was 500 FPS (new record for me, even with optifine! Good job mojang!), somewhat maximized was 320, almost maximized 250, 190 maximized, and 180 fullscreen.

@monkeybee

No the grassless dirt is the dirt block with data value one. Grass is unable to grow onto grassless dirt, so it makes sense that mycelium should be unable to as well.

I can confirm this. Playing maximized causes a consistent drop in framerate.