Jump to content


Popular Content

Showing content with the highest reputation since 07/24/2019 in all areas

  1. 9 points
    Hello everyone! I've been lurking on these forums for a few weeks and figured it would be worth getting into the conversation. I guess I was looking to get in touch with other Cosmos owners and get a feel for where everyone was at. Reading some of the recent beta posts and news regarding "new" versions of Cosmos obviously has some of us feeling a little shaken up. I'm an early adopter of the Cosmos. Pre-ordered before anyone had released reviews or impressions on it. It was the breath of fresh air I was waiting for in the VR world, as other HMD's just seemed to be slight improvements or variations of each other - Cosmos was one of the first in my mind to attempt breaking the mold and trying something new. After receiving it at launch I was a little worried. My play area is in a basement bedroom and gets little to no natural light. Off the hop it wouldn't work given the low light but I was undeterred, installing new lights and modifying the space. The visuals were amazing, the HMD fit great, games became playable but tracking was clearly lacking. Any form of shooting game that required the use of two hands was not happening. From release up until now I have seen a lot of improvement to the tracking. At the time of writing this I can actually shoot a bow or rifle with both hands, with the controllers only occasionally losing position or jumping slightly if I'm completely still. I own games that were relatively unplayable in the beginning and now I'm having little to no trouble playing H3VR, Boneworks, Sairento, Blade & Sorcery and so on. Just wanted to thank the dev team for their work so far, and to keep refining and improving the experience. I have zero issues with the Cosmos aside from controllers getting jumpy and occasionally missing a long range shot or two. If we keep seeing continual improvement I imagine a lot more people will be standing by HTC inside-out tech. Throwing more money at my system for a tracking upgrade isn't ideal at all. TLDR; Cosmos tracking was awful at launch, I've seen tracking improve a great deal since then. Will be standing by for more updates. Will not be spending an arm and leg for SteamVR Faceplate + 2x Basestation + 2x Vive Controller. First post! (Shoutout to my fave contributors on here - A-Jey, I'm loving your optimism and ride-or-die Cosmos mentality, you've inspired me to stick with the Cosmos on this journey, buying a different VR or spending more isn't an option. And TomCgcmfc, you are a true realist and I agree attention needs to be brought to the Cosmos' shortcomings, the pricepoint of it was no joke and we deserve to feel fully satisfied with the purchase.) @C.T. @stvnxu
  2. 7 points
    Okay a guy called CABAListic in Steam or fholger on GitHub has modified the openvr_api.dll in F4VR for Index controllers to fix the joystick issues in menus and maps and it works for the Cosmos as well. It tells the application that your are using Oculus controllers and gets around this incompatibility issue. You can download it from here "https://github.com/fholger/openvr/releases/download/fo4vr_v1.1/openvr_api.dll" and then copy it into your "Steam\steamapps\common\Fallout 4 VR" folder (always backup your old one just in case) this may work for other steam games that use this DLL as well.
  3. 6 points
    I originally posted here in the support forums very disgruntled that the cosmos was not natively supported by the bethesda titles, skyrim/fallout vr . well, with a little research I found a way into my controller binding settings and found a neat keymap profile for each game. turns out you can not only make your own, but you can download someone elses keymap profile under that game title and adopt it for use. even better, the key mapping on the cosmos seems to change for each game that you are playing and it remembers the last keymap profile for that game used, and auto loads it for you without any input on your end , set and forget. Be patient with this system, If it is giving you issues, I trust youll find an answer here on the forums or on reddit 🙂
  4. 6 points
    Step by step we're getting there. Maybe too slow for some users here but the developers making progress. As usual I tested Beat Saber. The room was far away from being well lit (lights off and cloudy day on sunset. I immediately could finish a level on expert with full combo where I failed everytime before due to glitches or track loss. Cross movements seems more stable now. So definetily a great move into right direction again. Also tried the rifle mode in Overkill VR. At least you can aim but still it's very stuttering, shaky, unstable. Still a lot of improvements to do there. I'd say NOW we're on that 90% some were talking about longer ago. Thanks for keeping up the good work on improvements. I wish you all a happy new year and many highscores and achievements in 2020 😉
  5. 6 points
    HTC Cosmos - Definitely on the right path towards correcting the inside out flaws of tracking issues for OOBE, still RIFT S is more polished. Nice update before the holidays...Maybe we can get Reset View / Reset Position by New Year's 2020. Haahaaa maybe that's a little too much.
  6. 6 points
    OK, tried it but since I was not really having any of the issues that this beta update addressed I did not notice any difference but I hope it helped some. I'm looking forward to the next beta that hopefully improves tracking and variable lighting conditions (actually the two are kind of related imho). Thanks to all the Vive engineers for all their hard work. Cheers.
  7. 5 points
    Just wanted to share this https://www.thingiverse.com/thing:4124195 HTC Vive Wireless Dual 30mm Cooling Fan. 2x - 30x30x6mm 12v Fans @ 7.5v (Low speed fan resistors I had sitting around) 1x - 1.3 ID x 3.5mm OD DC Jack This was built due to Grey/Blue screen flashes on the HMD, Falling through the world or slowly losing tracking on the Vive Cosmos during wireless play. Looking at logs in C:\ProgramData\Vive Wireless\ConnectionUtility\Log The HTC Vive Wireless would start with temps reporting [2020-01-19 17:36:58 +10 0xB70 INFO LOG] M_Temperature=36, R_Temperature=33 -After 20minutes play time- [2020-01-19 17:56:46 +10 0xB70 INFO LOG] M_Temperature=91, R_Temperature=62 After the modification was performed the log output reported [2020-01-24 14:45:39 +10 0x4394 INFO LOG] M_Temperature=30, R_Temperature=23 -After 20minutes play time- [2020-01-24 15:05:19 +10 0x4394 INFO LOG] M_Temperature=48, R_Temperature=49 Both of these were experienced with the same room temperature of 24c and 20minutes of playtime in Beat Saber. After extended use it originally used to display temperatures reporting [2020-01-07 18:19:42 +10 0x32B0 INFO LOG] M_Temperature=99, R_Temperature=63 [2020-01-07 18:19:52 +10 0x32B0 INFO LOG] M_Temperature=100, R_Temperature=65 [2020-01-07 18:20:22 +10 0x32B0 INFO LOG] M_Temperature=102, R_Temperature=66 With a grey/blue HMD flicker every few minutes. This has cut cut the temperature by half and resulted in no drop outs after hours of use. Cheers
  8. 5 points
    Hey everyone. Feedback and critical comments are just fine here. We encourage it so we can help making this better. However, let's keep it to that and no go at each other. We are all passionate about VR and new hardware. Going forward, if the bashing, insulting, and overall pushing on each other continues, warnings will begin to be handed out in the form or a 3 day temp ban from interacting on the forums.
  9. 5 points
    Just wanted to provide an update for those that might come across this thread. Unfortunately I had to do a clean install of Windows to get things sorted, but good news is everything is working great again with the new firmware installed. Not sure what went wrong when I did the HMD update last night, but obviously something in Windows went astray. Thankfully re-installing Windows is a fairly straight forward process these days so wasn't too bad getting up and running again. Thanks to everyone who provided suggestions trying to help, really appreciate it. And also want to give a shout out to @C.T. to say thanks for being so helpful, and assisting in getting me to the point where I realised something must have gone wrong with Windows.
  10. 5 points
    VIVE Cosmos – Beta Release Notes Released December 31th 2019  [Tracking] Controller Improved tracking of controller movement adjacent to the sides of the hip Improved tracking of controller blocked by the arm Improved forehand full arm swing Improved the reverse side of the controller tracking
  11. 5 points
    My priority for future updates: 1) Controller tracking wobble. When holding a controller still, the virtual controller should stay still too. This wobble even happens when the glowing controller ring is in clear view. What I do NOT want to see as a "fix" is reducing movement sensitivity, as when I move the controller a little bit (say, to aim a gun better), I need the controller to track that accurately. 2) Reset seated position. This is a highly requested feature still missing. 3) Allow the boundary lines to be completely invisible through the Lens configuration. Do not cap it at 15. If we are setting it to zero, we have a good reason (probably because we are sitting). 4) Improve frame rate compensation <90 FPS. Far too many artifacts in the current system.
  12. 4 points
    My Cosmos elite just arrived today. My only other VR setup was the original vive that died not too long ago. So I already had the 1.0 lighthouses set up and the wireless adapter configured. With that being said Setting up the Cosmos elite was not too hard. The difference in the HMD clarity is amazing. I did have a tracking issue with the wand controllers it came with. They were very shaky at times, It turned out to be my CPU running 100% all the time. I have a i7 9700k on a z390-e motherboard, 2 1tb ssd's in raid 0, and a 2080 super so this was a bit alarming. After a few hours trouble shooting, I found moving my wireless adapter to another pcie 1 slot dropped the cpu load to 60-70 % and the tracking is near perfect. I don't think the tracking is a good as the original vive, but it is VERY close. I am very happy with the cosmos elite combo. I am going to assume that with a few updates since this package is new that the tracking will meet or exceed the original vive. I am aware that the resolution is a lot higher and will need more processing power for both the image and the tracking to work correctly. I am sure once a few updates arrive it will run even better! I actually like the halo head strap better than the elastic band on the original. The speakers are amazing coming from ear buds from the original vive setup. I now just need another 21w battery for my wireless setup. I am not sure how long it lasted to be honest because of the trouble shooting I was doing. I honestly got tired of playing and the battery was at 1 dot even after a few hours of on and off again trouble shooting. So all in all I can definitely recommend this for some one wanting a new VR kit with external tracking, especially if they have previous experience with past vive VR setups.
  13. 4 points
    First I have to say, i'm a very critical consumer, as an engineer and It professional I expect a certain standard of quality. I was skeptical but after updating tonight this is a step in the right direction. Bow and Arrow games are now playable, the controllers snap into view a lot faster, albeit there is still some drift with the controllers. Over all thought the responsiveness of the tracking is much better from the last update. Having said this I'm still getting a lot of drift in a particular game, "The Curious Tale of the stolen pets". The controller drift and HMD drift has not improved at all. Please look into this, thanks.
  14. 4 points
    I feel a little bit cheated, will there be an extra for those people like us, who did buy a device that is already EOF after 5 months. This is not the way to solve our problems HTC, i hope HTC will come with some extra information and perheaps huge discounts for people who did buy the cosmos for 799 euro
  15. 4 points
    Hi, I have a Cosmos running wireless. after alot of the ryzen watchdog bsod problems I finally got i running without any problems (still on same ryzen) :-) I use the "Anker PowerCore Speed 20000" for my setup. It supports Qualcomm Quick Charge 3.0 (24W) "Output 5-8V ⎓ 3A / 8-10V ⎓ 2.4A / 10-12V ⎓ 2A" It seams to be working fine. it runs just over 3 hours before the need to recharge.
  16. 4 points
    @Meln what A-jey said! I won't recommend any batteries outside of the one we have on our website. However, there are users in that thread sharing their experience with other 3rd party batteries that you can take a look at for suggestions. Feel free to tag those users if you want more details. Everyone in this community is opened to sharing. Thanks,
  17. 4 points
    I ordered the Cosmos Wireless kit today. Wish me luck, I'll probably need it, lol! Hopefully I'll get it later this week and I'll let you all know how I make out. Cheers mates.
  18. 4 points
    There currently exists only one primary production model/SKU of Cosmos that's been released as of this point. Any variation you may currently see are small things like the box color or are limited region specific things. "Rev1" isn't coming from us.
  19. 4 points
    Who has said this is a hardware issue? I can't see anything from HTC on this? I am pretty sure you're incorrect. Having said that, inside-out tracking is really complex and took Facebook 4 months to become stable. I'm happy to give HTC another couple of months before I start to get concerned.
  20. 4 points
    Echoing what @A-Jey has said. This beta seems to be a step back in many ways, but it is a beta. If you don't like testing unstable/buggy software, go back to the public version. As I have said previously, it took Facebook 4 months to get the Rift S/Quest tracking stable. Given that the Oculus dev team is enormous, we need to give the Vive devs a bit longer. If you are experiencing particular tracking issues, log an issue report in Viveport, or post the details on here (with videos preferably).
  21. 4 points
    One problem I see is that Rift S developers got much more feedback and data to work with. But with only 5 people concerning about an unlucky beta version progress takes much longer time I guess. You could help by doing videos of the things that don't work and send it in, together with an issue report. Your data can help. We're a small community of users who had the balls to get this headset... now have the balls to help getting it better 😉
  22. 4 points
    Hah! That is strange .. I read in a VIVE Thread here in regards to the Headset somthing about XHCi Modes ( https://www.vive.com/eu/support/vive-pro-hmd/category_howto/headset-not-detected-due-to-usb-issue.html ) " Make sure that VIVE Pro devices connect via a USB xHCI port rather than to a port from a specific manufacturer, which might have a compatibility issue with VIVE Pro. " While finding out/googling more about the XHCi Mode i found this https://superuser.com/questions/480045/what-does-the-bios-setting-xhci-pre-boot-mode-do So i checked my BIOS and changed the settings from XHCI Mode = Enabled to XHCI Mode = (Smart) Auto and now .. That error is gone and the Dual Cams can be used. Happy me!
  23. 4 points
    I found a tricky way to redo room setup... Launch Steam -> Find bottom-left corner and click "Add a game" -> Choose "add a non-steam game" -> Browse your local file -> Enter C:\Program Files (x86)\VIVE\Updater\App\RoomSetup -> Select "Viveroomsetup" app and add selected program -> Launch Cosmos room setup via SteamVR dashboard Not that intuitive but fine for switching room scale/seated mode...
  24. 4 points
    @lamyipming - For transparencies sake, I'm comfortable sharing that the bulk of the Cosmo team's engineering resources are currently focused on tracking. Features and other UX tweaks will have higher priority once we improve a few key tracking scenarios hence why you're not seeing Vive Reality System related tweaks in the recent beta releases.
  25. 4 points
    Thanks @A-Jey @oxygen4004 Turned out to be a problem with Windows, not sure what went wrong during the update but after a fresh Windows install everything was working properly again.
  26. 4 points
    Okay I just tested. And it WORKS! I can actually move now hands to my face. The controllers, almost, don't freeze or spas out anymore (main word is almost) . I just played Pavlov and Gun Club VR and I can AIM!!! I could actually aim now through sniper rifle and other rifles. There is only one problem and it's that when you aim, the front controllers kinda wobbles. It moves from side to side a little bit but it's endurable. This is the best update so far! You made me really happy today, thank you very much! I'm looking forward to more updates until we reach the level of Rift S.
  27. 4 points
    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
  28. 4 points
    Issue solved... I bought a PCIe card with 2 USB ports Now it is working well
  29. 4 points
    Hi all, Our latest update is out now to improve your overall Cosmos experience! Open your VIVE Console, and you'll automatically see a "Software Update" button if you're not on this latest version. VIVE Cosmos 1.0.5 – Release Notes 1. Room setup performance improved for low light environments. 2. Resolved a USB audio driver compatibility issue where audio would not play on certain system configurations. 3. Updated multiple languages strings throughout the out of box setup, Vive Console, and Origin. - Support for multiple languages on “Learn more page” in controller pairing (Arabic, Chinese (Traditional/Simplified), Czech, Denmark, Dutch, Finish, French, German, Italian, Japanese, Korean, Norwegian, Polish, Russian, Spanish, Spanish-US, Swedish) - Fixed Russian string overlap issues in Vive Console - Fixed Japanese missing character in Origin - Support Czech language in Origin Next Update (Late October Beta) We have seen the community feedback and are continuing to work to improve tracking overall. Our next update targeted for beta at the end of October will work to improve the following scenarios: HMD: Improved low light tracking, with better prediction during fast movements Reduced tracking jitter Compatibility for Vive Wireless Adapter Controllers: Low light tracking stability – we will be continuously improving tracking accuracy in low light conditions High brightness tracking stability – we will be improving tracking accuracy in high brightness environment Overall improvement for prediction models when a controller exits the headset’s FOV Faster and more accurate positional recovery when returning into the headset’s FOV Improved near HMD tracking, which should improve archery mechanics in games Improved slow movement occlusion tracking prediction We will have more optimizations and improvements not mentioned here that we will detail closer to release.
  30. 4 points
    @JustinVive Thank you for the list of devices. Fortunately we had a Microsoft Wireless Display Adapter lie around and I could test it with that and it worked flawlessly. (I'm not sure if we missed it in our previous tests or did something wrong) As a matter of fact, our customer has his meeting rooms equipped with those to covering the whole company, thus it should be an easy way for him to us the screen sharing. Thank you again and I'm again happy with the help the forum could provide in such little time. Have a nice week everyone.
  31. 3 points
    I recently got a Cosmos and Vive Wireless and I would like to chime in. Not all PCI-E lanes are the same. Some of them are directly connected with the CPU (Good for Wireless) and some are handled by the Chipset (Bad for Wireless). I'm using an i7-3770 (clocked to 4.3ghz on all four cores) and an Asus Maximus V Formula motherboard (Yes.. it is a potatoe on paper but it works well enough with my 1080 Ti). The first two pci-e slots are directly connect to the CPU and I haven't had too many pixelation events when using the Wireless card on those slots. However, if put the wireless card on the other spots, I get constant pixelations, likely due to added latency. Right now I'm testing which processes (vrserver.exe, vrcompositer.exe, vivevrserver.exe, vivevrcompositer.exe) I can switch to high priority with Process Lasso as I'm getting some pixelations in demanding games. I want to squeeze as much from my 3770 + 1080Ti system. So yeah, all tips and tricks are welcome.
  32. 3 points
    I tried with a USBHub to power the Leap Motion, but it didn't work so probably the USB-C connection does nothing in terms of communication while using the wireless adapter. Eventually the only solution left to use was Vive Hand Tracking which proved to be very unreliable and buggy in combination with the Wireless Adapter (jittering, hand jumping, loss of tracking). Unfortunately not even the latest 0.9.1 update didn't manage to fix that so we had to scrape that project altogether and go for a standalone solution.
  33. 3 points
    Here's a bunch of gameplay from Boneworks on I agree still some issues with the rifle action. It is difficult to aim. Otherwise everything else is great. Played two hours and almost got dizzy jumping and running around. I love how Boneworks uses capacitive touch on some of the buttons.
  34. 3 points
    I use the Anker Powercore Speed 10000mah & 20000mah Batteries as they are output 2A @ QC3.0 12v (24w) Be careful a lot of QC3.0 batteries only output 1.5a @ 12v and are only 18w The original cosmos battery is 1.75a @ 12v so 21w and that's what is recommended. Cheers
  35. 3 points
    Went to beta release last night to check and see if the tracking is improved, can confirm it is not! The headset will not track my hands when playing boxing games, the boxing gloves drift in front of my vision obscuring what I can see. The tracking is also way too slow, when the HMD looses tracking of the controller often times when it reorients the gloves it's too slow and I miss my target. There is also too much drift in this HMD device, this is especially noticeable when playing games and standing still. Both the controllers and the HMD drift when standing still. Coming from the original Vive I know what is possible, this is a terrible state to be in, hire somebody if you can't figure this out.
  36. 3 points
    Funny. Boneworks works ok for me. (I just play like shit) *contains course sailor tongue language*
  37. 3 points
    Just buy the cheaper one before they are all sold out and save yourself $50 imho.
  38. 3 points
    I'm very sad by all the mean comments here. I understand that you are dissatisfied with the tracking right now and I was the same at first. Angry and saying this is unfixable hardware problem and even created thread about it. But after just 2 months that I joined - DEV team made so many updates that made the tracking tons better. When I was playing MMO Tera online, I knew developer from forum chatting. He was very kind guy and he once told me "The worst thing about fixing patches, is that as soon as you fix something - you break 3 more mechanics". Trust me the HTC team already knows that this patch broke something and they will fix it. I played yesterday for few hours and tracking with rifle is much better. I can actually zoom. All they need is just to fix the error in tracking that they created and keep improving on the rifle stance. We are much closer to Rift S tracking right now. We just have some tracking issues that are fixable.
  39. 3 points
    Hi guys, I have tested both games. This was a hell of torture for me even without sound. This is kinda hardcore horror. Scared the shit out of me, man. (Reiko's Fragment, Sinister Halloween, Both from Viveport). The Test-Build nothing changed here. But I have to say, it should't change anything, because for me the colormapping and gamma are totally fine. Sure there are some dark areas, but these are meant to be dark. I have already compared it with my oled TV. Looks the same. This is kind of an example, where we would benefit from an oled screen for a better immersive contrast in black levels. So, I am pretty sure, in this case everything is fine. I tried so many games so far. (Steam, Viveport, Revive) I haven't found any wrong color mapping in a game provided by Steam or Viveport. Best regards Clark
  40. 3 points
    Some first testing on Beat Saber: tracking is more precise now on fast controller crossing movements and less tracking loss on right controller to far left or left controller to far right movements. Still there's a bit floating around sometimes and still there's some tracking loss, but this is definetily one of the bigger steps forward. Thanks for this update 🙂
  41. 3 points
    IVE Cosmos Beta – Beta Release Notes Released December 2nd2019  [Tracking] HMD Improved the dynamic jitter UX Refined the tracking indication timing during room setup Controller Improved tracking of punching movement in boxing games Optimized tracking of throwing actions [Runtime] Fixed IPD display no showing up during tracking indication Fixed GPU memory leak [Vive Console] (BETA) Added support for “Performance Priority mode” in Settings/Video to improve headset display experience Rename executable file to prevent a bug where “Call of Duty: Modern Warfare” wouldn't run due to a filename keyword filter. [Room Setup] Updated localization strings for resetting room setup and adjusting the headphone position.
  42. 3 points
    There is a common problem with Firefox that starts steamvr when you visit sites that have some VR related scripts. Go to about:config, find dom.vr.openvr.enabled and set it to false(default is true). No idea why Firefox still does it after so much time or why sites embed these scripts.
  43. 3 points
    One of the reasons for me to buy the Cosmos is the Inside-out tracking so they can't argue that I should get the faceplate/sensor mod. I ask for a fully functional inside-out experience, nothing more and nothing less... @Dickytwo you playing on Steam account? Would like to have some Vice Cosmos competitors on my friends list. https://steamcommunity.com/id/a__jey/
  44. 3 points
    VIVE Cosmos Beta – Beta Release Notes Released 11/18/2019 [Tracking] HMD Room Setup will no longer be blocked by the high brightness notification. Improved tracking experience during dynamic movements when using VIVE Wireless Adapter. Controller Improved lower side tracking performance [Runtime] Fixed a bug where the boundary would not be triggered when the controller is static. Fixed bugs where Origin would behave abnormally when set as the default home environment. Fixed vignette setting can only be on/off on pass through but now also work on content to address Phr00t’s feedback [Lens] Fixed an issue where multiple transitional animations would occur when launching content. Improved controller pointer behavior when using Lens. [Origin] Updated environmental sounds and refined the tutorial.
  45. 3 points
    @hamez88, Cloudhead is still working on ironing out a few technical things for the Viveport release - there should be a formal update on the release very soon.
  46. 3 points
    Ya, I now have 2x QC3.0 Cosmos Batteries with QC3.0 wall charger I can now get all the runtime I want, or need, lol!
  47. 3 points
    All, I understand there is some confusion on this so hopefully this will help clarify. If you purchased during the pre-order but missed the redemption period for the 1 year, the inbox code will unlock the current promotion, which is 6 months currently. Go ahead and redeem this and follow the instructions below for getting the remaining period of your subscription. Please get in touch with our escalation team by emailing THIS ADDRESS with the following information: Your Name and Location (EU, North America, etc): A screenshot of your Viveport Account ID from this site (you will need to sign in using the account you use your Viveport service with and that you used to redeem the previous code) https://account.htcvive.com/troubleshooting : Proof of Purchase for your Cosmos purchase The team will confirm what you have redeemed and your eligibility for the Cosmos Pre-Order 1 year Infinity promotion and provide you with a separate code to complete the remaining full year period. @Dickytwo Please follow the instructions above and the escalation team will get you sorted. @Fink same for you. Please let me know if you have questions or concerns. Kind Regards, John
  48. 3 points
    This beta update ( made things worse for me. It introduced instability/compatibility issues to my Elite Dangerous game play. I was kicked out of the game at least five times during one session. It also brought back the low light warning to my Cosmos. These issues were absent with update Controller tracking is worse not better in my case, particularly my right controller. To HTC Vive engineers: I Know this is not easy, but it is what you guys do for a living. Please get this tracking fixed as soon as possible without introducing unintended problems. We are all pulling for you. It is very much in our interest to do so. Best of luck and I hope you can make some real progress with controller tracking and eliminating unintended consequences with the next update.
  49. 3 points
    I'm starting a thread on confirmed working batteries for the vive cosmos wireless. I am currently using the Omnicharge Ultimate which works great with the cosmos wireless, although a bit heavy. Please only post confirmed batteries. This should be helpful for those looking for extra batteries.
  50. 3 points
    Update! I found the bug. I am running everything towards another computer via remote desktop. Everything is connected to my game set in another room. I only use remote desktop (from my laptop) to start up the VR system. As soon as i kill the remote connection (from my laptop) the headset screens show everything OK. If I start the remote session again the screens go green. I am using remote desktop out of the box in win10 pro. I have also tried Team viewer and Chrome remote desktop, did not work but gave me other problems. So, if anybody use remote desktop and it works, please let me know. Now I can use the Cosmos, just kill and restart remote desktop depending on what i want to do.
  • Create New...