This repository has been archived by the owner on Feb 16, 2024. It is now read-only.
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.
On a superflat world in the malisisdoors environement with ~100 doors with these changes I go from 100 to 220 FPS, and allocation rate reduces from ~1.2GB/s to 800MB/s. Any more changes would require more significant refactoring of the code, but this should make door rendering less of a bottleneck.
I change a protected field type from a List to an array, but it looks like none of the malisis mods use it or even subclass RenderParameters, so it shouldn't cause ABI breaks.