Base Station FOV Viewer
A downloadable tool
A simple way to check the view ranges of your SteamVR 1.0 or 2.0 Base Stations in your play space. It supports 1 to 4 Base Stations automatically. To cycle though the visibility of the "FOV fields" press the 'A' button on in Valve Index Controllers, or click down on the touch pad on original Vive Wands. To open or close the Menu press the 'B' Button on the Index Controllers or the the menu button on the Vive Wands. I have also included binding for Oculus Touch Controllers in case anybody out there has a hybrid setup, this wont do anything for you unless your set up uses Base Stations.
Download
Click download now to get access to the following files:
Development log
- Now Support 1.0 Base Stations too!Jul 15, 2019
Comments
Log in with itch.io to leave a comment.
Is the only way to tell if you moved the beams enough, is to close and re-open the program?
Great little tool!
Any change of source for this project?
Or does anyone know of anything simple and clean like this to get a quick view of base stations with FOV and the chaperone/play aera?
It wouldn't be super difficult to remake using the SteamVR examples if nothing is out... but starting off with the project source would just be easier for my lazy ass ;)
for some reason wont download any help?
Been wanting a tool like this for a while, it's really sad SteamVR doesn't just have one included, it really help give me an idea where I could set up my Light houses and not worry if they could see things or not, thank you!
So, ran the program, but when i pull up the menu, its stuck on the floor instead of being attached to the wand and i cant access it. My base stations are v1.
the download isnt workin
Ended up working when i ran it first and allowed the program to auto launch SteamVR., which is odd. But fantastic tool for a new base station configuration, i love it.This worked great at first, great for double checking a new configuration. But now suddenly the program won't open at all, but creates duplicate processes. Very bizarre, and persists through a shutdown/restart/redownload. Anyone have this issue before?
Thank you so much for this tool. I have a tight space with a sloped ceiling and large desk, and I've been blindly attempting to improve tracking in my room to the point of desperation until I found your tool. In 20 minutes I had best tracking I've had in years because I could finally see where my coverage was. This should be a standard part of the Vive software kit. Again, THANK YOU!
This was absolutely perfect for my needs. Thank you!
Been having issues with my headset going grey constantly and being unable to troubleshoot since Valve removed the Room Overview tool in SteamVR.
This tool finally let me fix the issues. So happy! 🎉🎉🎉
Only piece I was missing, and I understand that's likely a SteamVR limitation, is being able to reposition my lighthouses and seeing the changes in realtime in the headset to help me finetune the positioning and angling of the lighthouses. A button in the ingame menu to trigger the "Quick Calibration" from the Steam VR developer menu would be perfect
Either way, awesome app, saved me a ton of frustration
Thank you so much! I am glad you found it useful.
And yeah I would bet Valve dose not want to suggest users move base stations while they are on. I would not recommend it either as they have moving parts equivalent to hard drive motors that could damage them selves if moved while spinning. Though its unlikely I still don't do it personally just in case is shortens their operation life.
They do provide a way to do it while the headset and lighthouses are active, the "Quick Calibrate" functionality in the Steam VR Developer Tools allows you to do that, though it's very clearly set as a developer tool 😁
But you're 100% correct with them having moving parts, so definitely not something to do often
Thanks for making this. It's really helpful when I am trying to figure out how to set up my room. I managed to get it to work, but not through the VR headset: I cant see anything if I look through the headset. I can see what is going on on the pc monitor. This still serves its purpose fine. hardware - HTC Vive + 2 base stations.
So I ran a test of the build today to try and reproduce this, unfortunately it work just fine for me and I don't have the resources to test it on a lot of different hardware configurations. If you would like, I could take a look at your logs to see if they give any hints at to what is going wrong. They are located at "C:\Users\<Your_User_Name>\AppData\LocalLow\MechaSquid\Base Station FOV Viewer\Player.log"
So I tried it on my laptop and everything works fine... Just a desktop problem. doing a clean install of everything and Ill post back.
Does this still work?
Yup it still should completely. If I get any reports it dose not I will fix it.
Hi. I've been using this program to position the one Valve 2.0 B.S.
Where should the green beam be placed in relation to the square?
How close should the "net or web" be to the square?
By square do you mean the marker at the center of your place space on the floor? If so this is part of that is part of the chaperon system. Ideally you probably want the green beams firing though about chest height if you are standing on the square. As for the "nets" that is the visualization of the fov, you just want to make sure that all of you intended play space in inside of them.
Thanks for Replying.
I do seated sim racing and last I used your program the single green beam is inside the chaperone and angled right in front if me from the left.
I only have One Valve Base Station atm, should I get another one? Can the V2 be run with a Version 1 Base station?
Version 2 base station are pricey. Which versions are better?
(This is from a Steam Support page)
(This is me talking)
So there is not a huge quality difference between the two, only get 2.0 if you have an Index or Vive Pro, other wise they will not work for you, and note that you will have to ditch your single 1.0 if you want to use 2.0. More base stations are better but if you are just doing cockpit sim stuff one could definitely be enough, it just depends if you are loosening tracking with your single base station.