Editor framerate improvement(s) #78
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
22 FPS! :) |
|
Improving the framerate further requires editing the BezierCurves library, which I will leave for another time/PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
fixes #40
I changed the track snap code to only execute when necessary instead of every frame. I managed to increase the framerate in the editor from 3 to 7 FPS with these changes, in a test map with a big yard.
Before (note the yellow FPS counter):
before.mp4
After:
after.mp4
7 FPS is still really low so I'm going to look for more code to optimize. Opening this PR as a draft for feedback