While you're here, please consider supporting GamingOnLinux on:
Reward Tiers:
Patreon. Plain Donations:
PayPal.
This ensures all of our main content remains totally free for everyone with no article paywalls. We also don't have tons of adverts, there's also no tracking and we respect your privacy. Just good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Reward Tiers:


This ensures all of our main content remains totally free for everyone with no article paywalls. We also don't have tons of adverts, there's also no tracking and we respect your privacy. Just good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register
- Valve puts the Steam Deck and Dock on sale again, get up to 20% off
- Unity attempt to clarify new install fees as developers revolt
- Terraria dev Re-Logic donates $100K to Godot Engine and FNA, plus ongoing funding
- Steam Deck OS 3.5 now in Preview with HDR, VRR and display colour settings
- Tomb Raider I-III Remastered heads to Steam from Aspyr
- > See more over 30 days here
-
Proton 8.0-4 is now in testing with a Release Candidate…
- Guppy -
Halo: The Master Chief Collection multiplayer seems bro…
- ElectricPrism -
Halo: The Master Chief Collection multiplayer seems bro…
- MayeulC -
Robot Gentleman dev of 60 Seconds! blasts Unity, switch…
- const -
Proton 8.0-4 is now in testing with a Release Candidate…
- Geamandura - > See more comments
Latest Forum Posts
- New Desktop Screenshot Thread
- StoneColdSpider - MS wants to buy Valve
- Cyril - Games with Unreal Engine do not work
- Grogan - GOL User Stats Discussion
- Grogan - Weekend Players' Club 9/15/2023
- Pengling - See more posts
[scaine@Groovy Misc]$ python vr.py on
Found LightHouse LHB-8EC485F4: address = eb:d5:71:cb:29:0e
Found LightHouse LHB-A3646DA1: address = e4:b7:92:e0:d4:50
Connecting to eb:d5:71:cb:29:0e
Connecting to e4:b7:92:e0:d4:50
If you don't get anything, at all, I can't imagine what the problem might be...
Last edited by scaine on 10 October 2020 at 8:42 am UTC
I haven't tested this, but you could try this:
python /path/to/vr.py && %command% && python /path/to/vr.py
Thanks jens. I'd already tried that, and tried using the `wait` command. But thanks to the way Steam forks off the new game, the whole command is run immediately. It's unfortunate, because this would have been pretty slick otherwise.
mmh, strange, I needed to do something similar with Ferals Tom Raider and ended up with:
nvidia-settings -a AllowFlipping=0 && gamemoderun %command% && nvidia-settings -a AllowFlipping=1
I'm pretty certain that it had worked here. Though I guess you are correct that it has to do with forking a new process, I guess Tomb Raider does not do this.
Did you edited the launch option for a certain game or for SteamVR itself? May be trying one or the other would make a difference.
PS: You could also wrap steam completely into this. I haven't looked, but I guess steam knows command line arguments to start an application (SteamVR) on launch, which would make this somewhat acceptable imho.
Last edited by jens on 10 October 2020 at 2:17 pm UTC
View cookie preferences.
Accept & Show Accept All & Don't show this again Direct Link
Wait... I got one output after repeating the script several times:
Traceback (most recent call last):
File "/home/marco/vr-lighthouse.py", line 30, in <module>
scanner.scan(2)
File "/home/marco/.local/lib/python3.8/site-packages/bluepy/btle.py", line 853, in scan
self.process(timeout)
File "/home/marco/.local/lib/python3.8/site-packages/bluepy/btle.py", line 840, in process
isNewData = dev._update(resp)
File "/home/marco/.local/lib/python3.8/site-packages/bluepy/btle.py", line 696, in _update
raise BTLEInternalError("Address type changed during scan, for address %s" % self.addr)
bluepy.btle.BTLEInternalError: Address type changed during scan, for address 40:4e:36:a5:37:a0
I also do have yellow warnings inside SteamVR but I guess that's just "normal" on Linux?!
View cookie preferences.
Accept & Show Accept All & Don't show this again Direct Link
What distro are you on? Are you on the Steam Beta? Are you on the SteamVR Beta? Can you post a screenshot of running the script in your terminal?
Just installed Steam through Pamac. Installed packages are: steam-manjaro 1.0.0.66-1 and steam-native 1.0.0.62-3.
I do have Proton 5.0.3 globally enabled on the Steam settings but I just Start Steam from Manjaro menu. No betas.
View cookie preferences.
Accept & Show Accept All & Don't show this again Direct Link
Here's a gif showing it.
I have no idea how to help you here, I'm afraid! Other than KDE, you're running what I was running when I got this working for the first time!
Like normal for me as it´s the same on Windows. I would not be suprised you didn´t know of this! Many don´t like I read here and there online ^^
What do you mean by "always output"?
When I ran the script, it was always like on the gif. No output at all.
After giving it up and restarting my PC this evening I do get the above posted error every time now. And the lh stations aren´t anymore on the KDE bluetooth manager nor is there any bluetooth device listed anymore.
Restarting on Windows I do have everything working fine though the bluetooth settings inside SteamVR did show some error now. Power reset of Vive fixed this. Have that yellow warning signs on Windows now, too. But base stations power up and down without issues.
https://github.com/ValveSoftware/SteamVR-for-Linux/issues/207#issuecomment-691535293