07-03-2018 05:38 PM
@andrewtric, Unfortunately since this seems like a pretty hardware specific issue - I would need that exact model of notebook on hand to reproduce and understand your individual user experience. The goal isn't to be in "extended mode" but to be in "direct mode" as "extended mode" causes all sorts of compositor issues and can force the HMD's framerate to diverge from the intended 90hz. Doing a print screen is always a little funky when dealing with extended setups but it seems like it's thinks there are 3 overall displays?
I would recommend continuing to experiment until you find a reliable procedure to launch the compositor. Aim to get "direct mode" working if possible rather than using extended mode.
07-03-2018 05:55 PM
07-03-2018 06:10 PM - edited 07-03-2018 06:11 PM
@andrewtric, since you're using a dock to connect the Pro, there are all sorts of additional complexities that are very difficult to account for. It looks like the dock relies on a registry file to scrape it's settings - that may be a path worth exploring. It looks like the surface may use Windows 10 S.
07-03-2018 06:31 PM - edited 07-03-2018 06:31 PM
Thanks @VibrantNebula and just downloaded the registry file and will try to reconnect my VIVE PRO at home later. I've a chat with this guy from Intel, he told me not to install the VIVE software, but start only with STEAM.
'My experience was as follows in 2016 was as follows. I installed Steam on the Surface Book. I connected my Vive Headset. I installed SteamVR, ran through set up. The start up tutorial started but was extremely slow. After that I installed Tilt Brush and that launched and ran better because most of the scene is empty space
'. I will reinstall everything this evening to try too. Below was his article on Intel:
Just wonder, if he able to connect his old version of Surface Book to VIVE; it must be a way for me to connect my Surface Book 2 with the VIVE PRO! Thank you very much @VibrantNebula for being patient with me!
07-03-2018 06:35 PM - edited 07-03-2018 06:44 PM
Another option. If I don't connect the Link box to my dock, I can connect the headset straight from the Linkbox mini display port to the USB type C directly onto my surface Book 2 if its better?
Something like this- USB C TO MINI DISPLAY PORT
07-05-2018 09:55 AM - edited 07-05-2018 09:57 AM
@andrewtric, I wouldn't draw direct comparisons between the Vive and the Vive Pro due to the massive change in bandwidth requirements as well as a complete change in the display signal pipeline. The ViveSW contains Viveport, additional drivers, and some companion software - It really won't affect the compositor in any meaningful way in regards to this cluster of issues.
As stated above, this is a pretty hardware specific thing - We don't have the ability to replicate your scenario with the exact hardware, software, cables, ect... I can't really speak to the USB-C port on that Surface. You'd first need to verify that that USB chipset can output Displayport 1.2+. I wasn't able to verify this using the documentation I was able to pull up. This is the adapter that we've had the most luck with.
07-05-2018 08:31 PM
Thanks @VibrantNebula for the information. I've cleared the Dock registry and will try again tonight. I've found something similar from LINDY- HERE. Similar product and I just checked with their support and they verified its a DisplayPort 1.2.
The previous user (who successfully paired hisMicrosoft Surface Book 2 to HTC VIVE) told me he didn't install the HTC driver. port and just jumped straight to STEAM. Will try that tonight too. Will keep trying!