AlpineGTA

I would suggest try running without OTT and just use OpenXR toolkit and the Oculus software at default resolution. Keep SS off or at 100% in OpenXR toolkit. I haven't actually tried it with my Rift S but I found that with my Quest2, adjusting the SS up or down in OpenXR toolkit was actually degrading my image quality (For example, In OpenXR toolkit, SS at 130% is actually the same as SS at 70%). I'm guessing this might be what's happening with OTT, so I would try it without OTT. If you want to increase your PD I would leave SS off or at 100% in OpenXR toolkit and adjust the slider up in the Oculus software instead. This works with my Quest2.

HI, I'm currently using an i5-11600K and since the MT patch I'm actually getting pretty good performance paired with a G2 and an AMD 6900XT. However, I'm curious does anyone have an opinion, do you think an i5-13600K will give another significant boost in performance with MT, given that it has more cores (14 vs 6)? I'm curious whether the upgrade would increase my fps overhead or allow me to tweak a bit more eye candy out of my 6900XT, given that the DCS fps overlay does say that I'm currently CPU bound? I'm aware it would also need a new motherboard because of the different socket. I fly only in VR btw. Cheers.

This has been a great patch for me, in terms of performance. I play exclusively in VR and I've gained a significant increase in performance and FPS. I've been able to turn the eye candy up, so VR feels even more immersive and I enjoy smoother gameplay in SP and MP. Not only that, watching track file replays back I can turn most settings up to high and I've never seen DCS looking so good! Very realistic at times. I know there are still some bugs and issues to fix but overall, nice one ED!

Hippo, Are you using your Quest2 via a link cable? I'm getting much worse image quality with my Quest2, using the same settings as before MT. The image, especially text is very blurry and more jagged & shimmery.

A glowing review of the PICO 4 in MSFS with a setup guide:

I prefer my Quest2 to my Reverb G2. I have a love/hate relationship with the G2. I like the extra clarity but I hate the tiny sweet spot and (dis)comfort. I've just switched back to using the Quest2 and the much better sweet spot felt like having blinkers removed. It's so much easier, for example, moving my head around the cockpit to look at and click all the switches during a cold start. You have to look at everything precisely with the G2 and more often than not things look blurry because it's difficult to keep everything in focus when moving your head around, especially when looking down at side panels. The headset moves around on you face more easily and you lose that sweet spot. People often comment on the comfort of the G2 but I find the Quest2, with the elite strap & battery, much more comfortable. Unlike the G2, the side straps are rigidly fixed to the headset so I find it stays in place better, is easier to adjust with the dial on the back (elite strap), is less prone to moving around on your face and along with the bigger sweet spot, just a more pleasurable experience. The link cable too is much lighter, thinner and more flexible than the heavy stiff cable of the G2, which I find myself having to be very delicate with for fear of breaking it. They're very prone to failure and expensive to replace, unlike the USB cable for the Quest2. The Quest software too is very easy to use and 'just works' compared to the G2, even using OpenXR. I also get a smoother experience and can user higher fps compared to the G2 (my settings: 72fps vs 60fps, no reprojection) And features like the passthrough are very handy to have on the Quest2. It also has built in hand tracking and who knows, maybe one day that will get support in DCS - just something to consider/dream about. The only real downsides that I dislike about the Quest2 are having to keep the battery charged, the slightly worse image quality compared to the G2 and some shimmering when looking at the horizon. Everyone's experience will differ of course but these are just some of mine to consider, if it helps.

I took a quick look at it but unfortunately it requires an Oculus developer account, which I don't have.

Has anyone tried this? I don't know if it's been posted before, I couldn't find a thread on it. Edit: Just realised this is the same software as mentioned a few posts above.

Maybe it's just the extra depth perception of VR making the textures 'pop' more?

Thanks!

I use the front rocker switch on my T16000M throttle for rudder pedals and in over 2 years of use it's worked fine. Recently however, the rudder pedals in my aircraft have started to 'twitch' erratically all by themselves, even though I'm not actually moving the physical rocker on the throttle. It's mainly the right rudder pedal depressing all by itself. This is a bit of a pain when trying to fly helicopters, or taxi and take off fixed wing aircraft! I imagine it's just due to age, the switch getting worn from a lot of use or something and I think I read somewhere that it's a known issue with this throttle. Does anyone know if there's a way to fix this? Maybe there's a way to take it apart and service it, or clean the switch or something. Or is it just worn out and I need a new throttle? Thanks.

Yes, I have a XFX Merc 319 AMD RX 6900XT, so it will be interesting to see.

I have a 2-3 year work laptop that happens to be a Dell G5 gaming laptop, I don't know what card is in it but it definitely isn't as good as a 3080. I took it with me on holiday last Christmas, paired with a Quest 2 , to get my DCS fix while I was away and it worked well, the performance was surprisingly good. So I'd say, yes it is possible. Bear in mind though, it was a year ago, so I can't remember what settings I was using in terms of visual quality, I was only messing around in single player, it was DCS 2.7 and a Quest 2, not a Reverb, so results will obviously vary.

I've installed the latest AMD driver update and mission editor no longer crashes to desktop for me.

I've just found this thread. It's happening to me also. I haven't got a track to upload, I'm away from home at the moment, but specifically it's when I open a multiplayer track to edit so I can enable external views, it crashes to desktop when trying to load the file. I can replay some older tracks, it only seems to be happening with new tracks, possibly since 2.8 but I'm not sure. And I'm using an AMD 6900XT also.

Just in case it's relevant, since 2.8 I'm also noticing a slight stutter every few seconds when looking down at the terrain, even though I'm keeping a steady 72fps. And I'm running standard Oculus software with a Quest 2 and an AMD 6900Xt card. So maybe it's not an Nvidia driver or OXRTK issue?

I've checked my settings. In your Oculus PC software, go to settings and under the 'General' tab make sure that you have the Unknown Sources option ticked that "allows apps that have not been reviewed by Oculus to run".

I'm not at home at the moment to be able to check, but in your Oculus software on the PC do you have, I think it's called, experimental features or open beta features enabled in the settings? You might need that enabled in order for it to work with DCS, but I'm not sure. And I'm assuming you have VR enabled in your DCS settings and also enabling the link cable in the software inside the headset once it's connected? I'm running a Quest 2 and my procedure is start the Quest PC software, Turn on my headset - make sure it shows green and connected in the PC software - put on headset - enable link cable in menu inside the headset - Start DCS.

I couldn't get fps cap in Radeon chill to work satisfactory enough so I turned it off. Motion blur and ghosting us usually due to motion smoothing, but if you have motion smoothing off then maybe it's the Radeon chill causing it. I would just turn off Radeon chill, motion smoothing and adjust your DCS settings (shadows off, turn textures down) until you can maintain whatever refresh rate you're running your headset at (in my case that's 72 fps with an quest 2). That's the best way to eliminate ghosting and stuttering.

Coincidently, I noticed the same thing last night with my Quest 2. I always play with ASW off because, as you've already stated, ASW on causes ghosting of moving objects. Therefore, I have my settings so I can play most scenarios at 72FPS with ASW off and everything looks nice and smooth - no ghosting. Sometimes however, usually on multiplayer or missions with lots happening, this can drop below 72FPS, so I thought the logical thing would be to use ASW off locked to 36FPS, but like you, I noticed this produced ghosting. Switching back to just ASW off and 72FPS the ghosting disappears. You would think locking it to the lower 36FPS would give better performance but that doesn't seem to be the case. I don't know why. On multiplayer I leave it on ASW off, 72FPS and it'll default itself to 36FPS when it needs to.

I was having a lot of issues flying smoothly since the last update. I was fighting the trim, I think it was heading hold mode trying to return me to my previous heading every time I tried to turn. Before I'd even touched a control, I noticed on the Syria Free Flight Instant Action mission for example, the helicopter was flying along on it's own in a sort of wobbling motion. Looking down at the cyclic, it was moving in an anti-clockwise circular motion, like stirring porridge, all by itself, even though I hadn't even touched my actual joystick, which was perfectly still. I then noticed in the Special Options I had a box ticked called 'Control Helper'. I don't know why I had this ticked or what it does but after un-ticking it it flies perfectly smooth again. And after setting all the other trim control options to my liking, thanks to AeriaGloria's excellent explanations (thank you!), I'm now flying and trimming the Hind nice and smoothly again with full control. So just a heads up to anyone who, no matter what trim options they have selected in the Special Options, might be struggling flying the Hind, it's worth checking whether you have 'Control Helper' ticked. As I said, I don't know what it does but it un-checking it seemed to work for me.

Yep, velcroing it to the head strap round the back and side so that it comes round facing forwards on the right hand side did the trick. It's much more comfortable now and no snagging or tugging at the back.

It's certainly not a bad suggestion but I think it does say in the FAQ to always use the right side of the runway, to avoid running into each other incase someone is coming the other way.

That's not a bad suggestion. My PC is in front of me, so I'm thinking, instead of having the cable draped over the back of the chair and because of the way it curves around the back strap from the clip, it'll be better having it somehow fed forwards and under my arm.