5ephir0th

Dont know what is this about, the "i dont want to update to open beta but i want a new release on stable" knowing that, when an stable is release, its just the last released iteration of the Open Beta, so, if you are afraid of the Open Beta problems why do you want that ED release it as Stable? No offense but it makes no sense...

I think you guys cant extrapolate what happen with DLSS on that another sim to what will happen on DCS, probably is the way the digital screens work on that civ sim what are causing the problems with DLSS and it doesnt have to work the same way on DCS. I havent see the same behaviour on digital screens on any other game with DLSS so i think its better to wait and see the results

Here is my settings and you have my specs at the bottom, 80hz and 2700px per eye, ffv activated on OpenXR toolkit, 80 fps stables

1. Increase the gamma for night missions, as easy as that 2. Every monitor and every VR headset has a differend LCD panel, calibration or color profile so its hard for any developer to calibrate the colors spot on for all, now that DCS is OpenXR native you can use OpenXR toolkit to calibrate all color related settings and make it fit you

As said, mesh in the same, resolution makes no difference about it, and Single Stereo Parser its avalible for DCS, but not on by default as are still on test, you can activate it via autoexec

Whtat happen with shadows? I use flat shadows for grounds and works better than ever, at least in MT

I think its because this MT implementation its parallel with the core being still ST, i expect they change the version number when MT finally substitute ST. The stuttering in MT is weird, i was having from time ago stuttering on the cockpit when i look around, now this stutter looks that dissapeared but now ground movement stutter while cockpit not

Thats not a DCS problem, thats your system specific, obviously the more a software use your CPU, more heat would produce, but if you already are hiting 80 degrees on DCS single core you have a problem with your cooling

If you mean SuperCarrier that an hefty one, until this update it was hard for my 4090 to maintain 72 fps on a populated one

Comparing War Thunder with DCS, this post must be just trolling...

People having big gains in fps and some guys still blaming ED… Ridiculous

I think some of you guys needs to relax, you dont even know what it will come on this patch, all you have read that will arrive with the patch its just pure speculation, big patches usually get delayed, same happened with 2.7 release

We still have to see how much fidelity the Typhoon will have...

Wrong calculations, you dont have to sum CPU and GPU to take the FPS, you have to take just the higher one. Frametime is the time needed by the GPU/CPU to finish the frame, GPU has to complete X work and CPU Y work to show the frame on screen, both start at the same time, not one after the other: To render X frame, GPU needs 10ms and CPU 7ms, both start at the same time and, once CPU finish, it will wait until GPU finish (3ms) to work on the next frame, in this case your "global" frametime is 10ms and you get 100 fps. If your CPU finish before your GPU, you are GPU limited, if your GPU finish before your CPU, you are CPU limited

It can be an update focused on core game

Because they set a date with more than a month in advance, last time they did something like, if i remember correctly, was with the 2.7 launch with new clouds, they announce the patchs same day as release

I expect multithreading and shadows fix, DLSS would be a great surprise but i think that would happen with the release of Vulkan

As readme say, it adds DLAA support to games that already support DLSS

If it wont reflect on screenshots then its a headset "problem", and by "problem" i mean it can be screen calibration, screen technology, lens, etc... from the headset. Now you can use OpnXR natively on DCS you could try OpenXR Toolkit as it lets you to change colors, shrapness, contrast, etc...

Maybe you was power limited?

The problem of MSAA is that is not very effective and blurry the image more than i like

No, its not a problem on the textures per se, Apache textures are way more higher resolution than the Viper or Hornet ones, you probably are running out of VRAM, what GPU is? Prior to my 4090 i have a 3080ti and running high textures on Apache maxed out the VRAM and it have 12gb

And you keep blaming ED... Update was not rushed, it was released over Open Beta and thats what Open Beta means, testing new features and let me tell you that, for being the first iteration, it came really well even with some bugs I will tell you again, PICO headsets don´t support OpenXR natively over PCVR streaming by now (it is supported on standalone), ED gave you OPTIONAL support for OpenXR on DCS, if even knowing that you still keep using OpenXR and suffer some bugs from your headset not having native support for the API its not a ED problem, that is like if you blame ED cause DCS crash when using OpenComposite with it. Keep using Steam/OpenVR and DCS (you dont have to do nothing for it) will run as prior to OpenXR update. No one is telling you that your headset is defective, its not even a software issue, just PC streaming not supporting OpenXR by now (maybe tomorrow, maybe next month, maybe next year, maybe it never get support)

Shaded lines is a shadow bug that they already are working to fix it, its not VR related as it happens to on 2D

You are telling just what you want. ED released support for an VR API that MOST of the game developers are using for his new games (and many of the old ones are migrating it), 48 hours after they released a hotfix that makes DCS not using OpenXR by default unless you force it without having to do anything, so those guy having bugs get solved. Pico doesnt support OpenXR natively over streaming, thats an ED problem? No, a Pico one, ED gives you the option to not using it and keep whatever other API you were using (OpenVR over SteamVR i think) I think the only ones who needs a tranquilizer shot its you, and maybe more than one