stvnxu

We love you @Fink!! Thank you!

@ypbrevar, Is your issue resolved now? I saw your other post the day after in this thread: "Turns out it was residual data left behind in the. TMP folder that was stopping downloads from occurring. Took over 6 hours to work out. Once I deleted all remnants of htc & vive from this folder, i could finally download viveport & drivers successfully." https://forum.vive.com/topic/6801-htc-server-down/

@ypbrevar, Is your issue resolved now? I saw your other post the day after in this thread: "Turns out it was residual data left behind in the. TMP folder that was stopping downloads from occurring. Took over 6 hours to work out. Once I deleted all remnants of htc & vive from this folder, i could finally download viveport & drivers successfully."

@ypbrevar Apologies on the initial issues you experienced. Glad you were able to identify and fix this. Thanks for sharing this with the community!

@Arek Translated for your language: Potrzebny będzie kabel miniDP na miniDP. Nie ma adapterów HMDI ani aktywnych konwerterów, które działałyby. Ale w powyższym przypadku jest to związane z aktualizacją vbios MSI.

For anyone else reading this thread experiencing similar issues, you can also refer to this for the solution: TLDR: Contact MSI support for vbios update.

Hey @Phr00t! Thanks for sharing this. Hmm very interesting! I'll submit this as a feedback report to our engineers to review if they haven't yet considered this in their development. Thanks again as always for contributing and helping everyone here 🙂 Steve

Glad you were able to identify the issue. Thanks for updating us and sharing with the community your status. Keep us posted once you've installed a better cooling option so you can play more games on the Cosmos!! Feel free to reach out anytime here in forums. The community here is beyond awesome, and quick to help. All the best, Steve

This is @T every time he helps us all. Thanks for sharing!!

Okay, thank you! Reported and will get back to you on this. Feel free to follow up end of next week. Steve

Hey @SazaOgai, Welcome to the Cosmos family! Apologies on this initial road bump you're experiencing. I'll work with you to get this resolved. Could you share us your computer specs? Please confirm that you are downloading the ViveSetup.exe through this link: https://www.vive.com/us/setup/ Please confirm that you are logged on as the main account user/administrator of your computer. When you open the ViveSetup.exe, you should be receiving a user account control notification. You want to click "yes" If you don't see this message, try right clicking the ViveSetup.exe and select "run as administrator" Steve

Hey Cosmos family, In case you haven't heard, we pushed out a new beta release that has some tracking improvements. Check out this post to learn more: The team is continuously working hard to bring you updates to improve your overall experience. Thank you for your patience!!! The community here and your feedback is what keeps us motivated and going.

Hi @sidnol / Aaron, Welcome to the Cosmos family! Apologies on the issue you're experiencing. This case sounds very unique and a first for me, but we'll help get you through this! Could you submit an issue report through your VIVE Console so that our engineering team can try to identify the root cause of your issue? Here are the instructions on how to do so: https://forum.vive.com/topic/6662-how-to-report-issues-through-the-vive-console/ Please make sure your headset is connected (red light being displayed on the side) and your linkbox is on. I don't need you to run room setup for this process. Just as long as it's connected. Once you completed this, please confirm here with your Trace No. Please confirm if you're using the correct power cable for your desktop. Thanks,

@oxygen4004, Thanks for the field report. I'll submit this to engineering and report to the Viveport Team. Have you seen other multiplayer games that are working that's on viveport? If so, what are those experiences?

@Arek Przepraszam za błędy ortograficzne i gramatyczne, ponieważ używam tłumaczenia Google do tłumaczenia i tłumaczenia naszej rozmowy. Jeśli nie masz Displayport lub Mini Displayport na swoim laptopie, nie będziesz mógł uruchomić zestawu słuchawkowego VIVE Cosmos. Niestety nie można użyć konwertera DP na HDMI.

Ditto ^

@Raber Have you tried the online customer support chat? They're much quicker and responsive there. https://www.vive.com/fr/support/contactus Nonetheless, I will still try to support you here as well 🙂 Thanks for sharing your Trace No. Can you share us what your computer / laptop specs are? Looping in my colleague @C.T. to see what troubleshooting options there are left here since it looks like you've exhausted everything I would've suggested. Steve

@Fink Thanks for following up! We just released Beta 1.0.9.2 :

@Raber, Could you verify your issue report Trace No? You should've received a trace no via email after submitting the report. What region/country are you located in? Steve

Hi @Raber, Apologies on this issue you're experiencing. Please help us answer the following to help better identify the root cause of your issue: Could you share us your computer / laptop specs? What solutions have you already tried that was suggested from the HTC support team? Could you submit an issue report for us? (Please have Cosmos headset connected to the computer and on. the red light is okay) https://forum.vive.com/topic/6662-how-to-report-issues-through-the-vive-console/ Thanks, Steve

Hi @Fink & @Ldrakeh, Thank you for sharing your insights! Great observation and proposed solution on addressing the tracking. Fortunately, I'm confident they're taking this approach, there's just a little bit more to solve to get it working in the standards of other headsets. It does take a bit more time, and I do apologize for that. Rest assure though, the updates will be ongoing until are customers are beyond satisfied with the inside-out tracking. That being said, the external sensor plate for the Cosmos is an add-on to give users the flexibility of customizing their perfect VR headset. The intention for the external sensor plate are for users who really want that sub-millimeter tracking, to use the VIVE or Index controllers, or to use the VIVE trackers in their environment. It is not intended for every user to purchase to meet the standards of tracking - we understand the current tracking with Cosmos isn't meeting customer expectations so we are working to address this in the sw updates. Nonetheless, I'll share your post to our engineering team! We love the support, patience, and constructive feedback from all of you. Thank you Steve

@Randonlag, Hmm, okay it's most likely not the device then. Could you submit in an issue report that'll collect your logs? I'll submit this to engineering team to figure out what the root cause is. Make sure to have your headset connected and on when you're submitting the issue report. Here are instructions: https://forum.vive.com/topic/6662-how-to-report-issues-through-the-vive-console/ Ping me here once you've completed this and I'll forward to them immediately. Please note we're rolling into the weekend, therefore, there will be a delay in response till at least Monday. I'll also tag my colleague, @VibrantNebula, if he can shed any light here. Steve

New release for our hand tracking sdk just came out today v0.9.0 Check it out!

@Kobboyz Glad the IPD adjustment knob is working! Phew. Now please identify what your IPD is and then adjust the wheel to that specific value. You shouldn't need to adjust the wheel after that unless you're switching your headset for another individual to wear. Possible reason why the value stops is because you've either reached the highest or lowest value of the IPD scale. Thanks for submitting the report! Steve

Hey @Kobboyz, Thanks for your patience in testing this out for us. I will work with you to fix this. Here's a series of questions if you can help answer them in order: Grab your Cosmos headset and try adjusting the IPD knob without putting it on. As you adjust the IPD knob back and forth, observe the two lenses behavior. Do the two lenses have any physical movements in relation to turning the knob? Whether the lenses are moving away or towards each other. If yes, then continue to the questions below. If not, then I'll work with you and customer support to address this. Couple questions: When you say "I confirm that it appears randomly when you touch the setting button," are you referring to the setting button as the physical IPD knob adjustment on the side of your headset? When the adjustment window appears, have you tried to continue moving the knob as it appears to see if the value increases/decreases depending on the direction you're moving? Could you help us submit an issue report? This will help our engineering team look deeper into this issue as this is the first of its case I've seen. Here are instructions to submit a report: https://forum.vive.com/topic/6662-how-to-report-issues-through-the-vive-console/ Could you try turning the knob in one direction and continue to do so until it reaches its limit? During that process, can you report whether you saw the adjustment window pop up and if you did, did the value change as you turned the knob? Note: It is intended for the IPD value window to quickly disappear when the IPD knob isn't being adjusted. It is intended for the IPD value window to be delayed by a few seconds after physically adjusting the IPD knob. The reason for this delay is to prevent the window from appearing and disrupting your play if the movement was not originally intended and was caused by game-play movement. Steve