Jump to content
 

Wearied

Verified Members
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

5 Neutral

About Wearied

  • Rank
    Contributor

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. THE BONE FINALLY WORKS NOW! I will let you guys know if there is any future errors!
  2. Thank you guys so much! Just a quick question, how exactly do I opt i to the beta? Is it in the settings?
  3. @stvnxu Hello! I was 100% referring to the Vive Console! My bad! And thank you so much for responding back!
  4. Hello dear reader! (And VIVE Employees!) It has come to my attention that in the game Boneworks. The glitch of flying out of the map with a windy screen is not on the developers of the game, Stress Level Zero's fault. After I talked with developers of Boneworks, this glitch is not fixable on their part. Instead, it is on VIVEPORT'S part. For some reason the software of VIVEPORT wants to fling your character 10,000 meters away from the origin point where you respawn, thus causing you to go into an endless void with wind noises. A quote from one of the developer's was "the vive cosmos was reporting a starting location of (0, 0, 10,000) meaning the viveport tracking setup is bugged by ten thousand meters on the z axis". Apparently this problem is present because Boneworks uses a different style of tracking that is called skeletal system tracking (I think it has to do with the special physics of your character within the game). It has been the lack of compatibility on VIVEPORT's end with SteamVR, so in order to fix this problem, VIVEPORT just needs to update their system to accept this skeletal system tracking. Hopefully my explanation was good enough, I'm trying my best to explain the situation, but some concepts I may have not nailed one-hundred percent. Please correct me if needed. To the Employees at VIVE. Have you guys noticed this problem before, for the VIVE Cosmos? If so, how is the progress on the compatibility of this Skeletal System Tracking? Also here is my output log of the error. Hopefully this helps! output_log.txt
×
×
  • Create New...