Xupicor

So it generates and inserts a local carrier frequency to make a signal audible for beacons that transmit "sans carrier freq". Alright! That makes sense. Does it work in DCS? Can we set up such radio beacons in ME?

If that's true, that's the first I hear about it, and I own it for a while. You can toggle the LEDs, but auto light up based on deflection? Of which axis? Good luck with your curves! I'm going to continue flying without them.

I know BFO refers to Beat Frequency Oscillator. It's a type of oscillator, it can be used in a given circuit to generate a signal of some needed frequency to do... Well, stuff. Depends. What does it do in the Huey? Is it supposed to be part of a frequency shifter making morse code in ADF radio audible? (Doesn't seem to work like that in DCS) Is it generating a constant tone heard when tuning a radio? (Not sure I can hear anything like that) Responsible for generating a carrier frequency? An own "beacon" frequency so that one Huey can be a Pathfinder and the rest can tune their ADF to its signal to follow? I couldn't find much about what it's supposed to do (mostly interested in the real thing, even if DCS doesn't model it).

I would like that too. Currently have it on an on-off-on switch, but a potentiometer would probably be nicer.

I've since played online in the Hornet and had no problems, but then I would get very subdued sounds in _some parts_ of replay tracks. I also went through them at x60 or so in order to get to the fun parts first, so I don't know if that was the issue. I've purged the tracks since then. (They were quite big) It seems intermittent or reliant on some combination of happenstances for me. I don't know how to replicate it, and it doesn't happen often. Only happened that one time in actual game (multiplayer) outside of the replay system. I've followed your instructions - here's my sound.log: sound.log.zip

Same problem here. In replay mode when in F10 map view the mouse will keep going to left top corner UNLESS it's on the top tool bar. There it works fine. The moment I move it on the map proper it starts to move towards the left top corner of the screen.

I don't think that's just F1 issue. I had almost no sound with a full AB in the Hornet today. That's something more general I think (though I do have the F1).

Yes, I did, works exactly like on the video. Just to confirm it again, I did it right now with "Georgian Standard" skin you get when doing Instant Action Cold Start on Caucasus.

Pretty sure it happens with default skins just as well.

It also happens in the Mission Editor. Easy to reproduce:

No worries, I'm happy it worked out for you.

I tried to muck about with but couldn't get it to work either.

So, that's in the in-vr menu resolution override. OK, using that and your resolution value I can see performance gains - though the image quality is affected (as expected). For the recommended value you mean OpenXR Tools for WMR -> "recommendedImageRect? Mine shows 3152x3088 which is indeed the default value in the in-vr menu. Alright, I can work with this info. Thank you. edit: @mbucchia thanks for the link. I have a question about this part: Is that the other way around? In a multiplayer training server with some things going on but relatively empty, I get around 45fps on the ground, app CPU is around 12500-13000, app GPU is about 16500. So I'm supposedly GPU bound according to the site, but FFR doesn't do anything for me. Even if I set it to Cull/Cull/Cull then the effect on framerate is negligible.

No effect for me. No idea why. Can you elaborate? Are you using "override resolution" in the vr menu of OpenXR Toolkit? Or are you talking about NIS/FSR?

Yep, I'm on 3080, absolutely no effect on my fps or frame time. It pixelates stuff, but other than that I can't see any effect on performance.

Absolutely no effect on framerate with FFR on my side. I've used the custom settings mode for 1/16-1/16-1/16 mode, and besides the fact that the whole screen is heavily pixelaterd I can't see any effect on fps or frametime at all. Is this implemented right?

Run "OpenXR Toolkit Companion app" and change them to whatever you need. I've got them on Ctrl+Alt+Numpad keys. The "down" shortcut opens the menu.

I'll try and see with the performance overlay, but 3ms would be plenty noticeable in framerate at around 50 baseline - it should go to around 60 then. In my case like I said, it's ether 1 or maybe not even that, since it fluctuates with or without enabling FFR anyway.

That's a good thing, though. It always gave me huge stutters wherever my fingers even went close to that slider. Heck, Sometimes a sudden head movement gave me the same! So the fact it's not shown anymore is a good thing. It doesn't dip performance!

Is FFR doing anything for you guys? I mean, I can see it work, I can adjust the settings, I see the two rings and everything, but even at max performance settings I can't see any impact on FPS. It moves maybe 1 fps up, but fps fluctuate for me way more than that over the time of a few minutes flying, so I can't say it does anything but make stuff look worse. Is there something I'm missing?

I'd second that - why artificially limit our options like that? I've got spare buttons on my mouse, why not let me use them? FIX: Open "....\DCSWorld\Mods\aircraft\MIG-21bis\Input\MiG-21\mouse\default.lua" Make a backup copy before editing. Look for this part: keyCommands={ {combos = {{key = 'MOUSE_BTN3'}}, down = iCommandViewTransposeModeOn, up = iCommandViewTransposeModeOff, name=_('Camera transpose mode (press and hold)'),category=_('View')}, }, Now, you can copy and paste commands from "....\DCSWorld\Mods\aircraft\MIG-21bis\Input\MiG-21\keyboard\default.lua", but you need to remember to change the "key" value from the keyboard binding to a mouse button. Like this: keyCommands={ --{combos = {{key = 'MOUSE_BTN3'}}, down = iCommandViewTransposeModeOn, up = iCommandViewTransposeModeOff, name=_('Camera transpose mode (press and hold)'),category=_('View')}, {combos={{key='MOUSE_BTN3'}},down=device_commands.RadioINTERCOM,up=device_commands.RadioINTERCOM,cockpit_device_id=devices.INTERCOM,value_down=1.0,value_up=0.0,name=_('Intercomm menu'),category=_('Radio Communications')}, }, In this case I commented out (using "--" at the beginning of the line) the whole "Camera transpose" command and added a comms command on MOUSE_BTN3. Keep in mind your changes may be lost on next (or any) update.

It wasn't an USB drive, it was system created partition on my system M.2 disk. Note the image I included in my post. This small partition still exists (but isn't accessible from or visible in Windows Explorer). Anyway, I installed a fresh Windows 11 Pro. A mistake, I quickly learned, because WMR wouldn't install correctly on it if it wasn't inplace-upgraded from Windows 10. I waved Windows 11 goodbye and installed Windows 10 Pro. I've moved my old Saved Games/DCS directory to the usual place and DCS loads it up just fine. Of course there's a plethora of other issues with trying to get WMR to work -and OpenComposite doesn't want to run now, which it did on 11... Stuff like that. But profile loading problem is resolved.

I was thinking about looking through all the registry entries that DCS is (directly and indirectly) using, but there's just way too many of that stuff as presented by Process Monitor. I didn't find anything by searching on some keywords in the registry either. Anyway, I installed a fresh Win 11 stable (refreshingly hassle free, but that's become more or less a given nowadays) and I'm on my way to setting everything up. I'll update when I run DCS.

They're not lost, they sit in the old directory. Just checked. I bet I can load them right back after the debacle with Windows installation is done. I'll report back. In any case, seems like the answer to the OP question is that there is no way to force DCS to use an arbitrary directory without using symlinks and the like. I mean, you guys would know if there was one, right? That's a pity, but oh well. For the moment, thank you for your time and attention.

I've found the same happen. Indeed, that setting is wrong. FIX: Open "...\DCSWorld\Mods\aircraft\MIG-21bis\Input\MiG-21\joystick\default.lua" Make a backup of that file first before you make any changes. Search for "Flaps". Change this: {down=device_commands.Flaps_TO,up=device_commands.Flaps_TO,cockpit_device_id=devices.FLAPS,value_down=1.0,value_up=0.0,name=_('Flaps 25 / Up'),category=_('Flight Controls')}, Into this: {down=device_commands.Flaps_TO,up=device_commands.Flaps_TO,cockpit_device_id=devices.FLAPS,value_down=0.0,value_up=1.0,name=_('Flaps 25 / Up'),category=_('Flight Controls')}, Restart DCS and it should work as intended now. I just tested it, so go ahead and try it yourself. You might lose the changes after an update (if they don't fix it), so maybe keep the instructions with the changed line handy. I'd rather change it again than plain replace the new file with the old one as you might undo some other fixes/changes that way.