wju

FYI: https://www.nytimes.com/2024/12/08/us/navy-pilot-brain-injury-topgun.html

the issue is not global/local but the behavior of UI-layer; i.e. you have to define all modifiers from all modules also in UI-layer to make settings behave correctly

not sure if it is intention, but as said in title: modifier defined in module is ignored by UI layer until is defined also within UI an example (see screenshots below) in module: custom modifier: VKB_BTN42 buttons binded: VKB_BTN42+JOY_BTN21 VKB_BTN42+JOY_BTN23 VKB_BTN42+JOY_BTN24 VKB_BTN42+JOY_BTN22 in ui layer: no custom modifier buttons binded: JOY_BTN21 JOY_BTN23 JOY_BTN24 then working butons are JOY_BTN21 - from UI JOY_BTN23 - from UI JOY_BTN24 - from UI VKB_BTN42+JOY_BTN22 - from module not working: VKB_BTN42+JOY_BTN21 VKB_BTN42+JOY_BTN23 VKB_BTN42+JOY_BTN24 these last three combos starts to work only when modifier VKB_BTN42 is defined in UI-layer, even though it is not used in UI. Is it intention? I use only two modifier DCS-wide, i.e. it is no problem to add it to UI, but some pilots may need more... thank you for your attention

VR is hardware, truth; regardless most of VR´s problems come from its SW implementation. On the other hand, VR capability is DCS´s the core feature for all VR pilots.

significant CPU boost in my favourite CPU_Test mission, i.e. FW190A, Normandy Quick Action, Airfield attack - just before attack well done!

please do not forget to share your frametime numbers after upgrade!

No, I have 3080Ti &12GB VRAM OpenXR overlay shows "used VRAM", whatever is means..

thanks, I just wanted to know, how bad is my "stone age CPU" (intel i7 7820X 4.7GHz & 32GB RAM) Since this spring, I am hesitating whether wait another "two weeks" for multicore or go to CPU upgrade. the screenshot is with the same DCS settings as yours, OXR 100%, toolkit - all improvements off; I am pretty CPU bound here

would You be so kind and share Your settings? (i.e DCS, OXR..)

thanks, very nice.

would you be so kind and share more details? I am very curious...

well, my espruino based "very ugly proof of concept" version is working! (left finger only so far, second espruino is on its way) the only issue was caused by my own stupidity; I have forgotten to plug bluetooth antena to motherboard and therefore spent two hours by thinking experimenting why espruino cannot be connected... As you can see, I have decided to build "ring" version with lipo battery (230mAh), as I hate gloves, battery can be smaller in the future, but this one was on my shelf the latching button swtitches on/off, where off can also be a charging mode; charging pins are not soldered yet. the only weird thing is when mouse becomes "white dot"; then it behaves oddly, i.e. moves with headset in oposit direction, (I understand why), but one can get use to it... anyway, guys @frenzon, @Sielu thanks for sharing!

ah, these I have also off

meaning the "HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Holographic" trick or something else? wired mouse version based on Arduino works fine, but the wire is annoying, maybe I am "the most ugly solution award" winner anyway, espruinos ordered.