stvnxu

@Kilanat The solution has been identified for Kastle in a separate thread. Kastle needed a vBIOS update. Shoutout to T for the help. Please refer to this thread:

Hi @Patrik, We apologize for the tracking issues you're experiencing! Let me help you try to resolve this - I'll need a bit more information from you to fully understand your tracking situation: 1. What software version are you currently on? To find out: Open Vive Console > Click Dashboard (three lines on top left) > About 2. Are you getting any notifications about your tracking environment when in the headset? (e.g. low lighting) If so, then try optimizing your environment based on the notification message. For example, a low lighting notification would suggest to have brighter lights to help with your tracking. Please submit an issue report for us to improve your tracking experience: https://forum.vive.com/topic/6662-how-to-report-issue-through-vive-console/ 3. What is it exactly that is not tracking? Your controller or headset? or both? Check your Vive Console dashboard - do all three hardware icons (2x controller, 1x headset) light up? 4. Could you specify what part of the process is unplayable? Is this regarding a specific content or hardware such as headset not displaying? Again, we apologize for these issues you're having. Our team is committed and addressing these with fixes in ongoing updates. Here's our promise: https://blog.vive.com/us/2019/10/07/vive-cosmos-continuing-update/ Here's our recent update v1.0.5: https://blog.vive.com/us/2019/10/18/vive-cosmos-release-notes/ Steve

@wky1995, You can capture camera image by enabling mirror view in your Vive Console settings then taking a screenshot of the mirror view window. Beyond that, users and developers cannot access Cosmos camera data at this time. Steve

Hi @Shezzar, Thanks for reaching out. Here are my responses to your issue: Your tracking experience can be improved with brighter lighting settings if you are getting a low lightning notification. There is two easier ways of accessing the pass-through camera feature! 1. When wearing your Cosmos headset, press the button on the left side of your headset next to the power indicator light. This button will activate your pass-through camera. You can turn it off by pressing the button again. 2. Double press the Vive button on your right controller. This will also activate your pass-through camera. Double press the Vive button again to turn off the camera. If this doesn't work, you'll need to enable this feature in your settings. VIVE Console > Dashboard (three lines) > Settings > Camera > Check the box with double press VIVE button to enable camera. If you're having tracking issues with the low light notification, you can send us an issue report. This will collect your logs and be sent to our engineering team to look into and improve upon in our next software updates. Here are the instructions to do so:

@Kev1966 Unfortunately, no updates yet. Thanks for following up. I've just re-escalated this issue and will hope to hear something back by this week. Stay tuned. Thank you for your patience.

Hi @Jean-François Watier, Apologies on the late reply! I schedule myself to respond to this forum section during the weekdays. I read yours, but it slipped past me to respond after. Sorry again for that! First of all, I'm sorry you are experiencing these issues. Second, your right controller never snapping back in place is an issue we are aware of, and our engineering team are looking at and addressing. Third, can you confirm you are still experiencing this with the latest software update (v1.0.5)? Lastly, could you help us submit an issue report through your VIVE Console, then provide me your Trace No.? I will personally send your report to our engineering team to look at your logs so that we may investigate along with the other similar ones and find a fix soon. Here are the instructions on how to submit a report: TLDR: Vive Console > Click > Settings > Go to Troubleshooting > Report issue > REPORT Thank you for your patience. Steve

Thanks again @T !

@Phr00t & @Fink, Our engineering team updated me last night, and they are aware of this and looking into it. That's the latest I have so far, and the good news is that it's on their radar and are active about this topic. I'll update you when I hear more here. Also, feel free to follow up end of next week. Thanks, Steve

Hey @TomCgcmfc, You are quick on our update! Thank you for sharing. I'll report this back internally and see if we can reproduce on our end. We're glad it's working though, and completely understand the confusion this error code may cause. Three questions: During Beta, did this error code ever pop up? Have you already tried restarting your computer? If so, does this error code still pop up? Could you submit an issue report through the console? Your logs will be collected and I'll attach it to our report. If you can give me your Trace No., that'll make it easier for me to find too. https://forum.htc.com/forums/topic/6662-how-to-report-issue-through-vive-console/ Thanks TomCgcmfc for being active and engaging with our forum community here! You've been super helpful for us all and we really appreciate you. Steve

Hi all, Our latest update is out now to improve your overall Cosmos experience! Open your VIVE Console, and you'll automatically see a "Software Update" button if you're not on this latest version. VIVE Cosmos 1.0.5 – Release Notes 1. Room setup performance improved for low light environments. 2. Resolved a USB audio driver compatibility issue where audio would not play on certain system configurations. 3. Updated multiple languages strings throughout the out of box setup, Vive Console, and Origin. - Support for multiple languages on “Learn more page” in controller pairing (Arabic, Chinese (Traditional/Simplified), Czech, Denmark, Dutch, Finish, French, German, Italian, Japanese, Korean, Norwegian, Polish, Russian, Spanish, Spanish-US, Swedish) - Fixed Russian string overlap issues in Vive Console - Fixed Japanese missing character in Origin - Support Czech language in Origin Next Update (Late October Beta) We have seen the community feedback and are continuing to work to improve tracking overall. Our next update targeted for beta at the end of October will work to improve the following scenarios: HMD: Improved low light tracking, with better prediction during fast movements Reduced tracking jitter Compatibility for Vive Wireless Adapter Controllers: Low light tracking stability – we will be continuously improving tracking accuracy in low light conditions High brightness tracking stability – we will be improving tracking accuracy in high brightness environment Overall improvement for prediction models when a controller exits the headset’s FOV Faster and more accurate positional recovery when returning into the headset’s FOV Improved near HMD tracking, which should improve archery mechanics in games Improved slow movement occlusion tracking prediction We will have more optimizations and improvements not mentioned here that we will detail closer to release.

@wandaweb, Ah love your determination and tenacity in resolving this! Thanks for finding and sharing your quick fix. We are aware that lighting conditions can affect tracking and will be pushing ongoing software updates to improve this. Your case is the first I've seen so I'll submit this to our internal team to address and fix for future updates. If you have the time, could you help us submit an issue report through your VIVE Console? This will collect your logs and allow our engineering team to pinpoint the issue and prepare a fix for a future update. Thank you again! Steve

@Tindelltech, Yay glad it worked out!! Thanks for your patience and sticking with this. Thanks again @T for all the help here.

Hallo @Gargoyle Vielen Dank für das Teilen Ihres Problems. Bitte entschuldigen Sie meine Grammatik, da ich Google Translate verwende, um diese Nachricht für Sie zu schreiben. Mit dem neuen Cosmos gibt es noch ein paar Titel, die noch nicht kompatibel sind. Dies liegt hauptsächlich daran, dass das Studio keine Bindungen für die Cosmos-Controller erstellt hat. W arbeitet derzeit eng mit Entwicklern und Studios in verschiedenen Geschäften zusammen, um ihre Titel mit Steuerelementen für Cosmos zu aktualisieren. Leider habe ich keine Zeitleiste für jeden einzelnen Titel und wann er fertig sein wird. Es gibt eine Problemumgehung für das Abspielen von Titeln, die noch nicht kompatibel sind, und zwar über die SteamVR-Community-Bindungen. Hierbei handelt es sich um Controller-Bindungen, die von der öffentlichen Community und Personen wie Ihnen erstellt und im Store veröffentlicht wurden, damit Sie sie anwenden und ausprobieren können. Diese Funktion wurde entwickelt, um sicherzustellen, dass alle Spiele mit allen Arten von Headsets gespielt werden können, ohne sich auf das Studio / den Entwickler verlassen zu müssen. Um dies zu versuchen, sind hier die folgenden Schritte: 1. SteamVR öffnen 2. Klicken Sie auf die drei Linien in der oberen linken Ecke 3. Klicken Sie auf Geräte 4. Klicken Sie auf Controller Settings 5. Klicken Sie auf "Controller" und stellen Sie "Cosmos" ein. (Stellen Sie sicher, dass Ihre VIVE Cosmos-Controller eingeschaltet sind.) 6. Wählen Sie Ihren VR-Titel 7. Wählen Sie eine der folgenden Community-Bindungen aus und wenden Sie sie an. 8. Wenn Sie keine sehen, bedeutet dies, dass sie noch nicht erstellt wurde. Sie können versuchen, eine zu erstellen, wenn Sie möchten. Hier ist ein großartiger Artikel, wie es geht. Ich bin mir nicht sicher, ob es eine deutsche Übersetzung dafür gibt. Lass mich wissen, wie es geht! https://steamcommunity.com/sharedfiles/filedetails/?id=1545634111

@T, you freaking rock! Thank you for identifying this issue and sharing it with the community. Super super helpful for us all.

Hey @wandaweb, Thanks for sharing your issue and sorry you're experiencing this. Let me help you fix this. Could you confirm with us what VIVE headset you're using? Did you recently add a mirror/reflective surface or change your lighting environment in your play area? If you haven't yet, please also submit your issue through here: https://www.vive.com/us/support/contactus/ Let me know the answers to the first two when you can. Steve