VRZach

@HackPerceptionThanks for the quick response. I had sort of figured that most of the programmable interface was pipe dreaming. Good to know about the primary and secondary stations. I didn't know that was part of the system. Also didn't know that pinhole, could be useful. Thanks again.

Hello, I'm developing a turn key product that utilizes the Vive. The product uses physical props and a "booth" style area of tracking. The product aims to use 2 base stations per booth in order resolve the occlusion issues caused by our untracked props. In some cases there will be many of these booths setup next to each other. For the most part we can solve tracking issues by using different base station channels and adding partitions between bays (as seen in other forum discussions). However, I have some questions on edge cases and how customizable I can make the experience. The main goal is make sure the users never have to touch SteamVR. Also to give some background, I'm using OpenVR in a OpenSceneGraph (C++) application on a Windows 10 computer. if not known then if you can answer the questions generically that would be great. Is it possible to set a base station's channel externally from the SteamVR configure channel interface? Can I set them via code or through command line? The SteamVR Status UI greys out any duplicate channel base stations. When this happens, how is it determined which "channel 1" base station is being used? by distance? by which base station is seen/configured first? When a Vive hmd/tracker sees multiple base stations, Is it possible to set which base stations are used for tracking via code? For example, to say I only want tracking from base station LHB-########. I tried to give enough information to allow for answers but not too much to be TMI, so let me know if more detail is needed. Thanks for your time