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
Just wondering, why are you focusing on generating a map? I feel like other things might be much more useful for example:
Averages
Damage per weapon
Damage per legend
Damage per fps
Damage per horizontal speed
Average speed by match
Also an overall detailed game history would be useful for those who don't want to pay for these stats trackers with half-broken APIs
Haven't touched kalman in like a year but if you're planning to release for others and want an electron dashboard for analyzing stats, I could build react ui for it
The text was updated successfully, but these errors were encountered:
The PoseEstimator class' purpose is not only to generate a map. Its main purpose is to find our location at any point in the input video. This means that at the end of each game parsed by the tool we can generate a match summary plot, with kills etc. drawn on the map.
This enables a lot of features in the future. For example, with a lot of parsed games containing information on the position of each kill and death, we can generate a heat map giving information about where the player tends to get kills, and where the player tends to die.
I like some of your average stat information! Particularly damage per weapon and legend, I will add those to the planned mid-term features.
Just wondering, why are you focusing on generating a map? I feel like other things might be much more useful for example:
Haven't touched kalman in like a year but if you're planning to release for others and want an electron dashboard for analyzing stats, I could build react ui for it
The text was updated successfully, but these errors were encountered: