The Sports2D package’s memory consumption kept trending upwards the longer I ran the program for. I was able to trace the “leak” pretty easily with Gemini. Basically, the program was storing frame data for each user because of a setting in its default config related to person ordering.
person_ordering_method = 'on_click'
Changing that setting reduced memory uptick significantly, but it was still trending up over time. Gemini was able to easily pinpoint why this was happening. Basically, we were still storing frame data in the program for post-processing. I vibe-coded a flag I could set in order to turn this off, and sure enough, the program memory stopped increasing after that.
Sticking around ~1,300 MB ain’t bad, considering yesterday I ran it up to 45,000.
My next goal is to implement a line renderer in Unity to show the character tracking.