troublemaker_na

Yes I want to do it, but it takes 8 weeks at the moment. Let me quickly (as quick as possible) get to something that works decently, then I will have the patience to look at it :-)

Oh my god, that is the problem. They are black. I knew about this controller incompatibility problem, and I searched all over to find out how my controller were. When I read that the base stations 2.0 are compatible with the elite I thought I was good. I completely missed this blue-black thing. Okay, so I just ordered 2 blue controllers. Hopefully that will fix the problem. Many thanks for the answers guys. Hopefully this is solved.

After one of my base stations broke, having my stations a little more than 5 meters from each other, I decided to buy 2 base stations 2.0. Now things are really bad. The controllers have green light, SteamVR sees them, but it says they don't track (now, somehow, the message that I have is that the controllers are standing by). The base stations have green light, and tracking fine. I tried to reboot, I reinstalled everything (all the Vive software and SteamVR), and I removed the wireless, to make things a bit simpler. I repaired (as in paired again) the controllers. Nothing. If I run room setup i get the message "Controller not visible". Can someone please help?

Strangely the cable didn't work, in the sense that the console doesn't see the wireless link box at all. Very strange. Before I try with the other cable, I want to try something else, because the problem occurs even when I am right in front of the box, in optimal position, just not very close. On the console I see that the reception is with 4 full lines, which would mean maximum. So I doubt it's the wireless connection. I noticed that the distance between the base stations is a little more than 5 meters. Hard to tell exactly, but maybe 5.30. I thought the maximum distance was 6, but I just read that it's 5. That would explain a couple of things. That would explain all that jumping around, and why the problem occurs when I do wide, quick moves with my hands. However, it doesn't explain why I have the problem only with wireless (I tried again with the cable, it goes very well). Also, it doesn't explain why sometimes I can play 20 minutes without problems. So, I wanted to ask: 1) would it make sense that the wireless connection makes somehow the larger distance between base stations more noticeable? 2) where can I get a sync cable? I can't find mine. I read it's a normal 3.5 stereo cable. I saw on reddit they recommended this one: https://www.amazon.co.uk/10m-3-5mm-Jack-Cable-Premium/dp/B001IPLKI2 Would that work? 3) incidentally, does anybody know why my nice, very low loss cable didn't work? Thanks for the help

Actually, the same does happen with Beat Saber, when I am swinging my hands wildly. I am very puzzled.

hey, I missed the notification of this message. Thanks for that, but I am reading it a little too late. I got this: https://www.delock.com/produkte/G_13007/merkmale.html It should be able to do the job, but I still have to receive it. Also, I found the SteamVR Performance Test: https://store.steampowered.com/app/323910/SteamVR_Performance_Test/ I ran that, and it went very well: So I think performance shouldn't be a problem. In the meanwhile, playing BoxVR,, the screen is blacking out quite often. BoxVR is not exactly consuming a lot of resources, and I am also playing at lower settings. I am also playing right in front of the antenna, head is not moving. Wireless communication shouldn't be an issue. This is really strange. Why isn't the same happening with Beat Saber?

Reread the instructions, I found out that the wireless link box was not well placed. Now it should be fine. It looks better, but I still have the problem. I can look straight to the wireless link box, so the signal shouldn't be a problem. It would surprise me if the problem was the CPU. Could be the Nvidia though.

Maybe closer wouldn't hurt either. Is there a chance I can find a cable extension somewhere? That is an SMA connector, isn't it?

Problem is still there 😡 After all, if the CPU is at 50%, I still doubt it can be the problem. I still think that the wireless is the major suspect. I noticed that, if I stand face to the receiver and I move my head up, the image kind of blacks out for a moment. Just for curiosity, what frequency does the wireless use? I read it's 60 ghz? And the maximum distance is 6 meters?

I did it yesterday after posting :-) Yesterday and today it was only jumping around, but i didn't have resets (screen turned blue a couple of times) and the image quality was good. Thanks for the help, so far it looks kind of good. I can at least play.

Hard to believe, but I spoke too soon. Screen still turning blue and/or white, and then black. Looks like the headset restarts. Also seeing things jumping all over; the impression is that there are tracking problems. Don't know how that could happen, to be honest. Other solutions that I have tried: reset headset and settings in the console switched to beta changed power saving settings as specified in https://www.vive.com/eu/support/wireless-adapter-cosmos/category_howto/turning-off-usb-power-management.html set power management mode to "Prefer maximum performance" in Nvidia control panel Still having issues. It worked kind of decently for days, and the past couple of days the problem is back in full vengeance. I am close to giving up. I reported an issue. The trace number is 20200426105047

hey, sorry if I didn't reply, but I wanted to take some more days to look at the issue, because there have been some developments. What happened is that the headset worked one morning, and in the evening the issue was back. So, because SteamVR was keeping searching for the headset, I wondered what would happen if I just started the Vive console. I really thought that I tried to start the console only before, and I had a message saying that SteamVR was not running, or Steam was not running, or something like that. So I was expecting that to happen again. Instead, I started the console, I put the headset on, I tried to start a game, and the game started. In the past 4 days I have been playing without problems, except once when I moved a base station and I redefined the play area (I was having rubber banding issues). But restarting everything solved the problem. I still have to try to start again Steam(VR) first and the console second, so I am not sure if that really was the solution of the problem. But at least now I can say with some confidence that the problem is gone. I do still have some rubber banding, but at least I can play :-) Concerning SMT, what is really not clear to me is how that can solve the problem is the CPU usage doesn't reach 100% in at least one core, unless it's triggering some bugs if it's on. I wouldn't expect that to be the solution.

Ah, very interesting, thank you. In the meanwhile I found something. That 100% peak in the GPU usage got me thinking. So i checked the driver version, and the version I had, installed by Windows, was much lower than the latest currently available from Nvidia on their site. So I disabled the stupid Windows automatic driver update, I uninstalled my older version (just to be sure), and I installed the new one that I downloaded from Nvidia. The installation failed. So I did some research, and I found out that I only had 2 GB left on my 1 TB hard disk. I use that hard disk only for games. Go figure. So I made some space, got more than 60 GB, and I installed the Nvidia driver. Well, now it's working pretty good. I am in Europe, so now it's 3:20 AM. I played for some minutes, but now I am going to sleep. I will try again tomorrow. But, at least so far, it looks like the problem was the Nvidia driver, or maybe not enough space on the hard disk (shouldn't I get some error in that case?). I consider the problem solved for the moment. Hopefully now it's time to play :-) Thanks a lot guys.

Okay, I wasn't planning on upgrading my machine at the moment. Before I spend some more money, can I know what the reason is? What is the difference between wireless and no wireless? I tried with wireless again, and The CPU doesn't go above 50%. The GPU, on the other side, has sometimes peaks of 100%. Why is that? I didn't see that when I used the cable. Oh yes, the hyperthreading thing. I couldn't find it in the BIOS. I am starting to wonder if the motherboard has it in the first place; I am honestly surprised i couldn't find it. Also in the manual there is no mention of it: https://download.asrock.com/Manual/X470%20Taichi%20Ultimate.pdf I tried shortly to boost the priority, I didn't see any difference. After that I didn't look at it anymore, because the CPU usage was actually quite low, as I said. I will try again.

Hi guys, thanks for the answers. I have been playing a bit, and things are a bit strange. First thing, my specs: 1) Processor: AMD Ryzen 7 2700X 2) Motherboard: ASRock X470 Taichi Ultimate 3) RAM: 64 GB @2866. I didn't want to pull a module out to look at brand and model, but if needed I can do it. 3) Video card: Gigabyte Aorus GeForce GTX 1080 Ti Xtreme Edition 4) Hard disk: Samsung 960 Pro NVMe 1TB 6) Power supply: Corsair AX760 That said, yesterday I could kind of play (Half Life), although with some flickering. Today I just had continuous disconnections; displays in the headset were turning blue, white, black. I mostly only had audio. The computer was continuously sounding like when a new device is plugged in. Yesterday it didn't look nearly as bad, although it did a couple of days ago. So i removed the wireless and I started with the cable. Started Half Life, no problems at all. I didn't really play, but there was no flickering. Image stable, everything looked good. CPU was stable at about 30%, GPU at 70%. It must be something with wireless. As to where the card is inserted, it's a few centimeters (about 3) from the video card. For a better idea, looking at the drawing of the motherboard from the Quick Installation Guide (on the 4th page): https://download.asrock.com/Manual/QIG/X470 Taichi Ultimate_multiQIG.pdf The slot PCIE1 is for the video card, which covers PCIE2 and it almost reaches the level of PCIE3. The card is inserted in PCIE4. In the coming days I will create an issue, but if it would be nice if someone could come up with an idea before I do that. Issue tickets tend to be quite expensive for everybody, and often don't come to a solution. Many thanks.