Muas

...unless you use the new 4096x4096 sized texture, now named pilot_f18_helmet_hmd.dds, which you can get from the default textures FA-18C.zip. New correct entry for the diffuse texture on the description.lua is: {"pilot_F18_helmet_hmd", DIFFUSE, "pilot_f18_helmet_hmd", false}; Only the default grey helmet will load, until campaign and livery designers update their custom textures. NOT A BUG.

I choosed the F-15EX, even though I fly the F-18 more often, but because it also has a spring loaded wheel for the radar antenna, and of course, there are a lot more buttons which are helpfull for VR flying. Yes flexibility is key. Thanks.

I don't own the device, I'm still trying to decide on which one... that's why. Yes, without the center spring it's a pain to operate, better to map two keys then... Yeah, I know the EX has that one, just don't understand why they didn't put a spring on the pinky rotary since (at least) the E was supposed to be a replica of the RL one. Anyway, thank you all for your answers.

How is the radar antenna elevation meant to be operated on the 15E throttle? I understand the pinky rotary is an encoder (not an axis, not center spring loaded), so I believe it will throw pulses for the down/up antenna movement. Does this mean it is a jumpy movement, not continuously smooth? Anyone with experience on this to tell how efficiently this works? Thank you.

I was starting to believe I was the only one suffering from this...

Only at close distance part of the arresting cable object can be seen (some face and without texture it seems), but as soon as the camera moves away a bit it disappears completely...

This does not have any effect, in my case. I came to the conlcusion that the headset is perfectly fine, this is just a stance issue. The slightest tilt in your head will be noticeable in the HMD, not in the horizon as it is supposed to be horizontal not matter your head angle. So either I get use to it, or try to correct it (or both), and the best for this is flying the Apache, with it's large HMD. I believe point 2) applies, in my case. The best way to confirm is to strap your headset on someone else, and see if the the same effect prevails. Who could foresee that VR would reveal such a thing? Now, the more I fly with HMD on, the more the effect gets less pronounced. Thank you all for your help.

These are pertinent issues, yet I don't think any of these really apply, because I don't see anything wrong with the horizon, in fact it seems to be perfectly leveled. Only the head mount display on the visor of the F-16 and F-18 called my attention, as their appear tilted. This first picture is what is displayed in my 2D screen, if I don't use VR. Everything is perfect here. This second one, is a screenshot taken when using VR. What is strange is that in the picture, it's the horizon the seems tilted counterclockwise, where the HMD projection seems leveled. But what I really see through the headset is the horizon perfectly leveled and the HMD projection tilted clockwise, as if the whole image we see in the picture was rotated a few degrees clockwise making the horizon leveled but the HMD tilted. I don't know how to explain this.

I just noticed this very same issue on my Reverb G2, only when I started using the HMD in the F-18 and F-16. I tried clearing the environmente but to no avail and I have my settings to Best visual quality... I think my horizon line is ok, it's only the HMD that shows as if my head is tilted a few degrees.

So why this only affects the HMD of these aircraft... never noticed any other issue... everything looks ok in Windows VR environmrent, can't tell about any other app, because I only use VR for DCS.

...and the same is happening with the F-16. no effect, still the same...

I can't get my F-18 HMD to align properly on the roll axis. No matter how I try to align it in the aircraft, it will always show tilted. This only happens in VR; in 2D it is perfectly aligned (pictures attached). Anyone else suffered from this? (i5-12400F, RTX 4070 Ti, HP Reverb G2 on WXR, no any other tools)

Kindly find below a link to a few recordings I did. The one where you see the cable animation is with no VR and single thread multi-thread (MT); the other two are with VR and MT, these are from the same track just one was recorded from the desktop. You see the cable disapearing upon trap, then reappearing in place after loosen from the hook. I tried VR in single thread and the animation still doesn't show, so it is not a MT issue, but it seems to be a VR thing. https://we.tl/t-dHqSmHZisg So it does seem not to be a MT issue. Either flown or played back track, the result is persistent: cable animation doesn't show on VR, but does show in 2D. NOTE: I edited my original text (hence the strikethrough) because I'm now aware that since 2.9 DCS_updater.exe is firing MT, being so, all my testing was actualy done in MT. So to wrap it up, in 2D the animation is rendered, in VR it is not. Carrier Trap VR.trk Carrier Trap.trk dcs.log

I'm using Windows Mixed Reality through DCS native openXR runtime (executable commands --force_enable_VR --force_OpenXR) in multithreading, but no other tools or third party apps whatsoever. My specs: HP REVERB G2, i5 12400f, RTX 4070 TI, 32GB RAM Later on I will try to record a track of a carrier trap from external view. Thanks!

I read somewhere it was fixed, but I cannot see the trapped cable animation anymore. Only when the cable is recovered to its position it appears again. Nothing is seen catching the hook or during recoil. I'm using Reverb G2. Anyone still seing this?

I have my 2D shortcut pointing to DCS_updater.exe, so to check for updates before running DCS.exe, and the --force_disable_VR option is not recognized by the updater executable. I believe it might work with DCS.exe, anyway with VR unchecked ingame it works perfectly. Thanks for the tip.

Simple. Now the "--force_enable_VR" makes sense: to be used when VR is unchecked within the game settings. That's just what I was looking for, one shortcut for VR another for 2D. Yes, I was missing the point. Thanks. I might try this anyway to see what else it brings. Thank you.

But to start DCS anytime just to un-check the "VR headset enable" selection in the DCS ingame settings, that's what I was starting to avoid... I will try this utility though, thank you very much.

I forgot to mention that starting using my shortcut (2) and closing WXR right after doesn't work because it closes DCS altogether... so what I'm trying to avoid is launching DCS just to switch VR ON and OFF ingame... Using the update utility... not really sure how to do that... and yes, it is that command line for a shortcut I was hoping for...

I have two shortcuts to run DCS through my single OpenBeta install: Shortcut (1) targeting "C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt\DCS.exe" --force_enable_VR --force_OpenXR which I run most of the time in multi-thread for VR; this fires WXR automaticaly and I'm ready to fly. Shortcut (2) targeting "C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS_updater.exe" which I run when there is a new DCS update, but Sometimes I just wish to setup some mission in the ME so I'd like to run DCS on my screen, no VR, but still, this option is firing WXR too, probably because I have VR "ON" in the ingame settings (I even wonder why I need the --force_enable_VR switch, because WXR starts anyway). So my question is: is there a way to setup some shortcut to run DCS with VR "OFF" so it doesn't start WXR automaticaly (eventhough VR is ON within the ingame settings)? Thanks.

I was about to ask this very same question, but found this... So it won't ever be possible to operate it by a centered rotary axis producing absolute values as per the F-15C? It's a lot slower to operate on a non spring centered rotary for it requires two movements, one to move, another to make it stop, not the best option to using it this way... I believe most of us will end up using buttons instead. +1

So that means that below a certain target the turbo goes off? Because the "turbo on" message doesn't stay there all the time...

Yeah, I think I didn't get it right, because in the overlay, the "missing target" message comes in the same place where "turbo on" appears replacing the latter, so I though it was related to it... yes, the target FPS is another feature. If I set let's say 60fps as target, then when low flying over forest, (F-15E, Caucasus) the "missing target" message appears, the fps comes down to 40/45 sometimes even less, and this is also because I have all the detais and shadows settings maxed out, I sure need to do some tweaking here. But the point is that if not using OXRTK/Turbo ON, I get much higher fps when away from the detailed objects. With Turbo ON, I can get stable 45ish flying high but still coming 30ish when flying low over dense objects areas. It's capping it too low, maybe I really need to lower the details settings. When flying time is scarse, I tend to focus on flying more than tweaking...

My experience with turbo mode was a bit of a let down... it keeps "missing the (fps) target", so I had to drop it down to lower figures than what I usualy get without OXRTK. Maybe I didn't set it correctly... so I ended up deactivating it, and currently it's the best overall results I get: no OXRTK no OpenXR Tools. Just WMR. This is performance wise, quality wise, I still have some small artifacts I would like to get rid of, like some trailing on exterior aircraft lights, and some "color ghosting" around moving objects. Engine exaust heat blur also looks bad, I will probably switch it off. Other than that I'm getting a very pleasant VR experience with WMR.

Same here. The best results I'm getting is using only Windows OXR, and DCS on MT. Anything else just degrades it. My specs: HP REVERB G2 i5 12400f 4.4GHz RTX 4070 TI 12GB 32GB 3000MHz