omohat

To start the game in pancake mode use the force-disable-VR parameter: "C:\DCS World\bin-mt\DCS.exe" --force_disable_VR

There's at least 3 solutions posted in this thread as a workaround until ED issue their patch: Replace the oculus files with older versions Use Virtual Desktop Use SteamVR Have you tried any of these? I'm using method 1. and its working perfectly but I also tested method 2 so know its also working well.

While we wait for you to confirm patch date, any chance you can give us some indications of which 3rd Party VR software you're seeing issues with when testing the fix. I'm really really hoping its not QVFR and OXRTK

Here's another alternative while we wait for the patch (Meta or ED - whoever gets there first). One kind soul on Hoggit has saved and uploaded his client and run time files from v62: I've tried it and can confirm it works. You need to the following steps: 1 - Turn off Oculus VR Runtime Service 2 - Copy these files into your ProgramFiles/Oculus/Support folder 3 - Add the the missing app.asar file in the oculus-client/resources folder from your latest version of the oculus-client The only issue is because he didn't share his oculus-diagnostics folder, the Oculus Debug tool doesn't work as theres a mismatch between the Debug tool and the runtime version. Other than that, everything works as before Meta pushed their update. Hope this helps people.

Thanks - looks like HonsVR is the consensus. Its a shame Reloptix don't do Crystal lenses. I use their lenses with the Quest3 and they're a really good product.

Thanks for the quick response and confirmation. Last question - do you think the Samsung Odyssey face pad you're using gives more space than the 15mm Pimax Facial interface? Or was the 15mm facial interface just not available at the time you were ordering?

Can I ask what your prescription is? Just trying to get a sense of how thick your prescription lenses are. Mine are -9 and -8 respectively to fairly thick - hence I'm worried about the eye tracking.

Great catch - I haven't used the CK37 much yet so I didn't pick that up (I've been focussing on getting up to speed on the A-A and RB75). I'll fix it tomorrow and upload a new version

Just bought the Viggen in the recent sale and loving it so far! The CK37 is a bit intimidating to manage all the navigation and attack waypoints so to help I've created a MATRIC panel for the CK37 buttons (plus quick access to the kneeboard since that seems integral to entering the required info). https://www.digitalcombatsimulator.com/en/files/3335233/ Feel free to it and and let me know if you find it useful or think it needs any changes. *Edited to update the order of the B6 - B9 waypoint buttons and to make the layout a little more compact

I've created a MATRIC panel for the T-45C - it has most of the systems mapped that are needed to get the plane off the ground and back down again. Hope its useful for people. There's 2 version available a full deck with the DEP and both MFDs (for larger tablets) and a small version with just the DEP (for phones and small tablets). You can download it here.

Bit late now but I'll respond incase its helpful. I've just tried these out and they seem to work well. You have to install a driver for a vjoy device which gives you 8 additional axis (per device and I think you can have more than one device) which can then be assigned to encoders and sliders in MATRIC. DCS then detects the vjoy device and axis and you can map them to cockpit controls. I've been using them so far for cockpit lighting dials where a lot of precision isn't required so can't say how well they would work for e.g. tuning to a specific frequency (I think if you put a curve on the axis it should probably give you the required sensitivity for tuning radios).

I was surprised to see how little love the F-5E Tiger gets in terms of panels and dashboards despite being 6 years old (no helios panel either ) so thought I'd do something to rectify this. I've started putting together a series of Touch Portal pages for the F-5E. These are based on a 12x8 grid of buttons and are designed to work on ~10 inch or larger iPads and Android tablets (apologies in advance - you'll need Touch Portal Pro due to the large number of buttons). I've built four panel pages broadly around different phases of flight rather than concentrating on slavishly replicating each individual instrument panel: Page 1 - Ground: commands for starting the plane and taxing to the runway Page 2 - Flight: commands for the takeoff, cruise, and landing phases (radios, nav, fuel, lights) Page 3 - Combat: commands for A/A and A/G combat (weapons, radar, RWR) Page 4 - Simulation: DCS commands (views, comms etc) For now this is a purely passive dashboard - it can only send commands to DCS, it can't receive aircraft flight information or state information via DCS-BIOS. I plan to implement this in the future so I've put the required buttons for this in the panels however, the screenshots show whats not functional at the moment. That said if you can get this working, feel free to redistribute a version with the aircraft info. Full information on the download page (including which parts of the panels aren't functional for now and any other limitations/omissions)