Chaos_Out

Hey, @NineLine and @BIGNEWY. I did a quick test (quick as in can't provide a track yet until I get more free time tonight), and have more bugs type stuff I'm gonna write up later, but just did a quick flight test and wanted to let you know the boresighting of the mavs seems off and not "zero'ed" in a way to be used in combat without tinkering. What I mean is that every time I'm actually in range to use the mavs, I typically have to move the mav left to lock onto the object that the TGP is locked onto, typically within 10nm of the target, AKA even with the auto boresight, paralax is still a thing. So another way to put the question is, what distance are the mavs boresighted at? Is this expected use, for us to still have to manually adjust the maverick even after an "auto boresight" was done via hotstart, air, etc.

It used to be boresighted in the air or from hot start, but changed some time back to that they weren't. I don't know exactly when, but as someone who used to setup my missions specifically in air or hot start with mavs already loaded to skip needing to boresight, I noticed after coming back from a break that they were no longer boresighted. I gladly welcome back this option.

Without any explanation as to why people need to activate the "hand controllers" setting and what relevance it has, you might as well add "trust me bro" to the end of your post.

My issue is that I don't have any single binding that would work across ALL aircraft. Perhaps the devs forgot we don't have full access to a keyboard since we have our headsets on. Due to what some aircraft require, even my modifier is different across some aircraft, which can be a pain to recall sometimes (like coming back from my break), but luckily I've flown my preferred aircraft enough to where I can remember pretty quickly.

This actually has changed. There used to be an option for this in each aircraft, which IS missing. I just came back after a break and noticed none were working, and that the aircraft specific binding option was removed. @BIGNEWY Why were the individual bindings removed? There are some aircraft that I can't have the same zoom keybind for, so having an option for each aircraft worked great. This is now an all or nothing for me. EDIT: referring to both VR Spyglass Zoom and VR Zoom

I thought I saw on here that someone found a slightly modified version of reshade that actually worked with OpenXR. They had a link to the d/l. I didn't test it myself or save it (both file and post), but it might come up if you search the forums a bit.

This is something I've always thought could be happening, as I also have a terrible time with OpenXR in MSFS 2020. Every setting and resolution lowest possible and still stuttering. From you or ED? Care to be more specific?

I wouldn't call it placebo, when most of those user reports are simply "I use steamVR, no stutter, when I use OpenXR, massive stutter." I'm one of those that thought using SteamVR with a G2 made one use the SteamVR motion reprojection. I can say for 100% fact that going from SteamVR to openXR, while mimicking the SteamVR settings and optimization mods as best as possible, the motion reprojection and performance IS worse, in both clarity and stuttering, for me and others on here (yes, used openxr toolkit). I have better performance in single thread DCS using SteamVR than I do in multi-thread openxr dcs. I have a 5900X and 3090.

OpenXR has been nothing but a pain for me. I gave up on MSFS 2020 because i couldn't get it to not stutter in the cockpit, even with EVERYTHING set to low (including res). I tested it a little bit in DCS when it went native but instantly noped out of it since it was stuttering vs my buttery smooth and clear OpenVR experience. I can't for the life of me understand why so much focus is being put on it when the entire community is dependent on one person and their 3rd party app (XR toolkit) for OpenXR to really shine. Especially now, when if I recall correctly, the dev has stated they need to take a break due to personal issues or something. The vast majority of the community needs motion reprojection for VR to function and/or be clear enough to be enjoyable, and it's been stated that the MR of OpenXR tools and OpenXR toolkit (great naming btw) is very subpar compared to what the steam client offers. I've been using Skate Zilla's DCS Updater/Launcher to launch the DCS standalone version with Steam VR, but if that ever breaks I'll simply move back to the Steam version of DCS. Until I can use that utility to launch the MT DCS into Steam VR, or any method I suppose, while being able to use OpenVR, I won't touch it. Can you tell I'm frustrated?

Yea, this happened to me too. I forgot about this part, when I had mentioned no matter what I do, this was one of those things I tried. It always got stuck. There's some imaginary resistance/hump that it has to be forcefully dragged over to be able to move freely. For example, like the guy above said I bound my TMWH side slider to the wing sweep handle, and found that if I use it right when I land and forcefully move it over that "hump", the voice attack "macro" will be able to finish with the wing sweep and put it into EWS. The other thing I tried was using wing sweep aft (the one that is grouped with Auto/Manual/Bomb mode) to 68 degrees, and that was how the handle ended up stuck at 68 degrees. If there is no manual action to break that resistance, no keybind will work. With this post, I was hoping someone could explain why that resistance hump exists or maybe point it out to someone at Heatblur that this could be a bug. Does anyone know how well they monitor these posts, like say how Nineline or Bignewy does?

I fly VR and don't like using a mouse or keyboard if I don't have to so I use Voice Attack. I don't even have a keyboard by me when flying it's that good now. I'm trying to automate some things with Voice Attack, and sweeping the wings back to emergency wing sweep after a carrier landing is currently on my to do list. The issue I've found is that, no matter what I do, the keybind "Emergency Wing Sweep Handle move Aft" just shakes in the 68 degree position (Yes, I waited for the bags to deflate, tail auth warning to go out, flaps up, cover open, handle up, etc etc.). Even using the mouse wheel takes a couple of spins before it finally pushes over. Clicking it with the mouse and using a "forceful" drag has been the main way to get it over into emergency wing sweep. Is there a reason it functions this way? Is there any way to get a keybind to work and not have to manually mouse it into emergency wing sweep every time? Thanks for the help.

As others have said, use Chucks guide as a baseline and then modify to your needs. I try to make my control mappings across the various aircraft as similar as possible to avoid having to re-learn each time i switch aircraft, i.e. flare is always forward, chaff always back, etc. Since the harrier and F/A-18 have similar style controls (even same stick?), use that for reference as well when mapping the misc stuff on the HOTAS.

So, technically, no, you couldn't do that as I mentioned, because I specifically said "without messing with any radio settings or F menus." This is a simulation with built in shortcuts for people who don't want to deal with every little tidbit of a real aircraft. I have that shortcut activated with easy comms. Not a single other aircraft has this issue with this setting, and as the person above you mentioned That's been my whole point this entire time. I think most dismissed the easy comms part, since, by the book, a radio switch does need to be toggled. I'm not trying to argue how real life policy and procedure is executed. Now that I have a better understanding of what the problem is, I could probably just say that easy comms is partially broken in the Ka-50 III. Partially, because you can still talk to ground crew in the F menu without having to toggle the radio switch. Keybind toggling rearm/refuel is broken.

Are you saying you actually get the ground crew to acknowledge your request to rearm/refuel just using the basic/default rearm/refuel keybind without messing with any radio settings or F menus? You can go Ka-50 III -> Instant Action -> Runway Takeoff (Caucasus) -> (when loaded) LAlt + ' -> pick any loadout -> and then the ground crew acknowledges and completes your request? Yes, I got it to work using the F menu, not with the default keybind. I'm not referring to bringing up the menu. To be more specific, I haven't rebound anything, I've been using the default keybind of LAlt + ' and then use Voice Attack to bring it up. Even manually pressing LAlt + ' doesn't change the outcome. This is the default keybind used in all of my aircraft and they all work except for the Ka-50 III. I rebound it to a random MFD button to test that, and it still didn't work. I refuse to believe that this is the only aircraft that requires a button to be switched for the ground crew to hear you. It especially doesn't make sense when I can get them to rearm and refuel using the \ menu -> F8 Ground Crew ->F1 rearm/refuel, without touching a single switch in the cockpit. Edit/Update: When I set the switch to GRND, using the default keybind for rearm/refuel did work, however, since I use the easy radio mode, and have never had to adjust anything in any other aircraft, I still feel like this is a bug.

I have a keybind that directly brings up the Rearm/Refuel menu when I need to use it. This has worked for every single module I've used (a lot of them). However, when I use it for the BS3, the ground crew never replies and I never get any weapons or fuel. To successfully get the BS3 to rearm/refuel, I HAVE to use the F1-10 menu options "Ground Crew -> Re-arm & Refuel" for it to work. The ground crew will then reply and proceed to arm and fuel. Is this a bug or done on purpose? Tested in both SP and MP, easy radio mode (or whatever it's called). Again, only module where I am required to go through the radio menu to rearm/refuel. Thanks