August Junkala
Assigned
Reported
Comments
To answer your question though, no I am not getting the issue any more. I haven't seen it in any sessions since the first instance. Just to be sure, I just started a fresh world and the only issue I saw was one reported by another user when first entering a world: only the chunk I was in generated. I could walk off the edge and slowly fell off until a few minutes later when the geometry started filling in.
When exploring new areas I use the highest available view distance (16 when I saw the issue, 32 now) otherwise I use 16 or lower (no point swapping extra chunks I can neither see nor have any need to see). I have always played with VBO off (the default as far as I am aware). Also when I saw the issue, I used the default❓ mem size (1GB), although bumped it to 2GB when 32 view distance was added since that feature is disabled with a smaller mem size.
Other issues I suspected could be related have also disappeared (i.e. chunk visual updates are no longer severely lagged, and chunks don't periodically fail to generate visible geometry at all).
Possibly fixes that are unexpectedly not universal (e.g. the AMD chipsets w/ problems can't take advantage of the fix).
Not that it matters, but I filed the bug so telling me the issue doesn't affect nVidia doesn't make a whole lot of sense to me.
OpenGL: GeForce GTX 765M/PCIe/SSE2 GL version 4.4.0, NVIDIA Corporation
I haven't seen it in a while, however I have an nVidia card so I don't think it is specific to AMD.
I have been playing with VBOs off.
It didn't happen in the most recent session at all, however my game had auto-updated to 30b. When it did happen I did have VBOs off. I'll try again with 29b and see if it happens and try to answers your questions.
On a side note, I was wrong about the Savanah, the new chunks (and the first chunks where I saw the error) are in fact Savanah, so it could definitely have copied from those chunks.
As I noted, I don't think it is wholly graphical. There is a place on my map where the elevation is high enough that I can enter the chunks. When I do that the environment (grass colour & sky) changes rapidly between biomes; as well as the biome listed in the log (in F3). Additionally moving through the chunk only works for a handful of blocks before it becomes difficult to move. I would assume that that is just the actual geometry for the block, but movement becomes jittery and sluggish until I move back out.
Additionally, I am not so sure there place in my world that is Savanah for it to have copied from (I often use 16 chunk viewing while exploring and haven't gone beyond the edge of my maps; none of which show any sign of Savanah).
If I have the chance I'll poke around a bit more this evening though, in case there is additional info I can provide.
No. It is an issue that either happens w/ low frequency on nVidia cards, or has been fixed on that chipset in the interim. Either way that is information that is helpful to programmers in identifying what the issue is. It allows changes that have been made recently to be evaluated as potentially exposing discrepancies between AMD and nVidia chipsets. If it has been fixed, that narrows down the possible set of commits to look at.
Low-level issues like this are a pain to diagnose to begin with; discarding information is not helpful.