DeltaMike

I don't My server has 8GB of RAM and it's gagging on bigger Liberation missions, gonna try upgrading to 16. My main box only has 32GB of RAM I imagine if you already have 64GB of RAM the 3D would be the shiznit

Because it doesn't work? Depends. Let's assume your headset is running at 90hz. Stutter can occur at any fps between 45 and 90fps. At the lower end of that range -- 45-60 -- you get early frames. In the upper end of that range, you get dropped frames. If you tend to run at the upper end of that range ,or if you're using SVR (which has its own issues) MR or some kind of frame-locking can improve the experience considerably imo. If you're running at the low end of that range, as I do, you're going to get microstutter. Which isn't terrible in OXR. Just a slight irregularity if you're looking straight down at the ground; feels like I'm riding a Harley (which I do when I'm not in DCS, maybe that's why it doesn't bother me). Problem with MR is, I still get microstutter -- looks exactly the same to me -- and have to deal with MR artifact on top of that. I have MR set to "auto" so it's off in DCS, where I don't notice the microstutter anyway (too busy) but it comes on automatically in MSFS where the hope is, someday I can figure out how to make it work. YMMV, depending on your settings.

There's making it as easy as possible for first time new users, and then there's dealing with the process for dealing with it every time DCS updates. I'll probably just go back to using mod manager myself. Yeah for me, once it's set up and opencomposite has a DCS profile, Skatezilla works fine. Try deactivating toolkit, turn off motion reprojection, set resolution 100% and PD 1.0, deactivate mods especially shader mods (all of em), repair DCS, delete extra files, try again

I think I may have discovered a problem with opencomposite.exe (with the help of ColinM) where launching from Skatezilla sends you straight to flat screen. To review, the global install procedure is Clean/repair DCS Download/run opencomposite.exe, set OXR as runtime Launch DCS It should launch directly into OXR, and after you run it once, you can see it in the Config window, where you can right-click on it and specify its behavior. Only problem is, if you launch DCS that first time from Skaetezilla, it'll launch with parameters --force_vr and --force_steam_vr. I think that's why some of us get sent to flat screen mode the first time we run DCS and have to go back and set opencomposite.exe up all over again. I imagine the same problem arises for people who purchased DCS from steam. If you launch DCS without parameters (and "enable VR" checked), opencomposite.exe works perfectly. And I can launch in VR from Skatezilla subsequently without any issues. Unknown if the same issue is present if SVR is not installed or is made read-only.

Here's how I would approach it 1. Deactivate Toolkit and turn off motion reprojection. If that doesn't solve your problem, I don't think OXR can be blamed here. 2. De-activate ALL of your mods, then clean/repair DCS, clear your shaders files and try again. If that solved your problem, first ask yourself if you need any mods. With a few limited exceptions, OXR plays best without em. If you must have your mods, add em back in one at a time to see if you can figure out which one it is and please post your results. (If you aren't using a mod manager, you'll quickly see the benefits of using one.) If that doesn't solve your problem, we're officially off topic. But, to continue anyway -- 3. Check background processes. For me, it's typically been something updating in the background. Usually Steam (good riddance). Winsimapp-pro is notorious for doing this. Etc. We all have a bajillion background processes running. Check em. The Startup tab in Task Manager is a good place to look. 4. Check your hardware profiles, especially if you're an AMD user. AMD drivers have a mind of their own. 5. Malware scan 6. Might need to ask on the hardware forum from there, but I could see the benefit of stress testing your system and checking your thermals first. Look at CPU, GPU and SSD. Thermal paste dries out, chips go bad, water coolers get bubbles. This is in order of relevance to the sub. Personally I would check background processes first, malware second Please put specs in your signature. ETA: in reference to edmuss' comment, I've seen performance tank when windows is ready to update, in other words if it's waiting for a reboot. which, i imagine you already tried that

The Washington Post estimated 2% of gamers overall use VR; Sony claims about twice that many are using VR with Playstation. Question in my mind is, where Windows is going with this. WMR is extremely slick; you want people to play VR, eventually it's gonna have to be as simple as plugging your headset in and putting it on. WMR is there, but Microsoft isn't even supporting its own gaming platform. At best, it made a half-hearted swipe at supporting the SVR API. Which leads to the question, where is Steam going with all this. Clearly, Steam and Facebook are trying to replicate the Apple "ecosystem" model. Facebook has been doing a decent job by all accounts. Steam, on the other hand, has (in my opinion) been doing a spectacularly bad job of hardware development. Currently almost half of Steam VR users are actually using a Facebook product, if that's any indication. And finally, where does that leave DCS. I think ED has done a great job of positioning itself in both ecosystems. The problem in my opinion comes from the stifling effect the Apple model has on hardware development. About the only option indie developers have, if they want access to the gaming market (including DCS) is to figure out some way to use the SVR API, which to my untrained eye seems complex and inefficient. Hence the push for OpenXR, I suppose. But, that leaves DCS in at least a temporary quandary, because Vulkan doesn't presently support OXR. People are working on it. Meanwhile, open-source solutions for OXR implementation have been moving forward at light speed, thanks to the efforts of a few dedicated developers (some of whom, ironically, work for Microsoft). As of last week, if you have a Reverb headset, and have a clean DCS install (one that hasn't been tarted up with all kinds of shader mods, which are going the way of the dodo) OXR is a one-click install. That's big news, and a harbinger of the future. Keep your eye on Varjo. They get it; that's our future. What do you call multi-core support, plus one-click OXR implementation, plus Varjo? Assuming GPU technology can keep up, I would call it "complete bliss." It's coming. And that's when VR will relegate flat-screen gaming into the dustbin of history. Until then, we are early adapters, nothing more.

aha. available on amazon at a slight markup. it does gestures. like salute, perhaps? maybe i could put it on my middle finger. you know. for keeping up international relations here's another Gestures.... hm. Landing gear up/down, canopy open/close (kind of a pain in some modules), goggles on/off. Salute. Others? I guess capto-glove can do the same thing. Question for all these things as a mouse-substitute is gonna be precision, recognizing most of us feel using a mouse counts as "natural movement" (I'm pretty sure my motor homunculus is holding one) But for $40... shoot I'd buy that just for the gestures alone.

Yeah VR necksaver is really promising, doesn't work in OXR (yet) but it definitely works

OK I'll admit that's pretty cool. The $16 mice don't do all that.

In VR, 90% of GPU tuning is figuring out how many (virtual) pixels you can drive. That doesn't change when you run a complex mission. (That doesn't mean you can run the exact same settings. But it's close.) I don't know that I would get too excited about this chip for SP/DLC. 3600x is enough and 5600x is more than enough 99% of the time If you're playing Liberation, you can try dusting off an old computer, use that as a server. That definitely works. I'll bet the 3D does also. Interested to see a head to head. It's clearly doing something. As for MP... there's only one benchmark that matters around here. Sounds to me like we have a winnah CPU times and GPU times are not unrelated, both are gonna go up in MP. But I don't think any of us are confused about where the bottlenecks are.

Yeah they have em on amazon for $16US. I could see it working with an F16 style grip but an F18 grip would be a non starter. Keep meaning to velcro a mini trackball to an actual kneeboard, which would work great in VR (especially if you take the nose gasket out so you can see under the hood)... very handy if you have live ATC or AWACS.

Yall are killing me. I'm looking at that little tower cooler in there... should be enough probably maybe. Meanwhile my PSU is saying, "It can nae take any more Captain...she's gonna BLOW!" Killing me.

Which may be the problem precisely. I'll bet a lot of people who are sensitive to the flicker have at least a family history of migraine.

Yeah same thing happened to me. Maybe because I have DCS on its own drive, or maybe that's how it is. I had to start DCS in VR (it actually started in pancake mode) then re-run opencomposite.exe, then DCS showed up in the window. I also had to select "Switch to OpenComposite" a couple of times before it "took." Sorry for the frustration. Things have been moving extremely quickly -- I'm amazed how much things have changed for the better over the last month. The developers have been working their fannies off (for free). Three cheers for that.

There's an overlay you can call up in the OpenXR Toolkit, see first post for links and install instructions

Yeah. I just got mine recently, what, six weeks ago? Looks like a bad fluorescent light to me. Beyond that I can't quite hold 60 over Syria without undersampling. Guess I'm just gonna be one of those 45fps fellers. All I can figure is, @edmuss has his 3070 on testosterone shots or something. @nikoel Did the install today, I can certify it's not idiot proof but it does work. Had to re-run opencomposite.exe a couple of times before it "took" but it did take eventually.

^It's one solution. He probably had microstutter. If your headset is set at 90hz, microstutter only ever goes away at 90fps and 45fps. For people like me who are usually loping along at 50fps, most of the time each frame is displayed twice, with an occasional early frame. If you're closer to 70hz, most frames are displayed once with frequent dropped frames. If the dropped frames are driving you bonkers, setting your refresh rate to 60hz solves that problem. Another strategy could be dialing up your settings to get yourself below 60fps, or locking your frames at 45 using MR or something. Nothing wrong with SVR of course. Pimax users seem to be getting great results with it. The problem I think is with WMR4SVR, and I believe the mischief might be happening after the frame has already been rendered. Which is why nikoel keeps banging his spoon on the table about how FPS doesn't tell the whole story here. About the only way to deal with WMR4SVR is frame rate locking. Which works great in SVR but not quite as well in OXR. For people like me, it's a close call. SVR with MR is definitely smoother. I just think OXR looks better and I can live with a little microstutter, long as it's down at the low end of the refresh rate range where you're getting frames early, instead of late. @Gravy Jones -- if you keep dialing up your settings, there's a risk of dropping below 60fps, at which point you'll start dropping frames again. If that happens, you could go back to 90hz if you want, only downside to that is, when you snap-roll the horizon will judder. Curious to know what the horizon looks like at 60. Whether it does anything for cloud shimmering and stuff. Are you doing helicopters? Jets?

hehe sucked another one in. ain't no going back now.

Edited I've been timing my trips perfectly lately -- sounds like I was out of town just long enough to get that merge sorted out. Thanks for all you do. Gonna try life in the fast lane (60fps/60hz) today. Wish me luck

In my experience with Skatezilla it has never messed with my settings and bindings. I don't think it does anything inside your saved games folder, far as I know That said, it's never a bad idea to have a copy of your saved games folder on an external drive, that'll be a lifesaver someday Speaking of the saved games folder, let's see what @nikoel says about all this, I think clearing that folder is part of his troubleshooting regime... so yeah, make a backup now while you're thinking about it

WAY faster, much better frame times. I've been playing Liberation lately, that'll bring any system to its knees. Smooth as butter if I play it on my server.

Is there a "best practices" approach to troubleshooting those runtime errors? I spent a little quality time in the discords this morning looking at this. I'm not sure there's anything new under the sun. Here's what I came up with -- for G2, Quest has its own issues -- recognizing I'm simply restating what's already in the first post in this thread. Which is worth reading, folks... Update windows, turn off HAGS (if there's no option for that, don't worry about it), turn off background programs (RGB, voice attack, winsimapp, etc etc) Un-f*** DCS. Uninstall all mods, especially shader mods, especially ReShade. (Mod manager is your friend.) Set pixel density to 1.0 and leave it there. Clean DCS using Skatezilla. Tell Skatezilla to use the SteamVR interface (under "rendering driver"), but make sure you have WMR set NOT to start SVR, and make sure you aren't starting DCS with the --force_steam_vr argument. By starting it from Skatezilla. Clear shaders files (metashaders and fxo folders) Rename D3DCompiler_47.dll and delete opencomposite.ini (if it's still there, which it shouldn't be if DCS was cleaned properly) See if OXR is working. Do this without the OXR Toolkit. If you've already installed the OXR toolkit, you don't have to uninstall it, but definitely de-activate it for this test. Open the OXR Developer Tools (the one you download from the Microsoft store) Check version Check settings. Check resolution at 100% or less, and check motion reprojection off. Pull up the "demo scene." If OXR isn't working, or is out of date, follow procedures for re-install (ie unintstall the three programs and then re-install using procedures in the first post) Once we are sure OXR is working, activate the OXR Toolkit (the one you download from Github) Check version Check scaling off (if scaling -- FSR or NIS -- is causing the error, there's a registry edit for that) ? It seems some systems just don't like the OXR toolkit Does that sound about right? What am I missing? I found one case where pushing resolution >150% caused issues, several instances where OXR was out of date, one where old ReShade files seemed to be causing issues, and generally a lot of not following procedure / skipping steps / making things more complicated than it needs to be. And I get the feeling a lot of that comes from not using Skatezilla, which I think is a key to success here

VR headsets tend to work best if plugged into a USB port direct to the motherboard, and they can be finicky, they may like one USB port fine and hate the one right next to it. I think most people are using a physical cable for DCS; check that and factor that in to your price (that's what I was gonna do before I bailed and got a G2). Take your PC out of the cupboard, it's gonna overheat and throttle.

There are some benchmarks on the 3D over on the VR forum. Seems to help quite a bit in heavy SP missions. Granted, I bought a dedicated server for less than what the 3D goes for, and that works too. Haven't seen any numbers in MP. If I were still playing MP I might invest in RAM first, for half the money

Wonder if this thing might help on the server side.