DerekSpeare

Here's the ASW thread: https://forums.eagle.ru/showthread.php?t=175199 It's likely to provide some good information.

:thumbup:

I don't know what voodoo majik they conjured up over there at Oculus, but this ASW is really worth it. I was VERY reluctant to redo my PC's with Windows10, but not only does ASW work, it's a good OS to boot!

:smartass: :smartass: Aerofly runs smooth as glass and looks good too...surprising! It's pretty light compared to DCS, but it's quite good and has an enjoyable VR experience. My testing with DCS, the CV1 and ASW lead me to believe it's a positive when running in AUTO mode. It kicks in when needed and limits the ghosting rather well compared to leaving it off. I recommend to use it only when you can't keep 90fps all the time; that's all of us, actually, with DCS. For iRacing it doesn't come on since I keep 90+ all the time, fortunately. Ultimately, though, the more hardware power each man has, the better. DCS is hungry for it...a fact we all know :music_whistling: :joystick: It's too bad DCS won't scale over multiple CPUs. I'd build something to run it WFO if it could be possible!

Updated to provide detailed instructions on how to edit the registry to enable Oculus ASW.

I'd love this and have also made this suggestion. The tooltip box size should be sized dynamically based on the amount of text it is to display. It would be good to be able to change the color to something like bright green to see it better.

You asked how to see it. My last post indicated how. Beyond that, you'll find abundant information out there on the benefits and liabilities of using it. Good luck!

You must be using Windows 8, 8.1 or 10 and you must be using the CV1. Use CTRL+KP3 to force it on. You will see the frame rates lock at 45.

I just checked the setup running the DK2 with the registry changes. No ASW for the DK2. I'm disappointed that they will stop supporting it. The DK2 is really good!

The DK2 is not supported for ASW. I read this somewhere. I'm running the DK2 on our Demo Chassis with W10. I need to make a check but I am 99% ASW isn't functional for the DK2.

Update: It's worth it...very nice! The improvement is subtle, but significant. I'd not have expected DCS to run so nicely :)

This ASW better be good...I've gone full nerd this week updating to W10 enterprise wide...gah! I'm presently doing my DCS/iRacing box, and so far it's been a breeze. I'm on to installing DCS so I'll report more later. *crossing fingers*

My next step would be to reset the BIOS to factory defaults and then try to flash again. If that didn't work, I'd pull the batter from the MB and clear CMOS and try the flash again. If that didn't work, I'd contact them for support.

I was thinking on this over dinner :smartass: I feel there's something going on with OC settings, or something...memory configurations could cause it as well if there is something not perfectly in line with what the bios wants.

When? I have autoupdating off on this box's OH installation. I hope to contain it at 1.9 until...well, forever...I'll roll back to 0800 if that's what it takes, but that will likely run out of time eventually.

@Fru: You can configure W10 to stop the autoupdating by making changes in the Group Policies. Here's how to do it: http://www.pcworld.com/article/3085136/windows/two-ways-to-control-or-stop-windows-10-updates.html Notify for d/l and notify for install are better than apply them automatically. ;) I'm concluding that the DK2 doesn't do ASW even with W10...ho hum. I'll confirm it once I take this box (in my sig) to W10. I decided to do it...though still procrastinating :P

I always do a full "SYSWIPE" when I redo computers. It's the best way to go, something many have learned to do the hard way ;)

This autoupdate "feature" is the MAIN reason why I am reluctant to go to W10 enterprise wide. I do like it much better than W7, however, save for the inability to disable updates like with W7-8.1; that's a BIG neg for me. Like many power users, I like to keep a firm grip on my PC's to keep them from "rebooting" and other things causing me excessive life stress.

Of course! :music_whistling: :music_whistling: :music_whistling: I've been really reluctant to take my main system to Win10 just to see what this ASW does. I've done three machines this weekend...sighs...getting tired of downloads upon downloads :joystick: Thank you for the information, though :) :thumbup:

Ok: Here's my question about ASW...can someone kindly let me know if ASW is working and what happens? I upgraded my i7-3820/GTX780 box to Win10 and have DCS, Oculus Home and all the other doodads installed and am using the retired-but-no-reactivated DK2 with it. When I run DCS and get into the bird I cannot tell if ASW is working or not. I hit CTRL+NP3 and then activate DCS's fame counter. I still see that the frame rates remain at 75fps; I'm guessing that the frames should go to 45. Is this the case?

Doesn't exist - though we would benefit from that feature!

Yes, and we're all better for it :thumbup: :thumbup: I kept forgetting to update the thread here. Possibly a sticky might be good.

Added update for recentering and zoom functions in VR: Enable RECENTERING and ZOOM for VR and bind it to a button/HOTAS: Options => Controls Tab => Left Dropdown (planes) => UI Layer => Recenter VR/ZOOM VR (bind to a button)

Is this specific one on your bug page here: https://forums.eagle.ru/showthread.php?t=165411 If I missed it, apologies for the redundancy...and if I did miss it all the more reason why I need highlighting to see things! :joystick: :pilotfly:

This has been around for a while. I didn't see it indicated in the VR bug list. There are no control element highlights in VR in the training missions (Tested with KA50 as an example). They are there in non-VR, but are not in VR. I hope it gets corrected :)