Thundersmoke

And I'll owe YOU a beer or beverage of choice. Thanks for posting this. I too was discouraged by the blocked off mouse area and solving this may have me tinkering with mixed reality again. It was super frustrating having the mouse corralled by invisible boundaries and having to work around it. Cheers!

I'm on 4090, Quest 3, Virtual Desktop. Previously, I was on "Godlike" VD and 1.2 pixel density and stable at 72FPS with good cockpit detail. Now I'm getting the same detail, nice sharp cockpit labels and gauges, on "Ultra" in VD (a step down in res), at 80FPS at 1.0 pixel density in DCS. I'd also dabbled with DLSS off and MSAA 2x, but hated the shimmer. So far as I can tell, I'm getting much sharper DLSS performance which has allowed me to dial back resolution and increase framerate. I spend most of my time in warbirds so I live and die by the engine gauges and like you, they gotta be sharp. And since all combat is close-quarters dogfights, motion blurring and smearing is a no-go. It's not perfect, but it seems a significant improvement. I'm definitely parking my settings here for a while to further evaluate. I think people are going to like Preset J.

I love the module, apparently have low standards for textures because I think it looks fine, and is a ton of fun to fly. If I want to just joyride and have a relaxing flight, this will be my go-to. My problem is, owning the Apache, I'm struggling to find the tactical niche where I'd reach for the OH-58D instead of an Apache on multiplayer servers like Grayflag. (I guess there's a reason the U.S. Army came to roughly the same conclusion.) The only thing I can think of is if the MMS can lase while just baaaarely unmasked and the rest of the ship remains safely masked, which the Apache can't do. But it's a fun and solid addition to the stable and I'm glad it's here.

TIL! Thanks!

As pilot, I pop open the George interface, move it to the Hellfire display, short press right to LOAL, and then long press right a couple of times to Trajectory: Hi. From here, George won't have a target that he's lasing, and you may have to re-WAS the hellfires from your pilot position. You can confirm trajectory settings persist through this transition on the Weapons page. Just remember, when firing from the pilot seat, you're not using the "consent to fire" button that you normally use when letting George lase things. You're squeezing and holding the trigger yourself. Took me a long time to figure out why I couldn't get missiles off the rail as pilot. Doing it this way, I think you should be able to get them to launch regardless of your ACQ source. It's just that the source will get them pointed in the right direction to pick up the buddy lase.

OP, it'll take some practice, and definitely defer to Bradmick and other SMEs, but efficient approaches are possible once you get a handle on the flight characteristics. The general sequence I follow is: From cruise speed at low-ish altitude Simultaneously decrease collective and pitch up to begin bleeding airspeed Manage the collective decrease and pitch up to keep your vertical velocity indicator roughly neutral (you don't want to be climbing or dropping quickly) As you get below Effective Translational Lift (ETL) at about 30 knots, you're going to lose a lot of lift. If you have a haptic seat pad or force feedback, you'll get some buffeting feedback and you'll feel this transition. As soon as you feel it or slow below 30 knots, gently pull in more collective to compensate, and begin to lower the nose. Again, strive to keep the vertical velocity indicator neutral. Most times, you'll be wanting to arrive at a hover in ground effect (IGE) at 50' or less. This will help cushion you. As you progress through the different stages, don't forget to be trimming. Once trimmed into a hover, you can either slowly set it down manually, or go into hold modes and then slowwwly lower collective from there. Again, defer to the SME videos and practice, practice, practice. Your right eyeball should basically be pinned to the VVI to manage your vertical velocity throughout this maneuver, at least until you have the feel and muscle memory down. As you get better with it, you'll be able to adjust the inputs to modulate altitude in loop with all the rest of the activities. Just remember, below ETL velocity, you don't want more than -300 ft / minute on the VVI. There be dragons. I spent an afternoon on a single player map, taking off from a FARP pad, flying around the airbase a bit, and coming back for a landing. Over and over and over. It was well worth the time.

This might already be obvious to you, but just be mindful that there are few different places where you can enter laser codes, and which ones you manipulate will depend on what you're trying to do. Laser Spot Tracker (LST): Changing this code (for example, to match a JTAC or fixed wing lasing a target), will enable (from the CPG seat only, I think) you to search for their laser spot. On its own, it does nothing else. In Wags' video, you'll see he uses it to find the lased target, but then handles lasing for his Hellfires himself. Laser Range-Finder (LRFD): Changing this code changes the code of your laser. For lasing your own Hellfires, it needs to match the primary (PRI) code for the Hellfires. If you're lasing for someone else, it will need to match the laser code of their laser-guided bombs/rockets/missiles. Primary channel (PRI): This is the code that your Hellfires are looking for. If you're self-lasing, it needs to match your LRFD channel. If you're getting a buddy-lase, it needs to match the code on your buddy's laser. Ideal use-case: On multiplayer servers with heavy, integrated PvE air-defense (Grayflag, etc.), some objectives are very tough to crack. But fixed-wing with excellent targeting pods (A-10's come to mind) can remain at standoff distance, lase the target, and your Apache can mask behind terrain: As pilot, establish masked battle position within range of target Drop a target point in the general vicinity of the target; set as ACQ source (this points your missiles in the right direction, enough to pick up the laser). Match PRI missile code to A-10's laser code Confirm his/her laser is on WAS Hellfires Configure for LOAL, high trajectory (to get it over the terrain you're masked behind) Rifle (note that as pilot, you'll be firing with holding the gun trigger, not the consent-to-fire / pickle button) Very fun way to safely take out some otherwise hard-to-approach targets. Edited to add: I'm doing this from memory, without the game up, so folks can feel free to correct if I got anything wrong. But hopefully this gets OP into the right neighborhood of understanding.

For those with high-end Intel CPUs experiencing this issue, the solution isn't nearly so drastic: Getting DCS onto the right CPU cores and freeing up the others for the less demanding applications will sort you out with respect to stutters on high-end systems.

This problem still exists, however, there's a workaround: You can "Edit Mission" and arrow down to the target coordinates field, entering the Lat/Long manually. Then Xfr Mission button. That gets the munition in question off the rail, and in my experience, normal functionality typically returns to the Smart Weapons page.

I can at least report some of the bugs must still be present. Had 6 x GBU-54's and 1 JSOW loaded today. Was able to XFER SEQ PT to JSOW and launch. Then, after that, change program to the -54's, and was unable to transfer the same nav (target) point, unable to take command of the TPOD and slew around and designate to XFER TPOD, or anything else. Couldn't cycle between stores. Smart Weapons page became mostly unresponsive. I was able to change the laser codes in Sensor subpage and transfer those to the munitions (which I'd done beforehand since I was working with a JTAC). But when it came time to start using the -54's, the page was pretty much frozen. Tried undesignating, tried resetting SAFE/ARM, tried resetting TPOD, tried cycling to guns and back to clear systems, tried unselecting the munitions from the program and re-programming / re-selecting them in PACS, tried everything I could think of. Very frustrating to cold-start, transit to AO for 20 mins, and then be unable to release ordnance. Here's hoping for a lengthy list of fixes on the 3rd or whenever next patch rolls out. Alternately, I'd be happy to find that I missed a key step. But I've been doing it successfully before, so...? Only thing I did differently this time is I pre-emptively changed the laser codes on all the -54's while en route to the target point. Sensor -> enter code -> Xfer Weapon -> Next Store -> repeat for all 6 bombs. I won't be doing that again, and will instead just do 1 at a time in between each attack run. Maybe all that manipulation and cycling of stores somehow fouled them up.

Hey Nick, sorry for the sluggish response! I did not find suitable workarounds and I've since gone all-in on VR for now. Which means my expensive WinWing MIP displays and MFDs are mostly sitting cold and dark while I play (doh! lol) at the moment. I feel like we're right on the cusp of a mixed reality breakthrough -- maybe ushered in with the Somnium VR-1 or Varjo XR-4 headsets. Just couldn't get it good enough for now and now that I've tasted VR, I can't go back. Hopefully in a few months I can revisit the multi-display, mixed-reality setup, but for now I'm leaning into full VR with Voice Attack, VAICOM Pro and a couple little helper tools like DCS The Way.

Ah, good to know. I think I've given up on the mixed reality for the moment until Somnium or Varjo knock my socks off with a next-gen offering. I've since discovered Voice Attack and profiles that allow me to operate the MFDs with my voice. If my wife walks past at the wrong time, she thinks I'm playing a very expensive game of Battleship. T5, right B2, right R6, right L3, left etc. Lol But it's a little painful to have the MIP setup and now not really be using it. So I'm looking forward to the VR1 or XR4. My credit card isn't. But I am.

Just some food for thought based on a recent discovery / breakthrough I had this weekend. For $10, Voice Attack, the free VAICOM Pro plugin, and a community AH-64 profile allows you to do a LOT with just voice commands. I know this is well known around these parts, and I've been familiar with Voice Attack since back in the Elite Dangerous / Star Citizen days. But I had no idea it was this capable now, especially for DCS. Cold start, manipulating MFDs, directing George as pilot, weapons, entering waypoints, directing wingmen, the works. I started just casually looking at it for a few minutes, and within the span of an evening I was down the rabbit hole and blown away by the capability. Within a couple hours of installing and reading the guides, I was able to hop into the cold start training mission, cold start the bird, move to front seat, and direct pilot George to take off, navigate around, announce my inbound arrival at a different airbase, add said airbase as a waypoint, fly there, and direct George to land. All with my voice! During certain portions, you'll be chatty cathy, but it's really fun. Then to land, you slow down, use "Flight" mode to get close to the LZ, then use "Hover" mode and "Slide Left," "Slide X" commands to get where you want, and lower altitude down to 0 and he'll set it down. Just wanted to offer the thought in case you wanted to mix in some voice commands to take some pressure off of the HOTAS work.

So I have the WinWing MFDs & displays (x3) and I've been trying to export the F-15E screens. Works fine in 2D just using the winwing software, but in VR, the MFDs have the transparent backgrounds and are more or less unusable. Is this why, and are Helios graphics the way to block out the video?

Thanks!! I did some more testing last night and found out that I actually had the settings right / mostly right, and my problem was that I was testing with the F-15E, which has the idiosyncrasy of the MFD exports having a transparent background for some reason. Changing nothing else except going to the Apache and Hornet, they worked fine. It's still obnoxious because I need to choose different profiles for each. In 2D, the center MFD will stay dark if there's no feed to it (airframes with only 2 MFDs) even if I have Left/Center/Right specified in the monitor lua. Now I get a video feed and "missing texture" garbage in 2-MFD airframes if I don't delete out the Center display in the lua. Either way, I look forward to diving in deeper on the links you provided this weekend. Very much appreciate it. Now on to figure out the best tool for chroma-keying / greenscreening out a window to see my physical MFDs in mixed reality. I think OpenKneeboard is still the best workaround, but that will be for tomorrow. First-world new-simpit / new-VR problems!

I'm getting so close on this. Sorry to revive it back to the top! So, I've followed all the instructions and guides here, and I'm getting my 3 (winwing) MFDs exported while in VR. BUT. They're being exported with like a transparent background and there's game video being shown in the background in with the exported content. Anyone run into this specific issue before and / or have any idea how to solve it? Just to cover the basics: confirmed monitor lua file has correct native resolution and also tried with the "optimized" resolution to which Virtual Desktop adjusts things VR_allow_MFD_out_of_HMD = true is in the file In DCS VR settings, "Use DCS System Resolution" is checked In DCS settings, the monitor lua is selected and game resolution is set to the full height/width of all monitors per the usual multimonitor guides Thanks in advance for any help, it's driving me nuts!