keisentraut

OMG... Turbo mode fixed my stuttering!!!!!! I wasn't even using the toolkit. My VR is now butter-smooth when I dial in my settings ingame. THANK YOU! THANK YOU! THANK YOU!

Another observation.... the DCS FPS seems to constantly go between a red CPU Bound - Main Render Threat and a yellow message. They flicker back and forth constantly. I think every time they change, I get a small stutter. So if I put Virtual Desktop to run at 72 hz, it doesn't matter if the DCS FPS slider is maxed out at 300. It only outputs 72 frames. And because of that, my outputted frames are usually constantly changing between 70-72FPS creating the stuttering. Is there anyway to override that 72 frame output cap and put it to...say 75 frames so Virtual Desktop is always receiving "at least" 72 frames from DCS?

Yes. As far as I can tell... the computer is running really lean.

I dropped my polling rate to 125. Disabling HAGS did nothing to improve my situation.

Ahh...that part is pretty good. I'm using the Quest codec maxed out at 200bit and I have a wireless transfer of around 2400 mbps using a wireless 6e router that is 3 feet from my headset and it's the only thing on it. PC is connected to the router via ethernet. My latencies from the game and the connection are usually around 10ms. That said, the DCS FPS overlay is showing all those spikes. Whatever is happening is definitely on DCS and/or my computer side... I get the same issue if I use a link cable, go potato mode, etc...

Like I mentioned above, I can run the whole game in potato mode and it still stutters. Hoping something in the log files sheds some light...

Here's one where I loaded into Nevada at 72hz. Single helicopter, no scripts, and my frame time was hovering around 17-18ms. Didn't even take off. dcs.log

SSW = I've tried disabled and always enabled. I don't run it on Auto. Refresh rate = I've tried 72, 80, 90 and 120 Pixel Density = 1.0 Quad Views = Off dcs.log DxDiag.txt

Running the Quest 3 on an AMD 9800x3d / RTX5080 / 64GB DDR5 using Virtual Desktop. No matter what settings I use, I get micro stutters. I feel like I tried everything I can find on YouTube. One thing that is puzzling me is when you look at my Frame Time, it looks like a heart beat and I'm guessing the stutters are happening each time that timing "line" pops up and down. Does anyone have any clue as to what could be causing this? I've tried this on Potato mode as well as God mode. It's the same story each time.

Nevermind... I just clicked on the blue section and dragged it over...

I have this exact issue. This only affects the Multiplayer screen only. What exactly did you change and to what setting?

I have this same issue. SimAppPro only works without the javascript error if I run the app with Admin privileges. I'd love to have a solution where I don't need to do that. Any ideas? I opened a ticket with WinWing.

I'm currently using reshade to brighten the output on my MFDs. I'm using a UIMask to target only the render area for those screens. So far, it works great. However, I can't figure out how to apply a separate reshade effect to my main screen. Is it possible to break the ReShade effect into two completely different areas with various effects applied to separately to each area?

Running without Admin privileges solved this for me.

I had this exact same issue. However, I found that if I turned off my USB display devices (Winwing MFD).. the game ran 100% fine. I tested with a buddy of mine who had the same issue with different model MFD USB displays. Game worked fine for him once he turned off the USB displays. If you have USB displays, turn them off and try the game against using just one screen. Then report back here what you find. I, personally, believe that the latest updated messed up the ability for DCS to handle these types of displays and still run the game. Curious what you all find out. Here's videos of DCS running with USB displays turned on and then turned off. The difference for me was night and day. https://drive.google.com/drive/folders/1cz9MfQ5li3PxpP9o1Z6tY8XzqT7yieRM?usp=drive_link