Mustang

nvidia 445.xx series have a serious problem with DCS World, I observed GPU clock throttling happening for no reason during sessions resulting in huge FPS drops, the earlier 442.xx drivers do not suffer from this.

I noticed heavy GPU throttling for no reason aswell with the 445.xx driver branch, rolling back to the 442.xx series solved it here too.

It needs to be applied whenever you start up the Rift and you're about to launch the sim, you can even do this while DCS is running though.

Have a look at this post here https://forums.eagle.ru/showpost.php?p=4256036&postcount=9 it seems using CLI executable along with server:asw.off truely enforces no ASW, far better than any other of the tools.

Is this dependant on server setting? I believe you need externals on to stop the camera following the seat, you like to fly in Blueflag server alot don't you where the externals are all off? I agree though the ejected pilot should be working regardless of server view enforcements.

I have noticed a pattern that the stats problem appears to be worse if the server cycles to a new mission, restarting the server with a new session seems to help.

That is a leftover from an older installation guide, I will update this shortly but for now just copy Bazar and it will work fine.

In 2.5.5 the host was called 'player' and you still had to make an edit to adjust the name, but it was more tricky since you had to edit a .cfg file to do this, in 2.5.6 you can just type the name in a box quite easily. Also to add this is a dedicated server thing only, the older DCS hosting method never had this problem.

It is the callsign of the server host as you say, it's down to the owner to adjust this on every server session launch.

The standby memory program? It's very simple to use just extract to any folder and just run it, just stick to the defaults and let it do it's thing in the background, you can halt it at any time and can be launched at any time too.

You can always try out a standby memory program like this one https://www.wagnardsoft.com/content/intelligent-standby-list-cleaner-v1000-released been using this for months now and it works very nicely.

Been an issue for close to 2 years, reported several times https://forums.eagle.ru/showthread.php?t=202284

In 2.5.6? Completely cleared up for me here, only 2.5.5 and earlier had this problem.

Yes this is a workaround, if the user uses low textures he will still see the modded ones, a bit of a hack. I've never used Saved Games folder for terrain modding (although others may have had success) this package is laid out to be injected straight into the DCS World directory.

Yes I removed the concrete looking textures for the FARP etc for now which resided within that Bazar folder, there should only be a Mods folder in the package.

Quick revisit to this mod, I have verified that this is compatible with 2.5.6 and there are no issues. Also I have made some small adjustments to the terrain.cfg.lua and removed some portions of the package such as the adjusted tree textures (the stock ones work much better) the package is updated in first post.

Using 4xMSAA at 1920x1080? Grab nvidia Profile Inspector and put enable 4xSGSSAA and it will make the trees look alot better

This problem appears to be resolved in DCS 2.5.6 :thumbup:

As mentioned above not today https://forums.eagle.ru/announcement.php?f=105

Good news, 2.5.6.43872 launches just fine now, thank you for your assitance and patience BIGNEWY :thumbup:

dxdiag.txt added to post #9 .

Screenshots attached of Windows 10 version and installed updates. edit: added dxdiag.txt DxDiag.txt

Bumping, fingers crossed I don't have to face this problem again with coming update.

Standalone always and no logs are generated, not even any clues in Windows Event Viewer.

None, this is the first time in many years that I've ever seen this kind of problem with DCS - completely clean DCS and even cleared Saved Games folder and the same result.