Marco Schaap

I do wonder what public documents the current implementation of the ECM is based on, it is my opinion that you cannot demand public documented evidence to change something if the current implementations is "based on how it works in the game is how we see it to be working."

+1 on this, I fly with the pilot body off because I don't like switching on / off all the time. But it looks better and more realistic with the body in place.

Did you set this in the SimApp config? I have the same issue with the MAN RNG knob and also the HDG and CRS knobs.

Same!

+1 I use DCSDTC for my MFD's in the Viper and I've encountered the same problem. I set up the FCR to use TWS, 80nm and 30 degrees azimuth but then it switches pages to NAV and it is back on RWS.

I think it's fair to say considering a subscription model could be a way to overcome financial worries or debacles associated with 3rd party module creators, but I think we'd overlook the fact that that doesn't magically fix the business model and might create an even worse situation. If there's really a problem with finances between Razbam and ED, let them deal with it. The modules impacted by the debacle are AFAIK all Early Access modules and come with no guarantee whatsoever. Although the intention of creating a module and selling it as Early Access will be finishing the module; there's no actual guarantee from ED or 3rd party it'll ever will. The influence we should and could have as community and users of the products is pay full prices for full functioning and complete products, and stop rewarding developers for incomplete products.

+1 Same issue

Thanks for this, going to use it tonight!

Can you try this? Only works in MT version I'm on AMD CPU (5800X3D) but it looks like it also helped my case.

I set clouds to standard which really helped my performance. Before this update I could run them at Ultra, but it now looks like a frickin' slideshow.

I recently upgraded my GPU to a 7900 XTX, I play solely in VR and was absolutely apalled by the performance. After extensive testing I found out that setting Clouds to Standard brought back my performance. I don't know what they did with the update, before I was able to run clouds at Ultra and have no stuttering issues (only a lower stable framerate). Now the gameplay looks like a slideshow when I set the clouds to Ultra.

Well, it's here now

Priorities my man...

Wild guess, and probably wrong, but could it be they changed something about the IC-process with all the "abuse" lately? Changed it in a way that the checks are now done prior to launching?

If you look at the specs of the first ever i3 with a clock speed above 2.8Ghz, you'll stumble upon i3-530, which has no AVX instructionsset on-board. From what I found, AVX on those desktop processors was introduced with the release of the i3-2120. With the current hardware from the last 5 years or so AVX should never be an issue, but the minimum specs should at least state the minimum requirements more clear than now.

It's here!!!

Is this MP compatible? It looks amazing!

Exactly how I do the BSGT procedure since a week or so. Employment of the mav's have been more accurate than ever!

I've manually resized all of the cockpit and external textures for the F16 using your method. I'm eager to test what difference it makes, in terms of load, quality and / or performance. Great find!

I disagree, the CPU handles all the draw calls. In case of VR these draw calls can be doubled, because they are drawn for each eye (or use a technique called single pass stereo, which is not available for DCS). Upping the resolution gives a greater mesh to render and thus increasing load on CPU. There are several other factors which can lead to being CPU limited, such as physics calculations, game logic etc. But that is not a factor in the main menu as far as I can imagine.

Don't get me wrong on this, but I still think 120% is a fairly high rendering resolution with a G2 and a 10700K. In that scenario you'd probably be CPU limited all the way, assuming your 3090 has some headroom, both GPU and VRAM wise. You might try this, to see if it brings any difference in menu: I find switching to F10 map especially more smooth. My menu does run with 90FPS, be it with or without this " mod". That is with 100% resolution and 1.0 PD in-game. The menu is actually rendering the hangar with the flanker in main menu and F10 map. Your mileage may vary tho. Kind regards.

I think the fact you render your picture @300% and then downgrade with 40% with FSR is one of the possible culprits. Try setting OpenXR to 100% and disable FSR and test again. I also have a G2, but then with a 6900XT. Running @100% resolution with 45FPS agl, and 60-85fps in the air.

You could be wrong. Comparing 2D to VR is not linear.

No MSAA with Native OpenXR, Reverb G2 @100% resolution in OpenXR Tools for Mixed Reality. Shimmering is minimal IMHO