Smashy

From Wags' RFHO video: "For all FCR datalink communications, it will initially be regarding multiplayer. Once the FCR and datalink are final, we’ll then add this for AI Primary members." Hopefully most, if not all, DL bells and whistles make it to SP.

@Vox I just watched your track and also created my own mission to test and can verify I'm also seeing this problem. HMD reject is set to ON for all parameters and MIDS range was maxxed out. I have about a dozen contacts from ownship radar and they all appear on the SA format. The only HMD symbology I'm getting to show is the one for the TUC'd track. Perhaps @BIGNEWY can take a look and potentially move it to the Bugs & Problems sub-forum if this isn't how it's supposed to work.

Try playing around with MIDS SETUP page. You can get there from the HMD format page. Experiment with increasing range with PB14 and see if that helps.

Honest question - given the info in the FAQ, can you provide detailed info on the massive MP problems you anticipate?

I'm just starting up with the Apache and if I have to be honest, George as pilot or CP/G isn't terrible. The interface is clean and concise and does about 80% of what I need. He obviously isn't as good as a good human crewmate but he is probably better than a lot of randos you'd find on some of the busier MP servers.

I'm having problems getting George to launch a Hellfire in LOAL HI/LO. I'm guessing it's because I can't get him to switch his acquisition source to a point from the nav database so the target is always out of constraints. Is this just the way it is? It's not a huge deal but just something I'm curious about after fiddling around with it a bit this afternoon.

I have no idea but I'm now following this Hannibal Lecter-level topic.

Once you get the seat and head position dialed in, you can save it to a snapview. By recalling the snapview, boresighting takes a few seconds. To save a snapview: LWin + Numpad[1-9] then RAlt + Num0 to save To recall the snapview: RCtrl + Num0 then the Numpad key you used in the previous step

Is the Apache manual being done by ED's dedicated documentation team that was mentioned in the recent past? Whoever is working on it, amazing job. It's very well done and a clear improvement over some of ED's past manuals.

Serious question: why do people like you take the time and energy to look for problems and then make snarky comments in a way that is clearly non-constructive when there are so many things about this game to learn and enjoy? It's not as if you're conducting methodical tests to provide useful feedback to ED. Instead, it's almost as if you make a conscious effort to find faults and not have any fun. Life's too short for that and I truly wonder what motivates posts like this.

One possibility is you have a modifier+axis bound to UHF volume. Did you check your axis bindings?

Brilliant list, thanks for sharing these @wilbur81! I'm adding these to my podcast playlist. I'm always excited to fly the Hornet and listening to these kinds of interviews just feed that stoke. The way internet gladiators bash on one module or another in that "my dad can beat up your dad" fashion strikes me as extremely immature. It's boring to hear Viper guys bash the Hornet or vice versa. It's a video game and meant to be fun. Sure I have my favorites (Hornet, Huey, Mustang and now the Apache is growing on me) but all the modules I own have something to offer.

Will the ability to have multiple versions still be supported once the unified release hits? I use OB (with minor mods and add-ons) as my primary but keep a clean stable install to troubleshoot and test things if I run into problems to help determine if the problem is on my end or not. It would be nice to be able to do this going forward, if not with stable at least with a previous version.

I played with this last night and you are correct. My mistake!

I'm not sure if this is the optimal solution but this fixed it for me: Edit <DCS base dir>/Mods/aircraft/Uh-1H/Cockpit/Scripts/AI/ControlPanel/g_panel_page.lua Find the following line (appx line 42): local shift_X = -0.65 Experiment with the value to position the AI crew panel to where you like. My multi-monitor configuration has a horizontal resolution of 6144 and changing this value to "-2.80" put the AI panel where I wanted it. It will get overwritten when you update/repair DCS so save it in a safe place or look for it in <DCS base dir>/_backup.### to find it again. Hope this helps.