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

Bug on trying to move over the edge of loaded playworld. #4979

Open
Ygarr opened this issue Jan 9, 2022 · 1 comment
Open

Bug on trying to move over the edge of loaded playworld. #4979

Ygarr opened this issue Jan 9, 2022 · 1 comment
Labels
Category: Performance Requests, Issues and Changes targeting performance Status: Needs Investigation Requires to be debugged or checked for feasibility, etc. Topic: Stabilization Requests, Issues and Changes related to improving stablity and reducing flakyness Topic: WorldGen Requests, Issues and Changes related to facets, rasterizers, etc. Type: Bug Issues reporting and PRs fixing problems

Comments

@Ygarr
Copy link

Ygarr commented Jan 9, 2022

v: 5.2.0
If the world not loaded properly and you stay on the edge of viewable blocks - you cannot move, stuck, cannot return to loaded part of world.
And it is a lot of waiting time need to stay while world began to load. And you wasting your time instead of go further.

@Ygarr Ygarr added Status: Needs Investigation Requires to be debugged or checked for feasibility, etc. Topic: Stabilization Requests, Issues and Changes related to improving stablity and reducing flakyness Type: Bug Issues reporting and PRs fixing problems labels Jan 9, 2022
@skaldarnar skaldarnar added Category: Performance Requests, Issues and Changes targeting performance Topic: WorldGen Requests, Issues and Changes related to facets, rasterizers, etc. labels Jan 9, 2022
@skaldarnar
Copy link
Member

skaldarnar commented Jan 9, 2022

Thanks for reporting!

This seems to be another instance of the well-known "world gen is too slow/performing badly/misbehaving". This is regularly happening during play tests as well. The severity/extent varies drastically on different machines.

We need to collect all the info we can get on this at one place at some point to really dig into what is happening here.

As a "quick fix" sometimes changing the rendering distance helps to re-generate the chunks (you can easily change it with Page Up/Page Down, I think).

Related Issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Category: Performance Requests, Issues and Changes targeting performance Status: Needs Investigation Requires to be debugged or checked for feasibility, etc. Topic: Stabilization Requests, Issues and Changes related to improving stablity and reducing flakyness Topic: WorldGen Requests, Issues and Changes related to facets, rasterizers, etc. Type: Bug Issues reporting and PRs fixing problems
Projects
None yet
Development

No branches or pull requests

2 participants