Skip to content

add tracker timeout setting#1787

Open
art0007i wants to merge 4 commits intoSlimeVR:mainfrom
art0007i:main
Open

add tracker timeout setting#1787
art0007i wants to merge 4 commits intoSlimeVR:mainfrom
art0007i:main

Conversation

@art0007i
Copy link
Copy Markdown

@art0007i art0007i commented Mar 14, 2026

Resolves #1505
SolarXR-Protocol pr: SlimeVR/SolarXR-Protocol#201

@github-actions github-actions Bot added Area: Application Protocol Related to communication with apps like the GUI, overlay, games Area: GUI Related to the GUI Area: Translation Improvements or additions to translations Area: Server Related to the server labels Mar 14, 2026
if (this.duration < 1f) {
this.duration = 1f
}
if (this.duration > 1000000000000000f) {
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the idea was that it's a floating point setting which is being multiplied by 1000 and turned into a "Long", so I put an upper bound to prevent potential overflow

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

make it long then maybe...

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe, but if it was a long, it would be in ms, which I think typing values in milliseconds in the ui would be weird.

I could make it so the server stores the number as a long, and the gui uses floats but performs all of the conversion before sending it, but from what I understand the solarxr stuff allows other apps to also listen to the same messages, in which case receiving a time in seconds as a float is 'nicer' than milliseconds as a long in my opinion

@Eirenliel
Copy link
Copy Markdown
Member

This doesn't seem to actually implement the functionality.

@art0007i
Copy link
Copy Markdown
Author

This doesn't seem to actually implement the functionality.

It just modifies the default behavior which is 2 seconds of no data = tracker is timed out, 5 seconds of no data = tracker is disconnected.

I made the time when the tracker is timed out but not disconnected adjustable, so I can set it to like a million and my trackers will never show up as disconnected, only timed out, which is what was suggested in the issue.

Comment thread gui/public/i18n/en/translation.ftl Outdated
Comment on lines +763 to +771
<Input
type="number"
control={control}
name="timeout.duration"
label=""
min={1}
max={1000000000000000}
step="any"
/>
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why not use a NumberSelector?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I want to be able to type into it

@art0007i
Copy link
Copy Markdown
Author

what does "SolarXR PR found but no change on the submodule." mean on the failing check?
I just updated my repo so that the submodule matches the current one that's in SlimeVR-Server/main, which includes the merged commit from my SolarXR PR

@sctanf
Copy link
Copy Markdown
Member

sctanf commented Apr 16, 2026

It got merged so it is probably just confused now, since the merged pr is still linked on this pr

@loucass003
Copy link
Copy Markdown
Member

if no done already you need to point solarxr to main

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area: Application Protocol Related to communication with apps like the GUI, overlay, games Area: GUI Related to the GUI Area: Server Related to the server Area: Translation Improvements or additions to translations

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Freeze rotation when tracker disconnects

5 participants