Another bug in 1.8, not as serious as the others, it's just hard to get pictures of bugs that can be shown via them, and also not reveal any new content. While you're not likely to encounter this one, because the conditions are loading the game with a 256x texture pack on, it might apply to 128x as well, and most likely applies to 512x too. Some little back notes on this bug, no, 1.8 will not support high resolution texture packs, it's more of a fix to prevent Minecraft from constantly crashing if you load one. This information is already public (if hard to find, as it was on IRC, and thus is sitting in about 100 personal logs of the channel), as it was requested in the #risucraft IRC channel, and jeb replied saying he added it.
I love Dark Cloud! I'm glad I found someone else too, it was non existent among my friends. I played the sequel too...wasn't as good though...
It clearly must have been nostalga that kept you from enjoying Dark Cloud 2. As it stands Darkcloud 2 is my favouritest game in existance of all time..
On topic though, it's still slightly hard to believe people are going so rabbid over a little delay.
How the hell did they make so many glitches? They weren't even modifying the cows, so how could they end up being 4-legged Enderman? They must experiment with the code all the time.
How the hell did they make so many glitches? They weren't even modifying the cows, so how could they end up being 4-legged Enderman? They must experiment with the code all the time.
Actually, from notch's latest blog post, it sounds like they did. Then there's the fact that stuff just likes to break, and when you pile obfuscation on top of that, it breaks even more.
How can they break the rendering that badly?
I have the answer: By not writing proper java code. Once they build the rendering stuff there should be no reason to change it to much. Adding stuff to the game should not be tied into the rendering stuff.
Rollback Post to RevisionRollBack
Best smp server: sapling.mclayer.com
Best server host: minecraftLayer
Lol, each update they make more glitches are added to the game and less glitches are fixed. They should make an update that fixes all the glitches they can find.
I told people they had a good reason for not releasing the game. But would they beleive me? No, they just wanted it now, buggy or not.
And yes, it is perfectly reasonable for them to mess with rendering related code. That is a place where you can optimize and improve performance, the lighting engine can quite possibly be tied with it, and hence changes happen.
Lol, each update they make more glitches are added to the game and less glitches are fixed. They should make an update that fixes all the glitches they can find.
They did that once. Do you remember 1.6?
Anyways, I'm wondering what they did to cripple rendering this badly, because it all felt rock-solid at PAX.
I told people they had a good reason for not releasing the game. But would they beleive me? No, they just wanted it now, buggy or not.
And yes, it is perfectly reasonable for them to mess with rendering related code. That is a place where you can optimize and improve performance, the lighting engine can quite possibly be tied with it, and hence changes happen.
Yes the new lighting system requires the rendering code to be changed. However they did this when they started to develop 1.8. That's over a month ago. It also played well at PAX I believe?
The only thing that could mess it up that badly a lot of last minutes changes (that always ends badly). And in that case they could just revert to what they had before that and fix the problem in maybe 5 minutes.
Rollback Post to RevisionRollBack
Best smp server: sapling.mclayer.com
Best server host: minecraftLayer
Yes the new lighting system requires the rendering code to be changed. However they did this when they started to develop 1.8. That's over a month ago. It also played well at PAX I believe?
The only thing that could mess it up that badly a lot of last minutes changes (that always ends badly). And in that case they could just revert to what they had before that and fix the problem in maybe 5 minutes.
Apparently, for some people, jeb included, it crashes every 5-10 minutes unchanged. The change that caused the rendering to bug out fixed the crashing, but, well, caused the rendering to bug out. He's temporarily reverted it, so we beta testers can play without models flying and stretching everywhere, while he works on fixing it.
Apparently, for some people, jeb included, it crashes every 5-10 minutes on the 'reverted' changes. The change that caused the rendering to bug out fixed the crashing, but, well, caused the rendering to bug out.
So first it ran nicely.
Secondly they make change to causes the crashing
Thirdly they make a change the fixes the second version but completely breaks the rendering in the process
How to fix this: Revert twice, it's not rocket science
Rollback Post to RevisionRollBack
Best smp server: sapling.mclayer.com
Best server host: minecraftLayer
Yes the new lighting system requires the rendering code to be changed. However they did this when they started to develop 1.8. That's over a month ago. It also played well at PAX I believe?
The only thing that could mess it up that badly a lot of last minutes changes (that always ends badly). And in that case they could just revert to what they had before that and fix the problem in maybe 5 minutes.
Reverting back has never been a great way to add new stuff or optimization to the game. That's like saying "oh a problem, let's not fix it, but instead run away and do whatever we did before."
The fact of the matter is that Java and programming in general is a risky thing. You wanna improve something, it always gets darker before the light, so to speak.
My dad likes to refr to this as the "intermediate broken state". When changing things, you typically end up breaking them before you finish the change. This extends to fixing any bugs introduced while making the change. You normally try to avoid being in this state when you need to release, but things happen.
Then of course everyone demonizes you for not deleivering on the date you expected. Its murphy's law in action. If something can go wrong, it will. Or in more accurate terms, off all the times things happen, something will go wrong some of the time, and you will notice that every time.
Nobody notes all of the updates where it came out on time and worked as expected. There is nothing noteworthy about it, so you forget about it. When something goes wrong, when there are major bugs or it is late, it inconviences you. You notice, and you remember. This pattern repeats. After a while, you remember the 10 times things went wrong, forget about the 100 times it went right, and start throwing out accusations that things always go wrong.
There is a lot of known new content in this update. People end up focusng on the few things that were pushed back, and accuse the update of being a mere shell. If you actually look at the feature list on the wiki, and highlight what we know is actually added, the vast majority of the features are present.
Another bug in 1.8, not as serious as the others, it's just hard to get pictures of bugs that can be shown via them, and also not reveal any new content. While you're not likely to encounter this one, because the conditions are loading the game with a 256x texture pack on, it might apply to 128x as well, and most likely applies to 512x too. Some little back notes on this bug, no, 1.8 will not support high resolution texture packs, it's more of a fix to prevent Minecraft from constantly crashing if you load one. This information is already public (if hard to find, as it was on IRC, and thus is sitting in about 100 personal logs of the channel), as it was requested in the #risucraft IRC channel, and jeb replied saying he added it.
It clearly must have been nostalga that kept you from enjoying Dark Cloud 2. As it stands Darkcloud 2 is my favouritest game in existance of all time..
On topic though, it's still slightly hard to believe people are going so rabbid over a little delay.
Btw, how did you become a beta tester? I thought Notch said there won't be any beta testing until after 1.8.
Notch didn't know that 1.8 was going to be THIS buggy. Besides, jeb hired me. =)
Read up a few posts =)
Actually, from notch's latest blog post, it sounds like they did. Then there's the fact that stuff just likes to break, and when you pile obfuscation on top of that, it breaks even more.
I have the answer: By not writing proper java code. Once they build the rendering stuff there should be no reason to change it to much. Adding stuff to the game should not be tied into the rendering stuff.
Best server host: minecraftLayer
And yes, it is perfectly reasonable for them to mess with rendering related code. That is a place where you can optimize and improve performance, the lighting engine can quite possibly be tied with it, and hence changes happen.
Anyways, I'm wondering what they did to cripple rendering this badly, because it all felt rock-solid at PAX.
"sometimes, wizards are so awesome, it hurts"
Yes the new lighting system requires the rendering code to be changed. However they did this when they started to develop 1.8. That's over a month ago. It also played well at PAX I believe?
The only thing that could mess it up that badly a lot of last minutes changes (that always ends badly). And in that case they could just revert to what they had before that and fix the problem in maybe 5 minutes.
Best server host: minecraftLayer
Not really, their plan with 1.8 wasn't to fix a bug, it was to add more content. More content = new bugs to handle.
May the force be without you.
Apparently, for some people, jeb included, it crashes every 5-10 minutes unchanged. The change that caused the rendering to bug out fixed the crashing, but, well, caused the rendering to bug out. He's temporarily reverted it, so we beta testers can play without models flying and stretching everywhere, while he works on fixing it.
So first it ran nicely.
Secondly they make change to causes the crashing
Thirdly they make a change the fixes the second version but completely breaks the rendering in the process
How to fix this: Revert twice, it's not rocket science
Best server host: minecraftLayer
Reverting back has never been a great way to add new stuff or optimization to the game. That's like saying "oh a problem, let's not fix it, but instead run away and do whatever we did before."
The fact of the matter is that Java and programming in general is a risky thing. You wanna improve something, it always gets darker before the light, so to speak.
This is standard.
May the force be without you.
Then of course everyone demonizes you for not deleivering on the date you expected. Its murphy's law in action. If something can go wrong, it will. Or in more accurate terms, off all the times things happen, something will go wrong some of the time, and you will notice that every time.
Nobody notes all of the updates where it came out on time and worked as expected. There is nothing noteworthy about it, so you forget about it. When something goes wrong, when there are major bugs or it is late, it inconviences you. You notice, and you remember. This pattern repeats. After a while, you remember the 10 times things went wrong, forget about the 100 times it went right, and start throwing out accusations that things always go wrong.
There is a lot of known new content in this update. People end up focusng on the few things that were pushed back, and accuse the update of being a mere shell. If you actually look at the feature list on the wiki, and highlight what we know is actually added, the vast majority of the features are present.
Oh good lord, I want to give Jeb a hug. :sad.gif: