RealDCSpilot

Good thing you found out that you were power limited.

https://varjo.com/products/vr-3/

@Rebel28 The safe standard procedure to launch any VR game is always starting the vr compositor(s) first. In case of WMR headsets and OpenVR game: 1. launch WMR, 2. launch SteamVR, 3. launch game. This prevents SteamVR from loading ressources to late (parallel to loading the game).

The flight model and the controls are so bad off, that the video you postet got an answer shortly after it's release: Keep in mind, the whole dicsussion is always about the fidelity of helicopters in DCS. ED's helicopter modules are really top notch, premium quality simulation. PC's Gazelle module, compared to the other ones - absolutely not.

@Baltic PirateYou are right about ED's helicopters, they really work like their real world counterparts. But the Gazelle module is far from working on the same level like the other helicopter modules. Just to name a few issues: it doesn't even work like a helicopter would, it's more of a futuristic anti-gravity vehicle where collective input causes magically stable uplift and cyclic input causes continuous rolling like an airplane with ailerons. The flight model also doesn't feature drag and rotor dynamics, this gets very obvious by watching it in flight - it always only rotates around a single fixed point in the center of the 3D model. It's on the lowest level a player controlled helicopter could be in a computer game, not fitting in DCS as a flight sim.

@hinapilotYou can also try to use process lasso to get more control about CPU core usage. 1. disable hyperthreading in BIOS if you don't need it 2. download and install Process Lasso, have VR and DCS running 3. open Process Lasso window and look for DCS.exe, vrcompositor.exe and vrserver.exe 4. set CPU priority to Always -> high 5. uncheck CPU priority Always -> Windows dynamic thread priority boosts enabled 6. set CPU Affinity to Always -> choose 4 cores here 7. set I/O priority to Always -> high 8. set Application Power Profile to highest possible 9. now repeat these steps for vrcompositor.exe and vrserver.exe, but in Affinity set a single CPU core of the ones that are left and not bound to DCS.exe

Get rid of the old S-Draw driver, we now have native support. Simply have the latest Gemini drivers from their website installed, calibrate and activate it before starting DCS. In DCS check special options and activate it there.

Yep, works exactly like in the RL video.

I find this is not a good comparison and doesn't say much. No AMD card tested, no combination of FSR or DLSS with a raytracing title available. Visual quality only mentioned afterwards, not combined with performance tests. The downgrade of visual quality does matter more in VR than on a monitor, like the latest FSR for OpenVR mod revealed. For me the image quality in DCS with extreme image quality settings in VR suffers pretty much from having FSR enabled. Fine detail like gras, objects like power poles and high resolution ground textures don't work very well with it. FSR is not for everyone, it may help on weaker systems where you need to turn down image quality settings anyway, but it is not an overall solution. I would prefer a much more "lossless" feature like DLSS for DCS.

The new RC1 seems to work with MSAA, but still everything at some distance does get crazy shimmering edges. Pretty bad for ground pounders. I also tried 2.0 and 3.0, but doesn't help with image quality. Sharpness is still superior just with standard SteamVR SS, MSAA and his ReShade filter.

@PickleMonsterAre you enjoying stalking me?

I also tested the RC1 release, the flickering edges are really horrible. Simply switching back to classic SteamVR SS settings and MSAA brought back the superior image quality and smoothness i was used to.

@zildac No worries, you're not doing something wrong. I'm on the same boat, tested it again and again. Simply going back to classic SteamVR SS settings and MSAA gave me same smooth performance as before and superior image quality compared against Fidelity FX FSR.

MSAA enabled basically breaks the process. It means that only the downsampling step will work (0.XX), it doesn't do the upsampling step. So you end up with a lower resolution and lower frametimes, but pretty bad image quality.

@f4l0 Any luck with the new ammo counter functionality for the 30mm cannon?

If anyone needs a set of G940 pedals, pm me. It's lying around, untouched for years.

That's pretty much the opposite DCS modules stand for, most people don't want an "always enabled" cheat-mode to be able to fly a helicopter module.

Some of the LOD stages also contain different color textures for buildings, it's really strange to look at an industrial building which looks grey in the distance and switches to red and grey several times if you come closer.

Most apparent in the F-16C, but also in every other module/weapon with thermal imaging capabilities, the visual effect for FLIR has become more and more degraded up to being completely useless. When can we expect a new and proper working shader?

@BIGNEWY Check the server [4YA] TRAINING 24/7 SYRIA (CAPTURE BASES), take a Mi-24P slot from Golan Heights, fly to the northern area of Sea of Galilee. In the plain area of Ad Dardarah there is a base with large radio masts and bunkers (guarded by a SAM). A bit south west of it, stands a single Merkava tank in the wide open fields. Petrovich is not able to see it, no matter from which direction i'm coming from. This is not a single problem, i've encountered it many times now since release. For whatever reason Petrovich is not able to see units on ground in plain sight.

After further testing i uninstalled it and switched back to the ReShade sharpening method. I had to disable MSAA to make it work right, with MSAA enabled it doesn't do the upscaling step (throws "Error when submitting..."). I find it not working well for DCS and VR, no matter if i use it to upsample from a lower res (0.XX) or upsample from a set resolution (1.XX). It may help with low-end systems and games that don't have that much visibility range, but the edge shimmering without MSAA in DCS is just awful. ReShade CAS and SS settings in SteamVR are still the best combination for me. The hype around FidelityFX just comes from people who see better frametimes from the lowered resolution, but don't look on the degraded image quality. Now i'm much more interested in what DLSS could offer for DCS.

That's another downside, it doesn't run on separate Tensor Cores like DLSS. So it takes away a bit of rasterizer rendering power.

Experimented a bit more, this time with 1.17 as setting (150% + 17% to nearly reach double panel resolution). It seems to do something, but i think it only reveals that "FidelityFX SuperResolution" is just a normal upscale rendering technique with a hype marketing name. DLSS is the far more sophisticated tech and superior against this.

Latest release seems not to work properly. The log file throws "Error when submitting for eye 0: 108" and "Error when submitting for eye 1: 108". What i see ingame is something like the lower resolution applied, but the upscaling part missing. I'll test the first release next.

It depends on the ground unit type, on release he wasn't able to see the Merkava tank for instance and after the latest patch he seems to also have trouble seeing Humvees...