Mustang

Thread bump, new version of nVidia Profile Inspector is out with more direct control of Rebar (options are inside the 'Common' section of the app) https://github.com/Orbmu2k/nvidiaProfileInspector/releases/tag/2.4.0.2

Is the MP scoreboard corrected in this patch or does it require more work?

Heya, this will work alongside the MSAA setting in game, recommendation is to match the SGSSAA with the MSAA setting in DCS so - 2xMSAA in DCS you use 2x Sparse Grid to match, it really does work well (P.S you can still use the ingame SSAA too but keep an eye on performance)

Try using Sparse Grid SSAA over the default SSAA in the nvidia control panel, you can access this via nvidia profile inspector - IMO this AA method looks and works alot better https://github.com/Orbmu2k/nvidiaProfileInspector/releases/download/2.3.0.13/nvidiaProfileInspector.zip

Stats all show 0

Also try using Reshade and the deband.fx shader, it does a real good job at alleviating this.

Update: just installed newer 522.30 and DCS works fine https://forums.guru3d.com/threads/nvidia-522-30-driver.445088/#post-6062489

Although this isn't benchmark related I can report that lots of people are purchasing them, the place I work at has many cards passing through to lucky recipients

Rgr FR4GGL3 saw your post over in the Guru3D forums - guess it's just a combo of hardware/OS/BIOS settings etc and I'm tripping up with this driver branch, I'll give it another go when another newer driver comes along.

522.25 was released today, installed and fired up DCS and was greeted with a crash during loading, reverted to previous driver and everything is fine again (GPU ASUS 3090, OS Win 10) # -------------- 20221012-172518 -------------- DCS/2.7.18.30765 (x86_64; Windows NT 10.0.19043) D:\Eagle Dynamics\DCS World OpenBeta\bin\dx11backend.dll # C0000005 ACCESS_VIOLATION at 723A4C24 00:00000000 SymInit: Symbol-SearchPath: '.;D:\Eagle Dynamics\DCS World OpenBeta;D:\Eagle Dynamics\DCS World OpenBeta\bin;C:\Windows;C:\Windows\system32;SRV*C:\websymbols*https://msdl.microsoft.com/download/symbols;', symOptions: 528, UserName: 'Mustang' OS-Version: 10.0.19043 () 0x100-0x1 0x0000000000014C24 (dx11backend): RenderAPI::DX11Renderer::initDevice + 0xB4 0x0000000000013F0E (dx11backend): RenderAPI::DX11Renderer::init + 0x34E 0x00000000000335FE (GraphicsVista): Graphics::Renderer::initialize + 0x4CE 0x0000000000178BE8 (Visualizer): smSceneManager::CreateSceneManager + 0x68 0x000000000084D14A (DCS): SW + 0x5236DA 0x000000000084B926 (DCS): SW + 0x521EB6 0x0000000001D4EDE6 (DCS): AmdPowerXpressRequestHighPerformance + 0xED5DE2 0x0000000000A7775E (DCS): SW + 0x74DCEE 0x0000000000017034 (KERNEL32): BaseThreadInitThunk + 0x14 0x00000000000526A1 (ntdll): RtlUserThreadStart + 0x21

If you are seeing over the top banding I'd suggest using ReShade de-banding shader, works a treat with DCS https://ibb.co/wrvSCzp

I've heard that this mod helps some way to make FPS a bit better on the carriers https://www.digitalcombatsimulator.com/en/files/3325364/

You have to create the autoexec.cfg yourself, just make a new text file and rename it to that filename then edit and enter the command line.

Nice video showing the AH-64 pit and the key

Updated https://drive.google.com/file/d/1WwNRVk2cfNsUgPTUHhzsY6kCu2J-hrFF/view?usp=sharing

Bump the Farclip in graphics.lua up to around 300000 from the default 150000 for your chosen visibility setting, that'll push the render distance out further.

SSAO enabled in options? If so disable and see if they go away.

oops dunno how I missed that, but be sure to check that you're applying this to DCS.exe and not DCS_updater.exe which the shortcut uses.

Try right clicking on your DCS shortcut icon on desktop and going to properties, under compatibility tick the Disable full-screen optimisations box.

If you have SSAO turned on it can cause this sometimes, look to see if you have it enabled or not.

This is a VERY nice 'mod' worthy of a title of an official module, only found out about this yesterday and I'm glad I did!

PM sent.

Of course you can, share it far and wide

Try this out guys - extract the Config and MissionEditor folders to root install of DCS and allow merge/overwrite of files https://drive.google.com/file/d/17BpEMbAXc30rSFOXN3JMkvju7sYDrFHZ/view?usp=sharing I have created two new visibility settings within the options page of DCS - 'Ultimate' (x2 the draw distance of Extreme) and 'Insane' (4x the draw distance of Extreme) The problem with object 'pop-in' was solved by increasing the Instancer buffer values in terrainoptions41.lua.