Mustang

This might help out edit: MS source https://docs.microsoft.com/en-us/windows/mixed-reality/enthusiast-guide/using-microsoft-edge#monitor-and-input-handling-issues

This trick seemed to help out a few VR users, YMMV.

Hey Alpenwolf not seeing you on comms so much, losing the drive to come on and fly.

https://forums.guru3d.com/threads/nvslimmer-nvidia-driver-slimming-utility.423072/ so this is your work at Guru3d

Noteworthy for the supposed fix: [Steam VR game]: Stuttering and lagging occur upon launching a game (Without using any Hardware monitoring tool). [3152190] https://nvidia.custhelp.com/app/answers/detail/a_id/5152

https://www.digitalcombatsimulator.com/en/personal/server/#allservers check here

My guessing is that DCS 2.7.0 will utilise features such as WDDM2.7 or greater and graphics features that just aren't available on the now very aged Windows 7 platform, you only have to look at the newer graphics that have been previewed lately to see this.

I've mentioned this on another thread but got no response but have any of you nvidia users tried the 465.21 devolper driver? https://forums.guru3d.com/threads/nvidia-465-21-developer.435779/ (see post #3 in link for alternative download location if you cannot log into nvidia website) had this running for a few weeks now and it's been very reliable in terms of stability and performance both in 2D and VR

https://www.nvidia.com/en-us/geforce/news/geforce-rtx-30-series-resizable-bar-support/

No, I have custom values for instancing in terrainoptions41.lua set so this never happens, I have posted this many times in the past in other threads but it largely goes ignored. edit: this was made yesterday in multiplayer using 3.0 distancefactor, see how it looks from around 10 minutes onwards.

Still an issue in 2021 with latest DCS builds, would be great to have the use of this feature once more.

https://ibb.co/GPzbtdR

If this is indeed a confirmed bug you could use the supersampling option in Oculus Tray Tools as a stopgap until it gets fixed.

https://drive.google.com/file/d/1XMdDzNrGIA0zVWQhBma7DR9NJRQsqPtV/view?usp=sharing link updated - I have added 'shadingOptions.lua' to this package, this file has edited values for terrain surface and tree gamma.

The watercompose.hlsl IC fail trigger will only happen the once after installing the mod, as mentioned in earlier posts, subsequent loadings will be ok.

460.97 is latest from nvidia https://forums.guru3d.com/threads/geforce-hotfix-driver-version-460-97.435791/ the performance issues are mainly affecting SteamVR/WMR users On a sidenote I am personally using nvidia developer driver 465.21 with DCS and it's been solid in both 3D and VR - P.S you can download the driver via the 3rd post in the link below safely without having to sign up with nvidia. https://forums.guru3d.com/threads/nvidia-465-21-developer.435779/

There is a newer 465.21 driver that might be worth trying, I have this installed and it seems pretty decent with my 3080 https://forums.guru3d.com/threads/nvidia-465-21-developer.435779/

DCS 2.5.6.59625 Open Beta

Sorry, I do not own that module so not possible for now.

Mod tested and verified working fine with latest DCS Open Beta 2.5.6.59398.

Yes the mod is still valid, thanks for the comparison check YSIAD_RIP

I've seen no mention of anything new for the Syria map in todays openbeta patchnotes. https://www.digitalcombatsimulator.com/en/news/changelog/openbeta/2.5.6.59398/

Another alternative is to open your options.lua in notepad++ (Users\<name>\Saved Games\DCS.openbeta\Config) and change line 7 to ["enable"] = false

Just remove the firevehicle.lua from the archive and it should work alongside that other mod.