windsurfingstew

Thank you. I think I understand now. If I put myself in the follower's position, I can see it is most difficult to pursue and get a shot when your lift-vectors are not parallel-ish (ie not both pointing toward the centre of the same turn in the same plane). So, if you can get your lift vector out of plane, in two dimensions, not just one, then it is even harder. Also, I don't usually use the rudder much, other than for landing and take off. This is a good tool again to make things difficult for your pursuer. I think I might set up a mission to try this.

Any chance you could be a little more specific on this? So, you're starting flat and level headed North with the enemy plane behind you. You mean pitching up very hard to say 60 degrees up, then rolling out and ending up headed West (or East)?

In reality, I'd imagine that going from full afterburners to then cutting the throttle and deploying the airbrakes would probably catch out most humans who were hard up your tail. And, once you've hit the brakes, you're wide open to a missile attack, as evasive maneuvers usually require you to start with some speed. Thanks. This has been helpful.

I guess my question was a bit like asking, 'When playing chess, and all I've got left is my king, and the other player has all of their pieces, how do I go about winning?' The answer is, 'You probably can't, so try not to get into that scenario to begin with'.

So, you're pretty much trapped then. You can hope for a mistake, or attempt an outrun, out climb, or out turn but it's likely futile. Could hope for a wingman to help. I guess all I can do is fly as erratically as possible without losing too much speed, ie making it as hard as possible for him to judge lead for his cannon, but that still leaves me open and slower for an IR missile shot.

You mean like this?

(Hopefully I've got the right part of the forum for this question.) Your favourite way to get someone off you six? In single player, I have a mission where I'm in an F-15 and dogfighting against an AI Su-27. Once it is on my six I find it difficult to shake. Clearly when there is a mismatch in aircraft specs, you may be able to outrun or out turn the other aircraft. But when planes are similarly matched, what methods do you use to get someone off your six? (I looked for a fart dispenser, but there isn't one in DCS!)

Thanks Of course, if default settings in an app then the user could leave them uninstalled. But, the benefit of them being installed with default settings is it allows single setting experimentation after. I am hoping my set-up can provide a working base-case for AMD/Quest3 users who want one. From there, they can change settings in Oculus, Oculus Tray Tool, OpenXR Toolkit, or DCS. It's just a starting point that works very well for me. No doubt it could be improved, but I feel it's 90% of the way there (for my preferences). It was a right mess before as there was IMHO too much mixing and matching across tools. It was only when I simplified everything that I started to see massive improvements. Two questions still on my mind are (1) the shadows from the trees appear a little too late, so when i fly over them, they are quite distracting. Not sure if this is a pre-load radius thing, or to do with the shadows or texture. Will experiment further on this but it's not bothering me much. The second (2) I have pixel density at 1.8. I'm wondering if this could be more than the total resolution of the headset. Eg perhaps the resolution generated by the system, times 1.8x, might be more than the resolution of each eye in the headset (esp given reduced FoV)? It's not clear if we are making the area 1.8 larger, or each of the width and length 1.8x larger. I guess this is something I can play with and work it out for myself. The main thing is that I now have a very stable base-case I'm happy with. Anyone with a similar spec and AMD/Quest3 will hopefully get a similar result. Any further tweaking is likely to be only a minor improvement, ie icing on the cake

Thank you all for your help. I have taken my rig from a stuttery 32 fps with mediocre visuals, to a smooth 60-72 fps with nice clean visuals. I have posted my complete configuration in this thread. Hopefully someone else with the Quest 3 and AMD combination finds it helpful.

When I first got my graphics card and headset, there were so many settings on so many pieces of software I was overwhelmed. Being an AMD grahics card, rather than an Nvdia also may have caused some confusion. I am posting my complete tuning in the hope that it can help others. This configuration has taken my system from a stuttery 32 fps to a smooth near constant 60-72 fps (single player moderate/dense low altitute), with better image quality (all on the same hardware). Hopefully my configuration can act as a starting point for anyone with an AMD graphics card and Quest 3 headset. 1) My PC hardware is powerful to begin with, with 64GB RAM, and a moderate overclock on the CPU and RAM. I already run DCS from a solid state M2 drive. 2) My AMD video card is currently top of the range. I chose the safe option of a moderate overclock. I kept all of the graphics settings standard. AMD bundles many tweaks that can be turned on, but my concern was that these would interfere with the other steps. These are all off for now. In summary, this is a powerful GPU, with moderate overclock, but none of the special bells and wistles turned on. 3) My Oculus software and Quest 3 are kept completely vanilla. I also tested my Link cable to ensure it could carry sufficient data. It tested as fast enough. 3) I installed the OpenXR toolkit. After a lot of experimentation, I kept everything here default. My understanding now is that features, such as upscaling etc, should be set in only one place. Setting them in OpenXR seems IMHO to conflict with DCS features that are meant to do the same thing. 4) Here is where things get more interesting. The Oculus Tray Tool MUST be run as administrator otherwise it won't work. I kept everything default here except for the changes shown in red. I have made a DCS profile. It's important to set it to start with windows. After much messing round with ASW settings, I found much better performance with it off. With any of the ASW settings on, the frame rate would stay stuck on the slowest setting it had been down to, even with clear blue skies and no scenery. It also had stutters, and some weird artifacts occasionally. I now understand what ASW is for, but sadly it doesn't work well for my rig. IMHO it is best to start with this off, and only try playing with it as a last step to see if it helps you or not. FoV 0.80 x 0.80 works well for my Quest 3. The black boxing is slightly noticable but it did hugely improve the performance. With VR you look at what you want, so the extreme peripheral vision is not that critical. 5) DCS settings have been chosen based on feedback from other users, reading and experimentation. I am using 1.8 pixel density which may seem extreme. For me, I prefer a high resolution and less clutter. I tried various combinations of upscaling but found the combination of MSAA 2x and a very high pixel density worked best. NIS also looks good, but different, compared with MSAA. Pixel density is the one setting I would turn up or down, to keep in the 60-72 fps range. That is I will use it as my master control. So, there we have it. I'd like to think that if you're a newbie, with an Oculus headset, and perhaps an AMD card, I'd start with these settings. If you're not happy with the frame rate, turn the pixel density down. I'd also then try experimenting with turning AWS on or changing DCS settings. I'm no expert. I'm quite new. In my attempts to get things running well for VR, I found very few end-to-end configuration examples. I hope you find this helpful. If you have any further suggestions, or disagreement, I'd love to hear your thoughts below. FINALLY Thanks to those in this thread who helped me out on this thread.

Thank you all. I have done a full reinstall of my Oculus and OTT, including Admin first run of the OTT. Works like a dream now. I suspect at some stage I'd tried to run it as my normal non-Admin user, and it got itself tied in knots.

Sorry for the newbie question. I've read quite a bit on both of these but am still a bit confused as to whether enabling an anti-aliasing and anisotropic filtering will: 1) For the same other settings, improve visuals but tend to decrease frame rate OR 2) For the same other settings, reduce quality of visuals but tend to increase frame rate

Where did you find the new version of the Oculus Debug Tool? Mine is still the old one and won't connect.

Sorry. When I said the service, I was referring to the 'Oculus VR' Service which is started and stopped through the OTT tool.

Thank you. That's quite nicely designed, so I'll still keep my modules etc but it will be like I'm a new user.