You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The evaluation currently executes every single tween every single frame when in reality we only need to execute the "current" tweens. oldTweens and futureTweens only need to be evaluated the very first time and/or whenever we seek to a time that results in a different set of "currentTweens".
rendering.nim's way of handling FFMpeg Instances
Due to some issues I had with the osproc module, I couldn't keep one single instance of FFMpeg but rather have to instantiate one, use it for a short amount of time and then kill it. This createds a bunch of "parts" files which have to be stitched together by a final FFMpeg command. This whole process could be avoided if we only had one single process. This most likely has to do with osproc's way of handling stdin has a hidden buffer of some sort that gets filled by frame-data.
core.nim's drawPointsWithTension and drawPointsWithRoundedCornerRadius
Sooner or later both of these will be deprecated and replaced with one better "drawListOfBezierPointsAndHandles" or something like that, but currently these two procs recalculate the new points every single frame for every point in every entity. This could probably be cached.
The text was updated successfully, but these errors were encountered:
Areas with Known Big Performance Impact
needs fixing
fixed
tween.nim
's evaluate(tweenTrack, time)rendering.nim
's way of handling FFMpeg Instancescore.nim
's drawPointsWithTension and drawPointsWithRoundedCornerRadiusThe text was updated successfully, but these errors were encountered: