CrispyPin/sinpin-vr
1
0
Fork 0
mirror of https://github.com/CrispyPin/sinpin-vr.git synced 2024-11-09 20:10:25 +01:00
Code Issues Projects Releases Packages Wiki Activity
SteamVR/OpenVR overlay for Linux/X11 that displays the screen in VR
44 commits 1 branch 5 tags 2.1 MiB
C++ 99.8%
Makefile 0.2%
Find a file
CrispyPin 858da78820 bump version
2023-04-29 18:31:54 +02:00
bindings use separate steamvr action sets for different modes 2023-04-29 17:40:03 +02:00
openvr init - display part of screen on a vr overlay 2023-04-02 14:34:52 +02:00
src color code lasers 2023-04-29 18:14:15 +02:00
.clang-format reposition overlay with trigger+B 2023-04-03 21:15:43 +02:00
.gitignore add release to makefile 2023-04-22 20:02:09 +02:00
LICENSE Create LICENSE 2023-04-22 20:47:34 +02:00
Makefile bump version 2023-04-29 18:31:54 +02:00
README.md update demo video 2023-04-29 18:31:17 +02:00

README.md

sinpin-vr

A SteamVR overlay for Linux+X11 that displays all your screens in VR.

https://user-images.githubusercontent.com/54243225/235313348-2ce9b2d8-8458-49f8-ba94-16e577c4f502.mp4

Note: only index controllers have default bindings right now, feel free to make a PR.

features

  • one overlay per screen
  • shows cursor position
  • global visibility toggle (default: long press left B)
  • reset positions (default: long press left A)
  • activate cursor input (default: press touchpad)
    • left mouse default: trigger
    • right mouse default: A
  • edit mode (default: long press press right B)
    • move screens around (default: trigger)
    • resize screens (move with two controllers)
    • push/pull screens (default: joystick up/down)
    • move all screens at once with the same controls by grabbing the purple square

performance

From my limited testing, this uses about half the CPU performance of Steam's built-in desktop overlay, if running at 60 FPS. Currently the default is 30 FPS which brings that factor to 3-4x. On my machine, the Steam desktop view increases cpu usage by about 100% of a CPU thread (looking only at the steam process), while this overlay uses around 25% at 30 FPS and 45% at 60 FPS.