Brass2-1

The shortcut is unchanged, but I discovered in the DCS Log the following: 2023-05-28 09:08:41.775 ERROR VISUALIZER (Main): OpenXR exception: runtime is not available However, OpenXR does run fine in another sim.

Did anyone find resolution to this issue? I did not have it initially, but it has now popped up.

This issue has cropped back up, again failing to initialize DCS in the headset despite launching in VR mode. Also, the main EXE now launches in 2D mode, despite having 'enable virtual reality' checked in the settings. Any more ideas @SkateZilla?

That worked. Many thanks.

"E:\DCS World OpenBeta\bin-mt\DCS.exe" --force_enable_VR This is unchanged from when the shortcut functioned. Thanks for checking in, @SkateZilla

Hi all, this issue popped up and random over the weekend - no software updates, no hardware changes. When I launch DCS via a force-VR MT shortcut, it loads correctly in VR mode; however my Quest 2 fails to enter the game and only displays my desktop. When I command DCS through the non-MT BIN using the Skatezilla launcher, I have no issues (apart from losing MT, of course). Is there some setting, whether DCS or Oculus, which can cause this?

I wasn’t able to find a way to force Oculus. I’m in the same position, performance is much, much worse using open XR.

Has anyone else seen a larger performance decrease with the forced use of Open XR with Quest 2? My frames are dropped by half (72 to 36) in single or multi thread branches using Open XR and with worse visual quality. If there are any tuning/settings suggestions I would love to try them, the game is unusable as of now.

Yes, exactly that.

Hi everyone, back to the Viper and HTS after some time away. I got a new symbology I’m not familiar with; a “cone” that correlated with a SAM site but did not move when I changed my designation. Is this the Wingman HTS-designation from datalink? I wasn’t aware DL designations had been added to the Viper for A-G.

That is terribly clunky.

OP, I'm blown away by the difference this makes. Thanks for posting. My frame times dropped significantly (didn't note numbers), and my FPS jumped from ~36 to 46-55 on the Supercarrier deck loaded with jets and consistent 60+ in the air (Instant Action, PG). 3070, 12700KF, mild OC on both, 32GB RAM @ 4600.

Thank you!

Hi All, long shot here, but I accidentally dragged my FPS monitor out of the FOV and I'm not able to see it anymore. Is there a config file that I can edit outside of the GUI to move it back to the default position?

Undesignate does function to “undesignate” in A-G mode, STT and RWS(edit - see @Tholozor’s post below) but in TWS it serves only to cycle through tracks as stated above.

I believe you need more airspeed on the jet for the Doppler effect to work. Note the difference in Mach between your screenshot and the clear ones above.

I feel like TXDSG only recently started working between the Hornet and Viper, but it’s definitely cool.

Most people are dominant in one eye, much as they’re right or left handed. I believe that right eye dominant is also most common, so projecting an image to the right eye is ideal for most users. To test your own eyes, point at something in the distance with both eyes open. Close one eye, and then alternate. The eye which the pointing finger is aligned with is the dominant eye. I am very much left eye dominant, so I use the HMD in both eyes in DCS. Right only is nearly impossible to use.

This works for CCIP bombing as well.

I’ve asked several Rhino and one Growler aircrew about just this topic. In some squadrons there aren’t enough HMCS to go around, so they’re prioritized - it’s perfectly logical to me that an EWO would be prioritized in the Growler. In some cases though, the user simply does not want a HMCS for various reasons.

As recently as Desert Storm, as mentioned above, the Eagle community both had supply shortages of tanks which affected mission planning and also regularly jettisoned the tanks when entering WVR combat (as was often the case). IRL, the double-ugly or asymmetric twin-tank loadout is very common both on Legacy and Super Hornets. There are some rules imposed on flight operations by asymmetric stores in the USN NATOPS, for example not exceeding 12* AoA on approach (Legacy). A high-rate spin can be caused by exceeding AoA limits while in an asymmetric condition; but spin characteristics are relatively unchanged from standard loadouts. Aggressive rolls at low speed (Sub-225kts) are also to be avoided when asymmetrically loaded. Also of note, the FCS is crucial to maintaining flight stability when loaded asymmetrically, and a jettisoning of asymmetric stores is recommended in some FCS degraded states.

No issues here.

Thanks for the quick fix on this. I ran into this issue with M08 as well.

The next few months will be great for DCS NavAir.

I’ve flown missions 1 & 2 now, I’m throughly impressed. Well done!