Darpa

I took the unit to my local PC guy (very knowledgeable about hardware). He re-seated the connection and then we gave it a try on his computer and same problem. He did say this is a very well known problem and said, in his eyes, the Rift S is next to junk from a hardware perspective. He said the reason is they wanted to make a cheap unit and they did - good for them but not so good for customers. He also mentioned I was lucky that it failed right off the bat because many people get stuck with them when they stop working after awhile. I have now returned the Rift S. So I am back to my original problem - Valve Index does not sell in Canada (better quality), The Rift S obviously has problems and the Cosmos turned out to have a bunch of problems also.

Thanks guy. It seems I am in a bit of a holding pattern. My ticket is still listed as open with Oculus but they have stopped responding to for many days now so I really hope they get back to me at some point in time. I have also asked my local PC expert to try and re-seat the cable when he gets some time as I am a clutz and maybe did not get it right when I tried. I must admit my move from my trouble free Vive to the Rift S has been anything put pleasant.

I tried both PravusJSB and Don's solutions (both made perfect sense and thank you for the suggestions) but neither worked. So, I pulled out my old HP Oman laptop (1070, Oculus ready) and set up the Rift S on it and the exact same problem happened. I have no idea why this happens but I am now assuming it is hardware related. I will talk to support to get a new unit.

PravusJSB... I certainly could try this also. Just to be sure, you are saying that instead of plugging in your Rift USB connector into your motherboards USB 3 port, you are instead plugging it into your 2080 Type C USB port using an adapter designed for that. Is that correct? Did you just plug it in to the 2080 port get it to work or did you go through the Rift setup from scratch and then plug it in? Thanks

Thanks Don, That is the most complete of any instructions to date. I very much appreciate your input and will set out to do this.

I bought a Rift S to use with DCS and ran into a problem as soon as I installed it. I have a long running thread going with Oculus support but we have not made much headway. If any one has any input or advice it would be greatly appreciated. Below is the summary I just sent to Oculus support about the problem: I have an ASRock Z390 Extreme 4 motherboard with 17-9700 and 2080ti. Pretty new machine with Windows 10. Problem: When you start the computer Windows reports a “USB device not recognized” and states it is the last USB device installed that is causing the problem (which was the Rift S). The Device manager instead of showing 2 normal Rift USB Hub entries will only show 1 USB Rift Hub entry and 1 yellow triangle entry entitled Unknown USB Device I have tried many USB 3 ports Gen1 and Gen2 - the only USB port I have not tried is the Type C on the Nvidia 2080ti (I do not have a converter). When Problem Started: When doing the setup for the Rift S - I got to the part where it said to plug in the USB and Displayport connectors. I did so. While the Rift S install application showed a successful hook up (everything turned green and it said all was O.k.), however just before that occurred Windows put up a notification saying that the USB device was unrecognized. The unit however worked perfectly. I could do everything. To confuse matters even more inside the Rift App there was a notification saying the Displayport connection had a problem (and yet everything continued to work perfectly). Important Part: The problem only happens on boot (I get a Windows notification and the yellow triangle entry in the Device Manager). When I unplug and replug the Rift S USB connection the problem is solved (the Unknown entry is replaced by s “Rift USB Hub” entry and everything works). Now everything will work on the Rift S perfectly until I reboot again. What we have tried to date: - Update the graphics drivers (I was only 1 version behind). Nothing changed - Uninstalled and reinstalled USB drivers. Windows did it automatically. All version remained the same. Nothing changed - Went through the hell of checking and re-seating the Headset cable (correct me if I am wrong but I think this can’t be a hardware based problem as the unit works perfectly and only reports an error on boot.) - In device Manager turned off power saving on the Intel USB driver. Nothing changed - I tried a long process of (while the Rift app was running) uninstalling and reinstalling the Rift USB HUB drivers and the Unknown USB Driver and letting them reinstall. Nothing changed. - On the support phone call tried a Rift S software repair. Nothing changed. - On the support call we switched to the Beta channel. Nothing changed. Key takeaway. The Device works fine and only reports as an unknown USB device on Boot. HOWEVER, I do not want to be unplugging and re-pluging the USB cable every time I use the machine.

Some very worthwhile points made: Don, Supuma… you have rightfully pointed out why I have just not gone directly ahead and pre-ordered the Cosmos. I know that while the specs initially turned me off the Rift S that many people, including yourselves it seems, are very happy with it for DCS. Hence my slight momentary dilemma Baldrick… yes, a gamble indeed. In regards to WMR, I tend not to get involved in foundational technologies that I have no long term confidence in. Eagle - Xtal, still don’t feel like I know enough for the uses I will put it to, but I wish the company all the luck in the world. I will follow closely Re: Index not in Canada… Yes - Valve is good at software distribution but maybe not so good at hardware distribution :)

It is VR headset decision time and I know many of you who use VR have been down this path and use VR for the same things I do (DCS/flight sims and driving sims mostly). So any comments appreciated and welcome. I, like most of you, want all the fundamentals - good resolution, as little SDE as possible etc. In addition my personal considerations are: - Works with all existing SteamVR games - No WMR based solution - Money is not an issue - High Quality audio Given that I live in Canada and Index does not ship to first world countries :) I think that leaves me with a choice between Rift S and Cosmos. Cosmos seems to certainly have better specs but it has not been seen in the wild yet. So my choices are pre-order Cosmos, buy Rift S, or continue to wait until some real Cosmos reviews come out once it is released.

The Index - is only available is certain regions of the world and I am not in one of those. I would have probably got it otherwise The Reverb - also no availability Rift S - does not have the specs I want Vive Cosmos - Still not available (but in the running when it comes out)

Hi, I am downloading stable version2.5.5.32533 (I do not use open beta). Could someone please tell me which (if any) of the following is correct: 1) There are no VR code optimizations in this version - those are yet to come. 2) All the changes that were discussed about VR optimization are now included even though there maybe continuing updates and changes 3) Some of the VR optimizations were included but not all. 4) No one is quite sure at this point in time what is or is not included and the folks at DCS will hopefully clarify this at a later date. Thanks for your help

I agree with jcomm... I am having a great time with this wonderful little plane. A very pleasant surprise and I hope there are other planes in their future.

As I long suspected... the meaning of life, the universe and everything is NOT 42. It is a brand new powerful VR machine, a crop of new 2019 VR headsets and the guy who produces your favorite piece of software telling you he found a 50% improvement in VR performance.

OK... all of this now makes perfect sense and I will follow the good advice provided. One quick follow up question. I have 3 ways to set SS. 1) SteamVR Global application default setting (which in my case as I noted earlier is 200%) 2) SteamVR per application setting which is a multiplier on top of the default 3) In-game SS (in the case of DCS using PD) imaken thanks for the math and overview. You seemed to lean towards using DCS PD. Is there any specific performance or other reason? I was planing to keep my Global at the default of 200% for all other general games. So in order to reduce SS for DCS I would have to set my SteamVR DCS application specific setting to 50% and then set DCS PD to 1.8 or 2.0. Or I could just to leave the Global SteamVR setting at 200% and then set PD in DCS to 1.0. Is there a performance or other reason to be using the DCS PD as the main determinant for SS? Thanks

OK, I get it now. Motion Smoothing is kicking in. SteamVr defaults to Smoothing ON globally and I can turn it on or off globally or per application. This is early days for me with this machine and I have only done a bit of testing but (so far) visuals are better with Motion Smoothing on with 200% Application Resolution in steamVR and a PD of 1.5 in the game than with 200% and a PD of 1.0. The only slight downside at the moment is a bit of propeller blur on the Yak-52 with Motion Smoothing but with jets it seems just fine. I actually did a few small setting changes and got Motion Smoothing to 45 FPS. So I can have 45 fps with it ON or 90 fps with it off when I drop the PD. So either way I don't think I can lose. I can get good visuals and smooth performance without Motion Smoothing kicking in or I can get very good visuals and smooth performance with it on.

Thanks for the reply's to date. Yes, steam defaulted to 200% when I installed it (I guess because of the 2080 ti). Still not sure why I would want to reduce either the PD at 1.6 or the 200% when the performance and the graphics are so good (I am not complaining at all about DCS performance). If I had not turned on the fps counter in both games I just would have assumed they were both running at 90 fps. It also is still unclear to me why there is no difference visually (graphics or performance wise) when there is actually 60!! fps difference between the two. Something does not seem to add up here. Also should there not be some difference in fps in DCS given the graphic complexity in the scene (number of planes, number of objects, cities etc. etc.)?

There is something I am not quite understanding re: Performance in DCS. I am just setting up my new VR machine (2080 Ti, i7-9700k, 32 MB memory, fast SSD etc.). The first 2 sims I installed are DCS and IL2-Great Battles. Both are looking great in VR and performance is silky smooth in both. In DCS I have PD set to 1.6 (so far) and the rest of the settings are balanced (some things on high, a few others still on medium and low) and I have no MSAA or SSAA. IL2 is reporting in its in-game FPS counter that I am getting 90 fps almost all the time. DCS reports in its in-game fps counter that I am getting 30 fps all the time. It is 30 if I am alone in a clear sky or 30 if I am low in a city with lots of other planes and vehicles. In SteamVR the settings>>Video>>Application Resolution (global) defaults to 200% and everything else is default. So how can one be reporting 90 fps and the other 30 fps and both are performing equally well from a visual and "feel" point of view. Thanks for any input.