DeltaMike

Oh you're gonna get a pretty picture. It'll blow you away actually. Just keep in mind, tuning your rig for VR is a bit more subtle than just slapping all the sliders all the way to the right. You may find, for example, that running low terrain textures, and low or standard clouds looks about the same but makes the rig run a lot smoother. We'll help you with that and there are plenty of tuning guides available. Rest assured, it'll be awesome. What you're mainly giving up with VR, as opposed to flat screen, is resolution. Spotting distance, instrument visibility, etc. Best way to mitigate that is to run your headset at its native resolution. With that in mind, 6700xt is a good, but not a great GPU for VR. It could use a bit more horsepower and quite a bit more memory bandwidth. I'd be cautious about biting off too much. If you look at the G2 for example, which is very popular in DCS, you need to be able to drive about 9.3 million pixels. Not sure I'd be eager to tackle that with much less than a 3080/6900XT. Quest2 "only" has 7m pixels and might be a better match for your GPU. I used to have a Rift S and found Oculus software (ahem... Meta) to be slick and friendly to the new user. You get native support in DCS. It's also cheap. I'd also look at Pimax 5K, which has 7.3m pixels. You'll get less resolution in your central vision, so instruments won't be quite as sharp, but you might like the wide field of view, which I understand is very immersive. The software is going to be an order of magnitude more complex but it seems to work amazingly well with underpowered GPU's if you don't mind the extra layer of complexity. Either one will give you a stunning picture with your hardware. VR puts a load on the CPU also, but you're in good shape there, you will be able to handle DLC like Raven One no problem. Really heavy missions like Liberation or MP might require some adjustments (more RAM? 5800X3D? Dedicated server?) but at least you have an upgrade path if you need it.

Make sure you disable automatic context switching in WMR. You want the setting that makes you manually have to press win+Y to change the mouse from desktop to VR. Note, sometimes you have to win+y to wake the headset up

Agree. I didn't test SAM since that's already been done to death. My attitude is, I paid for it so I'm using it, dad-gum-it @TED are you flying the Apache? Seems like Chill could be a fantastic option for that module

Puzzling. Jabbers' video strongly argued the proposition that performance is tightly correlated with DCS frame size. So far I've found the same relationship in OXR as in SVR. I'm not convinced OXR gives you better frame times (maybe). But in the testing I've done, the only time I got worse frametimes in OXR, was when I thought I was doing an apples-to-apples comparison, but in fact was not Not that there's anything wrong with SVR or WMR. I think there's something wrong with WMR4SVR but if that makes it possible for somebody to enjoy the game, then, cheers!

It's not clear how, when or if OXR will work with Vulkan. My bet is, it will eventually, and ED will integrate OXR along with Vulkan.

Don't get confused... DCS only speaks two "languages." Oculus, and Steam. The G2 doesn't speak either one, so it has to use one or more translators to convert Steamish into something it understands. Most people these days are currently using OpenXR as the "translator." You still have to tell DCS to use the SteamVR "API" meaning for all intents and purposes, DCS thinks it's talking to SteamVR, but any more you don't even have to install SVR etc if you don't want (and believe me, you don't want to) So, there are two sets of instructions. In Thud's article about "Nailing Your G2 Setup" you'll see the definitive guide to using SVR/WMR, which is the old way. That requires... well, a lot of stuff running in the background. This post gives you the alternative, and presently favored approach, which doesn't require anything running in the background Skatezilla's "updater" app is highly recommended. You'll set Skatezilla to use the SVR API, even if you haven't even installed SteamVR.

Consider asking in the winwing sub. I'm sure they will fix it eventually but I wouldn't know, I do NOT keep simappro running in the background, it's not needed. The only reason to do so, that I can surmise, is to synchronize lights. Which doesn't do much for ya in VR. Granted I'm not using profiles, and haven't needed it switching between F18, F14, and the various prop planes I fly in DCS and MSFS. But, my Orion 1 throttle would need recalibration to run with a collective so ymmv. -------- There are a lot of steps involved, setting up the G2. That's true whether you choose OXR or SVR. Having done both in the space of about three weeks, to me OXR is more straightforward and works better, assuming you start with a truly clean DCS install as per the instructions in the first post of the "quick start" thread. That first post is kept up to date so you don't have to wade through all 62 pages. Note, all the information in that post was learned the hard way... your "best practices" are right there In my experience, OXR and G2 play just fine with winwing. It's the only way to fly.

best optometrist i ever worked with, bar none, was at the va (sac)

No, you can't get rid of it. Yes, you have to live with it. For now.

65fps? Your system is running fine, it's doing a fantastic job actually. But it's only going to be smooth, ie free from microstutter if you're running either 72fps consistently, or 36fps consistently. So you want to be either at your refresh rate, or a whole number fraction of that. Best option is to turn ASW on, which solves a LOT of problems. Or, you could try running the headset at 120hz, you're pretty close to half that as it is, and that may solve most of your problems. If you don't want to use ASW, then whatever refresh rate you choose, you want to tune DCS to run at half that

I didn't get the keyboard tray. I'm close enough to the desk to reach it. Plus I'm in VR, I seldom go there anyway. I imagine the problem is, the keyboard mount has a lot of leverage and it would be easy to hurl the whole thing to the floor if you whack it the wrong way. I dunno about that thing.... This is the second set of MT chair mounts I've had, the old setup was a permanent install where I had plenty of room for everything and I never missed having the quick release. Current setup is on an Ikea chair in a really small multi-use space and I use the quick release constantly. So, depends on your needs I guess. (I'm travelling in an RV so, it's like the world's smallest sim pit) You can buy "star" bolts on Amazon for cheap if you decide later you want em, as I did.

It's extremely solid, no wiggle at all. I like the ergonomics of the side stick mount a lot. You'll want a short throw joystick, anything designed for desktop use will be fine. Trackball will work better than a mouse although you can make a mouse work. Get the quick release bolts, makes it easy to swing that stuff out of the way for work. If you're in VR, it's really hard to check six wearing a scuba mask; using a swivel seat undoes that disadvantage and with chair mounts you can still control the aircraft. You can sit close enough to your desk to use your keyboard without a special mount, which is good if you ever need to like stand up or something. Put "sliders" on your chair to replace the wheels; note it's hard but not impossible to find sliders for Ikea chairs in the US, google is your friend. I have not had issues using rudder pedals but it helps if the entire rig is on carpet or a large rug. Think of it this way; you're more or less reproducing F16 ergonomics (including the reclining position if you want). It's the bomb imo and I wouldn't fly any other way.

VR is different. For various reasons we run at whole number fractions of the monitor's refresh rate. With a 90hz monitor, for example, we are only ever shooting for 45fps. With a reverb G2, a 3080 is sufficient, and in VR enough is as good as a feast. Same could be said of the 6900XT. For the same price, in an SFF rig, a 3080 will run cooler (and your CPU might also, airflow in general is gonna be better) and it'll be less fiddly. You'll get fewer power spikes, something to consider if you're using a SFF PSU also. Whether you can squeeze a few more FPS out of it (you can't, that's been settled) is irrelevant If you might upgrade to a Varjo or Pimax, bring as much ass as you can and hope for the best.

Pimax never ceases to amaze me. I could never run those settings on a G2.

I uninstalled ReShade several weeks ago and lost interest in it, things have been moving fast around here last few months. If you have a WMR headset anyway. Might need to check the ReShade forums.

Just thinking, it might be handy to have 30-some-odd milliseconds to work with in MP

The concern is, that DCS is gonna have to fill the RAM back up again anyway. Perhaps it's a question of trading performance for consistency or something.

You could try 30fps using MR maybe?

Yeah the opencomposite.ini that was used in Jabbah's version has terms not found in the main branch ... does it run OK without it? (I'm not gonna have access to my rig for a couple of weeks)

Everybody does Online play is gonna affect CPU times primarily. That'll also increase GPU times a bit but that should only affect your frame times if GPU settings (resolution, anti-aliasing, textures) are really close to the line. Basically comes down to whatever you can do to optimize your CPU. Overclocking with Ryzen may slow you down on several levels. Make sure you have XMP profiles set for RAM. Clean out any background processes that might be taking up CPU cycles. In DCS settings, turn down anything that uses CPU. Water, clouds and especially shadows, which you might need to turn completely off. You might try reducing vis range and tree visibility although that doesn't help as much as it used to. Check your ping, if you're on wireless choose a 5G connection if you can. Or try a wired connection to your router. Other than that, sometimes you just have to live with it.

Go back and run the install program, this time select all the available in packages

I'm not using a Pimax. Can only help with DCS settings and general math. The whole thing of leaving PD at 1.0 is kind of a best practice right now. As is the idea of adjusting DCS frame size in just one place. Way it works is, the HMD software (in your case, PiTools) figures out how big a frame it wants to request from DCS. You can usually (not always) change this in the HMD software using some kind of scaling function. If you're also using Steam VR, there are a couple of places to change that request in there also. DCS can either comply or not comply, that's where PD comes in. You multiply those values (and sometimes the square of those values) to come up with a DCS frame size. That frame size determines how many FPS you're gonna get, the smaller the frame the faster it runs (but the less information you have to work with). Basically my proposal is to set everything to 1.0 or 100% and adjust performance using PiTools alone. The only reservation I have about that is, it sounds like "Render Quality" is per-axis, so the work your computer is doing correlates with the square of that setting. So, once again, things can get out of hand quickly if you're not careful With a 2000 series GPU he's almost certainly going to have to undersample, so in other words PiTools is probably going to ask for way more than his GPU can give. So, he needs to do whatever yall do with masking and fixed foveated rendering and will probably need to have his Render Quality at some number less than 1. Probably not much less, maybe 0.9 and I doubt he will have to go below 0.77 or so We are also probably going to have to do something with textures, which seems to be a weakness of those 2000 series GPUs but best to get him running first before we start digging down into DCS settings. You've got him most of the way there, well done

Numbers? Aren't we kind of throwing out the baby with the bathwater?

You could also whip up a big giant mission in Liberation, that'll put a load on your CPU and eliminate a couple of sources of variability in online play. You definitely want MR off when benchmarking and CPU times are going to be way more helpful than FPS. If you don't want to install Liberation, here's the last one I flew; you can use with the Syria map, player is in an F18 off the generic carrier. If it's fubar (the AI being what it is, about half of them are) let me know and I'll gin up a new one for you First get yourself tuned for the Syria map using a solo free flight mission. Syria is different. Specify how you have water, clouds and shadows set because those all affect CPU times, definitely don't vary those things (or anything else) in your trials. liberation_nextturn.miz

Forum settings -- signature -- view others' signatures Pull up the frame counter in OXR Toolkit Companion App, you can see what kind of overhead the companion app functions are adding. I'll bet it's not much. For now you should probably focus more on your frame times than FPS. When you say your FPS is 28-35 with MR on, that means you're flipping between 22.5, 30, and 45 fps. Mine does that too (in MSFS) and it drives me bonkers. In OXR you get to pick which one you run at, and probably should to keep it from bouncing around. My theory is, you're getting frame time spikes that get averaged out when you have MR off but are gumming up the works when you have MR on. On my rig, such things come from power saving schemes. In my case, (AMD system) Adrenaline doesn't do a very good job of that so I "corrected" it. Seems like the NVIDIA drivers do a much better job in that regard. In your case I'd see what Windows is trying to do to save the whales at your expense, so you can "correct" that as well. I imagine you'll want to get into BIOS and see what your CPU and GPU are doing. Did you overclock your CPU? (you should) Is it stable? Is your RAM running at the right speed? (assuming that's even a thing for Intel chipsets) What do your thermals look like? (I use Prime95 to test these things). Same goes for your GPU in terms of overclocking and thermals. At some point you might want to stress test your GPU (I use this) and do a VRAM check to make sure you didn't get a dud. Edmuss is undersampling, that's why he can run those settings. You should be able to run the same settings in your rig at native resolution. Pixel density should be 1.0 for both SVR and OXR, don't mess with that. Assuming Steam global resolution is 100% and per-app resolution is 100%, and you aren't using FSR or NIS, then you should be able to run 100% in the OXR Tools and get roughly the same FPS numbers. If any of those assumptions are incorrect, post up what you're doing, I'll do the math, edmuss will correct my math and you'll be off to the races.