Jump to content

T

Verified Members
  • Posts

    31
  • Joined

  • Last visited

Posts posted by T

  1. I covered my 2 front cameras and moved the controller between the up/down and 2 side cameras. When the controller was in front the 2 covered cameras it would lose tracking but when it was seen by any of the other 4 cameras it would start tracking again. So the side cameras are tracking but how good I can't tell.

    I also had problems twice on my right controller, it would appear as being some meters in front of me and looked like it was still tracking or it was only sensor tracking. Even if I touched the controller to the cameras it wouldn't come back to me and I had to switch it off and on for it to work again.

     

    @Synthesis

    • Like 1
  2. 4 hours ago, Tindelltech said:

    I have reached out to MSI.  They have told me i'm using the latest version of Vbios that are available.  My VBios version is: 86.04.7D.00.29

    Googling your VBIOS version of 86.04.7D.00.29 brings me to this result :

    Quote

    I have an MSI GE63 Raider RGB 8RF laptop with the Nvidia GTX 1070  and  had experienced the black screen issue after approximately 30 seconds with my Oculus Rift S. The only workaround had been to use the Nvidia  417.71 driver. Anything newer than the 417.71 driver would result in the black screen issue. I opened a Tech Support ticket with MSI and they emailed me an updated VBIOS for my GTX 1070. My VBIOS version was 86.04.7D.00.29. The updated VBIOS is 86.04.7D.00.37. I simply unzipped the file they sent me and executed the BAT. file contained within.  I  then updated my Nvidia driver to the current one which is 436.15 and all is well, no more black screen.

    So at least for the GTX 1070 at the MSI GE63 Raider RGB 8RF laptop the 86.04.7D.00.29 VBIOS is broken for the Rift S and there is an updated version for it that fixed it. Also from the same thread the updated version fixed the problem for the GTX 1070 for a MSI GE73 Raider RGB 8RE.

    Another post for the Valve Index which also shows that the problem is not limited to one headset:

    Quote

    I have a MSI GE73 8RF ......

    ......

    Waiting for new nvidia driver didn't solve my problem so I contact MSI support with my MSI system configuration.

    They immediatly replied this :
    As for the HDCP error:
    Please update Current VBIOS: 86.04.7D.00.37

    .....

    You can't blame me if I think that what MSI support told you is wrong.

    In that last post for the Valve Index, a workaround that has been discussed in other cases is to use a old nvidia driver that doesn't produce the fault like the 417.71 one. Mind you the latest drivers claim that they added support for the Cosmos so old driver might not work.

    • Like 2
  3. You never mentioned if you have the latest VBIOS for your graphics card.

    From the Oculus Rift S Troubleshooting Tips which has related information:

    Quote

    I’m experiencing issues with my MSI laptop.

    • If the newest drivers don't solve the issue, please reach out to the MSI support team to update the VBIOS that enables HDCP on the DisplayPort.

     

    Your laptop being labeled "VR ready" doesn't mean that it's actually completely compatible. There is no such standard.

    And if your problem is with the VBIOS you will have similar problems with the Oculus Rift S.

  4. Do you have the latest VBIOS?

    Based on some reports [1], MSI GP73 Leopard 8 RF and possibly other MSI laptops [2][3] needed a VBIOS update to work with the Oculus Rift S and the latest Nvidia drivers. This fix might apply to the Cosmos too.

    Also the latest Nvidia drivers "Adds support for the HTC VIVE Cosmos VR HMD".

    If you don't have the latest VBIOS, you will have to contact MSI support and ask them for it. There are many different laptop configurations so don't pick a random VBIOS flash from the internet.

     

    PS: My forum nickname T was given to me automatically after first login with no option to change it even though I setup my InfinityTag and everything else in Viveport and can't find any other place where that nickname might have come.

    • Like 2
×
×
  • Create New...