[Feature Request] group Charts by session, not date #526

New Issue

MrUnknownDE · 2026-04-05T16:20:27+02:00

MrUnknownDE commented

2026-04-05 16:20:27 +02:00

Originally created by @jan-Sanku on 3/1/2025

Explain in detail what your suggested feature would be used for.

the new charts are awesome! but they do have some slight problems in how they're currently paginated/grouped. if you're active at night, specifically around midnight, all of your sessions will be split across "2 days," so you can't get a full chart of any session that lasted past midnight.
on the other hand, sessions that technically happened on the same day, say one around 01:00 and another around 23:00, are grouped on the same chart, making all of the data small. this isn't very useful!

so i propose that charts (optionally?) be grouped by session. how do we do that but account for crashes and restarts? set a timeout (possibly variable in settings) for which you have to be offline for a "session" to count as terminated. i think 1-2 hours is reasonable.

Describe how it would look if it requires a UI.

indeed a problem is how to select sessions in the UI. i think the date that the session starts on should count as its "date", and every session on that date should simply be indexed from 1.

so if i log on for the first time on 2025-03-01 at 23:00 local time, the session is dated for that day (even if it lasts past midnight) and numbered as "session 1" for that day. if i log out long enough and get back on 5 hours later, that'd be session 1 of 2025-03-02, and if i log on again on that day it'll be session 2 and so on. there could be a drop down next to the date selector to pick your session, or something idk i don't do UX.

either way, regardless of how it works, some way to not exclusively use dates for the charts would be great! and of course this could just be optional if there's people who prefer their charts to be cut off by midnight.

*Originally created by @jan-Sanku on 3/1/2025* ### Explain in detail what your suggested feature would be used for. the new charts are awesome! but they do have some slight problems in how they're currently paginated/grouped. if you're active at night, specifically around midnight, all of your sessions will be split across "2 days," so you can't get a full chart of any session that lasted past midnight. on the other hand, sessions that *technically* happened on the same day, say one around 01:00 and another around 23:00, are grouped on the same chart, making all of the data small. this isn't very useful! so i propose that charts (optionally?) be grouped by session. how do we do that but account for crashes and restarts? set a timeout (possibly variable in settings) for which you have to be offline for a "session" to count as terminated. i think 1-2 hours is reasonable. ### Describe how it would look if it requires a UI. indeed a problem is how to select sessions in the UI. i think the date that the session *starts* on should count as its "date", and every session on that date should simply be indexed from 1. so if i log on for the first time on 2025-03-01 at 23:00 local time, the session is dated for that day (even if it lasts past midnight) and numbered as "session 1" for that day. if i log out long enough and get back on 5 hours later, that'd be session 1 of 2025-03-02, and if i log on again on that day it'll be session 2 and so on. there could be a drop down next to the date selector to pick your session, or something idk i don't do UX. either way, regardless of how it works, some way to not exclusively use dates for the charts would be great! and of course this could just be optional if there's people who prefer their charts to be cut off by midnight.

MrUnknownDE closed this issue

2026-04-05 16:20:28 +02:00

Sign in to join this conversation.

No Label Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature Feature PR Welcome PR Welcome PR Welcome PR Welcome PR Welcome PR Welcome PR Welcome PR Welcome PR Welcome PR Welcome PR Welcome PR Welcome PR Welcome

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/VRCX#526