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.

Sign up for GitHub

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

Jump to bottom

Merge CaveBiomeMapView and InterpolatableCaveBiomeMapView #601

Open
IntegratedQuantum opened this issue Jul 31, 2024 · 0 comments
Open

Merge CaveBiomeMapView and InterpolatableCaveBiomeMapView #601

IntegratedQuantum opened this issue Jul 31, 2024 · 0 comments
Labels
optimization a performance problem that should be addressed or an optimization idea refactor shuffle a lot of code around terrain
Milestone
Short-Term Goals

Comments

@IntegratedQuantum
Copy link
Member

The only difference between the two is that the CaveBiomeMapView creates storage for an additional layer of 2d noise.
This noise layer could be moved into a separate cache, instead of regenerating (and reallocing) it every time.
And when it's just fetched from a cache, there is no reason, why we can't use it in the InterpolatableCaveBiomeMapView as well.
At same time it could also save some performance.
@IntegratedQuantum IntegratedQuantum added optimization a performance problem that should be addressed or an optimization idea terrain refactor shuffle a lot of code around labels Jul 31, 2024
@IntegratedQuantum IntegratedQuantum added this to the Short-Term Goals milestone Jul 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
optimization a performance problem that should be addressed or an optimization idea refactor shuffle a lot of code around terrain
Projects
None yet
Milestone
Short-Term Goals
Development

No branches or pull requests
1 participant
@IntegratedQuantum