Repository navigation
First run: no red errors for a working stream; USB setup steps (.136) - #25
Merged
Merged
Conversation
A fresh .135 install streamed Quality 120 at 119 FPS of 120, but the dashboard's notification bar showed the 5 s tracking and pose diagnostics as red errors the whole time. The bar now skips those diagnostic tags; crash_log.txt and the Logs tab keep them. A handshake timeout while the headset app starts logs at info. The README's first-run steps name Register ALVR driver and Devices -> Wired Connection, and say SteamVR restarts once on the first connection.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Found by a first-time setup of beta.2 (
.135) on a Quest 3 over USB: a fresh folder, no session file, Wired Connection switched on. It streamed Quality 120 at 119 client FPS of 120 (1100 Mbit/s, ALVR latency 35 ms), but the dashboard showed a permanent red error bar.[Q3PW_TRACKING_RX],[Q3PW_POSE_EXTRAPOLATE],[Q3PW_UDP_SEND],[Q3PW_ENCODE_QUEUE],[Q3PW_LATENCY_STAMP],[VIEWS]). They stay at error/warning level, socrash_log.txt,vrserver.txtand the Logs tab keep them for the measurement tools.TryAgain) while the headset app starts logs at info instead of error.Local
fast_build.py test: all suites pass, including the newstream_diagnostics_do_not_notify.