Jump to content

Raysangar

Verified Members
  • Posts

    10
  • Joined

  • Last visited

Posts posted by Raysangar

  1. On 4/8/2020 at 7:33 PM, Shen Ye said:

    Okay, looks like that card is straight up incompatible due to certain dependencies when it comes Direct Mode. Your new GPU should fix this (we checked the logs and that was the only cause of the error), let us know if you have any issues when you install the new GPU.

    Hi! The new GPU has just arrived and now everything works perfectly. Thank you so much for all the help!

    • Like 2
  2. 1 hour ago, Shen Ye said:

    Okay, looks like that card is straight up incompatible due to certain dependencies when it comes Direct Mode. Your new GPU should fix this (we checked the logs and that was the only cause of the error), let us know if you have any issues when you install the new GPU.

    Perfect, thanks for the info. I'll let you know once I get the new GPU

    • Like 1
  3. 1 hour ago, Shen Ye said:

    Okay we will take a look at the logs - could you do another report issue so we have the logs with the latest nvidia drivers please? Thanks!

    Sure, I've done it. The code is 20200408163740

    Than you again for your time. I really appreciate it!

  4. 6 minutes ago, Shen Ye said:

    Great. In regards to error 210 are you using any adapters or 3rd party cables to connect your Cosmos? Are your Nvidia drivers up to date?

    I'm using the original cables and I've just installed the latest drivers and the error persists 

  5. 1 hour ago, Shen Ye said:

    According to the logs, those USB ports are indeed running at USB 2.0 speeds, with no errors. We suspect your Windows OS is lacking the necessary USB 3.0 drivers for the NEC/Renesas USB 3.0 controllers that power your mobo's USB 3.0 port. I had a look on ASUS's website and it doesn't look like they supply Windows 10 drivers for them, but you could try going into Device Manager and seeing if you can get Windows Update to find newer drivers for the USB controllers. If that doesn't work our engineering team is suggesting you take a look over here for the original drivers (but please check the controller model and version you have when selecting the correct driver): https://www.win-raid.com/t834f25-USB-Drivers-original-and-modded.html

    Side note, we noticed you're using an Nvidia GTX 760 2GB, we have some concerns with how well your experience will be on that card as its performance falls short of our minimum specs.

    Hello Shen!

    I've installed the drivers and it seems like the USB port error has gone, but it still keeps failing to turn on. This time the error that always prompt is the code 210. Any idea about how to fix this? Restarting the VIVE Console app doesn't seem to work as suggested on the support website. I've reported a new ticket to upload new logs (2020040813235).

    About the GPU, I am waiting to receive a new one, but I don't know when I will receive it due to this unfortunate virus situation. So I wanted to test the headset to make sure that it works fine.

    Thank you! 

  6. 4 hours ago, Shen Ye said:

    very strange. Could you go into Vive Console > Troubleshooting > Report Issue and submit an issue? It will upload the logs and provide you a trace number. If you could send that over, we can take a look into it in more detail.

    Sure, the trace number is 20200407141035.

    Thanks!

    @C.T.

    • Thanks 1
  7. Hello and thank you for your reply!

    I've reported the issue and I tried to reset the headset, but unfortunately it didn't work either.

    Here is the info that you asked:

    - Custom PC with Asus Maximus IV Extreme motherboard

    - Yes, I'm sure that I'm connecting the USB cable to a USB 3.0 port

    - Regular Cosmos

    - Yes, all the cables are the official ones

     

    Thank you again for your time!

  8. The VIVE console prompts this error every time I try to turn on the headset

    The USB cable must be connected to a USB 3.0 or higher port on the computer.

    I'm 100% sure that im plugin the cable to a USB 3.0 port and I've tried all possible solutions from support website, but the error keeps appearing. Are there any clues about what could be the issue here?

    I would really appreciate any info that you could give me.

    Thank you guys!

    @stvnxu @C.T.

×
×
  • Create New...