This repository has been archived by the owner on Nov 13, 2023. It is now read-only.
Add merger that supports ambient occlusion evaluation #24
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hmm, I can also see the chunk borders. Kind of cool with LODs but... :) And this is broken too: |
This is due to the anisotropic interpolation between vertices if all diagonals are oriented the same way, as noted at the end of this article: https://0fps.net/2013/07/03/ambient-occlusion-for-minecraft-like-worlds/
… written in years.
bonsairobo
force-pushed
the
main
branch
2 times, most recently
from
1bd1c6c to
af0582a
Compare
bonsairobo
force-pushed
the
main
branch
2 times, most recently
from
5dfcb24 to
790ac87
Compare
bonsairobo
force-pushed
the
main
branch
4 times, most recently
from
3199918 to
4e9e0c1
Compare
bonsairobo
force-pushed
the
main
branch
7 times, most recently
from
8645945 to
a69d051
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is still not correct as can be seen in the image below, but I think it is close. It can surely be more optimised as it is likely calculating the AO value multiple times per vertex position. I was thinking that perhaps a hash table of Stride, i32 in the merger could be used to avoid recalculation.