Floyd1212

1) Sending them one at a time with RFHO seems to be the only way we have found, as well. I was also expecting to be able to send a whole set of targets, but maybe that is still coming? Maybe part of the LINK functionality? (I have heard the LINK function as having to do with linking the TADS to the FCR, so I'm not sure.) 2) Using DataLink, you can send over all of your targets points (and other points) at once, replacing the points the receiving aircraft has in their database. Wags shows how to do this in his video series, if you haven't messed with it yet. You can also select a single Txx point on your TSD and use XMIT to send it to a specific wingman. They cannot fire on this target directly, but can now use it as a DIR TO point, or as a ACQ source. Only RFHO sends enough info to your wingman for him to launch an RF missile while staying behind cover. One more note: After you perform your FCR scan and have a bunch of returns, you can use the TGT function on the FCR page to store all of the returns into your database at once, then use the DL functions to send all your targets to your wingman at once. Edit: After re-reading your initial post, it sounds like you are already sharing targets that way in your first part, so I'm not sure what you are asking in your second part.

I have seen drivers get updated in Windows to where the triggers suddenly become a single axis, resting at 50%, instead of two independent axis from 0-100%, and wondered if that may have broken your Joy2Key remapping. But it sounds like everything still works outside of DCS, so not sure what the issue is.

Do your triggers show up as a single split-axis, or as two independent axis?

Yes.

Yeah, I'm not sure Copilot is doing you any favors with that description. Try Googling the terms "settling with power" and "vortex ring state" that scoobie mentions above, and read up on those subjects from reputable sources. Also, don't ever reduce the engine power back from the FLY position (all the way forward). You can manipulate the collective as needed to fly the helo how you want, but leave the power levers alone.

@Raptor9 Can you ask the team to take a look again with the new info and tracks above? Thanks!

It's a known bug, that will hopefully get fixed one day. Another workaround that is mentioned in that thread when ground air is not available, is to move your cyclic around after starting the engine(s). The APU off/on method doesn't always work for me.

I think the official answer is that FCR is not fully supported in multi-crew yet. Coming soon.

Here are two tracks recorded specifically for this bug report, so they are very short and to the point. The XMIT NAK bug is reproduced here, in addition to a couple more bugs that are likely related to multi-crew. In the tracks, you can observe: #1 loads into first air-frame alone Orig ID is predefined in the ME as "11" Callsign is predefined in the ME as "1-1" #2 loads into second air-frame, and a human CPG joins him Orig ID is predefined in the ME as "12" Callsign is predefined in the ME as "1-2" #1 and #2 both switch Battery On and APU On #1 adds #2 to DL on Preset 3 FM1 by typing in C/S and ID, and sets TEAM and PRI for 1-2 #2 adds #1 to DL on Preset 3 FM1 by browsing the MBR DIR and finding 1-1 and adding Notice member 1-1 is added twice to the DL group. This happens when there is a human CPG in the aircraft. The second instance is deleted from the group, and TEAM and PRI are set for 1-1 At this point, DL is setup correctly for each aircraft. #1 sends #2 a text message The message is received twice by #2 #1 gets a XMIT NAK FM1 message, even though the message is received #2 sends #1 a text message The message is received twice by #1 #2 gets a XMIT NAK FM1 message, even though the message is received Hope this helps reproducing some of these issues. DL Bugs - 1-1 Solo.trk DL Bugs - 1-2 Multi-Crew.trk

Though it doesn't address your initial issue, if you jettison the stores that are now missing on that wing, the aircraft will get back in sync and will automatically step through the available missiles.

Because of the sideways force of the tail rotor, flying with the "ball centered" in "aero trim" will result in some "crabbing" through the air. This is common when transiting from one place to another well above the trees. If you straighten out the aircraft into a "nose-to-tail trim", you will have a left tilt in your flight to maintain a straight heading. This is how most pilots would fly when down in the trees and buildings so you can safely fit through tight spaces. If you search any of the terms in quotes above, you will find many discussions about this phenomenon in other threads, if you are looking to understand more. It should be noted that the current flight model exaggerates this effect some, so hopefully in the future it won't be quite as bad.

ALT Hold will not engage if you are pulling too much torque. Without more info on what you were trying to do, it's hard to say what the issue was. If the Guide doesn't help explain the parameters, post a track file and someone can take a look at what is going on.

I ran into this issue working on another mission, then made this simple mission as a test to verify the problem, and the problem persisted. I asked a buddy to check it out and it was happening for him, as well. The mission has 10 aircraft in it, each with their own DL IDs. When you load into any slot and go to the MBR DIR to add other members to a preset group, you should see 2 pages of members; 8 on the first page, and 2 on the second page. Instead, you only see one page available, showing you 8 members. The last 2 members would be on page 2, but there is no option to flip to page 2. If you add an 11th aircraft to the mission and try again, you get the option for the 2nd page, and it contains 3 members, as it should. The same problem repeats itself if there are 17-18 aircraft in the mission which should overflow to 1 or 2 members on a 3rd page, but the page is not available. Mission is attached for testing. Data Link MBR DIR Test.miz

The number of targets returned by the scan is displayed at the upper-right. Hopefully the Zoom function will make distinguishing these targets on the FCR page much easier.

If you go to the A/C > UTIL page you will see the FMC channels along the left side that you can enable/disable as desired to mess around without FMC assisting you.

Fair enough. I will admit my comments were made out of my own frustrations. I'm sure there are many hard-working people behind the scenes trying to squash these bugs, as well as bring us new features. For that, we are grateful, even if we occasionally have some sharp criticism to go with our gratitude. But... If you look at it from our perspective, we have a group of 8-10 guys that fly the Apache multi-crew, on both public and private servers, for many hours per week, and we constantly run into the same bugs. Not just one of us, but all of us. And not just on specific servers, but on many different servers. From our perspective, it is hard to believe that if ED employees were to do the same -- that is, fly the same servers the same way we do -- that they wouldn't experience these issues for themselves. I will gather some of my guys and record some tracks on a short mission to try and capture these issues early in the flight, and hopefully provide something useful for debugging. I will also extend an invitation to you, or any ED tester, that would like to fly with us one night, and see if you can experience any of these issues first-hand, out "in the wild", as we do.

It would be nice if ED would get 4 employees in 2 helos on the same server at the same time to test this. I can understand needing a track from a player for capturing some obscure bug that is difficult to reproduce, but how are you going to replay 4 track files from 4 players at the same time to see how they all interact with each other?

I also still experienced the exaggerated corrections after enabling ATT Hold while in a trimmed hover, before finally stabilizing and being rock steady. And when disengaged, the sudden change in attitude that needs corrective input with the cyclic to stay in position. No, I don’t have a track file from that last MP session. If I can grab a short track next time, I will.

I, for one, welcome the suggested "workarounds", until the problem is fixed. Especially considering it has already been 6 months. Those seem like better options than just finding another server to play on, or flying a different aircraft.

I wonder if a left-handed Alpha twist-stick on their collective would be better than using a twist-stick on the cyclic? I feel like separating it from the cyclic might give you more precise control, and you hand on the collective isn’t moving around much otherwise.

Yeah, that was what others were suggesting; check the axis binds, not just the button binds. Glad you found it.

Yeah, I think most would recommend replacing the WH base with a quality gimbal, and keeping the WH grip, if you like the feel.

I can now, thanks.

Yes, we get the NAK all the time, too. Two aircraft sitting next to each other on the pad; the message goes through, but we get the NAK anyway. Also, your second video is marked as "private" and cannot be viewed.

Are you both using “1” for your Orig ID? Each aircraft should have a unique ID and Callsign.