crazyave

I've got a question. From what I've read you need to run SteamVR to get tracking and OpenXR support. However, from what I have experienced and read on the forums, DCS Multi Thread does not work with SteamVR+OpenXR? So then won't you be stuck using single thread? ...and I'd assume ED will do away with single thread after some time, rendering the HMD unusable for DCS?

Looks like the old bug came back in the last update. All the trains have gone smokeless again.

Same problem for me and my buddy on two totally different systems. When in muiltiplayer it causes desync with the server from the client side as well.

I came from 2080ti + 8700k@5Ghz --> 3090 + 8700k@5Ghz/13900k --> 4090 + 13900k. It was a small change from 2080ti to 3090 and big (double+ previous upgrade) change from 3090 to 4090. The 8700k@5Ghz to 13900k was good for 10-15% improvement in 1% lows, but not much on the high end of fps. I feel the 4090 on 8700k@5Ghz would have been ok, just leaving a little on the low end on the table. BTW, I have 64GB RAM as well. Even on this highest end setup I still have to run reduced 70% supersampling on the G2 to get decent smoothness, and still have to put up with stutters/shimmers here and there at that. What I'm saying is even if you go big it's not enough to overcome the shortcomings of this game. Framerate is still an issue to contend with throwing everything at it HW wise. That said, the 4090 was the best bang for the buck investment in my system. (god it sounds crazy to say that about a 4090! Fantastic card) I don't have any experience with the 9900KF, perhaps you can extrapolate from my 8700K@5Ghz experience...

This is by far the best module I've bought in a long time. Great flight model, spectacular performance in VR, not many bugs, for me anyway; all on EA release! It's clear someone put lots of time and thought into this module and really gave it some love, it shows. They also had the skills to do a good job. Now if we could just get the even a fraction of that quality out of ED on the core game (especially) and their modules. I get 10x better framerate with this module than the F-16 !?!? Crazy. I can actually fly downtown Dubai without getting sick in VR. My mind is blown, hats off, major respect.

Great tips guys, thanks. I've tried everything mentioned, but I'm going back and double checking. I did find that I had forgotten to disable full screen optimizations for the new MT shortcut I created. But I played it back and forth with that setting and could not tell the difference. Now for the weird part. My usual flying buddy and I have been using DCS for the past 4 years. In that time we've come up with this saying "It's a bad (or good) DCS day". Basically it seems each time we play the game seems to behave differently. Not just in subtle ways, but some days it will perform terribly and others great. I had stopped using MT a while back when the performance stopped being good. Now randomly with no changes it's working fast again, at least as fast as ST with the benefit of some fixes that have only been applied to the MT version, like the bullet hole stuttering fix. I don't know how long it will perform well, but we'll see. Does anyone else have this kind of experience with DCS, where it seems to randomly change behavior and performance from day to day?

MT has massive stuttering making it feel like 10-20fps (even though the counters show 80-90fps and 7-10ms, it's totally wrong) and causing nausea. I'm on a 13900k and 4090, so it's not my system. I run very low settings. 70% understampled and med or less settings all else. No one has come up with any suggestions that have led to a solution or explanation. I have a clean install with no mods. ST also works great, no stutters, very smooth, same settings. SteamVR also allows you to run SteamVR apps with DCS running at the same time, that's huge! I cannot get Steam VR to run DCS with OpenXR, it just crashes loading.

I went back to all the track files for a mission that produces the issue and tried to play them back but they just end after 10 seconds, whereas the missions are about 1.5hrs. I'd either have to live stream it or literally put a gopro looking at my monitor due to the playback bug which doesn't allow playback, LOL. They are 52MB each, what a waste of disk space. The conditions in my mission are having an F-5 with full fuel, or close to it, two sidewinders on the wingtips. Chase down a fully loaded TU-22 and shoot it with guns, as he maneuvers or turns sharply, if you're in the wake turbulence the wings will rip off.

I get this too. If I fly behind a TU-22 and he makes any kind of quick turn or movement my wings go bye-bye. Even with hands off the stick. Is that realistic?

In the past we didn't have this issue. Is there now a dead zone defined in the throttle movement that's supposed to be there? The airbrake also randomly doesn't work, so I think there's a bigger issue with the module.

London and Paris look stunning, overall great work. I was surprised the FPS were as good as they were. That said, these huge cities with thousands of objects does nothing for VR users. Other than a casual high/slow flyby you'd never be able to play a sortie there due to framerate limits even at lowest settings. FPS is also down in the smaller towns I had missions in, love/hate on this one for VR. Definitely no love for VR users in this game. Unfortunately, the update, while it looks awesome, reduced performance for VR even more. I will now have to play this map less.

I'm on an HP G2, I'm using OpenXR plugin for WMR. with the Multithread executable.

Noticed this in a Las Vegas flight at night yesterday. One eye has some lighting effects and the other does not.

The Afterburner still doesn't consistently come on for me. They show advanced physically in the cockpit and fuel usage goes up, but no speed increase and no flame out back. Seems to happen when I'm flying at max power without AB for a while and then slowly advance to AB. I also frequently get an inverted radar display. The ground is at the top and the cursor does not move appropriately. Let me know if you need logs but pretty sure everyone will have this. This is in VR and single or multi thread.

Ok, so I got that and it does show which runtime is active, should the DCS runtime show up in that list? I'm only seeing SteamVR and WMR. Also, I still can't get the current resolution of the headset anywhere, how do you set or know what your "supersamping" or pixeldensity/etc is set to in OpenXR?

When I first installed the update I got stuck in this loop trying to run MT where if SteamVR was started then DCS would close, and if DCS was open SteamVR would close. It was not happy at all. I finally somehow ended up with the OpenXR for WMR kind of working. I had to force OpenXR from DCS with the --force_OpenXR option. However, I had to install the OpenXR tools for WMR to control the resolution setting, which does seem to work. The only big issue left with MT is that when I start a mission DCS hangs at 100% CPU on one core until I click away from DCS and back on it get the "This program has stopped responding..." or somethign like that, then I just click to wait and it instantly comes back. Really weird. The performance is more close to even now that I'm doing things like this. I'd still love to hear from ED about what the best way to run OpenXR is and how to verify you are indeed running it that way.

I wonder if certain settings in SteamVR+OpenVR perform much better than OpenXR. I'm using one of the highest end systems that can be built (4090+13900k+64GB RAM) and I'm seeing a big drop in performance with OpenXR + MT. I can't use fpsVR anymore to measure as that doesn't work with SteamVR+OpenXR. Using the built-in performance measurement it shows about the same numbers, but I'm just seeing a lot more stuttering and poor performance in the headset. I have my system tuned for the higher FPS vs visuals. I run 90fps (< 10ms) about 90% of the time with SteamVR+OpenVR. Now what I get is what looks like about barely 30-40fps (15-20ms+) with OpenXR, despite what the built-in performance counters say. I was running SteamVR+OpenVR at 70% resolution to get that good 90fps experience. I don't use reprojection either. When I switch to OpenXR + MT, SteamVR no longer controls the resolution, is it just running 100% then? If I had a way to adjust the resolution to match OpenXR maybe I could make a fairer comparison and get a better experience. Is there a way to do that? What other settings are lost in this change that need to be moved over to OpenXR? Since ED didn't mention being forced to use OpenXR for MT, nor any of the caveats of that change, I'm left in the dark here guessing about how to make my system perform using tools that weren't mentioned in the changelog.

I take this back, I seem to have broken things now, DCS won't start. woohoo!

I've always used SteamVR with Standalone DCS and after the update SteamVR doesn't open and if I open it DCS force closes. I had to dig through some old threads to find out that I needed to go into Developer Options in SteamVR and set SteamVR as the default for OpenXR runtime. Seems to work as it did before. Not sure if this negates some/all of the benefit of the patch though? I would hope not.

I've had a RealSimulator FSSB for several years and Logitech/Saitek pro pedals. I also use a warthog and cougar setup at times. I'm comfortable with the pressure stick in warbirds, this is the only one I have troubles with. The spit is definitely the next toughest handling warbird for me. Awesome input Bozon, thanks! I will definitely try those settings, I've never used saturation vs curve. I never thought about the wingspan vs fuse ratio, that makes a lot of sense, I thought maybe they just put on a small tail to keep the rear weight down or something. I wonder if the yaw in the mozzie is very realistic. Listening to actual pilot interviews for the plane no one mentioned that handling characteristic vs other things that are much less subtle in the DCS version. That much slip seems like a recipe for a hell of a snap spin, which interestingly rarely happens when I'm flying it.

My buddy and I really struggle to get this plane flying decently and consequently do not enjoy flying it, we have definite purchase regret but really want to like it. Unlike any other DCS modules it's the first time we've had to use curves on the controls up to 50+ just to stay somewhat in control. Particularly the yaw and pitch axis. I know how to fly coordinated with the rudder, but it seems no matter how hard I try I still end up flying with a wagging tail and the airplane flying 30deg to the direction of travel. It's impossible to use the guns or rockets to hit anything consistently due to it's sensitivity and instability. My brain tells me aircraft physics seem to not really be at play in its handling. Is there some setting I'm missing or way of practicing that's different than any other module which will help?

Thanks for this, worked perfect. Just had to export settings from old version and import to new one, everything I've tried works so far.

Seeing the same with the HSI pointer being locked. Along with afterburner not engaging randomly with throttle advancement, sidewinder on one wing tip causes 90deg roll when pulling hard up on elevator, plane disintegrates in the wake turbulence of other aircraft, sidewinder sound much louder than it used to be, even with volume turned down all the way. Last update of the F-5 added a lot of bugs.

Did you ever try the settings I shared? You don't have to think, just use them and you should see the same/similar results...

I'm on a Reverb G2. Too bad we won't know how much will be the doubling RAM or the CPU. I'm on the lookoout for deals on a new rig, might join ya...