-
-
Notifications
You must be signed in to change notification settings - Fork 525
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
feat: Remove SteamVR driver registration modes #2755
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just realized the (i forgor)
alvr/dashboard/src/main.rs
Outdated
// Kill any other dashboard instance | ||
let self_path = std::env::current_exe().unwrap(); | ||
for proc in sysinfo::System::new_all().processes_by_name(OsStr::new(&afs::dashboard_fname())) { | ||
if let Some(other_path) = proc.exe() { | ||
if other_path == self_path { | ||
proc.kill(); | ||
} | ||
} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I get the rough intent, but what exactly would the conflict be, as long as both aren't starting an instance of steamvr?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is helpful for a check I added on the driver side, to cancel driver startup if the driver instance does not correspond to the current opened dashboard. This is because by not unregistering the ALVR driver, multiple ALVR drivers might attempt loading. And we still want to support the use case of switching between multiple ALVR versions.
Since only one driver is allowed to start at any given moment, then we should also force to have only one dashboard
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess it's fine, I think we should probably output a warning when doing that so it's less confusing
Also fix the failing checks, ideally using the path shortcut thingy from the adb pr |
a3392f3
to
a1a42a0
Compare
a1a42a0
to
faf414b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The one comment + the failure on linux
9e9226e
to
9102c12
Compare
9102c12
to
42289f9
Compare
At SteamVR launch, unconditionally register the ALVR driver. Also remove driver list backup.
In this PR I implement some sanity checks, that are now necessary since there is no unregistration of the driver:
This should be sufficient to handle multiple ALVR installations (Steam release or not).
This PR should be merged only after #2754 and #2757