Madmatt_BFC

New version is looking incredible. Since the day I first downloaded this utility it has been the only way I launch DCS. Can't wait to checking out the new version when released.

After the latest hotfix (2.8.0.32235.1), cockpit warning lights still bugged for English cockpit as detailed above.

Oh thank god, i have been spending all day trying to figure out what was causing this mixmatch in the BS cockpit. Hope it gets fixed soon! Madmatt

Yes but how many speeds does it have? I am pretty sure It wasn't DI's Hind from 1996/98, but I seem to recall a video game from the 90's that depicted the Mi-24 and the fan actually had both low and high speed modeled. Or maybe I am just remembering it wrong... Anyone remember which title that was???

Apart from the 2070, what are your system specs?

Since around Nov 27th the server that hosts the update files has been having issues and unreachable. It's likely that during your install the program is trying to reach that server and timing out, thus causing your error. Homefries is aware of the issue (check out his post on page 71 of this thread) but it looks like he is currently away from home and said he will address when he gets back in town.

I found a fix for the BSOD issue triggered by the chdrv01-03.sys file. What I do is launch CH Control Manager, then select the icon for OFF mode, then continue to launch whatever installer that had been causing my problem. As long as you have OFF mode enabled and you leave the CH Manager program running (if you shut it off the CH drivers revert to either Direct or Mapped mode) whatever program that had been triggering the BSOD will happily run/install/whatever. I first discovered this trick years ago when trying to install Daemon Tools. That installer would also throw up a BSOD referencing the chdrv file and after much experimenting I learned that as long as you have CH Manager run in OFF mode, the signature check passes. Now, what is this CH Manager issue that the OP is talking about? I've been able to keep using CH Control Manager for years now with Windows 10 (freshly updated to 1909 even) without issue. I may have another fix if you mean that sometimes CH Manager becomes unresponsive and freezes. If so, the fix had to do with making a small change in the Device Manager. You need to make sure the box for "allow computer to turn off this device to save power" is UNCHECKED under the Power Management tab under Properties for all your CH Products devices. Once I did that I had no problems. In fact, on my main gaming rig I run CH Manager at system launch (CMstart.exe) so that my most recently loaded controller map is pre-loaded. I also have a full Thrustmaster Hotas rig and can seemingly swap between a CH Pro Pedal, a CH Fighterstick or my Warthog throttle and joystick without issue. Hope maybe something I said above helps you guys out. There is a way to keep CH Manager working under Windows 10. My system is proof of that.

When the Rift-S and Index came out there were a lot of comparisons between the two headsets and there were some issues that really seemed to penalize the Rift-S. However, now that most of those launch issues on the Rift-S such as white flashes and substandard tracking have been resolved with firmware and software updates I am curious if anyone has given them both a fair shake within DCS. I see plenty of Index vs. Reverb and Index vs. Odyssey + comparisons posted here but I am only interested in how the Rift S (with fixes) stands up to the Index in DCS. Also, I know that audio is another big pain point with the Rift S but for me that's no longer an issue as I added a set of Koss speakers to a headband mount I custom made. Now my Rift-S audio is as good or even better than it was with my CV-1 Rift. So for the sake of this question, its a non-issue for me. So any that have been able to test with both HMD's since all of the early issues with the S got sorted out, what are your opinions? Thanks in advance!

That setting is in your Bios but I wouldn't turn it off if I were you. That enables the Turbo setting on your chip which you would want to enable so you can hit the top Turbo speed of the 9900k (5Ghz). The CPU setting in bios is in the Advanced menu under CPU Configuration. It's directly below the entry for Intel Speed Step and is called Turbo Mode. Again you really should leave that on though to get the max performance of your CPU unless you are manually overclocking it, but if you are doing that you should have it higher than 4.7 since the chip stock hits 5.0Ghz when in Turbo mode under load.

I havent had the greatest luck with using different wireless headphones over bluetooth just yet. Seem to always pickup additional noise on the audio channel. I've experienced this both with a pair of Bose and Plantronics wireless headphones that I have had using a brand new bluetooth 4.0 dongle. Oddly, when I just use them to stream audio from my PC they work fine wirelessly. Its only when I stream audio from the Rift that I get issues. That said, are you sure your steel series headphones wont work? I had trouble with mine too fitting over the top of the halo band on the Rift-S and then I noticed that if I put the headphones around my neck first, put on the Rift and then adjusted the headphone earcups up under the headband they did work. Might be something to try out.

I haven't really had those issues myself but the Rift-S seems to want a 3.1 or at the very least a USB 3 port connection. You also want to try and make sure that its not sharing the USB controller with other power hungry devices. It's not always obvious but a single USB controller usually handles multiple USB ports. Most motherboards usually have at least two separate controllers on them. Check you Device Manager and you will see. You didn't really say but what is your motherboard and what USB port are you connecting to? Inside of Oculus Home, does it show that you have a USB 3 or 3.1 or 2 connection?

The latest PTC firmware revision for the headset will show up in Oculus Home as 1.8.1. The latest PTC version of the Oculus Home application will show as: Oculus App Version 1.39.0.272909 (1.39.0.272909) Combined I have been having no issues at all with white flashes, excellent tracking of the controllers and great performance. Still wish the integrated audio was a bit louder but I now usually run with headphones so that's not much of an issue for me any longer.

Launch Oculus Home on your desktop (not in VR). Click Settings along the Left side row of options. Then Click Beta along the top. Turn on the option to enroll in the Public Test Channel. Now you will get all the latest beta releases of firmware and Oculus Home code.

My flashes are also gone. The one issue I have now is that the grip buttons on the Rift S Touch controllers can occasionally get "sticky", usually the right one. Running the Oculus Monitor tool shows that about every 4 or 5 presses the input gets "stuck" and persists at about half pressure for upwards of a second or more before it fully releases. The switch is mechanically clean and its not physically sticking at all, but the sensor is reading it as still activated at some degree when I let go. According to those on reddit that are seeing the same thing the issue seems to be related to the magnets on the battery case and cover. Taking the battery cover off helps but that's not a good long term fix. I put some thin material over the magnets on the base on cover and that also helped alot. Current best thinking is that some of the cover and base magnets are a bit too strong and causing interference with the grip buttons touch capacitive sensor. There was talk of a Oculus fix forthcoming, lets hope so. For DCS it's a non-issue as I don't use the Touch Controllers in-game at all, but for games where you are constantly grabbing and dropping items and guns like in RoboRecall and H3VR, it is a massive annoyance.

It's just a mirror of what you see in VR on your monitor so performance cost is minimal. The GPU is rendering the game for VR and then porting it over to your monitor. There is some performance to be gained in certain games like DCS that allow you to custom set the resolution for the mirrored display. Lowering this resolution doesn't change the resolution inside VR, but what's displayed on your mirrored monitor is much smaller (because it's displaying at a new, smaller resolution), but it's usually not worth the effort as gains are typically small. YMMV of course.