5ephir0th

It surprise me how you guys can set 0.8 or even 0.7 without noticing the black border, i have been using this long time ago but anything below 0.92 i start to see the borders, maybe its due i have a small face, making my eyes stand closer to the lens...

As soon you say "VR" the answer is "The most powerfull one"

I’m just telling you where is your biggest performance lose and pointing you into a temporal solution while ED fix it as this topic is under the bug section, not benchmark one

Put terrain objects textures to off and you will see a good amount of the performance back to 2.7 levels, flats shadows are acting like default ones and frametimes between both was already insane on 2.7

Anyone can confirm that, apart from the see through shadow bug, they fixed too the flat shadows? I have no GPU right now until the new one get delivered so i cant test it

When i did i asked for a separate option for cockpit shadows and textures, textures one i think would save a ton of VRAM, but it looks that i will have the RTX 4090 before we have that option

We asked several times but still no response

Apart from the decrease of performance that comes with DCS 2.8, part of that due to the problem with flat shadows, i started to have some weird stuttering and lower frame on some situations that make no sense. I use an Quest 2 headset with OpenComposite + OpenXR Toolkit and, after some test, i see that if i disable OpenXR Toolkit the stuttering dissapear and FPS increase. I doesnt look that has to do with any particular option (postprocessing, FSR, FFR, etc) i just disable OpenXR Toolkit and stuttering is fixed so it look like some of the changes of DCS 2.8 has problems with OpenXR 1.2.0. I can recreat easily on Dry Dock Demolition, an instant mission for Viper on PG I would love to some of you test and give us some feedback and, if confirmed thats not only problem on my side, report to @mbucchia

Guys, those of you using OpenXR can you do some test with OpenXR toolkit enable and disable? it’s late and im going to bed but lasts test I was doing I found that, with OpenXR Toolkit enable i get like 20% worse performance than without it, this on an Oculus Quest 2. Maybe some change on 2.8 is in conflict with OpenXR Toolkit, tomorrow I will do more test

I have none of those option activated, so it shouldnt be related

You are not experiencing it, not because you clean te FXO and Metashader folder or the driver version, the bug of the see through shadows happens with Terrain Objects Shadows set to Off, its alreaady explained on the first post. On Flat the problem its that it doesnt works as flat shadows but as default, thats why the people that use Flat shadows are experiencing a worse performance ass default Terrain objects shadows it's a performance killer @Glide thats looks more of an aggressive use of LOD on shadows than a bug, it happen like that on VR but i always though that it wasnt so aggressive on 2D

Great to hear that Flappie, thanks!

Cmon, i already told on the first line of the topic... And it doesnt happen to all cause it only happens if you have terrain objects shadow on off for the bug seeing the shadow through the object or if you set as flat, that works exactly same as default (i already explained too)

That was i think, that a big part of the worse performance its for people like me that was using flat shadows on terrain objects, now we are forced to use default. It surprise me how a so obvious bug like this, that happen on VR and 2D wasnt found before the launch of the update or maybe they found and cant be addressed on time, in that case at least i have expected a note on changelog

Maybe it would help if we get some info ofwhat does it consist those improvement, maybe it only affects SteamVR, maybe it broken OpenXR...

It works ok if you has terrain objects as default, you can check the differences here: Default terrain shadows its a killer on VR, thats why flat and off options exists

I always fly on VR but it looks it happen on 2D and VR. Already did a clean of fxo and metashader folder, it makes no difference. Secondary shadows option makes no difference. Shadows on high quality Instant mission of Viper on ramp start at Caucasus so no new lights on airfields should apply Terrain objects shadow to default, normal behaviour: Terrain objects shadow to flat, it still looks like default: Terrain objects shadow to off, on airfields it still work like default but now you can see the shadows through planes and structures, even through the cockpit: On terrain objects it work as expected: So theres a problem with flat shadows and maybe at off

Off course

Well, DCS runs far worse, at least on VR, and i think i know why, shadows are broken. I was flying with terrain shadows on flat, not it looks like if you select flat or off it works as default and default work as off. Another thing is terrain objects render through objects. Secondary shadows makes no difference. And, if you ask me, clouds on vr looks worse now

They usually post the changelog before the update comes live

Thanks @BIGNEWY, very appreciated

It would be nice if someone from ED could confirm that the INTENDED update for tomorrow will be the 2.8, that way, if not, we will be ready

Makes no sense they spent time modelling internal panels while the LODs of so many assets on DCS are non existent, cmon, we have some BTR with 200k polygons without any LODs, it's ridiculous... At least i expect, if they have time to make those detailed internals, BS3 would be release with a compleat set of LODs but looking at the facts i have my doubts

I would to thank if someone from ED clarify about the "VR improvements" over the new clouds, last time we speak about the performance before release everything was "hey, it runs great, almost no different from the old weather" and the truth is, as long as you select a profile a bit cloudly it kills the performance...

No, it does not fix it, it just move it a bit further at the cost of double the performance penalty from high setting...