RoboHackfeld

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.

I really think I had solved the issue in the past with an old driver but could not remember which driver it was. Thank you I will definately try that. And with the 4070 ti the ASW does work? Maybe you can try it.

So just tu clarify, I am still figuring out how everything is connected. If I have to maintain 80fps I need to get a frametime lower than 1000/80=12.5ms? If I need to get 90 fps this one is like 1000/90=11.11ms. Correct? Right now I am playing with 80hz and SSW(40fps) so like 1000/40=25ms should be enough to get stable 40fps. The thing is, I am always switching between SSW and NonSSW to see what FPS I get and if it is stable above my 40fps for SSW but if I know my frametime just needs to stay below 25ms, better 20ms I could easily work with that than always switching between SSW and nonSSW.

Dont know exactly if it helps too free up some VRam but reducing the resolution for your Desktop DCS Window seems to be worth a try. null

U can use it to reduce your FoV to save some performance.

Good to know, the 5080 gives us nearly what we've expected. I am stil waiting for a good offer for a 5080 but it will be definately my next GPU. It would be nice, if you could share some more Settings you are using. PD in Meta Link, PD, Shadows and AA in DCS, DLSS (4.0?), your QVF settings for Oculus [Oculus] peripheral_multiplier=0.2 focus_multiplier=1.0 horizontal_focus_section=0.55 vertical_focus_section=0.55 and maybe how you setup your Oculus Tray Tool/ Debug Tool Thanks in advance and I wish you a lot of fun with your new GPU. BG Robin

I will check that out. What PD do you have for the peripheral area?

Ah okay thanks, I think Ive noticed that slider it was like bright blue on the right and dark, transparent blue on the right. Yeah I pumped it within DCS to 1.4 and left the QVF PD at 1.1 for the focus Area. I will play with those settings around and will test with stuttering. The log File will be uploaded tonight, when Im back home.

Well yesterday evening I've tried Meta Link with TurboMode off (QVF and OXTK) and ASW still was not visibly active. After that I started VD and wanted to see if SSW does work. In the past I always was very unhappy with VD because it does not have an Option to crop the FOV to save some performance and I always had to reduce Image Quality for a similar performance. About SSW: Wow that <profanity> just works. There are som Micro Stutters in heavy areas like big Citys (A10C-II Free Flight Syria) where I guess I have to play around a little bit with the VD Settings like Codec or Bitrate (Still havent found out where to setup the bitrate. Any Ideas?) But in general, 90hz Frq. and 45hz. SSW with MSAA 4x, and QVF, wich allows me to pump up the PD a little more, results in an absolut nice and smooth gameplay, except those micro stutters. I guess thats the way I have to go further. Maybe some of you guys have an Idea for the Micro Stutters? I guess its just the heavy areas and fast headmovement that causes that because the rendering does not catch up with the movement but maybe there are some tweak recommendations from you VD-Veterans.

Thank you very much. This helps me alot! =)))

Dear Pilots and Operators, how do I get the Deck crew to send me to a CAT of my choice? For example: I have a mission, where I spawn into a hot F14 while there are two TomCats launching from CAT 1 and 3. When I take over my TomCat the Deck Crew always sends me to CAT 1 where the other TomCat is preparing to launch while CAT 2 is empty. I've read something about the parking slot affecting the CAT to launch but there is no option in the Editor wqhere I can determine the parking slot for a hot (Engines On) Jet or am I missing something? Regards Robo

Okay could be possible, maybe there is something. But when you are using VD you are not using ASW I guess, since it is only compatible with Meta Link? While I am at work right now I can not try anything but could it be possible, I am using the wrong runtime? I think its Meta Quest Link Runtime in the Meta Link software , not really sure i have to check it later, but could it be possible that this one conflicts with Open XR and could prevent ASW from being visible?

I just unmarket the Box in the DCS Launcher to not use Quad-Views. Will try that later.

I tried all three Options: Both - OXR Toolkit and QVF - disabled Just QVF disabled Just OXR Toolkit disabled What I did not try, running QVF and turning of Turbo Mode in the QVF settings.cfg.

Well that also did not worked.

Would be nice if you could confirm that. If you have the same problem and maybe more ppl can confirm that its maybe not just an AMD issue. I know in the past it worked pretty good for me, some artifacts but it was smooth all over the place. Maybe Ive found something on reddit regarding problems with ASW in combonation with Windows 11 and maybe latest Win 10? Will check that out tomorrow and let u know.

Yeah and exactly that is my problem. If I switch between 45 capped no ASW and 45 capped ASW enabled there is no difference. The same jittering you descriped you have with ASW disabled but I have it with both modes. The thing is, if I turn on the ASW overlay in DCS via ODT, it says that it works and the ASW Frame counter rises rapidly. I really have no clue. Must be something with the AMD Driver?

Dear Pilots, I am running DCS Standalone on my PC (5800x3D, 6900XT, 64GB, latest Win11, Quest 2 via Cable) with VR and it works just fine offline and on small missions. I can maintain 72fps with QuadViewsForfeated. I also have the OpenXR Toolkit installed. If I join an online server or start my mission on a loaded Carrier the frames drops to 50-60 and, yeah... Thats not fun anymore The thing is I want to use ASW and I know it worked very well a couple of years ago. But I dont know what happened, if I turn on ASW via Debug Tool or OTT, (Strg Num2/3) it just dropps my FPS to half the Native Frequenzy (72/36; 80/40, 90/45). There is obviousely no reprojection, no matter I turn on the "Force 45fps, ASW disabled" or "Force 45, ASW enabled" mode. Is there anything I am missing in the Debugtool, Meta App, TrayTool or Radeon Drivers I am missing to turn on, so ASW is able to kick in? Maybe some experimental features? I run the 72hz mode with the slider to max (all the way to the right, 1.5, 5408*2736). I've found this on the internet, but I dont know where to set up the HMD Priority. https://communityforums.atmeta.com/t5/Unreal-Development/ASW-doesn-t-work-even-when-enabled/td-p/981940

Now I think I've found a compromise between Quest Link and Quad-Views-Foveated, @sleighzy mentioned earlier. I get a stable 72fps and deal with it until I get a 5080 or something like that next year.

Yeah I've already tried that but it seems, it only puts black bars on the edges and the pixels behind are still rendered because it does not gove a performance boost even on 50%.