5ephir0th

You can do all thad (customize DLSS profiles multipliers, change the preset, enable the auto exposure, etc) with DLSStweaks

This is new DLSS 4 with actual drivers vs leaked ones from CUDA Toolkit From: Reddit post

Those of you that had tried the new DLSSs are using the leaked driver from CUDA drivers (571.96)? It looks like with the new driver the lower performance is neglected, at least in other games. Can try right now, my 4090 its at nVidia RMA due to a burned connector...

I dont know hoy you guys got a big gain on quadviews, maybe i get a lower gpu frametime but the increase in cpu one is insane

Apache and Phantom textures are huge and very detailed, way above the rest of modules, being the other one the Tomcat but not has heavy as those two. the only “fix” i used back when i had the 3080ti is setting ground textures to low, that way i can keep the rest of textures on high, textures, resolution, antialiasing and shadows are the options that hurt most the VRAM

AH-64 and F4 both are the most heavy modules on VRAM and SteamVR consumes VRAM too, when i had the 3080ti (with 12GB too) it was impossible to me to fly the AH-64 due to lack of VRAM using Oculus or SteamVR, i had to put ground textures to low. Using VD with VDXR takes out the SteamVR layaout from the VRAM usage so take a look at VRAM and try lowering texture detail

Has been fixed on yesterday update, not before, now its a pleasure to fly with it enabled

No launch issues, binding lost and it runs on VR as good as before the patch

Store credit for me, invested on a module being developed currently To be honest, at least for me, it doesnt matter if its ED or RazBam fault, im a customer and RazBam stated on their first public announce that they stop giving support to their products, i gave an amount of time i thinks its enough and then asked for refund

Open a ticket and ask for refund, many of us have done it

RShift + P

Looks like ED updated the DLSS dll version to 3.7.0.0 one on this update, nice, one less thing to change after an update!

I bough the Viper for 30 or 35€ years ago, and M2000C for like a year ago for even less, so…

For wet deck you need to have enabled SSLR on graphic options. I dont see anything new

Can tell on Pico, but on Quest 3 i use (with Virtual Desktop) 264 at 500mbps over 265 at 200mbps and even over AV1, to me it has the better image quality but the best you can do is test by yourself, maybe you wont see any difference, maybe (if you are using wireless) your wifi can sustain the high bitrates needed for 264, etc.

Cant see the benefits of changing from 72hz and not achieving the target to go 120hz, kicking in ASW if you havent disable it and still not achieving the target as is 120 or 60 fps

Make sure you are launching the MT version of DCS, it doesn’t work on ST

The presets that generates less ghosting for me is F one, i only fly VR

Can you share wheres that info?

DLSS "versions" are not game or driver dependent

Just a note, watch your VRAM usage, with 12gb, depends of the module you are flying and your graphics settings it’s not hard that 12gb being not enough and the stutter start to appear

Tell me you are no trying to achieve 120 fps or even 60 fps with an 1080ti/6700xt at 1.5 PD that you told you have on another thread...

I have a nice +10-20% performance improvement accross all maps (Syria, Caucasus and Gulf) on VR, so very nice...

@BIGNEWY told on Reddit that you dont have to do anything it will be just a normal update no matter the version you have

You wont get stable 72 fps with a Quest 3 at 1.4 pd, MSAA enabled with a 4070, i get 72 fps stables with around that resolution, with DLSS on a 4090, so you can get an idea giving a 4090 can double the performance of a 4070 at high resolution Have you tried ASW always enabled instead of disable? i never got good results with ASW disabled unless i achieve the target FPS