Floyd1212

They have certainly been working on other aspects of the module, and I think the FM is very workable where it is right now. There are known issues, like the crabbing mentioned above, and rolling to the left when diving, break-out values for the hold modes, etc., but they recently gave us the FCR, and DL, though those are both still not working fully in MP. The upcoming LINK and C-SCOPE will be very nice. Assuming they do come back to the FM and tweak it further down the road, I'm okay with it for now. I am concerned, however, that making some of these adjustments will mean compromises elsewhere, and they have gotten themselves into a situation with the FM where making these small adjustments is not easy, and will upset other aspects of the FM. Or else, like you suggested, if it were an easy fix, why haven't they made the fix(es) already?

Still getting double entries in the DL group when adding members from the MBR DIR. Still receiving double messages when they were only sent once. Still getting NAK messages despite the messages being received.

Ah yes, that was one of the guys I was flying with. He said he spawned into a Huey and it just blew up. According to the RotorHeads Discord it gave you a TK as a result. Anyway, try out your Limas again tomorrow and see if they are working properly again.

I was flying on RotorHeads at the time when you said this was happening to you over the radio. I don’t think there is a problem with the missiles (we were using Limas on the server around the same time), but on that server your guided weapons (aka hellfires) are rendered ineffective after you have accidentally TK’ed a friendly unit. Did you return to the FARP to clear your name after TK’ing that friendly UH-1H at 9:21 pm? Maybe something else was going on, but I’m guessing that was it…

And maybe some other bug fixes we have been patiently waiting for?

In addition to WAS’ing the gun, make sure your HMD is the active Sight.

Tomorrow, maybe?

Does this work if the PLT is using the FCR and has radar returns, and the CPG is using the TADS and can then slave to the NTS by setting FCR as the ACQ?

Keep in mind that while in a continuous scan, the FCR will maintain the same heading, regardless of what direction you turn, or what you tell it to do. I don’t use the manual slew controls on the top of the FCR page, but normally use the TADS as ACQ, or PHS. (This is assuming you are using it from the back seat.). If ACQ is set to TADS, I have George slave to my LOS and then do a single scan. Or, if you have a human CPG using the TADS to search for targets, I use the FCR with my PHS so I can scan independently from my CPG. To get the FCR to stay forward, I think you might be able to set FIXED for the ACQ?

Yeah, like SharpeXB said, re-calibrate that axis in Windows.

Welcome to the forums. It shouldn't take much right pedal to counter the torque of the main rotor after unlocking the tail wheel, but it does take a little. If you leave the rudder axis at 50%, you will get some left yaw as there is still some pitch on the tail rotor blades at 50%. What trim option are you using for your pedals (twist stick)? Any curves on that axis? No other devices bound to that same axis? Is your twist stick showing up as a single axis that rests at 50%? When you pull up the Controls Indicator [RCTRL+ENTER] and you aren't touching your twist stick, are you saying that the rudder axis is pegged all the way to the left? A track file, video, or even screenshots can go a long way to help us troubleshoot your issue.

Don't you just enter one freq, then enter the other one, and it pushes the first one you entered to the secondary position? Then cycle between them as needed?

I have seen this before, as well. The message “TEDAC Unavailable” appears at the top right corner of the screen. If I remember correctly, I swapped to the front seat and wasn’t able to get it working either, and restored into a new aircraft. I’ll save the track if it happens again.

After looking at it again, maybe a Chinese HJ-10, based on the square shape of the launcher? Looks like some footage from some other ATGM found its way into that video.

That looks like a TOW missile. Wire-guided, not anti-radar. https://en.wikipedia.org/wiki/BGM-71_TOW

As a workaround, if your CPG deslots, and slots back in after the FCR is fitted, he will see the FCR properly. Of course, don't forget to cycle the rotor brake for him...

I wasn’t following SOP.

I have an issue with George not rifling on occasion, but it’s hard to say if it is the exact issue you are seeing or not. In my case, it is often after a rearm, and George will say he is engaging, but there is no missile constraints box visible in the HMD, and no missile comes off the rail. The solution is to SAFE the aircraft from the back seat, at which point George immediately ARMs it again, and all is working again. This may be due to having Ground Override turned on when landing to rearm, and some desync with the front and his laser not working.

We typically use FM1. We will try VHF and see how that goes. Of course, they should all work the same, right? With range/reception being the differentiating factor between them?

We definitely ignore the NAK messages, but we still consistently see plenty of other issues. Double messages received RQST for PP not always working some team members receiving data while others do not (and we are all still sitting on the tarmac together) data not being sent from the CPG, but the same data works when sent from the PLT

@BIGNEWY Can you confirm that someone is looking into this?

How much time/space are you giving yourself to transition? There's the "slow and smooth" approach, which should mean gradual adjustments all the way to hover over a longer deceleration, but shouldn't be too much drama. And then there's the "stand it on its tail" approach, which requires large amounts of collective and pedal right at the end as you are coming to a stop. I personally do a trim reset before starting the transition, and don't trim again until settled in the hover. This is not the recommended method, but that is the way my muscle memory is set, and holding the FTR during the whole transition would be a much different feel.

Let me start by admitting that I did not read all 73 pages of the thread, so forgive me if this has been addressed already... I am trying to troubleshoot an issue where teleportToPoint of a group results in the new group not respecting the "Hidden on MFD" setting of the original group. Is there a var I can pass when calling this function to keep the new units hidden? For example, in the Apache, when I enable SHOW > COORD SHOW > PLANNED TGTS/THREATS the enemy SAMs are displayed on the TSD. When I enable SHOW > COORD SHOW > ENEMY UNITS Control measures for other enemy units are shown on the TSD. This shouldn't be happening if Hidden on MFD is checked for the unit group in the ME, which it is for the original groups being teleported. Any suggestions on resolving this?

Sorry, what I was describing was the correct way to do it in 2D, which is also how it is shown in the manual. I was only pointing out to the OP that not only do you have to get your head on-axis with the BRU (bullseye pattern centered), but you also have to have the HMD looking straight down the tube (LOS reticle aligned with the bullseye). In his original post, it wasn't clear he was achieving both of these at the same time. VR users that render the IHADSS in both eyes do run into trouble getting things properly aligned. There are other threads that discuss techniques for this, including the "cross-eyed" method.

Don't forget, the LOS reticle on the IHADSS (the cross in the middle) also has to be centered on the bullseye, while the bullseye is centered in the tube. Is that what you mean?