Installed 1.7.2 and all maps, (pre1.7.2 and post) now have this rendering issue where i can only see that far away, and more of the map only renders when i start to get closer to it. This is a stark difference from how it looked in 1.6.4 and makes it real hard to play when relatively close mountains cannot be seen. I have it at the max render distance of 16 chunks, and have never had a problem like this with a previous version of minecraft.
Dev console in launcher and computer Info:
[19:04:54 INFO]: Launcher 1.2.8 (through bootstrap 5) started on windows...
[19:04:54 INFO]: Current time is Oct 28, 2013 7:04:54 PM
[19:04:54 INFO]: System.getProperty('os.name') == 'Windows 7'
[19:04:54 INFO]: System.getProperty('os.version') == '6.1'
[19:04:54 INFO]: System.getProperty('os.arch') == 'amd64'
[19:04:54 INFO]: System.getProperty('java.version') == '1.7.0_45'
[19:04:54 INFO]: System.getProperty('java.vendor') == 'Oracle Corporation'
[19:04:54 INFO]: System.getProperty('sun.arch.data.model') == '64'
[19:04:54 INFO]: Refreshing local version list...
[19:04:54 INFO]: Refreshing remote version list...
[19:04:55 INFO]: Refresh complete.
[19:04:55 INFO]: Loaded 1 profile(s); selected 'Collision891'
[19:04:55 INFO]: Refreshing auth...
[19:04:55 INFO]: Logging in with access token
[19:04:56 INFO]: Download job 'Resources' skipped as there are no files to download
[19:04:56 INFO]: Job 'Resources' finished successfully
Windows 7 64-bit
GT330M
4GB ram
Core i7 M 620 @2.67ghz
I am having the exact same issue and have also never had any problems pre-1.7.2. This is on top of my fps going from 120+ to no more than 60 if I stand still. Makes the game unplayable.
I'm having rendering issues as well. Lots of large chunks aren't rendering till i'm right on top of them. Didn't have this trouble in 1.6.4. Turning the number of distance chunks to 12 helps somewhat.
I experimented with the render distance settings for awhile and it seems that after anything more than 12 chunks it stops making a difference in terms of what is seen in the game. The mipmap settings made no difference for me, but i think it could very likely be a graphics card/driver issue because despite the wide range of bugs seemingly associated with 1.7, this specific rendering issue must not to be too widespread or I imagine there would be more people up in arms about what in my opinion is pretty much a game-crippling bug.
That said it is pretty absurd that Mojang put out such a buggy update, and some sort of rollback should really be done until they can fix most of this .
I've seen the problem as well. I even noticed mountains disappearing on the horizon when turning towards them (like they got shown/cached when not turned in the direction and started disappearing while I looked at them).
This is because the field to render is calculated as a triangle (pyramid actually https://en.wikipedia...Viewing_frustum) so you actually see farther out of the corner of your eye. This is apparently common in computer graphics applications.
Luckily for you Mojang has given you complete control over what version you run. Don't like 1.7? Don't run it.
Nice in theory, although since the new launcher, Minecraft does not seem to ask if you want to update anymore, at least I was asked no such question for this update. I'm sure its simple enough to run a previous version, but that doesn't change the fact that the update was basically forced onto users, and is very broken.
Anyway, i went searching through bug reports and eventually came up with this, https://mojang.atlas...browse/MC-31622 so it is apparently an issue that has been known about for awhile and pretty much done nothing about.
Nice in theory, although since the new launcher, Minecraft does not seem to ask if you want to update anymore, at least I was asked no such question for this update. I'm sure its simple enough to run a previous version, but that doesn't change the fact that the update was basically forced onto users, and is very broken.
The launcher runs exactly the version that the profile you launch with is set for. If it is set for "Latest version" then it will be the "latest version". Don't want to run the latest version? Change your profile to not select "latest version".
The launcher runs exactly the version that the profile you launch with is set for. If it is set for "Latest version" then it will be the "latest version". Don't want to run the latest version? Change your profile to not select "latest version".
Ah thank you, i guess this will be what i am stuck with till the bugs are fixed. If i had a map made in 1.6.4 that i used in 1.7.2, is it ok to then go back to 1.6.4 with this saved map, or should i just use a backup from before using 1.7.2 that is fairly of out of date now?
I don't know. At least partially it would depend upon whether or not you generated new chunks using 1.7, any 'new' stuff won't be understood by 1.6 and could cause problems. But there could be other implications as well, spawned mobs, or the like.
In the future I'd configure the launcher to always use a specific version on worlds that you care about using per profile game directories. Then if you want to play that world with a newer version you can create a new profile and copy the save into the new game directory, so you could always go back to the old copy and the old version.
I actually tried running the game as 1.6.4 today for the first time, and i am getting the same rendering issues that i am got with 1.7.2, with pre-1.7.2 backup saves and completely new files. I don't know exactly how this works but it seems that whatever changes were made in 1.7.2 are somehow affecting my ability to play the launcher's 1.6.4. Is there anyway to get a version of minecraft that is just 1.6.4 and does not have any 1.7.2 code in it?
Have you rebooted your computer at least once during this process? It's possible that there is some setting that is persisted in your GPU state that isn't being cleared otherwise.
I'm having the exact same issue. Upon game load - everything loads just fine. But as I start to move/run around, large sections are not properly loading. Buildings don't load until I'm on top of them, same with mountains, hills etc ...
I thought it was our server, so I created a new single player game. Same exact situation. Terrain is not rendering or displaying like it was successfully in previous releases.
Installed 1.7.2 and all maps, (pre1.7.2 and post) now have this rendering issue where i can only see that far away, and more of the map only renders when i start to get closer to it. This is a stark difference from how it looked in 1.6.4 and makes it real hard to play when relatively close mountains cannot be seen. I have it at the max render distance of 16 chunks, and have never had a problem like this with a previous version of minecraft.
Dev console in launcher and computer Info:
[19:04:54 INFO]: Launcher 1.2.8 (through bootstrap 5) started on windows...
[19:04:54 INFO]: Current time is Oct 28, 2013 7:04:54 PM
[19:04:54 INFO]: System.getProperty('os.name') == 'Windows 7'
[19:04:54 INFO]: System.getProperty('os.version') == '6.1'
[19:04:54 INFO]: System.getProperty('os.arch') == 'amd64'
[19:04:54 INFO]: System.getProperty('java.version') == '1.7.0_45'
[19:04:54 INFO]: System.getProperty('java.vendor') == 'Oracle Corporation'
[19:04:54 INFO]: System.getProperty('sun.arch.data.model') == '64'
[19:04:54 INFO]: Refreshing local version list...
[19:04:54 INFO]: Refreshing remote version list...
[19:04:55 INFO]: Refresh complete.
[19:04:55 INFO]: Loaded 1 profile(s); selected 'Collision891'
[19:04:55 INFO]: Refreshing auth...
[19:04:55 INFO]: Logging in with access token
[19:04:56 INFO]: Download job 'Resources' skipped as there are no files to download
[19:04:56 INFO]: Job 'Resources' finished successfully
Windows 7 64-bit
GT330M
4GB ram
Core i7 M 620 @2.67ghz
That said it is pretty absurd that Mojang put out such a buggy update, and some sort of rollback should really be done until they can fix most of this .
Nice in theory, although since the new launcher, Minecraft does not seem to ask if you want to update anymore, at least I was asked no such question for this update. I'm sure its simple enough to run a previous version, but that doesn't change the fact that the update was basically forced onto users, and is very broken.
Anyway, i went searching through bug reports and eventually came up with this, https://mojang.atlas...browse/MC-31622 so it is apparently an issue that has been known about for awhile and pretty much done nothing about.
The launcher runs exactly the version that the profile you launch with is set for. If it is set for "Latest version" then it will be the "latest version". Don't want to run the latest version? Change your profile to not select "latest version".
Ah thank you, i guess this will be what i am stuck with till the bugs are fixed. If i had a map made in 1.6.4 that i used in 1.7.2, is it ok to then go back to 1.6.4 with this saved map, or should i just use a backup from before using 1.7.2 that is fairly of out of date now?
In the future I'd configure the launcher to always use a specific version on worlds that you care about using per profile game directories. Then if you want to play that world with a newer version you can create a new profile and copy the save into the new game directory, so you could always go back to the old copy and the old version.
Have you rebooted your computer at least once during this process? It's possible that there is some setting that is persisted in your GPU state that isn't being cleared otherwise.
1) Go into video settings and turn OFF openGL
2) after you turn that off and IF you get statical lag, play in full screen mod using F11
--PLEASE TELL ME IF THIS DOESN'T WORK FOR YOU---
--THANKS---
I thought it was our server, so I created a new single player game. Same exact situation. Terrain is not rendering or displaying like it was successfully in previous releases.