So I have put minecraft down for awhile while waiting for the update, I come back load up 1.7.2 and I find that the edges of blocks all have white lines around them. Though I have a GTX680 and the proper aliasing settings, 8X AA and 8X Super Sampling, the white lines persist, and yes I have proper global and override settings, same result. Current R331 drivers for my GTX680.
Anyone else with high end graphics cards experiencing the same issue with 1.7.2, or has anyone come up with a way to fix it yet? Preferably I'd like to solve the issue without disabling my fancy pants graphics cards capabilities that is.
The last time I was around was the 1.6.4 update and I did not have the issue then. Reading around a little, the word seems to be the updated rendering code is doing something wonky in regard to aliasing.
Simple. Just disable the anti-aliasing. And try to enable them in game with the Super Secret Settings
You have no idea how much of a downer it is to have a GTX680 but be forced to use the softwares rendering... and if I could actually use those super secret settings instead of cows mooing/ glass smashing/ etc etc... then maybe, but I just tried switching to those settings and it did not work. So basically minecraft is kinda borked right now, lets hope 1.7.3 fixes this issue because a real solution to this would be great.
It's not software rendering without anti-aliasing, although I agree it's unfortunate that it no longer works.
You're not the first to mention this. I've used anti-aliasing for a long time, and it stopped working for me too. I don't get White lines though; it simply doesn't work. Ever since 13w38a (I think that was it), with the addition of shaders, anti-aliasing stopped working, and all sorts of other things changed.
i really hope that you have to code stuff for people that appreciate it like you...
Programmers who release crap code should be criticized for it, how else will they learn? I *am* a programmer, and I welcome critical feedback. If I do idiotic and game breaking code, I want to know.
Same goes for my resource pack, if I ruin it, I want people to yell at my for it.
Mojang totally botched the render engine, the need to be told they screwed up.
Programmers who release crap code should be criticized for it, how else will they learn? I *am* a programmer, and I welcome critical feedback. If I do idiotic and game breaking code, I want to know.
Same goes for my resource pack, if I ruin it, I want people to yell at my for it.
Mojang totally botched the render engine, the need to be told they screwed up.
I agree. If I mess up, somebody should tell me, or I'm going to just keep on making that mistake. It's not only the render system, minecarts and boats are broken as well. They no longer check where is a safe place to put you when you exit. You can exit directly into lava or even into mid air. It's gamebreaking.
After many tries I found a solution to activate antialiasing in 13w38a/1.7.2:
Please note: I tested this with a AMD Radeon HD 7770, so maybe it won't work on nVidia cards.
The only thing you have to do is to locate your options.txt in your minecraft folder.
Once you opened it, search for the term 'fboEnable:true'.
Now you just have to set this setting to 'false'. (I think this is related to Minecraft's OpenGl mode)
That was it. Simply go to your graphics card menu and choose your individual AA settings (Since I hadn't enabled Supersampling (SSAA), it didn't work correctly.) Please note: Do not press the Super Settings Button if you changed the options.txt (Minecraft shows you a blackscreen)
Programmers who release crap code should be criticized for it, how else will they learn? I *am* a programmer, and I welcome critical feedback. If I do idiotic and game breaking code, I want to know.
Same goes for my resource pack, if I ruin it, I want people to yell at my for it.
Mojang totally botched the render engine, the need to be told they screwed up.
Saying that "this is crap" is not critical feedback, nor is it constructive. Go file a report on their bug tracker.
Saying that "this is crap" is not critical feedback, nor is it constructive. Go file a report on their bug tracker.
Basically this. Saying "THIS IS CRAP MOJANG! FIX NAO!" just makes you look like an idiot. Contructive criticism is this: "Mojang, your new rendering engine has made it impossible for me to set Anti-Aliasing setting for my graphics card and use them in Minecraft, please look into this situation." < You see? Not hard.
Rollback Post to RevisionRollBack
The problem with the truth, is that it never lies.
The rendering in 1.7.2 is a complete train wreck; white lines everywhere, sky shadows when under a block, leaves and various other blocks having a 'draw distance' that is extremely obvious, etc. Performance is basically the same and nothing beneficial has been gained.
After many tries I found a solution to activate antialiasing in 13w38a/1.7.2:
This did bring back my anti-aliasing, so thanks! The game is no longer a massive mess of jagged pixels. Though I still get the annoying white lines around blocks. *sigh*
Seems like I'll still need to wait for this to be fixed.
Forced AA has been is broken since like 1.6, and yet they still haven't even bothered to include a proper anti aliasing setting in game, if you gonna break it at least replace it with something better.
1.6 didn't do anything to anti-aliasing so far as I know. It was FBO rendering that was introduced in one of the snapshots prior to 1.7 (13w38a?) that brought the shaders/shader support that did it, and at least for now, there's the way mentioned above to disable that. Hopefully this remains possible to disable.
Programmers who release crap code should be criticized for it, how else will they learn? I *am* a programmer, and I welcome critical feedback. If I do idiotic and game breaking code, I want to know.
Same goes for my resource pack, if I ruin it, I want people to yell at my for it.
Mojang totally botched the render engine, the need to be told they screwed up.
Ok then, here's your feedback:
1. As an actual moderator, the tone and quality of your post is 100% unacceptable and completely unprofessional.
2. If you really were a programmer, then instead of whining like all the little children you'd actually submit a bug report to the official bug tracker.
3. Did you even bother updating your drivers? I highly doubt it. And just FYI, Mr. "Programmer", just because the AA is applied by the game doesn't make it "software AA" instead of "hardware AA".
Saying that "this is crap" is not critical feedback, nor is it constructive. Go file a report on their bug tracker.
I've been harrassed 3 different times by Atlassian mods while they said that the bug didn't exist, couldn't replicate it or it was a "feature" and "intended".
On the very last bug I reported, I was told by one that Minecraft is a demanding game and I shouldn't expect my pc to run it well at all. For one, it never used to have a problem running it. Secondly, the nature of my bug report severely challenged that my lower-end pc couldn't handle Minecraft at least better on 3 different patches prior to 1.7.2+, and they still said it was a "feature" and "intended"..
I called them an idiot, left and recommend no one go there again. We're free employment for Mojang, beta testers without a paycheck. I understand this is probably more effective but I wholeheartedly agree with what Rayvolution has stated on the first page many times. If you can't even take your free labor seriously, that is a major problem on top of your current ones, namely the complete ass coding you're doing and getting away with.
People who support Mojang every full release are dumb. I haven't seen a stable one in a while, and not sure if that even counts because I joined the community just before release 1.4.2.
Just an FYI, all 3 bugs still exist. The last one was partially fixed because they reinstated the dynamic MPChunkCache coding, where it changes based on your render distance for Singleplayer. However, it's even different from whatever patch(es) it was in effect for at first because now on tiny/minimum render distance, the minimum chunk cache is 20-40 chunks. That makes it nearly equal to peaceful mode; spawn rates are equal to nothing. The difference between 121 chunk cache and 40 is gigantic, and 121 is still extremely small.
1.7 is more playable than 1.6 was, but it's still a majorly botched update and not even complete..
@grave since the stupid qoute feature wants to be breakeasy...
I know I'm going to get attacked for saying this, but what do you expect with a community that has a huge backing of a hugbox like Reddit? This is the very reason Notch fled to Reddit (before Jeb took over) is because hes a baby that cant stand criticism. This is a huge problem with lots of indie devs actually...they would rather go to communities who only suck up to them rather than receive actual criticisms on broken or otherwise boring core elements that need changing.
@grave since the stupid qoute feature wants to be breakeasy...
I know I'm going to get attacked for saying this, but what do you expect with a community that has a huge backing of a hugbox like Reddit? This is the very reason Notch fled to Reddit (before Jeb took over) is because hes a baby that cant stand criticism. This is a huge problem with lots of indie devs actually...they would rather go to communities who only suck up to them rather than receive actual criticisms on broken or otherwise boring core elements that need changing.
Hopefully you don't get attacked for it.. I understand what you mean, and I can be the same way at times. Not everyone wants critical, usually negative feedback. I wasn't complaining or being angry about my bug reporting either, I just stated a problem and got insulted by 2 different mods there. I can't really comment on other indie game communities/devs in general, but Minecraft is possibly one of the most problematic ones I've come across.
I don't want to be spoon-fed great content for "free" ("I paid for the game at x time for x price, I deserve anything beyond that" argument, etc..), but if you want to release something that people like and choose to do it for free, then do so instead of just half-assing it and then waiting for the community to rip you to shreds for not being consistent or competent.
The fact that the "sucking up" thing happens a lot in Minecraft bothers me. I actually did this once because of how excited I was for a full 1.7 release. I played through every 1.7 snapshot, all of the content was used by me. I experienced some minor flaws and major performance bugs, and so on. I was greatly impressed at one point by the amount of fixes from 1.6 to these snapshots there was, and I said so. After 1.7 came out and it was actually worse on many levels compared to some recent snapshots (or all of them, almost), I was ed. That was "the straw that broke the camel's back".
Kind of through with supporting Mojang, or this community. I'll pick one or two individuals for the team (Jeb is great, Dinnerbone needs to be fired, for example) that are appreciated, and a handful of players or forum posters that are helpful and insightful, but beyond that the rest I don't want to converse with. I've dealt with 1001 situations where something dumb was said over pride of the game. It's even beginning to leak into my favorite youtubers' personalities and I've almost completely stopped watching videos. Coming from a guy that was watching 2-4 hours a day of Minecraft related content a day or more at times, that's a huge drop off.
What Mojang, Atlassian, tons of the game's community are doing is driving many people further and further away. I'm not convinced that Mojang has or will release a playable game since Minecraft. And I'm not quite sure I'd even support them if they did just because of the reputation..
That being said, Mojang is a "one-in-a-thousand"-type game dev company for not charging for extra content/"DLC". I've seen it leaked into pc games more recently but this is the biggest reason why I'll never buy a console again.
I've been harrassed 3 different times by Atlassian mods while they said that the bug didn't exist, couldn't replicate it or it was a "feature" and "intended".
On the very last bug I reported, I was told by one that Minecraft is a demanding game and I shouldn't expect my pc to run it well at all. For one, it never used to have a problem running it. Secondly, the nature of my bug report severely challenged that my lower-end pc couldn't handle Minecraft at least better on 3 different patches prior to 1.7.2+, and they still said it was a "feature" and "intended"..
I called them an idiot, left and recommend no one go there again. We're free employment for Mojang, beta testers without a paycheck. I understand this is probably more effective but I wholeheartedly agree with what Rayvolution has stated on the first page many times. If you can't even take your free labor seriously, that is a major problem on top of your current ones, namely the complete ass coding you're doing and getting away with.
The issue has supposedly been resolved with the latest patch, and, if it hasn't, there's nothing stopping you from opening a new support ticket with proper documentation of the bug. But I don't see why you or Rayvolution think it's at all constructive to bemoan the community while taking pot shots and the dev team when they have to deal with the same pile of crap community that you have to. Calling the "free employment" idiots for filing your issue or prattling on about the minutia of the personalities of the community is just as cancerous as the mods that apparently called sloppy rendering bugs a feature.
I'd honestly like some links to your support tickets to see this personally because I really can't believe the handful of mods on Atlasssian would call this intended when they've been closing dozens of duplicates of this particular bug.
Anyone else with high end graphics cards experiencing the same issue with 1.7.2, or has anyone come up with a way to fix it yet? Preferably I'd like to solve the issue without disabling my fancy pants graphics cards capabilities that is.
The last time I was around was the 1.6.4 update and I did not have the issue then. Reading around a little, the word seems to be the updated rendering code is doing something wonky in regard to aliasing.
You have no idea how much of a downer it is to have a GTX680 but be forced to use the softwares rendering... and if I could actually use those super secret settings instead of cows mooing/ glass smashing/ etc etc... then maybe, but I just tried switching to those settings and it did not work. So basically minecraft is kinda borked right now, lets hope 1.7.3 fixes this issue because a real solution to this would be great.
You're not the first to mention this. I've used anti-aliasing for a long time, and it stopped working for me too. I don't get White lines though; it simply doesn't work. Ever since 13w38a (I think that was it), with the addition of shaders, anti-aliasing stopped working, and all sorts of other things changed.
The so-called anti-aliasing shader is not anti-aliasing, though. It's merely a very, very heavy blur shader.
(you will need to zoom in)
...now I get this. Look at those glorious trees!
Mojang didnt just mess up a little bit, they totally botched it. How did this garbage even make it as a release?
Programmers who release crap code should be criticized for it, how else will they learn? I *am* a programmer, and I welcome critical feedback. If I do idiotic and game breaking code, I want to know.
Same goes for my resource pack, if I ruin it, I want people to yell at my for it.
Mojang totally botched the render engine, the need to be told they screwed up.
I agree. If I mess up, somebody should tell me, or I'm going to just keep on making that mistake. It's not only the render system, minecarts and boats are broken as well. They no longer check where is a safe place to put you when you exit. You can exit directly into lava or even into mid air. It's gamebreaking.
I think that worked for me
Saying that "this is crap" is not critical feedback, nor is it constructive. Go file a report on their bug tracker.
Basically this. Saying "THIS IS CRAP MOJANG! FIX NAO!" just makes you look like an idiot. Contructive criticism is this: "Mojang, your new rendering engine has made it impossible for me to set Anti-Aliasing setting for my graphics card and use them in Minecraft, please look into this situation." < You see? Not hard.
This did bring back my anti-aliasing, so thanks! The game is no longer a massive mess of jagged pixels. Though I still get the annoying white lines around blocks. *sigh*
Seems like I'll still need to wait for this to be fixed.
1.6 didn't do anything to anti-aliasing so far as I know. It was FBO rendering that was introduced in one of the snapshots prior to 1.7 (13w38a?) that brought the shaders/shader support that did it, and at least for now, there's the way mentioned above to disable that. Hopefully this remains possible to disable.
Ok then, here's your feedback:
1. As an actual moderator, the tone and quality of your post is 100% unacceptable and completely unprofessional.
2. If you really were a programmer, then instead of whining like all the little children you'd actually submit a bug report to the official bug tracker.
3. Did you even bother updating your drivers? I highly doubt it. And just FYI, Mr. "Programmer", just because the AA is applied by the game doesn't make it "software AA" instead of "hardware AA".
I've been harrassed 3 different times by Atlassian mods while they said that the bug didn't exist, couldn't replicate it or it was a "feature" and "intended".
On the very last bug I reported, I was told by one that Minecraft is a demanding game and I shouldn't expect my pc to run it well at all. For one, it never used to have a problem running it. Secondly, the nature of my bug report severely challenged that my lower-end pc couldn't handle Minecraft at least better on 3 different patches prior to 1.7.2+, and they still said it was a "feature" and "intended"..
I called them an idiot, left and recommend no one go there again. We're free employment for Mojang, beta testers without a paycheck. I understand this is probably more effective but I wholeheartedly agree with what Rayvolution has stated on the first page many times. If you can't even take your free labor seriously, that is a major problem on top of your current ones, namely the complete ass coding you're doing and getting away with.
People who support Mojang every full release are dumb. I haven't seen a stable one in a while, and not sure if that even counts because I joined the community just before release 1.4.2.
Just an FYI, all 3 bugs still exist. The last one was partially fixed because they reinstated the dynamic MPChunkCache coding, where it changes based on your render distance for Singleplayer. However, it's even different from whatever patch(es) it was in effect for at first because now on tiny/minimum render distance, the minimum chunk cache is 20-40 chunks. That makes it nearly equal to peaceful mode; spawn rates are equal to nothing. The difference between 121 chunk cache and 40 is gigantic, and 121 is still extremely small.
1.7 is more playable than 1.6 was, but it's still a majorly botched update and not even complete..
I know I'm going to get attacked for saying this, but what do you expect with a community that has a huge backing of a hugbox like Reddit? This is the very reason Notch fled to Reddit (before Jeb took over) is because hes a baby that cant stand criticism. This is a huge problem with lots of indie devs actually...they would rather go to communities who only suck up to them rather than receive actual criticisms on broken or otherwise boring core elements that need changing.
Hopefully you don't get attacked for it.. I understand what you mean, and I can be the same way at times. Not everyone wants critical, usually negative feedback. I wasn't complaining or being angry about my bug reporting either, I just stated a problem and got insulted by 2 different mods there. I can't really comment on other indie game communities/devs in general, but Minecraft is possibly one of the most problematic ones I've come across.
I don't want to be spoon-fed great content for "free" ("I paid for the game at x time for x price, I deserve anything beyond that" argument, etc..), but if you want to release something that people like and choose to do it for free, then do so instead of just half-assing it and then waiting for the community to rip you to shreds for not being consistent or competent.
The fact that the "sucking up" thing happens a lot in Minecraft bothers me. I actually did this once because of how excited I was for a full 1.7 release. I played through every 1.7 snapshot, all of the content was used by me. I experienced some minor flaws and major performance bugs, and so on. I was greatly impressed at one point by the amount of fixes from 1.6 to these snapshots there was, and I said so. After 1.7 came out and it was actually worse on many levels compared to some recent snapshots (or all of them, almost), I was ed. That was "the straw that broke the camel's back".
Kind of through with supporting Mojang, or this community. I'll pick one or two individuals for the team (Jeb is great, Dinnerbone needs to be fired, for example) that are appreciated, and a handful of players or forum posters that are helpful and insightful, but beyond that the rest I don't want to converse with. I've dealt with 1001 situations where something dumb was said over pride of the game. It's even beginning to leak into my favorite youtubers' personalities and I've almost completely stopped watching videos. Coming from a guy that was watching 2-4 hours a day of Minecraft related content a day or more at times, that's a huge drop off.
What Mojang, Atlassian, tons of the game's community are doing is driving many people further and further away. I'm not convinced that Mojang has or will release a playable game since Minecraft. And I'm not quite sure I'd even support them if they did just because of the reputation..
That being said, Mojang is a "one-in-a-thousand"-type game dev company for not charging for extra content/"DLC". I've seen it leaked into pc games more recently but this is the biggest reason why I'll never buy a console again.
- C.C.
The issue has supposedly been resolved with the latest patch, and, if it hasn't, there's nothing stopping you from opening a new support ticket with proper documentation of the bug. But I don't see why you or Rayvolution think it's at all constructive to bemoan the community while taking pot shots and the dev team when they have to deal with the same pile of crap community that you have to. Calling the "free employment" idiots for filing your issue or prattling on about the minutia of the personalities of the community is just as cancerous as the mods that apparently called sloppy rendering bugs a feature.
I'd honestly like some links to your support tickets to see this personally because I really can't believe the handful of mods on Atlasssian would call this intended when they've been closing dozens of duplicates of this particular bug.