Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add mode for run telemetry #202

Open
vabold opened this issue Dec 20, 2024 · 1 comment
Open

Add mode for run telemetry #202

vabold opened this issue Dec 20, 2024 · 1 comment
Labels
engine Code involving engine (C++) feature New code good first issue Good for newcomers P3 Priority: Low

Comments

@vabold
Copy link
Owner

vabold commented Dec 20, 2024

Fun exercise left for first-time contributors. I ask that long-time contributors keep solutions to themselves - this can be a fun way for new people to get into the physics engine and figure out what really happens per frame.

The base game already has existing telemetry in the form of stats structs found in KartSettings. For example, in Grand Prix, the game tracks the miniturbo count, whether or not a start boost was applied, how many frames were spent in offroad, etc. Kinoko can be leveraged to track way more interesting data - how many frames were wasted in a full MT charge? What's the set of unique triangles and objects the run collided with? How many frames of trick airtime are there?

@vabold vabold added engine Code involving engine (C++) good first issue Good for newcomers P3 Priority: Low feature New code labels Dec 20, 2024
@malleoz
Copy link
Contributor

malleoz commented Dec 20, 2024

Can you clarify how this would be different from a generic "Frame Step Mode"? Is the idea that Kinoko itself would keep track of this telemetry data rather than the user defining their own code?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
engine Code involving engine (C++) feature New code good first issue Good for newcomers P3 Priority: Low
Projects
None yet
Development

No branches or pull requests

2 participants