Al-Azraq

The problem with the G2 is that it has a much greater resolution so it is more expensive to run and soften the image with the current techniques DCS uses. MSFS is a much more modern piece of software and you can really notice it is much better on VR precisely because of TAA. This AA technique is much less expensive than MSAA and works much better especially with deferred rendering where MSAA is especially intensive and doesn't work well (actually DCS kinda hacked it in). Unfortunately I don't reshade will be able to apply TAA as this technique needs motion vectors and that should be added by ED. Hopefully it will come with Vulkan.

Most likely your CPU is holding you back a lot, it will even in 2D so in VR it is much worse. MSFS is a modern game with modern rendering techniques including TAA and DLSS coming which is a much better AA solution than MSAA especially under deferred rendering. This alone will give MSFS a solid advantage over DCS in both image quality and performance.

Thanks a lot for the testing! Personally I don't use MSAA because it is hacked into DCS right now. When DCS switched to deferred rendering a new AA solution was required because MSAA doesn't work very well in deferred rendering and it impacts the performance a lot, but we never got it. One of the advantages of deferred rendering is to have multiple light sources without extra performance impact, ever wondered why ED introduced deferred rendering but we never got real lighting from light sources in DCS? Yep, you guessed right, because thanks to the ancient MSAA the performance will be destroyed (even more). On VR the issues are much more noticeable and MSAA with deferred rendering creates the infamous 'shimmering', which we will not get rid of no matter how much MSAA or supersampling we apply with our NASA PC. You can turn off MSAA but then you have a non-aliased image with shimmering as well. There is a reason why optimised VR games like Alyx use forward rendering with MSAA. We need alternative AA solution for deferred rendering like TAA or DLSS, that will solve many many of our VR picture quality issues in DCS. Hopefully with Vulkan.

It only affect the Picture in Picture images so mirrors, TGP, Maverick, etc. the regular MFD pages are not affected by this setting.

hahaha sorry to bring you the bad news mate. Eventually you will get used to it, learn to love VR for its strengths which are many.

That is happening to us all, no fix so you will have to learn to live with it.

You can also add more voice commands to a single action. For instance, due to my Spanish accent VAICOM has difficulties understanding the word "auto" so I add a different command for the actions including that word. Maybe instead of "tally wildcard" make an additional command as "spot wildcard"? I highly doubt that Windows recognises the word "tally".

@Jayhawk1971have you tried this? I will try it next time I fly Zone 5:

Personally I prefer to keep my G2 at 90hz and aim for 45 FPS but yeah, increasing the SteamVR SS really improves everything. Shimmering will be impossible to solve because of deferred rendering not going well with MSAA and the lack of an alternative AA method, but it helps a bit to have higher SteamVR SS especially within the cockpit. I keep my setup clean of any mod including OpenFSR. In summary, I'm running SteamVR SS at 80%, mid to low graphics, and I'm always at 45 FPS. Reprojection rate in the Tomcat is higher than in the Hornet but still manageable and even I'm thinking about pushing a bit more to 90% but it looks good enough now.

Personally I tried OpenFSR and decided to remove it. For instance, with SteamVR SS at 100% and OpenFSR at 80%, you get the same performance results as SteamVR SS on 80% but you add another layer of upsampling and artifacts. For the SteamVR SS at 80% gets me better image and it is easier to control, debug, and tune.

I prefer to just not add another layer of processing with FSR. I just use SteamVR SS. So for instance in your example I will just set SteamVR to 70% and it will look better than FSR at 0.7 IMO.

Your problems with the Tomcat sounded like headset disconnect issues at first but if you say that other aircraft are fine then I don't know. My issue exactly is that I just get worse performance which also happens in 2D.

This is a great explanation, thanks for taking the time. Personally I went for 45 FPS with reprojection and tried to give it as much as overhead as I could so the reprojection works better. I get 10-11 ms GPU on the Hornet but 16 ms on the Tomcat which is also enough but you can really notice the Hornet is smoother despite fpsVR showing the same 45 FPS. Of course, 90 hz in DCS is not easy and you have to give up a lot of fidelity to achieve that including MSAA which makes everything look really shimmering. Textures on medium I can stand, Low terrain as well, low shadows, and shadows off for ground objects but shimmering just looks completely terrible.

In addition to setting up your IPD correctly, also make sure you are wearing the headset correctly. I am new to VR and took me a while to learn and adjust the straps so my vision is perfectly aligned with the lenses. Put your headset on with the straps up and once you are happy with the image keep holding the headset with your left hand and pull the straps down with your right. Adjust the straps trying to not lose the headset position. Do not overtighten so you are comfortable but at the same time not letting the headset to move a lot. The straps on the back of your head will go lower than you expect, and wear the headset like a helmet so it is a bit loose, not like a cap. Once you have everything setup it will stay like that forever. When you want to remove your headset do not use the straps, just hold the front with your left hand and pull the straps up.

I've got into VR recently so still playing with the options however, forget about keeping 90 hz in DCS no matter what setting you use. You can get pretty close with my system by disabling MSAA but then you will have a lot of shimmering and jaggies. I settled with a mix of mid to low settings, SteamVR at 54% and 45 FPS locked with reprojection all the time. Reprojection causes the fast moving planes from you have some ghosting but I will live with it. For VR you want your frame time to be stable above everything else, then reduce it below 20 if possible and use reprojection. The more overhead from 45 FPS you have the better reprojection will work.

Hey man, I am also new to VR and your Tomcat is my favourite jet in DCS followed by the Hornet and the difference in performance is abysmal between these two. I run DCS in a mix of mid to low settings and I can lock to 45 fps (so reprojection works its magic and increases it to 90 FPS) with both the Tomcat and Hornet. However, in the Hornet, as I have way more overhead from those 45 FPS, it runs much smoother than the Tomcat. If I disable reprojection and unlock the FPS, I get much more FPS in the Hornet.

It is set at 100% fixed I think.

While shimmering is really annoying, you can't fix it even at 100%. So I decided to take a bit more shimmering but much better frame rate.

Yes, I tried it for 100% SteamVR resolution and 0.8 on FSR and it worked great in order to keep 45 FPS with reprojection. However, I'm not so sure it provides and advantage to just using 80% SteamVR so I decided to keep it simple and just use the SteamVR resolution. I'm very happy with 54% to be honest.

So I'm new in VR as well and decided to try these settings. I was running DCS at around 80-100% SteamVR resolution and settings on mid-low with MSAA aiming for 45 FPS and while reprojection runs well and I could deal with it, I decided to try aiming for 90 Hz. I disabled MSAA and reduced the resolution to 54% and I can keep 90 hz while in the air! I disabled also reprojection as it has a 10% computation cost more or less so when I'm on the F-14A using cold start Nellis instant action mission, I sit at around 70 FPS which totally doable. I have more shimmering of course, specially when on ground as there are more non-aliased elements such as fences, columns, lights, etc. but I'll get used to it. With this I don't get ghosting from enemy planes passing by and total smoothness. Clarity within the cokpit is great and enough. Sure 80-100% looks better but DCS is unoptimized in VR. Looking forward for Vulkan, with newer AA techniques we should see a great improvement in image quality and hopefully better performance as well.

Please post your results, I'm interested. Understanding how VR works and the different options there are is a bit complicated at first but once you get it, it is relatively easy to tune it and get your visuals where you want it. Of course your hardware will be a limitation but still doable. For all the horror histories I've heard about DCS VR, it is not that bad. This doesn't mean that DCS VR doesn't need MASSIVE work from ED but it is doable right now. I will test more this afternoon.

Hello! So I have noticed that it is not possible to order Jester to lock an specific radar contact. You can do it if you are in TWS and have AIM-54 onboard as in that case the system assigns a number to each track and you can order Jester to lock an specific track using that number. However, if you are not in TWS or you don't have AIM-54 onboard, the system doesn't assign this number and you can't lock an specific contact using AIRIO. If you disable AIRIO and use the wheel instead, you have to option to do so as shown in these screenshots from a Grim Reaper's video: So this means that it should be possible to integrate this into AIRIO. I understand that it would be difficult to integrate it directly into AIRIO as saying the azimuth or knowing which number in the wheel is assigned to each contact is impossible. But I've been thinking and if this idea could be introduced I think it could be a good solution to have this critical ability built into AIRIO: Would it be possible to issue a command that makes pop-out a text message that lists all the contacts with the REL. AZ. and DISTANCE as in the wheel, with an assigned number 1-8 , and then order Jester to lock them by saying that number? For instance: Player: "Lock Specific Target" Result: Text message is shown with: 1. Rel. Az.: 20 Distance: 13 nm 2. Rel. Az.: 18 Distance: 37 nm 3.... Player: "Lock target 2" Result: Jester locks bandit 2 Rel. Az.: 18 Distance: 37 nm I hope something like this could be implemented as having the ability of locking an specific contact is very important. Best regards,

This is the right answer. With the current renderer and the AA techniques used, antialiasing is not applied to every object in the scene such as fences and clouds. What we need is TAA, which applies to the whole image while performing much better. Personally I’m new to VR and all this shimmering has been a total turndown for me as I have it even for other planes on the ramp. EDIT: I talked too soon. I decided to give it a fewer dirty tries before work and I must say that I had very good results. First, I pushed the pause button on the Mixed Reality Portal. I don't know if that improved the frames in the game but at least I've got rid of that annoying screen. Then, I put 100% resolution on SteamVR and the shaperning on FSR at 0.2 (scaling is 0.8) Shimmering is much much improved and performance is good. Actually I didn't notice much impact when using 100% resolution (I guess it is due being locked at 45 FPS and having overhead). It is good even in the Tomcat on Nevada Cold Start which is a busy ramp. GPU sits at 70% usage, so I'll try to increase some graphical options or maybe the resolution for extra clarity. I find the graphical fidelity enough with my current settings and I would appreciate more clarity rather than better shadows. PC is on my signature.

So after getting DCS VR tuned and at the point where I found it comfortable, I decided to give W11 another try. I disabled HAGS and another option concerning variable refresh rate that was right below it. I am very happy to say that my performance in W11 is the same as in W10 if not better thanks to the better scheduling for Alder Lake. Sure I lost time formatting and whatnot but I have learned some things along the way. Thanks to everyone in this thread for helping me!

Thanks again to both! Definitely something was wrong in my configurations, good part is that if you are getting that performance I should be able to as well after I find the culprit.