MackTheKnight

yea, tried reinstalling varjo base. I was not running the dfr mod, but I am running openxr toolkit. Going to try removing it and see what that does. EDIT: Looks like that was it. So for some reason this new version of DCS doesn't like OpenXR Toolkit. Thank you all!

Previous version worked fantastic in VR MT, with my Varjo Aero. After today's update, I can no longer launch the multithread version of DCS in VR on the Aero. All I get is a blank black screen. Have done a full clean/repair of DCS with no improvement. ST opens, but I hate the sacrifice in performance, now that I'm spoiled by MT. Checked the Varjo forums, and it seems like I'm not the only one with this issue.

Running DCS latest version open beta, MT mode, with DFR in the Varjo Aero. In night missions I have a repeatable crash to desktop in the harrier. To replicate, all I do is start the jet up, turn on the TPOD, and then turn on the FLIR HUD mode. As soon as the FLIR HUD mode is toggled on, the sim crashes to desktop. Not sure if this is specific to running DFR yet or not. If someone NOT running DFR could test above, I'd appreciate it!

This is happening to the entire VMA-513 squad on a daily basis. We fly the harrier exclusively, and every single one of us has this issue since the 2.8 update. The work-around that seems consistent, is to open DCS and load into a single player mission before joining a multiplayer server. Once you do that, no more crash for that session. But as soon as you close & reopen DCS and attempt to go directly to a multiplayer server and spawn in the harrier, it immediately crashes to desktop.

I'm curious - have you experimented with simply disabling reprojection outright? I too was struggling with reprojection, including some strange screen tearing and flickering on my Valve Index. (Have an HPG2 on pre-order) Disabling reprojection via the steam control panel solved this issue for me. (It's called motion smoothing in steams lingo) -Mack

Thanks Guys and especially to Voyager for pointing out the 30 minute bug. I think that's what I'm seeing! -Mack

Hi All, Really enjoying the P47, but for the life of me I can't figure out what I'm missing. Is there a fuse or switch hidden somewhere for the Oxygen system? I can't seem to get it to turn on from a cold-start, and suffer from hypoxia at high altitudes of course. I'm probably missing something simple, but would appreciate it if someone could enlighten me. :helpsmilie: Thanks! -Mack

Thanks All - I've just started flying the Spitfire and have noticed this happening in multiple missions I fly. I thought I was doing something wrong that was causing it to burn-out the bulb for the reticle...

wish we could get this tomorrow!

Sounds like I should give this process lasso thing a try just out of curiosity. I honestly don't care what the cpu/gpu usage stats show as long as I'm getting good FPS with no hitching. And my FPS is solid now since getting rid of that Intel utility that was screwing my system over. I ran a mission last night and the FPS never dropped below 60 and was generally hovering around 100. That is a far cry from the annoying hitching and low 20 some FPS I was getting before, so I'm a very happy simmer now! I haven't tried the F18 in the Oculus yet, as I wanted to get more familiar with all the systems before jumping into VR. But I'm hopeful that my VR performance has improved dramatically as well, thanks to figuring this out!

here's a screen-cap, while sitting on the carrier deck...

Hi Lefty, Yes, I have MSAA set to 4X. In the Gulf map, I'm now getting FPS in the 60s at the air-field and 100+ up in the air. Prior to figuring out the cpu affinity issue I was getting low 20's no matter what settings I tried along with constant micro-stutters every few seconds. So happy to have it fixed now! For reference I've a 1080Ti GPU OC'd to 2050/6005. (Under a custom water loop - don't try that on air) -Mack

Do you ship these to Canada?

I'm running great at 2560 X 1080. No issues running ultrawide monitors with DCS.

Thanks - corrected a mistake in my write-up. It's actually broadwell-e, not sandy. I can never keep-up with the code-names. :music_whistling: