Nealius

Have you noticed any warping after finishing turns? After executing a turn and rolling wings level, AI will then slide a bit in the opposite direction of their turn, as if the turn overshot some predifined flight path and they're warping to correct. It's not an issue when the player is on the inside of the turn (as AI will slide away after rolling out), but when the player is outside the turn in parade formation it typically ends in a mid-air or near-mid-air. It's not unique to the campaign or Tomcat AI, but I've never seen anyone else bring it up yet.

I just flew this mission and oddly had no issues with AAR. AI warping laterally into me and causing mid-air after rolling out of turns in parade formation however.....

I can sympathize with the VR issue, particularly when trying to do combat spread without yardstick.

If the triangle is hard to spot, align the tip of the intake with an imaginary vertical line coming down from the apex of the RIO's canopy frame. That's roughly the same alignment.

Did a double-check and found I had my HI/LO/PAL/PLM bindings messed up

The "switch" being "Oculus set as active OpenXR runtime" setting? I tried appending the forced OpenXR command to DCS.exe and got "unrecognized command" error.

Would be nice to have the lock function automatically when the flap command is triggered, much like the gear lever lock in the Mossie and just about every other module that has one.

I'm lost on this OpenXR stuff. My Oculus client is set to "Oculus is set as the active OpenXR runtime," but I understand we need to add a command to the .exe properties to force OpenXR. Are those the only two steps for Quest 2? There's so many posts about complex dances with 3rd party software so I'm lost.

The diamond does a horizontal scan that cycles through various vertical positions when I enter VSL LO.

Anyone found the VR head position to be where the pilot's stomach would be? If I raise my head to match the headrest (which also seems massively huge along with the rest of the cockpit in VR) I'm staring straight at the canopy bow and can't use the reflector sight at all.

VSL Hi must be the one I thought wasn't working right, then. I could have sworn there was one mode where the diamond scanned vertically across the windscreen without going outside HUD limits.

I frequently have diamond issues with these modes as well. I'll have to go back to identify which specifically, but in one or two modes the diamonds never appear, in one mode the diamond appears, moves vertically up, then immediately disappears forever, and in....whichever scans horizontally it works as advertised. Previously I recall the diamond appearing and scanning in almost all modes, without vanishing.

Totally off topic but where'd you get that internal sound mod?

More complex and nuanced than common sense. Outside of stuff directly access from public DoD websites, unless you have a contact within the DoD to verify a document's security there is no way to verify it.

I first noticed it on the -40 and at that time it was egregious.

D30 appears to be partially fixed. At at certain LOD the artifact appears again, particularly on the port side. Note artifacting on the far Jug (HV-F) but not on the near Jug (HV-R):

I'm going to add to Urbi's criticism with two playability points: 1. TACAN doesn't appear to work, which makes naval ops a bit rough 2. Pitch trim is overly sensitive with inconsistent trim amounts (usually too much) being applied to taps of the trim hat

Anyone have documentation? I can't even find a copy of NATOPS for the B on the net. Only J models.

I use the Quest 2 with Oculus resolution set to max and DCS PD set to 1.0. The gauges are readable enough. For the ones that aren't I go by visual cues. The altimeter, for example, we only really need to see the ten-thousand and thousand digits (leftmost 2). The rest I just go by where the needle is on the gauge, much like a clock, since I know where 1~9 are on the face of the gauge.

I have a feeling most of us will be doing it the DCS way once it's released, like we did with the F-1. Active pause at desired dive angle, altitude, release speed, pickle, watch where the bomb impacts, adjust pipper to put it on the crater, note mil setting. Unpause. Rinse and repeat.

Where's the go-pill option?

Posting for help here since we still don't have a Mossie subsection in the Liveries forum (but we have one for the nonexistant Me.262.....) I've downloaded a few of the newer user liveries now that the template is out, but one of them is having this issue. Anyone know how to fix the bort numbers?

In attached track, the AI behave erratically when engaging a group of 3 Ju-88s, lolygagging about and shadowing them until they gain altitude after their low-level anti-ship run. If you reduce the number of Ju-88s to 2 in the group, the AI engage immediately during their low-level attack, which is the intended behavior. AI-Ju88.miz

It looks like we're seeing progress, but slowly and independent of forum discussions. It mostly seems to be people throwing attitude around in response to any skeptical thinking applied to the FM, with the FM silently being tuned to address it just like the excessive adverse yaw issue. Best to avoid bringing it up for your own sanity/faith in humanity and wait for improvements to come when they come. I've given up on any kind of civil discourse here.

I do the same with a waypoint, at 500' 300kts 7nm BRC, but that doesn't prevent them from climbing close to 1000' first before then diving to 500' and going direct to waypoint. This causes issues when breaking the deck, as the last aircraft launching violates pattern altitude for the first section in the break.