TAIPAN_

Anyone that's running QuadViews at high resolution - is the new spotting OK? Can you see the dots in the centre region with high SS?

It's mandatory actually. To use PimaxXR and QuadViews you must launch DCS in OpenXR mode. All you need to do is run the ooenbeta multithreaded exe and it runs in OpenXR mode automatically.

Try nvidia control panel increase virtual reality pre-rendered frames from 1 to 3

I came here from the search after trying to get OBS setup to work with my VR system & DFR/QuadViews using OBS-Mirror, I was finding a lot of performance issues compared to not using OBS. This test is very useful thanks! Without OBS I get 90fps nearly always, but OBS gives me alot of dips. I've been on x264, so I'll try switching to HEVC. Would you mind sharing your other settings for OBS-mirror and OBS? Mine are below, curious if there's anything I can change to reduce the impact on performance: Video output: Recording Encoder: OBS Mirror is set to right-eye only, and I've dragged it so that it cuts a bit off the top and bottom to fit in the 4:3 aspect.

Strange, the Munkwolf keybind is the only one I have for that control as well. I was testing on instant action and figured maybe they have easy comms on that may have blocked it, but just tried in a fresh mission in the mission editor and it still doesn't work. Tried both a key and a button. However using the comms menu will open the radio even in the air (works just like easy communications does). That's what makes me suspect the bind is broken, because usually the comms menu button will not be able to call the radio if you're in the air.

Will this be included in 2.9? Running the mod that fixes the cloud shadows is getting a bit tedious, because of the pure client IC now including shader changes, and the recompilation taking a long time whenever adding/removing the mod for pure client servers

Yep that's where I copied it from. Unfortunately the bind does nothing, only the comms menu works. No big deal I guess, it just looks shoddy to be inconsistent with easy comms turned off.

If you do #2, then you don't need to uncheck #1. I do similar - voiceattack joystick button to recenter mouse bound to the same button I use for the DCS bind for "show cursor". Then if I want to use something hard to reach with my head like the ejection seat behind me, or the A10 CDU then I just move the mouse and it takes over. Not sure if DCS ever patched this, but currently there's absolutely no problem having the best of both worlds as long as you re-center the mouse with a tool.

For DLSS I think the DLSS 3 framegen only works with HAGS on and only on flatscreen, VR will revert to DLSS 2.0 (which doesn't require HAGS). At least this is what I've learned from the MSFS guys. I've also heard that MSFS has an issue with the way they render the glass cockpits, so if DCS does that differently to MSFS maybe our MFDs won't have the same blurry text issues that MSFS has with DLSS. Fingers crossed! A side issue is enemy aircraft spotting/scaling will get worse as we up our resolution in our headsets for this tech. My hope is that DCS fixes the aircraft scaling as well to cater for such high supersampling and DLSS technology. In the crystal when running high SS on the center portion the "pixel dot" that represents the aircraft becomes invisible ie its lost in the process of SS and up/down-scaling. Even with the contact spotting "dot mod" it doesn't really work because of the extra DFR supersampling. I don't have the same problem in IL2 as that doesn't use a pixel/dot system to represent distant aircraft, I believe they simply scale the size of the aircraft more appropriately the same as other objects are scaled (like terrain etc) as we get further away. They've done a great job to be honest in fixing spotting and DCS should look to IL2 GB when fixing this to find out why the difference is so vast.

So we still use the "communication menu" button to transmit as if it's an FC3 low fidelity module, or as if its on easy comms? If you add the bind for transmit it doesn't actually trigger the radio menu: {cockpit_device_id = devices.RADIO_RSIU4V, down = radio_commands.Transmit_Btn, up = radio_commands.Transmit_Btn, value_down = 1, value_up = 0, name = _('RSIU-4V Transmit Button - Push to Transmit'), category = {_('Throttle Quadrant'), _('Custom')}}, I'm guessing the button is non-function, which makes it at odds with every other DCS full fidelity modules. The only one that doesn't have a PTT button...

Yeah QuadViews is some advanced tech, that we are thankful DCS is willing to use. MSFS doesn't use it. I use balanced for MSFS but still it's much smaller benefit than DCS. The fact that they've announced MSFS 2024 instead of fixing/finishing 2020 first is a bit of a bummer but at least we have DCS willing to commit to the long term.

1) yes when you select load profile and browse the folder structure, you should be able to find your old bindings saved in Saved Games\DCS.openbeta\Config\Input folder. eg my throttle bindings are saved in the file "VPC Throttle MT-50CM3 {3829FD80-4545-11ee-800B-444553540000}.diff.lua" If there's two files named after your device, one will be the old bindings that you had an the newer one could be based on the new ID after changing USB assignments. Usually the one with larger file size is the one you want, in any case take a backup and can try again if you pick the wrong one. 2) Yes MSFS ensure you have eye tracking turned on in Pimax software, and in PimaxXR companion app. Then running MSFS with OpenXR toolkit (ctrl F2 to open) enable it and the preset eg "balanced". Quadviews setting won't even be looked at by the toolkit or MSFS since it only works in DCS and Pavlov, it won't hurt anything either. Mine is on always.

Losing control inputs can happen because Virpil devices often get re-assigned new Windows device IDs when changing USB ports. Might be something in their firmware, because I have VKB, Virpil, Total Controls and Winwing which are all fine when changing ports EXCEPT for my Virpil throttle. Are your pedals also Virpil? The fix is fairly easy though but you have to do it for every aircraft you've mapped (and every other game/sim). In DCS controls menu, at the top of each device use the dropdown to "load profile". Do that for every plane and it's restored. The alternative is to map just one button so it creates a new GUID file in the Saved Games\DCS.openbeta\Config\Input folder. Once you see the new file you know the new GUID, so go and rename your old Virpil device to the old GUID. It's a real pain when you have alot of modules and other sims. For this reason I try not to switch my Virpil throttle between ports. You can leave Quadviews enabled all the time, only two games support it so it won't hurt other apps they just ignore it. The other options "prefer framerate.." and "lock to half framerate" will affect all apps though and need to be changed any time you want different.

I'm also trying to bind axis for the various HUD brightness controls as well as the two radio volumes among other things.

Did you have the stutter before eyetracking? I've noticed a stutter creep in sometimes after my PC has been running for a while without a reboot (like 1-2 days), then on a clean reboot it's usually ok. Can see the stutter in the FPS having little drops, still haven't narrowed it down. Kind of annoying to get this on a fresh new build with clean windows install, but I guess we run so many other apps/services we just always gotta keep on top of tuning it up. Let me know if any setting helps, I want to get it as smooth as possible even if have to disable some candy.

Yeah the wiki says a side effect of not seeing performance metrics correctly if using turbo mode (I think the QuadViews install has it on by default). https://mbucchia.github.io/OpenXR-Toolkit/other-features#turbo-mode The FPS should be correct though. If you get the QuadViews companion app you can test with turbo mode off vs on pretty quickly. As for turning on eye tracking and DFR, I turn it on everywhere. Other settings should only be set once though, like turbo mode. Also some settings should be turned off when using quadviews like DCS bloom and lense effects, as well as not using some of the openxr toolkit features that can interfere like FOV changes. Wiki of quadviews explains.

There's also the point of disagreement about the state the cockpit is left in after the default sequences, many of us have our own custom startup procedures so when we feel the need to use Autostart (I do that in between flights if I really need to get another beer or take a piss), then we can know the finish state of the startup is as good as our own startup would be. Having autostart be different to our own start means a process of trying to remember what the autostart misses, especially if we use autostart less frequently. Without customisation ability, it's much easier to just do it manually than to try and figure out what's not done.

Did some more flying with MFD planes, and the Hornet with the center MFD especially was a bit annoying for the neck. The button I bind to show the cursor (bound to the LALT C command), I also added a voice attack bind to move it to the center and then down 100 pixels. That gets around the issue of the cursor being where it was last time you used the mouse, and the 100 pixel offset helps your neck. Usually you won't be clicking up high anyway, so putting the cursor slightly below the gaze seems to work well. So I'm using a Hat Depress for this, hat left for mouse left, right for mouse right, up and down for wheel up and down. I only wish the mouse wheel command would work on a HOLD down basis, as turning on the JHMCS etc means you have to spam it to take the brightness all the way up. null

Great thanks, now the job of finding a spare hat switch that is not going to impact any particular aircraft.... Not sure if I will bind the scroll wheel as well, or just the 2 buttons.

Yeah I think if you use the mouse it stays where you put it for a bit, but once it disappears it will center upon reappearing when you push the joystick button. So Joystick button switching to mouse is OK. Mouse switching to joystick button is not OK, unless you wait for the cursor to disappear/recentre first. But I need more flying time to know for sure, haven't had time to do a full long mission with the new headset yet. Just been performance tuning and adjusting my default head positions in the settings at the moment.

It might even bypass OpenComposite entirely if you're using the MT exe

Eye tracking should be in the new version soon. Once you setup quadviews you won't need FSR etc. Currently on the beta I get 90fps with 200% supersampling on the centre eye tracked area, and downsampling the peripheral with a 4090 7800X3D. Resolution set at 3800x4500 (80% in oxrtk). For your system you may reduce the SS and use quadviews just for FPS purposes, but play around and see what you like. TallyMouse made a tool to help adjust quadviews settings https://reddit.com/r/Pimax/s/twXkSV0A01 54500

Just tested this with the Pimax crystal, binding a joystick button as left click. Currently you do not have to disable the mouse. I push the joystick button, which makes the cursor appear, then I move my head over MFD buttons and push the joystick button it works quite well. Then I moved the mouse and it worked fine to take over, wasn't disabled at all. I think this is quite a nice combo for MFDs & UFCs etc where you don't need to rotate knobs and just need alot of button pushing while flying, saves you from taking the hand off the stick to find the mouse.

Have you guys tried out the "button as left mouse" joystick bind I the UI Layer category? It would remove one step of the process, though I'm not sure if it still relies on actual mouse cursor position which probably still needs to move to the center of the gaze. I'm still setting up DCS on my new computer or I'd try it myself, maybe later.

Nice! Mine should arrive in a day or two. Will be my first time at VR in DCS, though I have tried with IL-2 in the past. I gave up VR because of too many compromises in previous headset and the overhype was a let down. I think the Crystal is the turning point where those that won't compromise on clarity like me can get started. I've got a 5800x3d CPU and selling my 3090 to get a 4090. With MT I can't be bothered changing CPU for a 5% difference because it requires a whole new build (motherboard, ram etc) but the 4090 will help alot. What FPS do people shoot for to get smooth in the crystal? Has anyone posted recommended settings for the crystal with DCS in OpenXR, Nvidia panel, and DCS settings? I'm starting from scratch so would be great to know a good initial setup.