RoboHackfeld

So you guys would say, spotting a plane from up to 5nm is realistic, everything above that should not be realistic? I`m looking for information like that now for quiet a few years and never found a specific point where someone says, "you can not spot a plane that is above XX distance". Would be nice to get some information from real fighter pilots. Beside the tweaking for better performance in relation to good graphics, the spotting of other fighters is my major issue since I am in VR. And what I found out so far: No AA is better than MSAA is better than DLSS. But I think in my last test ist was like: No AA ~ 13nm (A10CII) MSAA 4x ~ 11nm (A10CII) DLSS ~ 8nm (A10CII) All tested in VD - high; PD 1.2 - with my Quest 2. Since I moved from VD to Meta Link because of performance I have to update this test. Maybe will do it today. The Spotting Dots Feature, I really dont like. Its just not realistic and looks awfull.

Here is the module: Some Screenshots from my 2D Setup. Those are the units that cause the problem at low approach but only when there are 4 to 5 of them on fire. It happens not alway but when it happens its arround T700-T850

At first, thanks for this very on point analysis and for providing those charts. When you say the times are okay for the first Seconds, could it be, that spooling time (strg + y) could mess up those frame times? Sorry I did not mention this earlier because I did not think this could be a problem but when you say it is okay at the beginning it is always when I run the mission, I turn off symbols, set my cockpit position activate auto pilot and than hit several times strg+Y so I can skip time until action on the ground begins, where my problems start. The middle of the tracks, where the heavy spikes appear, yes thats what I am talking about and I already tried to lower settings, I lowered everything to potato really the lowest settings of the low but in this situation I guess my CPU can just not handle all the AI Units, what they are doing and the smoke effects. I will prepare an empty mission and will have a look at those log files. Thanks Robo

stats_20250412_104858.csv Here is the CSV without QVFR Turbo Mode. Performance wise didnt change much and I think those stats are quite similar? Butmaybe now there is more load on the gpu or am I wrong? Edit: QVFR: Turbo Mode = 0 - No success Disabled OXRTK - No Success Exited some programs like Steam, Tobii experience. - No success; maybe I will try more of that and disable programms like Afterburner, NZXT Cam, HWInfo etc. Here is what I described very early in this thread, that the frametime rises frequently and than - boom- back down.. rise, rise , rise ,rise - boom down. And thats why I think there is something going on with the rendering/animation of the smoke. In that video I have active pause mode turned ON and I am looking directly at that problematic situation while the smoke is moving. So I think there are different stages of the smoke-rendering-animation-thingy where the load raises and than when the smoke animation resets itseve (visually not noticable and just my theory) the frametime goes down. Dont know what happening there in the background. Could it not just be, that my CPU is just too week in this particular situation? Idk if you know this mission. It comes with the A10 Modul. Syria, Armored Convoy. For my benchmarking, I star tthe mission activate Autopilot and fly in circles untill T=500 (so the action begins) than I fly to the convoy. The first units apearing, some artillery, some trucks, when they are shot down and burning and I look into their direction I got the problem. If I fly past them there are alot more units and also more units burning I dont have this problem. My Frametime raises to like 10 but not more and my frames stay stable. I think this one is a combination of my "weak" cpu and the mission.

Thanks @sleighzy and thanks @Qcumber for your help. Yes I have QVFR installed and only the size of the focus area adjusted in the config file. So I will run the tests again without the Turbo Mode of QVFR. I never noticed I have enabled bloom effects. I will disable that too. But than I can not record the statistics right? dcs.log Logfile is attached.

Could you show me how it looks at your side? Do you have a log like that? Just to understand that correctly, If there is 2025-04-11 15:45:27 +0200, 72,0.13823,283,163,5319,35 Time: 2025-04-11 15:45:27 +0200 FPS: 72 appCPU: 0.13823 - 13,823ms renderCPU: 283 - 283us = 0,283ms renderGPU: 163 - 163us = 0,163ms Vram: 5319 - 5.316GB Vram%: 35 - 35% Is that correct? So the two render points are too high? AppCPU is the frametime I guess? Yes this one is arround 1-6ms if I am up in the air unless there is a lot going on and I am close to the ground. Than it raises and I think at 14 and above or something like that the frames go below 72fps. What do you think about the values at the beginning of my CSV Files? There it looks better and of course that is always the point where I am up in the air, gpu bound with 72fps and theoretical fps of about 100+. For example: 2025-04-11 15:42:09 +0200,72.0,8100,186,17,6519,43 appCPU: 0.8100 - 8,1ms renderCPU: 186 - 186us = 0,186ms renderGPU: 17 - 17us = 0,017ms Vram: 6519 - 6.519GB Vram%: 43 - 43%

Turbo mode was Off yes no mods except of the Empty Hangar Mod. Should I activate/oben OXR Toolkit befor starting the game? I run 64GB of DDR 4 3200 dont know if that could be something?

@sleighzy I think, it just means that the bitrate is locked to that rate. It is not variable. So here the csv files. I made one with and one without HAGs. Turning HAGS Off just made it worse (dropped under 50) but could also be a different situation where maybe the situation on the ground was just a little differen. stats_20250411_154112 NO HAGS Begin Row 197.csvstats_20250411_152947 HAGS Begin Row 216.csv

Okidoki, have a meeting this morning after that I will do some testing. Thanks!

You are talking about the overlay which shows FPS, CPU and GPU [ms] in yellow? But how to export that?

I will provide the GPU Load as well but I noticed that my gpu is just bored in those situations. But can not tell you the exact Load of the gpu. And yeah I also think my cpu is overloaded. Its just those situation where the CPU Load (AI Units all over the place, moving, shooting, exploding, triggers, SAMS, Radar......) just moves past the GPU Load so I am cpu bound and my CPU just is not able to push more. If I turn my head away or just move away from those situations everything is smooth and I am GPU Bound with 72fps and theoretical Frames over 100 up to 140. My Router, I think it can not provide more than 866. I also tried 150 Bitrate with another codec but that also did not help. The router is directly next to me, just one arm lenth. Dew to the fact, I have the same problem with Oculus Link via cable I dont think it is bitrate related. It just tells me to turn OFF GameBar which I already have and HAGS which is also worth a try. Will try that one next.

@Qcumber here are the screenshots/photos. I think it all looks pretty good and like normal behaviour. I just ran also some more tests: Test 1: Caucasus, Airfield full of static Smoke Result: No problem. Frametime raised to 10 maybe 11 but was constant and smooth. Test 2: Same Airfield, Static units (10 vs 10) shooting at each other. Waited till some Tanks begin to smoke Result: No problem Test 3: Syria, two groups of Tanks (10 vs10) driving at each other and when in range firing at each other. Waited till some Tanks begin to smoke Result: No Problem Test 4: Syria, two groups of Tanks (25 vs 25) driving at each other and when in range firing at each other. Result: Almost completely stable, at the first run I had the same problem with my tests yesterday (Armored Convoy Mission) but the two tests after I could not reproduce that. Test 5: Armored Convoy Mission. Resut: same result like yesterday. Now I really dont think it is the smoke. I think this mission is just very heavy with lots of different AI Units, moving, shooting, exploding, smoke, me and my wingman. I think this is just too much for my 5800x3D Maybe if I find the time I will run a dedicated Server on my rig to see if that could take some Load from my CPU.

Thanks for ur reply, I will provide those screenshots tomorrow and will check the CPU load. I also tried the other codecs and lower bitrates without any success. And like written above, same Problem with Meta-Link. Now after 2h of testing its bedtime.

Dear Pilots, now I got a 5080 and I am pretty happy with this card until it comes to burning units or smoke in general. For benchmarkI use the A10 CII Mission (Armored Convoy). It runs all the way smooth until a couple of Units (4 or more) begin to burn and the smoke kicks in. Than if I look into the direction of that units my framerate drops constantly from 72 to 68 to 62 to 58 to 55 up again to 72 to 67 to 60 to 56 to 72 and so on. My Frametime jumps constantly into the other direction from like 8 to 10 to 12 to 15 to 18 to 8 to 11 to 13 to 16 and so on. I think that is because of my CPU is limiting but is there any possibility to make smoke hit less performance? I tried every setting, I even lowered every setting to the absolut minimum and nothing helped. My Latency in VD is always between 40 and 60 and Networking around 8 - 12 ms but the same happens if I use the link cable and Meta-Link In my video if you look at the FPS Counter in the Top. Sorry for the bad quality. System: Quest 2 with Virtual Desktop (5G) (Ultra) H.264+ VDXR 400bit (Same Problem with Quest Link) 7 5800x3D NVidia 5080 64 GB (4*16GB) 3200MHz M2 SSD Swapped the DLSS File to DLSS 4, Preset K via NVPI Below are my DCS Settings And my Nvidia Settings via NVPI Best regards and thanks in advance Robo

Okay coming back to this topic I also can confirm now, that ASW just does not work with AMD cards. I got a new 5080 installed drivers and did not change any other setting. ASW kicks in and works just out of the box.

We`ll i've done it like written above and it worked. I see the difference in visuals but performance is worse than MSAA 4x. I did not expect that. null

Well just to clarify, I dont need DLSS Swapper anymore? I just need the latest Nvidia Driver, the NVPI and select Preset K under DLSS - Forced Preset Letter? And I have to do this before I start the game right? Can not change it on the fly? No DLL change in DCS directory necessary? Ingame I choose DLSS - Quality. No DLAA Is there any message or something so I can be sure DLSS 4 is running correctly? - okay I found this DLSSTweaks Overlay aaand last but not least: NVPI has to be set to the right profile with the right exe (DCS. MT) and it has to be running when I launch DCS?

I will check OC maybe next weekend. Than I have a lot of time to make some tests. Yeah I got the gigabyte card for 1400€ which is just a bit over the MSRP Gigabyte announced back in January, so its okay for me. Ii I can get another Card like an ASUS Prime for a good price within the next 27 days I think I will replace it but if not I ll keep it. @Qcumber How did you manage to get 3320MHz with only a 447MHZ OC on a 5080 FE? Isnt the the Base clock at 2640MHz? My Gigabyte runs out of the box with 2850 MHz and 1875MHz memory clock in Steel Nomad which I am pretty fine with.

Still not sure if I send that card back to the shop but like I said, it seems to be a Gigabyte Feature which should not affect performance. Gigabytes statement to that was "Its not a problem and It wont be in the future." Wow, thats alot for the FE. Not bad! Your doing the OC with Afterburner?

Got the Gigabyte 5080 AERO which first was some kind of a downer. To explain that: I really wanted to have that card, because every test is positive about that card but what no one tells us is, that there is some kind of magnetical FanStop which makes some noises when the Fans switch to FanStop, not when the computer is shutting down, only when it is active software forced FanStop because Temperature is under 50°C or what ever you set up. Since I know its not a problem, first I thought it is related to bad or poor bearings, yeah it is really not a bug its a feature and I dont know why the hell they doing something like that, just let the fans run out on their own..... And it is not only related to this card, if you search for Gigabyte GPU FanStop noise it seems that all Gigabyte Cards have this "Feature" doesnt matter if Aero, Aorus, 5080, 5090, 5070 ti, .... even 10xx Cards from the past have this. But yeah it only happens after I quit a game. If I am at the desktop the temperatures never went up so far that the fans start spinning. A lot OT but maybe important for some other pilots trying to get a Gigabyte Card. Havent tried OC yet, only and thats what I do with every card, I raised the power target.

Well here just my two cents to the 5080 performance compared to my old AMD 6900XT. Short? Its massive Long? I havent tested much so far (No DLSS 4 or something) but just out of the Box I jumped at my Benchmark Scene which is A10 II over Center of Aleppo in Syria and my FPS jumped from 50 (GPU Bound) up to 90 which is my max Hz, so there should be still Headroom and I am pretty sure the bottleneck will most likely the 5800x3d and not the GPU. On my Carrier Test with a lot of static object, like Planes and vehicles, nothing changed so far. When I look to the "Mother" its 55fps (cpu bound) like before, but thats like I said a problem of my cpu. If I am moving to the CATs or just looking up front its stable 90 fps. I am pretty amazed and will come back here when I found some time to set it all up with the DLSS 4 workarround and stuff.

Im running with VD because I can just start the Headset, start VD and I am ready to go. No cable, no Oculus Tray tool and no Meta Link that sometimes just does not work at the first start up. The downside is, I am fighting with some lagspikes, I dont have with Link, but they appear once per 10 Minutes or so and only in crowded areas.

Dear Pilots, I spent almost the whole saturday inside the mission editor to figure out how it works. It lead me to a small mission with just a couple of trigger options but a lot of units moving towards a specific point (Palmyra in Syria) where the other faction has a lot of units defending that town. (All together like 100-120 units, tanks, bmps, AAA, SAM, Arti...) When I launched the mission the problem was that when I get closer to Palmyra and look in that direction even if I am still 20nm out of the city, my FPS went down from like 120 to 60 fps with spikes to low fiftys/high fortys. (I fly in VR) So I thought about, what is the problem. Would it also be a problem if my Plane and me where spawned like 200nm away from Palmyra? Does it matter if the vehicles move or stand stil, does every waypoint of an AI Vehicle decrease performance... Is it them shooting at each other or is it just every single thing they are doing? What causes that heavy load, I think on my CPU? Would it also be a problem if my Plane and me where spawned like 200nm away from Palmyra? So I was just reading a little bit on reddit and here in the ED Forum when I went to bed and found some threads about using the DCS Dedicated Server for heavy mission. So the threads where from the ST era, this should not be a problem today or am I wrong? I mean the explanation was that the performance-drops where caused by the poor or even no multi core optimization of DCS. With the dedicated server they where able to push all the action of the AI units to other cores while the game itself runs on one of the other cores. So my question is, should I give it a try or is it just not neccessary today with the multi core optimazion of DCS and I can safe that Space from my SSDs. Best regards Robo

On your side it is. But what we see in the Youtube Video is not, imo.

There is no SS active (PD 1.0 and Resolution 100%), the settings are not maxed out (e.g. Lod 0.6, Visible Range medium) and the 9070 XT is not able to deliver stable 72 fps. This is not acceptable imo.