some1

Use lkg-release, beta will not work. Reinstall is not required, just restart WMR.

Yes, just switch to lkg_release as instructed in the link, that should help.

Recently Windows Mixed Reality for SteamVR has been updated with some internal changes to improve performance. It's been on the beta branch for a while, but now they pushed it into stable. Reworks how graphics buffers are shared with SteamVR, reducing overall GPU memory utilization in most cases However, this update seems to crash DCS when it runs out of VRAM. Best way for now I think is to downgrade WMR for SteamVR: https://www.reddit.com/r/WindowsMR/comments/tz5clr/how_to_downgrade_your_windows_mixed_reality_for/ Or try the OpenXR mod for DCS.

Standby lets you have the second frequency ready and flip between them with a single button press. Easier than to type the whole frequency manually, or switch between multiple channels to find the right one. It's more common in civilian aircraft. In DCS usually VHF and UHF are used to talk with other aircraft and tower. Others are seldom used because few aircraft have those, but every DCS airport tower has frequencies listed for every radio. The Hornet has two combined V/UHF radios. In real life, UHF is the military aviation range, VHF AM is the civilian aviation, VHF FM is the general military band mostly used by ground troops, hence why it's useful in a helicopter meant to work closely with other units on the ground (same with A-10). HF is the general use shortwave band which allows over-the-horizon communication. If you're wondering which aircraft has which radio, I've included that in my spreadsheet. https://forum.dcs.world/topic/275689-dcs-aircraft-spreadsheet-dates-equipment-capabilities/

Nah, that looks exactly like the regular Hornet power levers. They talk about customisation, so maybe swappable HAT/button switches like VKB is doing? Ah well, we'll know soon enough.

In other aircraft, when you press push-to-talk button, the comm menu will have label of the radio you have activated, for example in the Tomcat it's: In the Viggen, both FR22 and FR24 radios are just labelled "AM Radio", regardless of which one you use.

I don't think you need anything extra, there are default profiles in DCS already.

Personally in game I prefer to start the right engine first, because otherwise the left power lever will obstruct the clickspot for the right starter switch somewhat. As has been mentioned in this thread, British do the alternating routine, depending if it's even or odd day of the week, at least according to Ed Macy's book.

Whenever the rotor blades get near FLIR field of view, they cause image brightness to flicker. It's like there's some FLIR autogain always on, independent from manual gain control, and the bright blades flashing on the camera cause the whole image to darken. The blades don't even have to be visible on the camera feed, just looking slightly below the rotor is enough to affect the image. The image brightness stops flickering when I look straight down, so it's not a shadow. Here's an example how rotor blades look on Apache FLIR footage, they don't seem to affect the rest of the picture. https://youtu.be/1vp26PCZzBY?t=307 flirNight.trk

If you launch from cold start, you have to turn the radar altimeter on, it has been changed in the latest patch.

Looks fixed in the latest beta.

Yes, apart from fixed polarity the image still looks the same as I posted before the patch: https://forum.dcs.world/topic/295201-new-flir-rendering-system/?do=findComment&comment=4917158

Only the swapped polarity has been fixed. The rest is still "WIP".

Same for me, activity streams, like "unread content" button take forever to load.

I don't have such addon but my guess it would work without any problems. Technically it's just a wireless keyboard, it will perform the same actions as your regular one. Of course if you buy a bluetooth version then you'll need a bluetooth dongle for your desktop PC, but I see at least some of them come with a dedicated USB 2.4GHz receiver.

That's not true as I already stated in this topic. For me the new AntimicroX can't reconnect to the wireless controller after it had been turned on/off, something with which the older version has no issues. Though if you use it with a cable that won't be a problem.

That's weird. I have the latest Xbox series wireless controller and antimicro has no problems with handling the thing. It also detects all my joysticks including the most recent devices. Ultimately, the joystick programming interfaces haven't changed for years, otherwise your brand new controllers wouldn't work in 10+ years old games. In regards to wireless controller, mine turns off after ~10 minutes of inactivity, but I can turn it on again when needed and it is recognised again by DCS and antimicro. If you get annoyed by that, you can always plug the USB cable from the charger.

https://github.com/AntiMicro/antimicro/releases No need to install anything else, run the exe, assign keyboard buttons to triggers (I used B and V keys), assign those keys to TEDAC in DCS, done. It handles the triggers on xbox controller as separate axes, so you can press both at the same time and it is properly recognised by DCS.

AntimicroX had issues when my wireless controller turned off due to inactivity and it prevented it from turning on again. I'm currently using the original antimicro software, it's a bit older but does the same job and has portable version, just unzip, setup the keys and that's it. Joystick gremlin is more powerful and complex tool, better choice if you want to do more than just assign two keys to the triggers.

Mostly it's down to personal preference and subjective "feel". Just like some people are fine gaming on a console at 30 FPS, while some prefer 60 or even above 100 fps on their monitors. An animation at 45 fps is not perfectly smooth in 2D, and it's not perfectly smooth in VR either, but for some people it's good enough. Of course that's no taking reprojection into account. With reprojection you're technically at 90 fps, it's just half of the frames (or more) are interpolated by the headset software, with varying success. Even with reprojection off, some level of motion smoothing is always enabled as the headsets can update each frame with new position data in postprocessing.

The headsets are the same screen resolution, but for some reason they decided to change what is considered "100%" in G2 settings.

What used to be 100% on his G1 is now 50% on G2. Running G2 at 60% is already above the native display resolution and would equal 120% on Reverb G1. At least in Steam, but it's possible that OpenXR follows the same logic.

Very true, especially FFB pedals are even more of a rarity than FFB joysticks My pedals (Slav Device) have a damper and a spring that is relatively easy to remove, so I just take it out for helicopter flying and install it back for aircraft. A "damper+no spring" combo is great for helicopters but not very practical for flying fixed wing.

A trim feel system is incorporated in both the cyclic and pedals providing a control force gradient with control displacement from a selected trim position. A trim release switch allows momentary disengagement of the trim feel system. That's what Ah-64 manual says. The trim release switch is the one on the cyclic, there are no other switches on the pedals themselves.

What he wrote is unrelated to the previous post you quoted from MSFS guy. Jabbah simply explained how a v-sync works to you. But that's nothing new, every headset does that by default. And every monitor with v-sync on (but with more frame buffering). If a software reports 70 fps, then in the headset it is a mix of 11ms and 22ms frames and this is, in general, not a very smooth experience. "If you get a mix of 90fps and 45 fps the report will say 64 fps". What Jabbah said. However, his last sentence is where I see the difference on my system, and finally we're getting somewhere. Jabbah claims that with 12-20ms frame times you will get 45 fps. That doesn't work, I still see framerate in the 50s, 60s, 70s with OpenXR, and that, as Jabbah explained in the quote above, means the frametimes are still fluctuating. So whatever "soft" lock there should be around 45 fps, there is none on my system. And there are other people in this thread writing that they get 50-60 fps with OpenXR. That may explain why some people say OpenXR is noticeably smoother, while others don't see much difference. It's true that a locked 45 fps on a 90Hz headset may be a smoother experience than 70 fps unlocked, even without reprojection.