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

After returning, the non-reset of the map results in performance strain. #73

Open
IoIqq opened this issue Mar 31, 2024 · 2 comments
Open

Comments

@IoIqq
Copy link

IoIqq commented Mar 31, 2024

After multiple landings, I realized that I might repeatedly touch down at the same location. Due to the brief duration spent in each such area, every landing effectively uncovers a fresh chunk of the world, thereby incrementally increasing the computational load on my game.

@adamkad1
Copy link
Contributor

After multiple landings, I realized that I might repeatedly touch down at the same location. Due to the brief duration spent in each such area, every landing effectively uncovers a fresh chunk of the world, thereby incrementally increasing the computational load on my game.

Thats been acknowledged by the author since early times, but they have no idea how to fix that

@IoIqq
Copy link
Author

IoIqq commented Apr 20, 2024

After multiple landings, I realized that I might repeatedly touch down at the same location. Due to the brief duration spent in each such area, every landing effectively uncovers a fresh chunk of the world, thereby incrementally increasing the computational load on my game.

Thats been acknowledged by the author since early times, but they have no idea how to fix that

And it seems there is a probability of landing at a previously visited location.

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

No branches or pull requests

2 participants