Terrain-relative height proof of concept #44
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 isn't really intended to be merged - I've basically taken a stab at what was discussed here #33 and would like a general idea of how horrifying the implementation is from someone who has a better idea of how things are supposed to work.
I used the class name suggested in the discussion, but it's probably not a good choice as it might get confusing with there also being an ECS that also has entities.
It should probably automatically dirty itself when new LOD is streamed in or out as otherwise a feature that is only represented at certain LOD levels may lead to a node ending up underground or floating. I've not implemented this yet, though.