Julian M
- gamemango
- gamemango
- America/Havana
- Yes
- No
6 issues
Key
Summary
Status
Reporter
Assignee
Created
MC-7298
MCL-2665
Changed Description:
What I expected to happen was torches would look normal.
What actually happened was the torch flame animation appeared translucent when there was water behind it (see pictures below).
Steps to reproduce
1. Place/find water
2. Place torch next to water so that the torch can be viewed with the water behind it.
3. Observer that the flame animation looks more see-through than it used. When there is no water there,the flame looks normal.The pictures are of the same torch, just from different angles. The same problem persists with other torches seen in the background.
Deleted Comment:
Here is a crash report when in fullscreen mode
Added Attachments:
crash-2013-12-26_13.08.20-client.txt
I posted this as an issue because it used to work fine with repeaters until a recent snapshot.
I have tried it again and you are right, it seems that I can't reproduce it. Should I delete the issue? It did happen the first time. I was cooking up some spruce wood to make charcoal. I used 2 spruce planks as a fuel to cook 3 logs and then I used charcoal to cook some more. Before the 2 logs were done, I moved the one charcoal I had at the time to the fuel slot and added 28 more logs to the top slot in the furnace. When I put the logs in the top slot, the number did not change from 1 to 29 but instead stayed at 1 and I though that I had just lost my wood but once the one log finished cooking, the other 28 took its place.
Also, through testing to see if I could recreate it under the same circumstances above, I had a similar graphical issue with the spruce planks disappearing from the fuel slot after one of the 2 cooked. It only happened once and I could not reproduce it but I did take note of the direction in which the furnace was facing in case it is a directional bug. It was facing south. The time the other bug occurred, the furnace was also facing south. So maybe that has something to do with it.
The Debug screen is the only way I was checking my fps. If it helps, I am using intel hd 3000 on late 2011 13 inch macbook pro.
EDIT - I have further tested and it seems that the fps actually can go past 30. The problem is that the game performs better when using the keyboard shortcut or the option menu to change to fullscreen. I was getting ~15 fps less when using the native mac fullscreen button.
EDIT 2 - Try turning your render distance up (I found my results using a render distance of 8 chunks, I tried it with 2 chunk render distance and the difference was much less noticeable)
Do you want me to be in fullscreen mode using the os x fullscreen button when I crash it?
I posted the crash report when in fullscreen mode
Here is the complete output from the console. It still looks messy in the launcher, just not when I paste it
[19:40:55 INFO]: Minecraft Launcher 1.4.4 (through bootstrap 5) started on linux...
[19:40:55 INFO]: Current time is Jun 24, 2014 7:40:55 PM
[19:40:55 INFO]: System.getProperty('os.name') == 'Linux'
[19:40:55 INFO]: System.getProperty('os.version') == '3.15.1-1-ARCH'
[19:40:55 INFO]: System.getProperty('os.arch') == 'amd64'
[19:40:55 INFO]: System.getProperty('java.version') == '1.7.0_60'
[19:40:55 INFO]: System.getProperty('java.vendor') == 'Oracle Corporation'
[19:40:55 INFO]: System.getProperty('sun.arch.data.model') == '64'
[19:40:55 INFO]: Refreshing local version list...
[19:40:55 INFO]: Refreshing remote version list...
[19:40:55 INFO]: Refresh complete.
[19:40:56 INFO]: Loaded 5 profile(s); selected 'gamemango'
[19:40:56 INFO]: Refreshing auth...
[19:40:56 INFO]: Logging in with access token
This problems still exists for me on 14w31a using OS X 10.9.4 and java version 1.7.0_65. The fps does occasionally spike during gameplay to rates higher than 30 (I think this is due to the new rendering code introduced in 14w30a) but it is still mainly stable at 30 fps. I have seen it reach up to 120 fps for a second before dropping back down.
I do not have VSYNC enabled. Also switching the game to Java 6 does not solve the issue. I will note that when running with java 6, the fps fluctuated from 30 for longer periods of time, stabilizing around 40-45 for about 5-10 secs before stabilizing at exactly 30 again for most of the time.
I also checked the snooper settings and saw that the game is unable to determine the display rate of my monitor correctly (snooper reports monitor display rate as 0 when it is actually 60).
Enabling VSYNC brings a whole other problem as this too locks the fps at 30, even at lowest video settings and render distance (but this should be a separate issue so I will work on that later).
This problem has been fixed with java update 1.7.0_65 and no longer occurs