Jump to content

joellipenta

Verified Members
  • Posts

    75
  • Joined

  • Last visited

Posts posted by joellipenta

  1. 2 hours ago, stvnxu said:

    @HoZy Thanks HoZy lol.

    @Sago36 & @joellipenta - Our eng team is out due to holidays, but I'm actively collecting the information here and will share with them once they're back to identify and resolve this issue.

    @joellipentaWhich USB 3.0 AA cable did you buy? It seems like this fixed the grey screen issue as reported from Fink and other users. Not confirming this is the solution, but want to gather more data for engineering to look into. Also, are you experiencing this issue in any other game such as the screen flickering grey?

    @Fink - With your issue resolved using the USB 3.0 AA cable, have you been able to test Boneworks through successfully?

    Thank you everyone.

     

     

     

    @stvnxu The cable I used is this one:

    https://smile.amazon.com/gp/product/B01KRO8D20/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1

    I actually had Boneworks crash about an hour ago while playing wired so now, I'm back to square one. I cannot figure out why this game is crashing for me. Are there any other logs that could be helpful?

  2. 4 hours ago, joellipenta said:

    I just got one as well as upgraded my CPU cooler to a Corsair Hydro H100i. Only problem is, I'm laid up with a bad back. Going to try some testing later so we'll see!

    So I switched back to wireless, installed the new CPU cooler (stress tested and it's running super cool) and booted up Boneworks. Did the height and standing things and watched the box drop with the title. Looking good!

     

    And then it happened again. The world disappeared and I heard the falling noise again. Screen was all black. Didn't even make it to the main menu and it's not like the wireless adapter was on long enough to even get warm. I submitted a report, uploaded the logs, and put the headset down with a bad taste in my mouth.

    I'm at a loss at this point. I don't want to accept that I spent over $350 for wireless components that simply do not work. Help, HTC!

  3. On 1/27/2020 at 10:35 PM, HoZy said:

    I've got a good quality usb 3.0 A-A cable on it's way, 1.5M because 1m is too short for me. 
    Will add that to the list of tricks and see if there are any improvements. 

     

    Cheers

    I just got one as well as upgraded my CPU cooler to a Corsair Hydro H100i. Only problem is, I'm laid up with a bad back. Going to try some testing later so we'll see!

  4. 8 hours ago, HoZy said:

    Something I haven't seen mentioned here, Check the temps of your Wireless. 

    C:\ProgramData\Vive Wireless\ConnectionUtility\Log

    Open up your log and look for M_Temperature, 

    Post an exert of when it starts, and then 30minutes later. 

    It'll probably be hitting about 90c and Overheating. 
    Causes controller tracking to lag, sometimes grey screen flashes & other times you straight up fall through the world depending on the game. 

     

    Cheers

     

    @HoZy I haven't used the wireless in a few days but here's the first entry of what you mentioned:

    [2020-01-19 21:57:18.374 -5 0x1954 INFO LOG] M_Temperature=31, R_Temperature=25

    Here's 33 minutes later:

    [2020-01-19 22:30:58.374 -5 0x1954 INFO LOG] M_Temperature=91, R_Temperature=72

  5. 1 hour ago, HoZy said:

    Something I haven't seen mentioned here, Check the temps of your Wireless. 

    C:\ProgramData\Vive Wireless\ConnectionUtility\Log

    Open up your log and look for M_Temperature, 

    Post an exert of when it starts, and then 30minutes later. 

    It'll probably be hitting about 90c and Overheating. 
    Causes controller tracking to lag, sometimes grey screen flashes & other times you straight up fall through the world depending on the game. 

     

    Cheers

    Thanks for this! I'll take a look when I get home. I have noticed it gets pretty hot and have been considering adding a small fan, but I'll check the logs and let you know. 

  6. 1 hour ago, stvnxu said:

    Hey @joellipenta,

    Thanks for sharing and apologies on the issue. I've submitted an earlier report when you started this thread. I'll update that with the latest information you just provided. Our engineers will investigate. 

    Are you using the battery that is provided with the wireless adapter? Or a 3rd party? 

    Steve

    This happens with the provided 21W battery or a 3rd party one. 

    • Thanks 1
  7. On 1/15/2020 at 2:34 PM, stvnxu said:

    Thanks for the video @joellipenta! I'll share this with the team to look into. 

    @ACME are you using a Cosmos with the wireless adapter? Or is your Cosmos tethered and you still experience the similar symptoms reported in this thread?

    Thanks,
    Steve

    @stvnxu I switched back to wired and did some testing in Boneworks today and had no glitches whatsoever. I played for almost two hours straight with no issues. So, it has to be the wireless adapter that's causing this. My PC more than meets the specs so I'm not really sure what else is causing the issue. Maybe excessive heat from the adapter? The CPU seems to be cool enough so I'm not sure what else could be the issue.

    @Synthesizer

  8. 27 minutes ago, TomCgcmfc said:

    @joellipenta Go back to wired for much better performance and stability imho.  Buying any Vive headset just because there is a Wireless Option is not in itself a good reason right now imho.  It's nice tech but not quite there yet.

    Normally I'd agree and stick with what works but I paid a premium price for a product and I'd like it to work. I know that's not always the case and sometimes things fizzle out, but my PC meets the specs, I purchased everything, and it should work. I get the limitations of the tech and it does work fairly well. I guess I'm just hoping there's something I can do to help alleviate this issue. 

  9. On 1/18/2020 at 6:29 AM, ACME said:

    Tonight I removed the wireless module from the Cosmos and installed it to my original Vive again: Played Boneworks for 4 hours, completing the "Streets" level. Game ran stable, no crashes. Steam VR two times lost connection to the HMD, but after restarting the HMD I was able to continue playing (the game itself had not been influenced by this issuses).

    So, for me it's clear: The Cosmos is the Problem.

    I found this post on Steam in the Boneworks forum:

    Being flung into the void is a typical result of your controllers reporting NaN as their position - I get the same by launching the game with my controllers off, and then turning them on.
    In short, it's the physical hands suddenly interacting with the environment in ways that it shouldn't due to poor tracking.

    *Update* I played for about an hour straight in Boneworks yesterday and it was great! I fought some baddies, explored, and had a blast...until it "glitched" again. This time, I didn't hit a save point. So, another hour in that game wasted. I want to play this (and several other games I mentioned) but I'm so apprehensive because of the random crashes. I may try going back to wired before my next play session but I really don't want to. The whole point of me getting the Cosmos was for the wireless freedom.

  10. 19 hours ago, VibrantNebula said:

    @joellipenta

    Do you have any video captures of the issue? One thing I'd maybe recommend when this happens is to access the SteamVR dashboard which should allow you to see the SteamVR' compositors ordinate grid - you'll be able to see the center of the room and the floor plane and will be able to tell if SteamVR's coordinate system is getting shifted.

    Here's a video of it happening. I got further than I have but it still happened. 

  11. 17 hours ago, VibrantNebula said:

    @joellipenta

    Do you have any video captures of the issue? One thing I'd maybe recommend when this happens is to access the SteamVR dashboard which should allow you to see the SteamVR' compositors ordinate grid - you'll be able to see the center of the room and the floor plane and will be able to tell if SteamVR's coordinate system is getting shifted.

    Where in the settings is this? I'm working on getting a recording now. 

  12. I'm running the latest beta for Vive (and SteamVR) as well as the latest Nvidia drivers. Whenever I play certain games, I run in weird issues that I haven't really seen many others mention. For example, I'll be playing Boneworks and out of nowhere, my view will glitch and it'll be like I'm "stuck" under the map and I hear a sound almost as if the character's falling. I can't do anything but quit the game. Because of this, I'm still incredibly early on in the game (the lack of checkpoints doesn't help). I thought it was just Boneworks so I played some other games. This also happens in Doctor Who as well as Blade & Sorcery. 

     

    I am using the wireless adapter and am wondering if that may be contributing to it. Haven't had a chance to switch back to wired. My PC an i7-8700k, an EVGA RTX 2080, and 16GB of RAM. I've tried the game on both HDD and SSD drives to no avail. I tried sending logs after the last crash in Boneworks but they failed to upload. Any suggestions on things to review/try? I haven't been able to play much at all lately since I can't make any progress without crashes. Thanks in advance!

  13. 1 minute ago, stvnxu said:

    The Wireless Adapter for Cosmos comes with everything you'll need.

    You do need to install the PCI e card and mount the antenna on your monitor or anything you prefer. From there, mount the adapter on with the battery pack and you're wireless!!

    Thanks,

    Steve

    When can this be ordered? It still says Coming Soon on the main HTC site. Will it be available from Amazon as well?

  14. On 10/27/2019 at 3:23 PM, Dickytwo said:

    I think it has now come to the stage when pre-order guys have to make a choice whether to keep this 'not fit for purpose as sold' headset.

    For those that do, I would expect some sort of olive branch made by HTC for their faith. Whether that is a discount on the base station tracking module or something else, some gesture needs to be made.

    Beyond all the crap, this product is a huge rip off as is. Even if HTC fix the tracking issues, how are you going to placate the people who pre-ordered this expecting so much more, even just something that worked out of the box?

    I have decided to keep it because I'm not having as many issues as others have reported. I'm on the 1.0.7 beta build now and have seen improvements with tracking. I do have issues still with sniper games or bow and arrow games, but it seems like the prediction has improved (albeit slightly). Lighting hasn't been an issue for me either. However, I agree that something should be done for early adopters who have kept the Cosmos. Even though I've been generally happy with it, for the price, it should've been more stable from the get-go. I read constant posts on Reddit and other sites where users have simply given up and returned it. To be honest, I almost did as well. However, adopting tech does come with risks. Had I waited a few weeks, I don't think I would've purchase the Cosmos. That being said, I have enjoyed my time with the unit and expect improvements in the upcoming weeks. 

    Please don't make me regret this purchase, HTC. I have supported you in the past and would like to do so comfortably in the future.

    • Like 3
×
×
  • Create New...