The Compositor class creates an instance of the Compositor for the application that can be used as a factory for a variety of types in the Windows.UI.Composition namespace spanning the visual layer, effects system and animation system. To pull the container and start it on the module, choose your hardware. Manages the session between an application and the system compositor process. I also welcoming conversation about VR, and games that may or may not be on steam. The container is Debian Bullseye release based, featuring the Weston Wayland compositor. I know this may not help the OP, or anyone who has commented thus far, but perhaps others who run into the same problem like we have.ītw shoot me a PM(+)Friend request if any of you play Hordez, Hover junkers, Airspace, or any of the other MMOs currently out for vive :)
#LAUNCH COMPOSITOR SOFTWARE#
I will add, I experienced the same problem with mine, and it happened a few times, first time I tried fudging it with a laptop that used a gtx 960 (desktop card ver), which is insufficient power lol, but the second time I experienced it was on my current rig with a 1070 in it, the issue for me was resolved by tweaking display settings in my PC and doing a few power cycles, as well as reinstalling steamVR and Vives own software for it.
#LAUNCH COMPOSITOR WINDOWS#
By running a Wayland compositor directly in your Windows machine, you avoid all the aforementioned problems. Ideally your Vive should be plugged into HDMI, I'm not sure what it's support is for display port options, I also had no knowledge it could be run via DP instead of HDMI. With the WSL subsystem on Windows, it is actually possible to run directly (albeit through an X server and so far unfortunately only OpenGL software) a Wayland compositor and clients.