RoyMi6

Exactly that, it works great with the Warthog throttle. I've just got the most basic cockpit made out of unfinished wood, but in VR it doesn't matter at all - all that matters is the positioning, and it's spot on :)

It could be worse, I do notice it updating... because I can't stop it auto updating in the background and it maxes out the bandwidth of my 5meg home internet connection and brings everything that uses the internet to a halt! It's a pain in the backside in more ways that one.

Use your physical switches but look at the MDF in your Rift? That's essentially what I'm doing with the Warthog... Also got to love these new problems that are coming up as this technology advances - I mean I see where you're coming from but you've got to admit that wanting to output screens to an real life MDF that duplicates the same information inside a totally VR simulated cockpit is a pretty first world problem :) Saying that, if DCS would just add support for this we could perhaps have Microsoft Hololens supported greenscreen cockpits! :D I've changed my mind, I second this request!!

I've not confirmed this myself but I read somewhere that the CTRL+numpad settings are only made available if you enable the registry setting. I.e. Oculus have basically said that since the update the registry setting is not required to enable it, but adding the registry setting allows those key combinations to work. Worth a try if you're having issues and want to tinker. Also, it's worth pointing out that ASW isn't designed as silver bullet to "fix" a game like DCS. The performance improvements required to make DCS work as a VR flight sim are still as essential as they were when the Rift/Vive first launched, it's just not we have this neat little software solution that helps out in certain circumstances. It's easy to bash on it when you're looking for flaws (if you read the technical documentation it lists every flaw that people have mentioned here, elsewhere and more) but if you stop looking, and start playing, you'll quickly stop caring - at least I have :)

The latest version of Steam VR has added Asynchronous Reprojection. This is the Valve solution to the Asynchronous Timewarp that has been used with the Rift since its consumer launch. This made the Rift better device for DCS (in some regards, some still prefer the Vive for the field of view) as it allowed a much smoother experience below the native 90fps required to match the refresh rate of the display. While the Rift has already taken another step forward by adding Asynchronous Space Wrap (essentially the same idea but also copes with positional tracking) this improvement makes the using the Vive a much more pleasant experience. You might have already tried Asynchronous Reprojection via the Steam Beta but if not, get back in there and see the subtle improvements. In the real world it translates as being able to slightly increase the supersampling or texture resolution to improve cockpit readability before performance drops to nauseating levels - good times! http://www.roadtovr.com/steamvr-update-adds-asynchronous-reprojection/

From my testing I don't notice any improvement from pushing supersampling above 1.8x. I've actually settled on 1.5x as going back and forth I couldn't find any noticeable improvement in legibility in game.

AMD drive updates allow you to use ASW on their cards now:

Sorry, why isn't the GTX970 VR ready? The min spec has recently just been lowered to the GTX960 because of ASW. Every game available via the Oculus Store will run fine on your GTX970. Just like with anything on the PC however some games will take advantage of other graphic card and OS dependant features. You also don't need to update to Windows 10. Just Windows 8. Pedantic, yes, but really what's actually holding you back from updating to 10 anyway - especially when it was free for so long.

I'm literally on the other side of the world from my computer right now so can't test it myself. Anyone tried it in DCS yet? (It's basically ATW but for positional tracking) On my mobile so hard to get all the links together but basically you'll need an NVIDIA card and need to add a new registary key to enable it.

Couple of moments always come into my mind and since I've had the Rift DK1, DK2, CV1 and the HTC Vive I've got quite a few of them... but to keep it short... First was when my friend and I first got our DK2 (went halfers on it) and it was acctually a similar experience as you describe above. We got DCS up and running and he was sitting in his chair in the cockpit of the F15 on the tarmac. He started gushing about how good it was and I asked him to pass me the headset while standing next to him. If I remember right it was actually the first game we tried and the positional tracking so with the DK2 it meant I was now stood outside the cockpit. I promptly told him to shift himself from the chair and was able to "step" into the cockpit. Was a great feeling :) Second was when we started play some MP. Just a couple of COOP missions. I hadn't noticed that I was flying around with full afterburner on so when we were heading back to home base I ran out of fuel. My friend was on a regular monitor and due to the lack of resolution on the DK2 I couldn't get a bearing on the runway so had to ask him to lead me in with wingtip smoke on. To this day I don't think I've done a more perfect landing in DCS and I actually landed with exactly ZERO fuel to spare. When I stopped moving none of my control surfaces were functioning and there was sweat dripping down my back! Last but not least just the other day one of my less "gamery" friends was over trying the HTC Vive. He's been a bit dismissive of the immersion factor but there's a game that lets you use a variety of pistols and shotguns. He was doing quite well with the close range targets so I got him aim at one of the more distant ones with just a pistol. To help aim he asks if he can use "two hands" with the pistol - to which I reply "of course". But instead of just trying to manhandle the two controllers to hold the gun he promptly DROPS the controller in his left hand onto the ground... "what the hell man?!" I ask... "I thought the table was real..." he replies - needless to say he got a fair ribbing for that one :)

You can indeed have them both connected at the same time. If the game is well written enough you can even have multiplayer games with yourself! :) As others have said when games don't support you choosing what device to use it can be an issue. Luckily DCS seems to prefer the Rift over the Vive so that's no real issue. Additionally all Vive games will favour the Vive over the Rift so that's not really an issue either. So yeah, saying that, I've never actually had to unplug either device apart from using one application called Big Screen - but that might be fixed now that it officially supports the Vive. Not tried it in a while...

Subjectively I'd say that Vive is about 10% worse than the Rift when it comes to the screen door effect and pixel fill issues - which is what you're really referring to. The problem is that the Rift isn't 100% what you need to play DCS. The Rift is only maybe.... 70/80% what you really want. You can get by with the Rift, but there's a learning curve to understanding what things say when you can only JUST make out the text. By being only 10% worse it really drops the experience down to a 60/70% kind of satisfaction with the Vive. Some have argued that they don't care as it's the field of view increase with the Vive that makes the difference, but playing in the F15 I don't know how anyone can do it with the Vive and the radar - even with 20/15 vision without experience of what it MIGHT say I find it hard to read exactly what's going on. However, this could all mean nothing if it's physically painful to wear the Rift with glasses... I suppose the only thing to consider is that permanent adjustments could be made to the headset to allow your glasses to fit better - like cutting away some of the foam.

I own both. I've tried both side by side playing DCS. While technically the FOV might be narrower it's not something you notice if you actually play the game rather than focus on the issue. While technically you might get more god rays on the Rift, again, it's not something you notice when you actually start to fly. While technically the Vive might have the brighter screen again, I can't say I noticed until someone pointed it out and I went back to check. However, one thing you do notice is that if you put on the Vive and try to read the cockpit instruments all those positives are blown out the water by the decrease in apparent image resolution. The added bonus of ATW with the Rift that means you don't feel lightheaded just after getting past the loading screen is a bonus, but I'd happily concede that this is something I hope the Vive also implements. I'd also say that I spend double the amount of time with my Vive demoing VR to people. The room scale stuff is fantastic and simply blows a lot of stuff out the water when you compare it do the standard Rift demos and titles. But if you want to play a flight sim, and read real world scale cockpit instruments at the same time, you're doing yourself a disservice buying the Vive instead of the Rift. While it's a hard choice to make, the logical conclusion is the Rift for simming in my book. Like anyone else, it's just my opinion, but owning all the DK1, DK2, CV1 and Vive I know how the technology has progressed and what matters - resolution over a couple of degrees FOV is going to win every time when you use the thing day by day. FOV simply doesn't matter when you can see things clearly compared against a wider FOV that makes things blurry. The current batch of "made for VR" Vive games routinely focus on lower detail experiences and ones that don't would immediately benefit from a higher resolution screen. When touch comes out for the Rift those games will have a whole new life.

Yeah, it's a strange one as from my (limited) testing it wasn't even letting me bind it to another keyboard button! It used to work just fine on any key/joystick button you wanted but ED have REALLY fragmented the VR development between the various versions of DCS (1.5, Beta, 2.0)

Joy2Key is likely to allow this. This is how I originally bound my joystick to the left mouse button back when I had this working on the DK2. I've not got DCS2 so can't test it works at the moment but worth a shot.

Thought I'd chime in with my own thoughts - as I say in the OP this was nothing more than a project to allow me to use my HOTAS. It's been in a box since I bought it 6 months ago because I was never able to mount it correctly and make it usable on my desk. Using it with the Oculus headset gave me the motivation to rearrange my priorities and I'm super pleased with how it worked out. I also think there's the same room as ever when it comes to pits and I'm actually keen to help a friend that's trying to make a millimeter accurate cockpit as much of the enjoyment of a pit comes from the building and finding solutions to problems - like the cheapest way to get the screens working in an F15 pit :D When it comes to finishing it I'm actually going to coat it with black plastidip - which will give it a rubberised texture finish and yeah, sandpaper all around! Yeah, the MSFFB2 is such a star - such a shame that FFB joysticks are so hard to comeby as I've tried to get a couple of friends into WW2 flight sims but it's just not the same without FFB. 3DOF motion platform in the works ;)

So I've always wanted to do this but the perfectionist in me never allowed me enough time to create something that looked as good as I wanted. With VR however, appearance of the physical hardware comes waaaaaaaay down the list of priorities because once you've got the headset on it makes little to no difference whatsoever. With that in mind my friend and I put together the "cockpit" below with the basic design requirements: 1) It holds my warthog and sidewinder with room to spare for a second keyboard/mouse for ease of use setting things up 2) It's no deeper than my current desk That was it. The second requirement that it's no deeper than my current desk was required so that when not in use it wouldn't infringe on the VR playspace for the HTC Vive headset that I also own. Complicated by the fact that the throttle unit really needs to sit beside you the unit itself actually the same depth as my desk and simply pulled in and out from against the wall when I need to use it. With no prior design we put it together in an hour and a half. I plan to tart it up a bit with a lick of paint and installing a hub on the desk itself so that there's only one cable from the unit to the computer. Considering it was made from leftover wood from my new bathroom installation the total price was effectively free to me - so double win. Hope this inspires some others to get to work on a really simple build of their own! :)

You really don't... :)

Hi Andrew, Sorry for the late reply! I'd seen your question and though I'd responded but obviously not! If you wanted just to have just one, and only play DCS, I'd buy the Rift. The perceived resolution bump is very nice (but not so much that you should expect a different experience - you'll still have trouble spotting targets without labels) and combined with the current state of asynchronous timewarp (ATW) just makes it a much more playable experience. Saying that though, the Vive will no doubt come along with their own implementation of ATW... sooo then it will just be resolution... ach, but side by side it's just that little easier to read the instruments with the Rift and that won't change... I suppose I'm saying the Rift is better for DCS. If you can sell your Vive for a profit (which is likely given current delays) then buy a Rift then it's win win anyway :)

I've got both. My rambelings after receiving the Rift CV1: https://forums.overclockers.co.uk/showthread.php?t=18726269 and the same for the Vive: https://forums.overclockers.co.uk/showthread.php?t=18727285 Two years ago I was tinkering with DCS to work better with the DK2 as well: http://forums.eagle.ru/showthread.php?t=129920 I cover a lot of my thoughts in those threads but specifically the differences between the Rift and Vive for DCS I would say: 1) The Rift lenses tend to result in more light rays compared to the Vive - but you don't notice during gameplay unless you consciously look for them. 2) The Rift built in headphones are super convenient. 3) The Rift screen is better for DCS. Same resolution but the Rift pixel fill is better so there's less screen door effect so ultimately text (and instruments) is easier to read. 4) Due to built in asynchronous timewarp the Rift feels much more pleasant to play with as the framerate is kept in the sweet spot more often (it's not perfect though). For example though, that lagging you get in the menus in the Vive doesn't happen at all, so even before you start flying you feel much better :) Anything else I can answer? Another thing I'd say, if you've got the Vive, you don't need the Rift... but if you didn't have Vive, I'd buy the Rift - and get touch as soon as it launches :)

Yeah, dam. Don't have the standalone installed. Removed it to free up some space while I used the OpenBeta exclusively with the DK2. Oh well, only 6 hours to download on my measly 5meg :( EDIT: Wait, I remembered there's a couple of command line switches I can do! http://forums.eagle.ru/showthread.php?t=114030 Giving that a shot first. EDIT2: I got it working! YOU CAN READ THE COCKPIT PEOPLE! AAHHHH!!!

I've only got the OpenBeta installed at the moment... With the Rift work with that or do I need to download "normal" DCS via the web / steam?

For anyone looking to getting the most out of their DK2 at the moment I made a thread in 2014 that covers a lot of the topics people are bringing up here. Covers topics like how to use your head as a mouse pointer, improving visible of planes at a distance and legibility of tooltips in the cockpit. http://forums.eagle.ru/showthread.php?t=129920

You're not doing anyone any favours with that logic. With the various ways the graphics card architectures, drivers and game optimisations work running in the rift does not equal an instant 50% decrease in FPS - at least not long term. If you're getting 75fps with vsync enabled in the Rift you cannot, with any certainty, say you're getting "150fps" and expect that to be a useful metric. Also, as someone with two 980's, I know you're pain - DCS has always been slow on the uptake of the latest and greatest technology but I really hoped SLI would have been on the cards out of the gate with the new engine.

Appears to be a duplicate of this: http://forums.eagle.ru/showthread.php?t=151041