Mustang

You have to create the file yourself within Saved Games\DCS.openbeta\Config and then enter the command and save.

The pink ones are specular maps, don't touch those but the others should be editable.

DCS World OpenBeta\Mods\terrains\Caucasus\Models\Industrial\Industrial.texture.zip all the textures for electricity pylons are the ones that start with "vyshka" within that zip.

https://forums.eagle.ru/showthread.php?t=266136

Probably been suggested already but have you tried pressing Left Alt + Enter while playing?

I use this on the 104th server everytime I fly, do not run any missions beforehand or anything like that, just start DCS and immediately join the server and it should work just fine.

nvidia 445.75 driver causes this, roll back to earlier 442.74 or earlier and the problem will be solved. edit: this is affecting other titles as well https://forums.guru3d.com/threads/445-78-hotfix-gpu-randomly-stuck-at-low-core-clock-while-gaming.431594/

I just ignore the ping I see in the lobby if it's bad and connect directly via IP.

Op Desert Eagle V2 trackfile from server side (from same session as USMC_Trev posted above) https://drive.google.com/open?id=183akjvhZMV25nmI-fqoc1OYdSJi7akc7

Remember in the old days when ED devs would host a large MP session to expose bugs? Why not do this again?

The 104th server was hosting an event yesterday that required a registration and password, today it is back on public server rotation and is open to all.

You're on DCS stable 2.5.5 maybe? If so that could be the reason since 104th is currently on latest 2.5.6 OB and due to the changes in netcode/version you won't see the server.

Yes that should be how it works, your aircraft shadow and the ones from other clients/AI etc should be visible, strange maybe you could post a screenshot of your settings?

Take the moon out of the mission and watch those dots disappear, this has been a bug for quite some time.

This does exactly that.

I have altered the filename of the package now - sorry this is a simple on or off for shadows, I don't believe it's possible to selectively deactivate shadows for just the trees.

Yes that is the correct package.

One other point to raise is that this mod also affects the 'default' terrain shadows setting as even that renders flat shadows out to a certain distance so even with the 'default' setting there is a benefit to be had.

That is the aim of this mod, yes.

Recently produced video showing what the mod does

https://drive.google.com/file/d/1iHGdH4-G2H8RFnkWIkxwOpAkvocV0KT4/view?usp=sharing This mod deactivates the flat shadows of practically all scenery objects (notably trees/forests and buildings) within DCS World, only leaving shadows for own aircraft and surrounding objects such as ground units and other aircraft. The main benefit to be gained from this is to retain the cockpit shadows while turning off nearly all external shadow sources, this mod is especially useful for VR users who are familiar with having to turn pit shadows off. To gain the most out of this mod the user should select Terrain Object Shadows as Flat, the other shadow setting in the DCS options can be set to what ever the user desires. Also included in this package is a tweaked NVG shader for clearer cockpit reading, a modified overcast shader (adjusted luminance levels) and a very popular modification for smoke columns. To use this mod simply extract the 'Bazar' folder to the root directory of DCS World and allow overwrite of files, alternatively you can use this mod with any manager you want.

I choose to cap at 60 because my screen is 60hz and I don't want it to surpass that, which is what happens with Fast Sync enabled - also I have normal vsync disabled in DCS options so it doesn't cancel out Fast Sync being enforced by the driver.

See attached.

I use Fast Sync and 60 FPS cap on the sliderbar within the NV Control Panel and disable VSYNC in DCS options.

There is a problem with the 445.75 driver that randomly drops GPU clock speeds while flying resulting in these unexplained framerate drops, there has since been a hot fix driver out that supposedly corrects this (cannot verify since I'm still on 443.59) https://forums.guru3d.com/threads/geforce-hotfix-driver-version-445-78.431342/