AlpineGTA

Yes I did the bitrate test and it was fine. The cable works absolutely fine, it's just that initial startup. It's not that big of a deal, just a minor annoyance having to start it twice, I can live with it until the official cable arrives and I'll see it that's any different. Cheers.

That looks like a nice mod, I will probably just wait to get an Elite strap. How are you managing to get up to 1.7? I have mine set to 90Hz but mine will only slide up to 1.5. In any case, I'm getting 5408x2736 with 1.5 and nice clear gauges, any higher and I don't think my GPU could handle it anyway. One minor issue I am having, the first time I load up DCS, activate the Link cable and put the headset on, I just get a flashing white screen inside the headset, even though I can see DCS loaded up and running on the PC desktop window. I have to close DCS and the Oculus software, start it up again and it's fine second time around. Strange. Btw, I'm running DCS stand alone with the open in VR ticked in settings. I run it by just clicking the DCS desktop icon and it automatically starts the Oculus software.

So, I've had my Quest 2 for a couple of days now and compared to my Rift S I'm very happy with it. The Rift S is still a very good headset but the Q2 is a noticeable leap in clarity. First the negatives: The head strap, as I'm sure everyone's aware by now, is not very comfortable. It's fine if you're casually playing wireless VR games but for DCS, where you have to keep a snug fit to your face so that it doesn't move around, to keep a steady sweet spot, I find I have to tighten the strap so much that it's uncomfortably tight on my face and after a few minutes it gives me a pressure headache to the back of my head. It takes a lot of fiddling to get it so it doesn't give me a headache but doesn't move around too much either. But if the cheap strap is how they've kept the price lower and made it more portable and you're able to replace it with a better one, then I suppose that's fair enough. I'll be buying the better Elite strap when they're available again from the store. The Link cable I have is not the official one, I have that on order, in the meantime I'm using a third party USB cable, which works, but it's quite thick, stiff and inflexible, so I can feel the weight of it tugging at my head, which can be a bit annoying. The Rift S cable feels much lighter and more flexible, I don't really notice it. Hopefully the official Oculus Link cable will cure this annoyance. At first I was disappointed. With my Rift S I was getting a solid 40fps but with the Q2 I was getting variable low 30s fps and I didn't notice much of an improvement in visual clarity. There's noticeably much less screen door effect, but apart from that I was underwhelmed. I had it set to 90hz with the link cable and tried a pixel density of 1.2 in the Oculus settings but I still wasn't noticing much improvement is resolution. Finally I thought, I'd just turn the pixel density up to the max it would go, which was 1.5 and just see how it ran, expecting it to be a stuttering 10fps mess. Amazingly, as soon as I restarted DCS I could see immediately a big difference. I loaded up a quick free flight mission and as soon as I saw the cockpit it was a bit of a wow moment, the difference and improvement over the Rift S was very obvious, everything is very clear and easy to read, all the dials and gauges, without having to lean in or use the VR zoom. And surprisingly I was still getting 30-36fps and even though it's still not the solid 40fps of the Rift S, I can happily live with that. So basically, to see a real improvement over the Rift S, make sure in the Oculus settings, you have your Link setting set to 90hz and the pixel density as high as it will go. Obviously you will need a graphics card that can handle it. For reference I'm running an AMD 5700XT, which is not the latest and greatest but seems decent enough for now. So overall, I would say for anyone considering switching from a Rift S to a Quest 2 and can deal with the Facebook requirement, it's a worthwhile buy. I can read all the dials, gauges and MFD screens clearly. I did have an issue on some aircraft even though the dials and gauges were clear, the text on the side panels still looked smudged and blurry, even if I zoomed in. I realised later this was because in the DCS settings I had the cockpit resolution set to 514dpi, I changed it to 1028dpi and the text on the panels was nice and clear and readable, just like the gauges. So something to check, if you have your pixel density cranked up and your cockpit text is still blurry.

Yes, I get it too, only on the channel map when flying warbirds. No idea why. I think, if I'm remembering correctly, it doesn't happen when I first play a mission, but if I then replay the mission I get the effect you describe.

Does anyone know what the delivery lead time is if you order a Quest 2 from the Oculus store in the US? Is there a long wait time? Edit: Never mind. If you just go on the Oculus store and place one in the shopping basket it will give you a delivery date. I decided to pull the trigger and order one. It should arrive this Friday (20th Nov). I also ordered a Link cable but that will take three weeks to arrive, so I ordered a cheaper non-Oculus one online, next day delivery. I couldn't have a new headset this Friday and then wait three weeks to try it with DCS!

Thanks for the reply, it does sound like it should be a noticeable improvement over the Rift S.

Have you used a Rift S and if so, would you say the Quest 2 is a significant improvement? I've been considering upgrading from my Rift S to a G2 but I'm feeling a bit put off by all the reports of what a hassle WMR is to get working compared to the Oculus software, which I'm already used to. And also the need, I think, to have Steam for WMR installed also to get it to work, which I assume will need a Steam account? Yet more accounts to set up and sign into that I'd really don't want to have to do. Since I'm already using using Oculus and used to it, I'm feeling more inclined to upgrade to a Quest 2, if it's a significant improvement?

Yes, cheers, I was going to try it last night but I got into doing some dogfights in my MiG-15. Off topic I know, but because of the diverse things you can do in DCS it's easy to get side tracked. I'll have another look at it tonight, unless I end up strafing trains with my Gazelle or something! :D

Yes, it's choppy for me too. I never had a problem with the previous A-10C before the Tank Killer upgrade. I'm guessing maybe it's to do with the extra processing required to run the new helmet mounted sight.

I'm really glad I got the Gladiator K when I did. I'm sure the NXT is a good stick but I prefer the extra buttons on the base of my K. They make up for the lack of buttons and switches on my T16000M throttle. And when I do finally upgrade my throttle and reassign the controls I have currently mapped to my joystick base to the throttle base, it will free up those joystick base buttons to map them to some functions on the righthand side cockpit panel, adding even more to my VR immersion.

Ok, thanks for answering. That seems like a pretty good battery life anyway. My sessions are never that long.

Does the link cable also charge the headset whilst you're using it, so there's no danger of it going flat during long sessions?

Yep, practice definitely makes perfect! After an amazing VR flight through the valleys on the Syria map, I emerged into Beirut and managed to pull into a perfect hover over the city and just sat there for a few minutes admiring the view. It really does feel satisfying when you manage to suss it. I even managed to transition out of the hover, fly over to the airport, transition back into a manually controlled hover and put it down gently on the tarmac. Something I've never managed to do before in the Gazelle. For anyone still struggling it really is worth the effort of persevering. It suddenly makes the Gazelle a joy to fly instead of a frustration.

Thanks. I'll keep practicing!

I'm really struggling with this too. Before I can even attempt to get my aircraft anything like stable to engage the auto hover, trying to slow down to below 18km/h, as soon as I go below a certain speed and get slow I go into a dizzying spin that requires full rudder to counteract. What's causing this spinning whenever I get slow. I obviously must be doing something wrong, not have my AP and/or trim configured correctly or something? Thanks.

I used to get this error quite a lot. At the time I was running Windows 10 OS on the original standard hard disc drive but I installed a 500GB SSD drive and I had DCS installed and running on that, so I was using two drives. Since then I've done two things. I've upgraded my graphics card and I've installed a 1TB SSD drive and migrated both my Windows 10 OS and DCS onto the one 1TB SSD, so they're both running off the same drive. I no longer get that crashing. Whether it's the new graphics card, the fact that everything is now on the same SSD, a combination of both, or just a coincidence, I couldn't tell you. But maybe the information is useful. I hope you fix the problem, it's definitely a frustrating one.

Yes, the SU-25 does not have a clickable cockpit. Not sure about the Mustang, I haven't flown it in ages.

Yes, it was the scroll wheel. I'm still getting used to using a trackball mouse with my left hand after being accustomed to using the Oculus controllers. It must be quite a sensitive scroll wheel. Thanks for the help.

I was starting a dark and cold instant action mission in the Viper last night. When I put my blue cross mouse pointer on the cockpit lighting knob and went to rotate it with the trackball on my mouse, the blue cross disappeared and instead of rotating the knob it moved my head position horizontally forwards and backwards in the cockpit. No matter what button I pressed I couldn't get the blue cross cursor back and get out of this 'mode'. It just kept moving me forwards or backwards. I tried quitting the mission and tried again several times but it kept doing the same thing. I'm aware of the keyboard commands: RCtrl+RShift+Number Keypad 2,4,6,8,5 etc. to move your VR position around but this isn't even what I was trying to do, I just wanted to rotate the lighting knob and I didn't even touch the keyboard. Other aircraft are fine, so is it maybe a Viper bug? It was a night time mission and I did have the flashlight on so I could see the knobs in the cockpit. Could this possibly have a bearing on it? I did also have my head turned quite heavily, along with moving the cursor even further with the trackball, to reach the knob on the side panel, before attempting to scroll the knob with the mouse scroll wheel. Perhaps this combination of inputs was enough to glitch it into a different input?

Yes, I would agree, manuals help a lot. Each has it's own merit, video tutorials and training missions are really useful, but as Redsavina says, sometimes you can get a bit lost when a tutorial assumes you already know how to do this or that and that's when referring to the manual becomes really useful to find out how to do something. Basically, using a combination of everything, I find, is the best way to go.

Ok, thanks for the reply. It's always good to have the option to carry R-77s

That's a really interesting idea. I didn't know DCS would pick up a PS4 controller as a wireless device. I really like my T16000 throttle but wish it had some buttons and switches on the base. This could be a good solution until I upgrade it.

What's the difference? How do you fly it? I've never noticed any instant action or training missions for it. Do you have to create you own in the mission editor to fly it?

I'm in the USA and shipping for me was $41 via DHL, on top of the $179 I paid for the stick. I was surprised how quickly it arrived to. I think I ordered on Thurs evening and it arrived Monday afternoon. :thumbup: I just want that VKB TECS throttle now to pair it with that hopefully will be released one day! :smilewink:

My new Gladiator-K arrived today, three days sooner than expected, which was a nice surprise. I've attached a few pictures next to the T16000 stick for comparison. They're both similar height and footprint so, just like the T16000, it makes a good desktop or chair mounted stick, which is how I'm using it. First impressions, compared to my T16000, are the stick is much lighter to move and axis seem to have a much shorter throw. Not that I think one is necessarily better than the other, it just takes getting used to. It's also a joy to have more hats, switches and buttons on the stick itself that I can more usefully map to different functions, as well as retaining plenty of buttons on the base itself. So far I've only had time for quick free flight and instant action mission but already I can feel it increasing the immersion in VR having a bit more realistic feeling stick. So far I'm pretty happy. VKB even send you a nice little coaster that I'm using as beer mat! (#dontdrinkandfly!)