Jump to content
 
C.T.

Cosmos Beta release - 1.0.12.2

Recommended Posts

VIVE Cosmos 1.0.12.2 – Beta Release Notes 
Released May 7th 2020

[Runtime]  

  • Cosmos & Cosmos Elite
    • Improved double image effect when hit heavy loading content
    • Updated the hidden area mesh to solve the content crash that built by UE 4.24
    • Fixed error 210 to avoid only show black screen and error 216 to avoid miss detect SteamVR status
    • Improve the stability when cable or adapter (miniDP to DP) hotplug
    • Fixed compositor initialization fails on AMD graphic card for the PC does not install DirectX 9.
    • Fixed vrserver cannot be closed normally after Vive Console was closed
    • Fixed the screenshot notification does not disappear
    • Fixed reading the AMD graphic card driver version incorrect
  • Cosmos 
    • Fixed the ViveLens didn’t auto relaunch at some cases
    • Fixed reading the AMD graphic card driver version incorrect

[Vive Lens]

  • Fixed blurred scene when pressing "Return to origin" in Origin
  • Thanks 1

Share this post


Link to post
Share on other sites

😍  merci pour la mise a jour

Share this post


Link to post
Share on other sites

😍 J ai testé pavlov vr zombie c est beaucoup mieux le tracking avec le fusil a deux main  😍

enfin c est mieux  

merci pour votre travail très bon 😍

Share this post


Link to post
Share on other sites
6 hours ago, C.T. said:

VIVE Cosmos 1.0.12.2 – Public Release Notes 
Released May 7th 2020

[Runtime]  

  • Cosmos & Cosmos Elite
    • Improved double image effect when hit heavy loading content
    • Updated the hidden area mesh to solve the content crash that built by UE 4.24
    • Fixed error 210 to avoid only show black screen and error 216 to avoid miss detect SteamVR status
    • Improve the stability when cable or adapter (miniDP to DP) hotplug
    • Fixed compositor initialization fails on AMD graphic card for the PC does not install DirectX 9.
    • Fixed vrserver cannot be closed normally after Vive Console was closed
    • Fixed the screenshot notification does not disappear
    • Fixed reading the AMD graphic card driver version incorrect
  • Cosmos 
    • Fixed the ViveLens didn’t auto relaunch at some cases
    • Fixed reading the AMD graphic card driver version incorrect

[Vive Lens]

  • Fixed blurred scene when pressing "Return to origin" in Origin

@C.T. just wanted to be clear on this recent update 05/07/2020.  Has it already gone public or is it still a beta?

C.T. just giving you some digital bullshiza

VIVE Cosmos 1.0.12.2 – ***Public*** Release Notes

Tracking still gets stuck/frozen.  Hopefully HTC is planning to slap the VR industry in the face with with a massive update for inside-out tracking...very soon!

  • Like 1

Share this post


Link to post
Share on other sites
9 hours ago, C.T. said:

VIVE Cosmos 1.0.12.2 – Public Release Notes 
Released May 7th 2020

[Runtime]  

  • Cosmos & Cosmos Elite
    • Improved double image effect when hit heavy loading content
    • Updated the hidden area mesh to solve the content crash that built by UE 4.24
    • Fixed error 210 to avoid only show black screen and error 216 to avoid miss detect SteamVR status
    • Improve the stability when cable or adapter (miniDP to DP) hotplug
    • Fixed compositor initialization fails on AMD graphic card for the PC does not install DirectX 9.
    • Fixed vrserver cannot be closed normally after Vive Console was closed
    • Fixed the screenshot notification does not disappear
    • Fixed reading the AMD graphic card driver version incorrect
  • Cosmos 
    • Fixed the ViveLens didn’t auto relaunch at some cases
    • Fixed reading the AMD graphic card driver version incorrect

[Vive Lens]

  • Fixed blurred scene when pressing "Return to origin" in Origin

Thanks for this update, but I have a few points I would like to mention. First of all (I will talk again even though it looks boring) the updates are taking a long time to come out, this version took more than 1 month, and for the delay I would have liked to see an improvement in tracking, where everyone knows it is horrible, and that already make 8 MONTHS. I don't want to look boring but I'm talking as a consumer, can you focus on improving tracking? 8 MONTHS and it is still problematic, in that time there was some improvement but far from perfect. It is starting to look like you are not wanting to say that the product is defective and there is no way to improve more than that, because within these 8 months you have already had some updates and even a new headset. And the problem continues. Sorry the outburst is that it is really frustrating you buy a product that came with a problem and in 8 months it will not be solved, mainly coming from a company like valve.

  • Like 2

Share this post


Link to post
Share on other sites

déçu déçu encore nul nul nul la V R  me dégoût de plus en plus 😪

Share this post


Link to post
Share on other sites

🤪 il y a méme pas eu une mise jour pour le tracking  c est abuser quand méme 

     j ai peux téte parlez trop vite pour le tracking  

Share this post


Link to post
Share on other sites
13 hours ago, lamyipming said:

So no improvements on tracking?

Deadly. They focus on patching those affecting its Elite version. But tracking issue for in out, I feel it is pretty deadly over as it should be design fault, can't fix at all. That why it takes 8 months and still no matching to rift s..........

  • Like 2

Share this post


Link to post
Share on other sites
1 hour ago, lam0218 said:

Deadly. They focus on patching those affecting its Elite version. But tracking issue for in out, I feel it is pretty deadly over as it should be design fault, can't fix at all. That why it takes 8 months and still no matching to rift s..........

I also believe that the product is defective and will never have a 10/10 tracking score. Which is a shame, but I hope they improve to an 8/10 point
However, I believe that as they have improved a lot since launch, I think it can improve even more, they just need to focus on that problem.
However, taking a month for an update and having nothing to track is difficult to improve.
As I said before, the biggest problem (besides sniper mode) is tracking too close to the headset, far above and far below.
My impression is that when the headset completely loses the control light, it is completely lost, which explains many of the tracking problems.
High above = see only the bottom of the control
Far below = (hands down) = see also only the bottom of the control
Too close to the headset = he sees only one light and does not understand that it is the control.
Sniper mode = the rear control overlaps the front light and loses it.

So if there's anything really bad about the cosmos headset, it's the control and the way it was designed for the cameras to identify where they are. It would also explain why they returned to the elite cosmos for standard control.

If they go back and study the best way to get the headset to track the controller lighting, I believe they can improve tracking even further.
Well, I still believe in the valve (even very discouraged), but please take the time to improve tracking.
And try to release updates more quickly mainly focused on tracking, even with little improvement release the update so we can give feedback

  • Like 1

Share this post


Link to post
Share on other sites

Please sign in to comment

You need to be a member in order to leave a comment

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...