lamyipming

Not Cosmos specific, but I think it's worth to share. https://nvidia.custhelp.com/app/answers/detail/a_id/4957/~/variable-rate-supersampling%3A-improve-image-quality-in-vr Instead of by program as in the article, I set the global settings below: Nvidia Control Panel \ Manage 3D settings \ Global Settings \ Virtual Reality - Variable Rate Super Sampling = Adaptive So the theory is, instead of supersampling the whole screen which would be GPU costly, this setting can bring extra supersampling in the central region which is usually where your focus is. I tested it in Pavlov, the image quality is really great! I love my headset even more now. So I think it's good to share to you guys, to enhance the image quality by just a simple setting, at no extra hardware cost. Credits to /u/Orthello77 in Reddit. Original post:

I read somewhere (not sure in Reddit or here) that someone experience that tracking under bright white light is somehow worse than a dimmer, warmer (yellower) light. I use Cosmos in the living room, where my ceiling lights can switch between different modes. So after reading that, I try to switch to a different light mode. And there I have it, super sweet accurate aiming! In case your lights can switch into night mode too, please try it. Or if you don't know if your lights can do so, try switching it on and then off quickly a few times. Feel free to share your experience below. I am not 100% certain if this works for everyone. Hope this helps.

Although it's still hard to aim accurately, Pavlov is at least now playable. I manage to get the kill/death ratio close to one. Haven't tried Onwards and Zero Caliber yet, but I guess they require more aiming at a distance since these two are more slowly paced, which is impossible for now. Well done team. This is the first time I have some fun in shooting games with the Cosmos headset.

Thanks. Starting the Vive Wireless first solved my problem. Please delete the post if you wish. I get used to starting Vive Console which automatically starts SteamVR with wireless detected without issue. However a game (City Car Driving) requires SteamVR to be turned off when starting the game - for some strange reason the game must launch SteamVR by itself. But in that way SteamVR won't detect the wireless headset since Vive Console isn't launched. That's why I asked. For anyone else encountered the same issue, you should start Vive Wireless to establish the connection first - don't rely on Vive Console to do that for you.

Launching SteamVR directly will not automatically detect my wireless headset, unless I start Vive Console on my own. Any fix?

If you BeatSaber was super laggy, most probably it is your Nvidia GeForce Experience that automatically optimized the game to best settings and set the in-game supersampling to something high. In-game SS multipling Vive's SS means a ridiculous resolution and that's why your game can't run. Setting the supersampling in the game back to 1 will fix the problem.

In my region I can only find the PD version but not QC version of the said Anker powerbank. https://www.anker.com/products/variant/PowerCore-Speed-20000-PD/B1275011 However I'm very afraid if QC is a must for the headset and if it doesn't support PD, then I will get another useless purchase.

so still no transparent boundaries or quick way to disable the chaperone

Another potential issue is that I play in front of a huge, bright 65inch TV which is supposedly refreshing at 60hz.

I guess the actual path might vary for difference people, so I can't tell where it is in your PC. The way I found mine is to use a software called Sandboxie. I used Sandboxie to launch VIVE Console, adjust the chaperone settings in Lens, and close the VR. It will crash for some reasons, but Sandboxie can log what files have been modified by Vive Console in the independent environment. Find the correct text file location and there you can change the alpha from 15 to 0. Or let's hope Vive will fix this soon.

LED light bulbs has some invisible flickering at high frequency. Not sure if this can be a problem for the tracking cameras. Can anyone compare the tracking performance between a room lit by florescent lights and the same room with LED lights? Or has HTC done testing on this in their lab? @stvnxu

I think we won't see any update soon probably because of the situation in China. That's fine, I just hope everyone is okay.

If your only concern is about watching movies but not shooting games, Cosmos is excellent. I have tried to use BigScreen to watch a movie and it's like a personal IMAX which is super great. Things you might need to worry about: 1. The sweet spot is quite narrow and you might need some time to find the perfect way to wear the headset. But once you get used to it, this won't be a big problem. 2. You might find some light leak coming from your ceiling light which ruins your immersion. But it is fixable by placing some cloth to block the gap. 3. You don't need much space if you set it to seated gaming to skip setting the boarder. 4. Room brightness is less of a concern now. In a dark room the tracking might stop working (so the hands won't move), but there won't be a pop-up or any warning to block you from watching the movies. 5. Screen door effect - I don't have any comment for that. You have to experience yourself.

Do you have any information about when will this fix be implemented? Still have this problem in 1.0.9.6 and there's no mentioning of this issue in mid-Jan beta update. @stvnxu @C.T.

To do list: 1. Tracking optimization 2. Room orientation: recentre 3. Option to disable boundary

Now I wonder what's meant by "the most wanted function". Just want to make sure we're on the same page. We want good tracking in two handed shooting games.

So I've done some testing, in case anyone wants to know how to switch to wired when the battery dies and don't have a spare battery Using original link box power cable L1 of course can power the wireless adapter on the headset, but the problem is that the cable is relatively short so you can't really move around. Using a PD power socket together with a quick charge USB cable that can support 3A current cannot power the wireless headset. Seems the headset doesn't recognize a PD communication even though it can support up to 50W. Using a Quick Charge 3.0 socket plus a 5 meter USB 2.0 Type A to Type A cable cannot power the wireless headset. Using a Quick Charge 3.0 socket plus a 5 meter USB 3.0 Type A to Type A cable CAN power the wireless headset. I have tried to use this combination to play beatsaber for an hour without problem. So Quick Charge 3.0 seems like a must. Also you need a USB 3.0 blue cable. I guess length is not a problem.

Can I play with the Vive battery that comes in the Vive wireless package? I wonder if using a 15w or 18w battery for Cosmos will do any damage to the headset or wireless adapter.

This has not been fixed in the latest 1.0.9.2 beta firmware. @stvnxu

In the video they are using a handgun, which is still playable with one hand. HTC you are lucky they didn't test it with a rifle, otherwise it would be way more shameful comparing to others.

I feel like the controller tracking is little bit lagging behind my movement after I switch to wireless. Playing beatsaber 360 with wireless is great, but the game is noticeably less "responsive" now. Anyone experience the same problem?

I just hope we can get a major tracking improvement before Christmas. Sigh...

I have found a fix that may solve the problem of setting boundary to invisible. Hopefully they will fix it in the next update. https://forum.vive.com/topic/6989-temporarily-disabling-chaperone-or-collision-boundary/

I have been struggling to find a way to temporarily disabling the chaperone for some seated games or video player app. The problem is that my sofa lies outside of my standing play area. And when I lies on the sofa outside of the play area, there is no way to turn off the boundary. The boundary lines are always visible. The only way to solve was to rerun the room setup and change to seated playing - and then setup the boundary again when you want to switch back to standing play area. 1. Dragging the transparency setting in the Lens menu to the far left zero does not solve the problem. 2. Tweaking the file in "C:\Program Files (x86)\VIVE\Updater\App\ViveVRRuntime\ViveVR\ViveVRServer\config\default.vrsettings" does not solve the problem. (setting "CollisionBoundsColorGammaA" : 0) 3. Complaining on this forum repeatedly does not solve the problem. Today I found a fix. Hope this helps anyone who faces the same problem. First terminate Vive Console and Viveport. Then use notepad to open the settings file "htcvr.vrsettings" located in "C:\ProgramData\HTC\ViveSoftware\ViveVRRuntime". There you can see that even if you have dragged the transparency all the way to 0 in the Lens menu, the "CollisionBoundsColorGammaA" is still set to 15. I think that this is a bug of the Lens software. Somehow they set the minimum value of the dragging bar to 15, instead of 0. Manually changing the "CollisionBoundsColorGammaA" to 0 will disable the boundary completely. (You will need to save the file with admin right.) HTC, please fix this in the Lens settings. Be it a bug or a feature, users should be able to set whether they want a boundary or not. It is very very annoying we cannot temporarily disable the boundary COMPLETELY in the Lens menu. @stvnxu

Apparently my repeated complaints about disabling the boundary - or setting the boundary to completely transparent, i.e. exactly zero, didn't get passed on to the engineers. If I sit near the boundary, the lines are still clearly visible and there's no way to disable that. I don't understand where did HTC get the idea that all users must always want to stand in the center of the play area and will never once in a while sit on the sofa which happens to be located exactly at the freaking play area boundary to enjoy some movie with the VR headset. Yeah the users must still want to see the boundary lines so much even though they drag the opacity settings all the way to the far left. Let's always show them the boundaries in the movie player, it's good for them. Please, HTC, this should be a very easy fix. I mean, this is my last post about this. If this never gets fixed, I'll just accept my fate and be responsible for my poor life choices.