RealDCSpilot

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...

Try to get your nose down to regain a bit of forward flight and quickly reduce collective for a short time to change rotor blade speeds.

Last time (before latest patch) i tested this "by accident". Made an attack run with ATGM, Petro locked a target. Then i switched to rockets and Petro still had the target locked but the pipper switched to rocket mode. When i started firing the sight was also in ATGM launch condition, so i could hear the tone. Pressing fire launched the rockets and Petro also fired his ATGM... So he kept his lock all the time.

It has been mentioned a lot already, it's VRAM overflow. As soon as this happens, Windows tries to cache VRAM ressources to RAM (so called Shared Memory). From there your whole system goes into a crazy data shoveling loop (CPU, HD and RAM controller workload rises). If you are lucky, it takes some time to sort itself out. The other only thing you can do is lowering VRAM buffer usage (by turning down render resolution and texture quality for instance).

Okay, just switched back to 466.77, re-enabled resizeable bar and smoothness came back again. There is definitely something wrong with the latest driver. It's not directly measurable in frametime or fps, it's more that image studdering and warping through motion smoothing goes bonkers. I think it's more of a problem of Nvidia driver and SteamVR interaction...

@Cyph3r Hi, isn't it a good time to think about a FFB base designed and made by Virpil?

Something definitely changed with the latest driver update or DCS updates. I'm getting performance degradation too, but still hesitating switching back to the previous driver.

If 2.2 or 1.8 aren't looking realistic something is wrong on your end.

Thanks to the new free-to-play program, any risk has been removed.

It's the Apollo Program of Flightsims.

My performance dropped also (on open beta). It started with the Mi-24P release, yesterday it got even worse with the Marianas. I'm wondering why Marianas runs that bad, it's land mass and number of objects is so much smaller than any other map.

I don't remember a single point in time since 2016 where this was different. I can assure you that this is the module's standard behaviour since release. Frustrating, yes. Welcome to the club. And no, it never is or was ED's fault.