omohat

Ah ok - didn't know that.

I'm guessing this fix didn't make into yesterday's patch? I'm still finding the green (right wing) light won't switch off.

Yes because when I'm using TACAN for navigation the ADI is showing the yellow course line correctly (selector is "up" for TACAN). When I want to switch to VOR or ILS I move that selector to the bottom VOR/ILS position

I'm trouble with a few of the instrument navigation tools and despite checking the manual and youtube I just can't figure out what I'm doing wrong. Issue #1 (F1CE & F1EE) - VOR/ILS I can tune in a VOR/ILS station (correct frequency and VOR to Marche). I can hear the morse code from the station (TACAN volume is turned off so it has to be the VOR/ILS station) but I can't get the VOR station bearing to show up on the IDN (in the CE I've selected VT mode and in the EE I've selected RNAV-N and switched the Narrow needle selector to VOR). Despite this, in both the CE and EE the VOR needle stays stuck to N indicating it's not picking up a signal (despite me hearing the morse code from the station). As a result I can't intercept the glidescope for an ILS approach. It's driving me nuts. What am I doing wrong? I've got no problem tuning and navigating off TACAN stations (including course/omnibearing and using the Autopilot to "catch" the omnibearing course) Issue #2 (F1EE only) - TACAN offset I can configure TACAN offsets in the CE fine but in the EE no matter what i enter for distance and angle, when I switch to RNAV-VA it doesn't seem to reflect the offset distance and angle in the IDN. Not as annoying as the above issue because in the EE I can always configure an INS waypoint for the offset position but i don't understand how I'm doing it correctly on the CE but same thing on the EE doesn't work. Any ideas?

I literally came here to report this bug with the right (green) light no switching off. Glad to see its already in hand - shame we'll have to wait ~6 weeks for a fix. Just going to have to remember not to turn on any lights while on a PVP server.

So as an example I have a SP offline mission I've created where I'm looking for bombers about 80 miles away. With a human WSO its no issue - he puts the radar into 100 mile and then starts working the gain until we can see some faint returns. We then head towards those returns until the target is close enough to lock and then we can start tracking and setting up for a missile shot. The same mission with Jester I've got no way of locating targets beyond 50 mils. I understand you don't want pilots "playing WSO" but perhaps something in the Jester menu to convey context to Jester to get him to change his normal behaviour rather than outright commands? e.g. "Looks like our bogeys are a long way out" = Try 100 mile search? or "Bandit is closing fast" in Boresight or Cage = Set Aspect knob to Nose or Fwd and you can introduce a little randomness into it to convey the fact that its a team working together rather than the pilot treating Jester like a command menu wdyt? Keeps the immersion while allowing us to guide Jester a little more to what we want?

Is it just me or is there no way to get Jester to do certain things with the radar like put it into Boresight, set ranges other than 25 and 50 (like 10, 100 etc), or change the Sparrow aspect knob in order to be able to constantly see target heading closure etc. Is there any way to get Jester to do these or only a human WSO can do these things?

So I have a FFB stick and I was facing this issue that the trim setting was having no effect; the trim indicator was showing full nose down trim but the plane was pitching up violently unless I applied3/4 forward stick pressure (checking the external model showed that the stabilator was not moving with trim adjustments despite the indicator in the cockpit moving). Disabling Force Feedback on the Mics tab solved the issue but I've lost force feedback effects natively (which I did have before). Luckily I can still use an external program to generate FFB effects (VPForce Telem) but this feels like a bug somewhere in the FFB implementation.

Thank you so much for this! Its such an improvement over the standard cockpit - so much more readable. No longer feels like I'm sitting inside Darth Vader's jockstrap Any chance you're thinking of doing an english version of this - that would really be the icing on the cake

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)