Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Voxels at edges of map affect those on the opposite side #225

Open
fkaa opened this issue Oct 28, 2015 · 2 comments
Open

Voxels at edges of map affect those on the opposite side #225

fkaa opened this issue Oct 28, 2015 · 2 comments

Comments

@fkaa
Copy link
Collaborator

fkaa commented Oct 28, 2015

For example, you can place blocks in the air if there is a corresponding block on the opposite side of the map. It also affects AO stuff (mostly because it's done through texture lookup (?) and it wraps (?))

bug

@rakiru
Copy link
Collaborator

rakiru commented Oct 28, 2015

I imagine this is largely a deliberate thing, as the map used to loop. You couldn't walk in or affect it, but it was rendered and you could place blocks off it. It does need fixed of course, but at least some of it should be easy to find as it's explicitly done.

@iamgreaser
Copy link
Owner

If you just want to prevent the wrap on the AO and it affects the compat mode which still lets the map wrap, I really don't care - as long as the compat is "pretty much there" (i.e. the map still wraps) and the only issue is an AO artifact, then if someone wants to cry about it feel free to just punch them in the face.

This DOES make me realise that the shader will need fixing, though, just so that the heightmap doesn't cast a shadow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants