[zcd]dARKtROOPER

For me it pushes the FPS, limits flickering shadows, does AA and looks better overall in the 8KX then without DLSS. It is quite the opposite for me in VR.

I am using a canted display VR HMD (8kX) and in the night I get strange behavior for lighting (and shadows)- like what has been posted here and there in the forum, but none seemed to fit exactly. Depending on height these rays seem to grow and shrink and grow and shrink. I added a screenshot which shows what I mean, except for the dynamic changes to it. Also, the shadows re a bit strange/doubled as some other light, cloud, smoke issues (2D/3D, doubled and so on- but that’s another issue but it could be to the same cause, so I thought I mention it).

There is always vendor specific tuning in AAA Games for many reasons - I don’t see any point in not using features provided if they boost Quality and FPS and are free to use, as the NVidia and AMD features do. Also, DLSS is quite adapted so it’s not a niche extension anymore. I know – it’s more of a philosophical debate then a technical one to many, just like many get scared if people ask for VR support. If it makes better quality and fps and is not too much hassle to implement, well then do it – if its more cores, more VRAM or precision with 64bit or proven extension. Besides I doubt that our debate here does anything – engineers will evaluate do ability, cost and effect and that’s it.

DLSS is awesome, I have used it in a lot of games now. Especially in VR it’s amazing, you get some AA/AF like effects, lots of flickering stuff stops and, in most cases, it sums up to just look a lot better and it increases FPS, in some cases dramatically - not using it is pure nonsense! So, if we get the optimized multicore, Vulcan implementation (most of my 16/32 cores a bored in DCS) and they use the DLSS Support of Vulcan down that road, that will truly boost performance and most likely open options for optimizing graphics fruther and still have smooth FPS on all maps and altitudes.

Thanks for the feedback! since its working, I havent bothered cleaning up further. I dont use much mods, just lately started adding a few aircraft - but removed all again except the A-4E-C, Hercules and Military Aircraft mod.

Is it "normal" that there are still errors in the dcs.log? seems a a lot for no reasons I can think of. dcs.log

SOLVED - After everything checked out as far as I could tell, I looked through more of the logs and I notived that in the none crash logs there where entries to missing files for the mods of the Eurofighter and JAS 39 - no Idea why. Delteted those two mods and the A 10C II worked again.

I can run all modules, but the A10C II wont to anything or better crashes the game as soon as the loading would be finished. The logs show this: # -------------- 20220115-233210 -------------- DCS/2.7.9.18080 (x86_64; Windows NT 10.0.22000) L:\SteamLibrary\steamapps\common\DCSWorld\bin\GraphicsVista.dll # C0000005 ACCESS_VIOLATION at 8A173CCB 00:00000000 SymInit: Symbol-SearchPath: '.;L:\SteamLibrary\steamapps\common\DCSWorld;L:\SteamLibrary\steamapps\common\DCSWorld\bin;C:\Windows;C:\Windows\system32;SRV*C:\websymbols*https://msdl.microsoft.com/download/symbols;', symOptions: 528, UserName: 'marcr' OS-Version: 10.0.22000 () 0x100-0x1 0x0000000000023CCB (GraphicsVista): Graphics::ModelPtr::release + 0x1B 0x000000000019A9E0 (CockpitBase): cockpit::ccIndicationRenderParser::change_brightness + 0xEC0 0x0000000000359A18 (CockpitBase): cockpit::VR_capture_holder::update_capture + 0x22E28 0x000000000001BEA0 (ucrtbase): _execute_onexit_table + 0x170 0x000000000001BDB7 (ucrtbase): _execute_onexit_table + 0x87 0x000000000001BD6D (ucrtbase): _execute_onexit_table + 0x3D 0x0000000000345362 (CockpitBase): cockpit::VR_capture_holder::update_capture + 0xE772 0x0000000000345488 (CockpitBase): cockpit::VR_capture_holder::update_capture + 0xE898 0x000000000003FC37 (ntdll): RtlActivateActivationContextUnsafeFast + 0x127 0x00000000000541B0 (ntdll): LdrShutdownProcess + 0x170 0x000000000005401D (ntdll): RtlExitUserProcess + 0xAD 0x000000000001C66B (KERNEL32): ExitProcess + 0xB 0x0000000000019FEC (ucrtbase): exit + 0xAC 0x000000000001A0C1 (ucrtbase): exit + 0x181 0x0000000000A31100 (DCS): SW + 0x72FF80 0x00000000000154E0 (KERNEL32): BaseThreadInitThunk + 0x10 0x000000000000485B (ntdll): RtlUserThreadStart + 0x2B DxDiag.txt

Since Vulkan is the way, there is hope Anybody know if this is a general support? The Topic is linux specific, but if it works on that driver, why should it not on windows: Vulkan Now Supports NVIDIA DLSS in Proton on Linux - The Khronos Group Inc Vulkan Driver Support | NVIDIA Developer

ok, strange..., did you try discord ? they where quit helpful to me, maybe they have some better advise then my greenhorn tipps

I got it working thx alot to Special K @ the DCS Discord - in short: 1) Check that you can reach all ports you need: only focus on 10308 and 8088 - from externaly in TCP and UDP (UDP not checkable) - check that your provider is giving you a public IP, not Carrier-grade NAT' ing you 2) Ensure you are using the same client and server versions and branch - this got me since i did make a mistake in the iterations and copied the none beta over to the server at some point - I only play beta at the moment which will NOT show the none Beta. So easiest way: ON the server it will show "OpenBeta" in the folder name, the icon and start menu - ensure that is the case if you are running the latest version of DCS. ( Afte lots of double checks and WireShark where I saw that Client and Server did a short communication on 10308 UDP, i figured for some reason they dont understand each other - in my case diffrent Client and Server Versions of the Game) As soon as I got that - it showed up and was working. If stil some trouble you might check on your "server" if it is listening to the ports for 10308 for TCP and UDP, and also 8088 TCP with netstat -ano | Select-String "4760" with 4760 is the current PID when running Check that your firewall on the Router AND the Server OS are letting the prots through - I added up this skript - not all is needed so just use the one you are interested in - works for the Windows Firewall only. # DCS TCP inbound rules New-NetFirewallRule -DisplayName "DCS TCP Inbound" -Direction Inbound -LocalPort 10308 -Protocol TCP -Action Allow New-NetFirewallRule -DisplayName "DCS TCP Inbound" -Direction Inbound -LocalPort 10309 -Protocol TCP -Action Allow # DCS UDP inbound rules New-NetFirewallRule -DisplayName "DCS UDP Inbound" -Direction Inbound -LocalPort 10308 -Protocol UDP -Action Allow New-NetFirewallRule -DisplayName "DCS UDP Inbound" -Direction Inbound -LocalPort 10309 -Protocol UDP -Action Allow # DCS WebGUI TCP inbound rules New-NetFirewallRule -DisplayName "DCS WebGUI TCP Inbound" -Direction Inbound -LocalPort 8088 -Protocol TCP -Action Allow # TacView Realtime Telemetry New-NetFirewallRule -DisplayName "TacView Realtime Telemetry Inbound" -Direction Inbound -LocalPort 42674 -Protocol TCP -Action Allow # TacView Remote Control New-NetFirewallRule -DisplayName "TacView Remote Control Inbound" -Direction Inbound -LocalPort 42675 -Protocol TCP -Action Allow # DCS SRS TCP1 New-NetFirewallRule -DisplayName "DCS SRS TCP1" -Direction Inbound -LocalPort 5002 -Protocol TCP -Action Allow # DCS SRS TCP2 New-NetFirewallRule -DisplayName "DCS SRS TCP2" -Direction Inbound -LocalPort 5003 -Protocol TCP -Action Allow # DCS SRS UDP1 New-NetFirewallRule -DisplayName "DCS SRS TCP1" -Direction Inbound -LocalPort 5002 -Protocol UDP -Action Allow # DCS SRS UDP2 New-NetFirewallRule -DisplayName "DCS SRS TCP2" -Direction Inbound -LocalPort 5003 -Protocol UDP -Action Allow So thanks all for the help !! - as often a few things and a human mistake made the trouble... (Would be cool if the Server Version was shown on the WebGUI )

That is interessting.... I did not notice that thx for that hint - one screenshot is from 2 days ago, the other from today, since i did not make a screen shot of that before - I did run the update on the server also today but it did nothing - will check to see in the logs.

Hi all, I have set up a dedicated server @ Home on a elderly Xeon PC and Win Server 2022. So what is working? 1) See the Server on the machine as up and running... 2) See the Server as up and running on the profile page on dcs site 3) See the Server on DCS Server Tracker: Servers (glowie.xyz) 4) Checked the ports 10308, 8088 on can you see me - seems to work (nothing on 10309) 5) Start/Stop the server from the DCS Website works I also added firewall rules to the local server and of course to the router so that canyouseeme.org works via those ports (courtesy of How to Host a DCS Server - Full Step-by-step Guide - ServerAcademy.com) # DCS TCP inbound rules New-NetFirewallRule -DisplayName "DCS TCP Inbound" -Direction Inbound -LocalPort 10308 -Protocol TCP -Action Allow New-NetFirewallRule -DisplayName "DCS TCP Inbound" -Direction Inbound -LocalPort 10309 -Protocol TCP -Action Allow # DCS UDP inbound rules New-NetFirewallRule -DisplayName "DCS UDP Inbound" -Direction Inbound -LocalPort 10308 -Protocol UDP -Action Allow New-NetFirewallRule -DisplayName "DCS UDP Inbound" -Direction Inbound -LocalPort 10309 -Protocol UDP -Action Allow # DCS WebGUI TCP inbound rules New-NetFirewallRule -DisplayName "DCS WebGUI TCP Inbound" -Direction Inbound -LocalPort 8088 -Protocol TCP -Action Allow # TacView Realtime Telemetry New-NetFirewallRule -DisplayName "TacView Realtime Telemetry Inbound" -Direction Inbound -LocalPort 42674 -Protocol TCP -Action Allow # TacView Remote Control New-NetFirewallRule -DisplayName "TacView Remote Control Inbound" -Direction Inbound -LocalPort 42675 -Protocol TCP -Action Allow # DCS SRS TCP1 New-NetFirewallRule -DisplayName "DCS SRS TCP1" -Direction Inbound -LocalPort 5002 -Protocol TCP -Action Allow # DCS SRS TCP2 New-NetFirewallRule -DisplayName "DCS SRS TCP2" -Direction Inbound -LocalPort 5003 -Protocol TCP -Action Allow Trying to connect via the public ip i get: Connecting via local network (192.168 ans so on) i get server offline - also for other random ranges of IP's - are there IP like mine with the 91 starting banned or not allowed?? Trying some random IPs delivers the same results (other 91's) so it looks more like its checking the IP Adresse in terms of text rather than actually trying to get a sever behind that adress. And in DCS the server is not shown. Any hints to my mistakes or tipps for advanced troubleshooting are higly welcome!! ThX! Only thing I noticed, after first login, it has never asked me again for a login, when starting the server, but since its synced to the profile correctly i guess that is working. And any tipps on the hardware: its a 4 Core Xeon E31220 @ 3,1Ghz. Currently only 10GB - I would upgrade the ram to 16 or 32, as soon as i know its working... not the best anymore, but its a "fair" machine, doing nothing else other than some backups once a week.

Just tested it with the default settings in the FSR mods cfg file with DCS - does not provide a high difference - at first glance it might reduce about 0.5ms on the GPU frame times which in both cases hangs around 69% utilisation and gets to about 50 FPS once moving on the base /air (Persion Gulf, Cold Start, F 18, 8KX 100% Resolution). On the other hand it looks like the cpu is just a little bit slower with FSR and actually seems to limit the FPS since its frame times crawl up a tiny bit, which in the none FSR are normally just below the GPU. In both cases its just one thread on the CPU spiking and maybe 4 in total. The GPU also has head room, so not sure what is slowing down the frame times - but this was just a fast unscientific test (clouds are different etc.). The image did become a bit more uneasy, there are "circular moir effects" on the concret just in front of the aircraft when starting it up with FSR and the image seems more unstable/busy, without FSR it is not as much noisy and it is easier on the eye. Also the "Circular" FSR Focus area is noticable or better the outside which is lower and not upscaled in resolution on the 8KX with default values, but would be barable if it would pimp the frame times more. So more tuning i guess to get a benefit, but since it will not do AA with FSR... not sure how much effort that is worth it. Also the single core spikes start to be a problem in general to the higher FPS..

I have pretty much the same to say, it would be a great opertunity to bump up speed with existing hardware, actually use the potential of the GPU (its not always in the 90% utilisation) and the reconing of DCS - it could also implement FSR since they seem to coexist just fine. I will try and see if this works, since there are benchmarks out there of people using a 30xx with dlss and fsr in comparison, maybe it will work Mod bringt AMDs Fidelity FX Super Resolution für SteamVR (mixed.de) or directly GitHub - fholger/openvr_fsr: Add FidelityFX SuperResolution to SteamVR games but its not on par with the DLSS solution in speed and quality.