Scuby

I was unable to reproduce it in the original DCS version. Meanwhile, I will update to the latest version: DCS 2.9.7.58923 and monitor if it shows up again. Although the above was observed after a cleanup, my feeling is it might still be an artifact of some shader madness going on.

Observed in Nevada (pictures) and Sinai (non-pictures). Following conditions apply: DCS World OpenBeta VR - MT Versions 2.9.6.58056 (04/AUG/2024) Instant mission, Nevada F-16, Free Flight (as pictures) Instant mission, Sinai F-16, Free Flight, seat: Ground Attack (observed) Reverb G2, Windows Mixed Reality AMD 5900X, 32GB RAM, RTX 4080 Shaders were cleaned up after updating to above version (so pre-start session) via the DCS launcher CleanUp button.

Actually, it appears it is unrelated to motion blur. Motion blur setting is off while these pictures are taken. Also shadow stripe effects. Pictures taken in Instant mission, Nevada, F-16, Free Flight.

Good that this was already reported (though three years ago in 2020!). Just noticed it during mission taxi on Ramat David airbase. Indeed the signs indicating the runway headings need to be flipped. To add: Unfortunately, more than one sign is wrong, e.g. not only the sign at intersection India, also at Juliet, etc.

thanks! this issue startled me a bit, but now it is clear.

In my opinion, this would be a very usefull feature for all DCS modules and support broader hardware (and DIY) compatibility. Perhaps in such way that it allows the user to determine and set the precise axis coordinates by a button, at which its (throttle) hardware position requires a detent to be. I reckon most likely for Afterburner for any model, and perhaps also for Idle. Perhaps as a part of the axis tune window? Can't wait for this feature to show up in the release list. Thread rated "5 stars" and set "to follow"

I'm interested in this too, only your answer may be interpreted both ways depending how you look at it So, could please you clarify for us if your measured 1ms advantage is on the OpenComposite side or the native OpenXR side? My guess here is that you meant: native OpenXR performance is better than OpenComp. Thanks mate.

DCS OpenBeta with OpenXR + WMR Toolkit + WMR + Reverb G2 appears to work fine.

Roger. Will see what I can do about that and if it translates well to video, while recording VR monitor output.

You might want to try the "OpenXR mod", which includes and allows to set FSR from its menu.

Jup no other dx devices are bound to any other axis, for both the pilot and cfg selection. Meaning probably causing this is a slight movement in hover by the AI pilot, which I was able to visually verify at low altitude daytime from the cpg seat.

I have experienced the occasional barrel roll - in 2.7 and 2.8 beta - to me it appears only when excessive rudder input is given (skid) while banking for a turn at "higher" forward speeds. When flying coordinated or slightly outside center - this roll never happens. I also frequently use the switch seats between back/pilot and front/cpg while in hover. What I do is always reset trim and then maintain hover, before switching to the front/cpg seat. When switching to back/pilot, I mainly focus on "catching" the yaw with the rudder since this will most likely be your doom if not stabalized quickly. Now I think of it, perhaps also focus on your collective lever position when switching to back/pilot. You'll want this to be (close to) the same as you have left it. Too much above or under original position might exuberate yaw and fcs effectiveness. Unexpected barrel rolls in the AH64 are super fun though... made me happy!

It appears that while in hover (switching seats from backseat/pilot control to frontseat/cpg control), the AI pilot ever so slightly moves to one direction instead of maintaining a steady hover. I have come to believe this has always been the cause of the reported TADS issue. I have not tested what would happen if (from the frontseat) the AI pilot is commanded to perform its hover... i.e. if this would stabilize it in space.

Good question! I'd like to learn what each graph color stands for exactly, since it was not directly obvious to me. I assume at least one for sim render and one for 3d render?

Hello! I can't figure out the following issue I'm encountering: When in CPG seat, with TADS sight selected and unslaved at 12 o'clock well within functional limits and with a stable hover (AI controlled), after letting go of my physical controls for the TADS cursor, the TADS sight always appears to continue slewing to the right (only horizontal movement). For the TADS cursor I have programmed the RHG manual cursor to my flightstick X & Y axis and I have experimented with various deadzones for the X axis, however even with big deadzones, it appears that the TADS sight still keeps slewing to the right with the same slow speed. Also no double axis assignments. I'm using a Virpil WarBRD base and do not experience any problems with the physical axis either as cyclic in the PLT seat, in any other DCS modules, or any other simulator for that matter. The axis are 100% jitter free. What could be causing this slewing to the right? Thanks for your help!