- Registered Member
Member for 11 years
Last active Fri, Oct, 26 2012 23:18:21
- 0 Followers
- 484 Total Posts
- 65 Thanks
Aug 15, 2012Posted in: Minecraft ToolsQuote from ferret99gt
Just spent a bit tinkering and finding all the dependancies as 64-bit. I've uploaded my 0.1.2 Win32 build from the other day as well as a 0.1.2 Win64 build to github now.
These are built from TK's 0.1.2 files, so they probably won't work on Intel GPUs. However, they do have the Minecraft 1.3.1 blocks from the updated pymclevel.
Thank you kindly, make sure other people see this.
Aug 13, 2012Posted in: Discussion
Hate it or tolerate it, the chances are we all have to deal with it. This seldom-discussed bug has been plaguing our games for weeks now.
Anyone who has generated a new map since 1.3 came out has probably noticed quite a few of these black spaces. Here are some interesting facts to clear up some misconceptions in the minecraft community:
- It is not a hardware-related issue, the bug WILL occur regardless of specs
- It is a glitch that occurs when generating NEW chunks
- These black spaces will NOT show up on older maps unless you explore new chunks (which is why so many players deny the bug even exists due to sheer ignorance)
- The dark areas can be cleared up by updating nearby blocks
- The lighting has to be re-calculated to fix these chunks, which means an update will not likely fix any current dark areas
- These dark patches are saved upon logging out and are a part of the map data, not merely a graphical glitch (further more these dark patches can be observed on MCEdit)
- It IS possible to fix any affected chunks with 3rd party programs such as MCEdit
Unfortunately fixing these chunks is no easy task (honestly who feels like updating the lighting manually in-game?) , relighting any more than a few thousand chunks with MCEdit can take hours, and the application will almost certainly crash.
It is possible to select smaller sections of chunks and manually relight small sections of your map (to prevent MCEdit from crashing), but depending on your world size this task would be tedious at best.
This brings me to my conclusion; How does everyone else deal with this bug? Do you fly around your map with torches fixing every dark spot manually? Fix it with MCEdit? Ignore it?
I am also wondering if there is a tool other than MCEdit which can relight chunks efficiently? Any mods?
1.4 is a long ways away, and so far I've heard no progress in tackling this overly prominent bug. 'Dealing with it' until then is not an option.
tl;dr: How do I 'work around' this bug?
Jul 6, 2012So... 1.3 is being released with these issues? Even the lighting issue?Posted in: Recent Updates and Snapshots
To all of you naysayers who have ****-talked me in the past because you assumed these bugs would all be fixed before the update... **** OFF. You can no longer hold onto your little snapshot argument, your ignorance is bravado.
Jun 29, 2012Posted in: Recent Updates and SnapshotsQuote from FrostyWolf
This has been a issue in multiplayer forever. Notch has even attempted to fix it a couple of times. Unless one of them stumbles across something in the code along the means of MakeLightingLookLikeCrap=True, don't expect it to be fixed anytime soon.
Sad but probably true, this was one of the primary reasons I tended to play mostly singleplayer 95% of my time. Sad to see the game suffer due to such a poor decision.
These bugs might still be fixed eventually, but single player will never be as stable as it once was, which is rather depressing.
Jun 29, 2012Posted in: Recent Updates and SnapshotsQuote from Xylvion
You know. . . you don't have to publish your single player world, that way it stays singleplayer. . . and lag is probably because of your computer (:
Take your trolling elsewhere.
Jun 28, 2012The lighting issues are really starting to **** me off, Jeb and Nathan have thus far neglected the bug, and have shown no signs of even acknowledging it exists.Posted in: Recent Updates and Snapshots
But whoop de do, ("guess what? It's a hardware problem, not a update problem, your computer just sucks!") or ("It will be fixed in the next snapshot anyway!") This is how the minecraft community responds to everything wrong with their precious game, I have seen these two arguments time and time again on the forums, in relation to the lighting bug.
I don't like to brag about my PC specs, but lets just say I can more than handle any game at max settings. Secondly, every thread that acknowledges a bug gets shot down, with the OP getting belittled. The snapshots are here for testing and reporting bugs, not pretending they don't exist.
Further more, almost every week for the last 5 or 6 weeks (who is keeping track?) I've seen someone say "they will fix X bug in the next snapshot, stop crying". Clearly Mojang isn't going to fix these bugs if everyone keeps quiet about it.
Jun 23, 2012Affirming that these issues are a direct result of one's lackluster hardware is a complete farce. Having a top-of-the line PC which I have built and customized myself, I would anticipate flawless preference in regards to "hardware issues". Moreover it is worth noting that these lighting issues have become unduly prevalent in a snapshot several weeks ago. In all fairness lighting issues such as these have regularly occurred, albeit with much less frequency. However, seeing these dark blights on every chunk of observable landscape is unforgivable.Posted in: Recent Updates and Snapshots
Also, in relation to the comments posted above which suggest the issues is a result of using Intel processors, I can confirm this is fallacious. I am currently sporting 6-core AMD 3.2ghz processor and these issues are still occurring.
Anyone who has been using the latest snapshots has most likely been experiencing these issues. Once the anvil world format was released Minecraft was experiencing numerous lighting glitches, however it was hastily "fixed" (at least for the majority of players). I am not experiencing frequent lighting issues as of 1.2.5 at the very least. However a recent snapshot was evidently responsible for these issues, around the time of the SSP-SMP merge, while I am merely speculating that these issues go hand-in-hand, it does seem very likely that these lighting issues are the result of "server"-to-client elucidation issues. Which explains why these complications remain even after unloading and reloading your map.
Clearly these issues need to be addressed based on the fact that it clearly affects most players, regardless of computer specs/setups/processor brands.
Jun 21, 2012Posted in: Recent Updates and SnapshotsQuote from Jassie
I don't have the issue. I haven't had block lag or mob glitching in any of the recent snapshots.
Oh it's there, and it's certainly not a hardware issue.
The problem isn't immediately apparent, but the little delays and desynchronization issues really get annoying. Especially in combat situations.
Everyone is experiencing this issue. It has nothing to do with specs, and everything to do with the snapshot.
Jun 21, 2012I was just about to make a thread about this, these lighting bugs have kept me from enjoying Minecraft for months now. Every piece of terrain looks like ****, and it has neither been mentioned by Jeb or Nathan on their twitters.Posted in: Recent Updates and Snapshots
I doubt we will be seeing a fix any time soon, but hopefully it gets sorted out before 1.3 is out officially.
- To post a comment, please login.
Mar 1, 2012This might have messed up alot of things, but at least it isn't as bad as that update which prevented us from posing at all if someone replied to the the thread while we were wrinting a reply. That was just horendous.Posted in: News
Feb 23, 2012Caves will be fixed, along with the lighting glitch (and hopefully some other glitched caused by the new world format) by next week at the latest.Posted in: News
I don't blame Jeb for not doing these fixes this week, he was occupied with Mojam and Lego World, lol.
- To post a comment, please login.