Rmnsvn

When I run DCS in VR in multithreading with reprojection disabled CPU frame time stays close to the refresh rate (around 16ms) no matter what I do (e.g. in the main menu). The moment I switch on reprojection CPU times go to expected 1-2 ms in the main menu. Is this intended behavior? It doesn't happen in single threaded version (CPU time always as expected no matter reprojection mode). 12700kf, 3080, reverb g2. The issue doesn't change with any other settings.

I’ve been having stutters basically since switching to VR. Sometimes it would feel almost good, sometimes not. After fiddling around with settings I’ve come up with a setup that would give me consistent 11-12 ms per frame both GPU and CPU time which seemed like a sweet spot for me. I changed G2 to 60 Hz (flickering doesn’t seem to affect me much). The only remaining problem was dropped frames. The issue has become more pronounced recently so I decided to dig internet a bit more and found 3 solutions which completely eliminated dropped frames and keep perf overlay of OXR green as dollar. The first 2 seem to be the most useful. Give them a try and see if it helps your problems if you have any. I’m sure the things here were already discussed on the forum but I decided to share what helped me make my game playable again. I run OXR without any shaders or toolkit with 10 gb 3080/12700kf combo on Win 11 1. Go to computer management - performance - data collectors set - event trace sessions. Find Holographic shell and stop it. If it helps, do it every time you start VR. I have no idea what it is but apparently there's some sort of conflict between WMR and this service after 22H2 update which causes notable stutters. In my case I was sitting at frame times consistently below 12 but performance overlay of openxr was constantly changing between green and red (lost frames). Same with SVR (purple frames). As soon as I stop it it turns green and stays green. 2. Go to windows search, type services, launch as admin. Find power, double click it, change start up type to "Disabled". Apparently, it tries to manage power of the CPU and when disabled, CPU runs at consistent (max?) power. 3. DISCLAIMER: doing point three should be safe for your system but all what you do in the registry editor is completely your responsibility. If you are WMR user, you probably noticed that when VR is enabled (WMR app is running), in display settings you have 3 extra monitors. Those are virtual desktop and are used for various apps launched inside VR (such as browsers, etc.). In WMR every such app requires a virtual desktop and to avoid a lag when opening one of those it creates 3 in advance. If you're not using VR for anything apart from gaming, you can disable those. For me it reduced CPU consumption for window manager process or whatever it's called. It may also possibly slightly reduce VRAM consumption as those desktops will not be rendered in the background (or at least that's my understanding) Go to regedit and go to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Holographic Add DWORD 32 bit PreallocateVirtualMonitors and change value to 0 Happy flying!

@BIGNEWY @NineLine any news on this issue? When can we expect a fix? The cockpit is ridiculously shiny and it’s been more than a year since it was reported. thanks in advance!

Seeing Baltic states in DCS would be great. There was/are plenty of airfields built during Cold War

Please see attached track file. It feels like it's impossible to use AG radar with the frozen image. Steps I have a steerpoint near the airfield, I set the radar to get a good picture with DBS2, I let the radar do the sweep, I freeze the image and then slew cursor to the desired location on the frozen image. The actual SPI moves twice as much (see the SPI through helmet in the track). This renders the radar pretty much useless if you don't bring a TGP with you. F16 AG bug.trk

Yeah i tried that but didn't really halp with the jaggies. Thanks though.

Thanks @silverdevil. To use DSR is it enough to choose the resolution in DCS or you have to change your system display resolution?

Hello, Looking for a little help to get rid of the shimmering issue. I run DCS in 12700K and 3080. Basically, no matter what AA settings I use I get bad shimmering all over the screen. Currently I'm set to MSAA x2 and SSAA x1.5 with 27 inch screen at 1440p resolution. The following video shows the problem. Take a look at the horizon line and the outlines of all the objects and textures. I am basically use settings close to Spudknockers' and he definitely doesn't get the same results on his videos. Here's what I tried so far: - Clean up and slow repair - Using Nvidia DSR at 1.78 and 2.25 - Using Transparency AA and MFAA via the Nvidia control panel - Using 4x MSAA and x2 SSAA - Using Anisotropic filtering at x8/x16 The issue persists at all possible AA and AF settings inside and outside DCS. Attaching my DCS settings, a track file and the log files. Thanks for any help in advance! Shimmering test.trk dcs.log DxDiag.txt

I find George utterly imprecise with the gun. He finds the target, lazes it, shoots it and rounds usually fall long no matter if we hover or keep flying.

Alright, so trim for any asymmetry it is. Thanks all again!

Thank you all for your opinions! It would be interesting to see some reference to one or the other but I’m struggling finding any. Thanks anyway!

I know it has been brought up a couple of times but I am just looking for confirmation. It seems very odd to me that on a FBW airplane like F16 we have to trim for bomb dropped from one wing. I've spoken to an ex block 52 pilot from Polish air force and he told me that when you drop a bomb the aircraft slightly drops wing to the heavy side and corrects itself in a few moments. Same behavior is observed in the other sim I'm being told. So, do we expect some changes to FCLS any time soon to eliminate the need to retrim when dropping bombs or it is "correct as is" now? Thanks in advance!

Solved by slow repair, fast repair didn't help.

Hi. Jut updated to the latest version of DCS and can't see any servers. ip v6 is enabled, I did a repair, I did reboot the computer, I rebuilt the saved games folder. Running out of options. Log attached. TIA dcs.log

Thank you! Very useful.

1060 user here. After 2.7.7 had to crank all the settings down and was getting 37 fps with everything low-low except basic textures and was getting GPU usage at 100%. Yesterday decided to try and add shadows on high and msaa x2 and guess what? Same 100% gpu usage and same 37 fps. Weird!

Perhaps, one of the developers couple reply? Track hold clearly is broken and doesn’t work at all. It’s far too easy to replicate. get a target in TWS, shoot a phoenix, if the target is lost before pitbul phoenix never gets activation command on the track hold target.

Situation: me fighting a Mig, launching a Phoenix. Mig notches me for a second and I lose track but it’s kept in track hold (TTG around 20 sec). Phoenix never activates on track hold target, flies past it. 2 questions: is this intended behaviour? If yes, what is the purpose of track hold? I fly with Jester if that matters. Thanks in advance.

Ok thanks

I did not too. Wonder what happenes if you do.

What I noticed is that reducing your settings to below low (msaa off, shadows off, no reshade, vis range medium, clouds low, heat low, basically, all on low) gives the same FPS that I had before with clouds high, msaa x2, shadows low. Also changing from F14 to yak 52 does no fps change for me (before it did). It almost feels like FPS is capped at some value (40 for me) but in menu I get 200 plus so not the case.

Same here. I7-7700HQ+1060, was smooth before the patch, now -10-15 FPS. Cleaned the FXO and metashaders. Reinstalled driver.

Ok now. What happened to F16 g onset tuning for Cat 1? Doesn't appear in the changelog. Has it been moved back?

Hi What exactly is a 6 minute left hand holding pattern in Case II/III aproach? Is it regulated somehow like each turn - 1 minute; 2 minute legs or it is up to the pilot to select turn/leg length? In a T-45 manual I found a description of a pattern to be 2 min turns with 1 min legs. Thank you in advance!

Has anyone had any problems auto landing the A? I've just tried twice and both times after G/S capture the Autothrottle couldn't keep the AOA constant jumping all the way from Idle to Mil and back forcing me to disconnect it and keep the power relatively constant to keep AOA yellow. Moreover, the autopilot coldn't keep the plane on the glideslope and the first time I crashed into the Stern, Second time landing well before the 1 wire. Haven't tried the B recently but had no problem before. Thnks for input in advance.