jaguar56

Love flying the Huey and for some reason it comes fairly naturally to me. But the tailstrike issue is fairly severe. If the rear of the Huey gets anywhere near the ground, it seems to take the rotor off. Sometimes after landing it barely rocks back even when I know it is coming and have full forward cyclic, bye rotor. I thought it was just me, but I ran a search on tail strikes in real Huey's and no such problem exists. There was no discussion on it to be found anywhere. It would seem that if it were an issue there would be information on it. That points to the model. It seems the tailskid is just there for graphics. It might not be possible to "firm" that up, but there needs to be some way to protect the tail rotor. This could be why a lot of pilots consider the Huey a handful. This tail rotor issue is the only problem I have with it. And it's a big one. It is not fun to fly for 30 minutes to an objective that has uneven ground and lose the rotor ending the mission.

Watched it happen tonight. On Shadow Reapers Syria Modern - Had just captured Sharat and the strange vertical screen popped up from the downed TV Tower. It happened exactly when the field switched hands from neutral to blue.

Unfortunately, I don't have images. but another related situation is a "storm" pattern coming up a couple of times recently. Best I can describe is like metal filings to a small magnet. It goes up at least 1K feet in elevation and is quite large. When I first saw it, I thought it might be an actual sand or dust storm. I have also worked through the horizontal patterns that stretch to infinity. They look like the issue is related.

Just purchased the Apache module yesterday and use Q2. The offset was the first thing I noticed. So, I started a search on how to adjust it and found it was not possible. The Apache module is very deep and complex. And the IHADSS is a central function. With it being off it makes it that much more difficult to learn. Based on what I am reading in all the threads, every VR user is just enough different to throw this off. The user and headset that ED tests with got lucky and is right on track. But it seems at least 50% of us are not. Put me down as voting for the ability to adjust it. If it has been done in other modules it is clearly not asking for something impossible. These are expensive modules. It is not right that people can't use it properly due to this issue. Please stop fighting it and just make the adjustment possible.