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

The block_buffer value in flush_block_buffer may be too aggressive #4

Open
telarium opened this issue Apr 18, 2017 · 0 comments
Open

Comments

@telarium
Copy link

I was running into performance issues when writing Python code that would set a single block every few seconds, resulting in some fairly significant frame hitching.

Eventually I was able to track down the problem to the "vm:write_to_map()" operation in the flush_block_buffer. Currently it is writing to the map even if the block_buffer contains only a single block.

if #block_buffer >= 1 then

I would suggest changing this to a higher number so that it doesn't copying a 16x16x16 mapblock every time a small number of blocks have changed.

I'm running this project on a 32-bit ARM processor with OpenGLES v1 support.

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

1 participant