MetaMarty

I found out that my HOTAS warthog throttle has a nice unused friction slider that is configurable. I mapped it to the zoom function. It works fantastic, being able to instantly zoom towards the HUD or other place in the cockpit. :) The center detente is the normal zoom position, so you can feel where the normal zoom is. Anyone else has a good function for this slider?

The first time I tried this mission, I stayed low and found a line of AA in my path that completely destroyed me. I figured the clouds may be a way to stay out of trouble and decided to stay high as long as possible. Contacted JTAC near IP point 1 at 14000 feet and it gave me the tank column coordinates. I hooked them in the TAD and point the MAVs at them. When within 10 NM, I pointed the nose down to 15 degrees and engaged PATH autopilot. I don't know if the MAVs are supposed to work through the clouds, but after a TDS up short, the first MAV locked and I decided to simply shoot it through the clouds. I repeated this procedure 3 times, slewing the MAVs a bit each time. In total, I shot 4 Mavs and hit 3 tanks without a single shot in my direction. I never entered below the clouds. Mission score was 51. I doubt that this is how it should be done, but at least I killed 3 tanks. They never knew what hit them.

During the whole first campaign I believed the Abris cursor was way off from the cursor on the HUD. Turned out that the system is using the laser designator to find the distance and uses that distance to calculate the position of the Abris cursor. :doh: So to sum it up: If the Abris cursor does not match the HUD cursor, press to lock button on the cyclic to do a distance measurement.

Had the same problem. I actually used the mission editor to find out what I was supposed to do. The trick is that when you get reassigned to the rebel base, the message states you should attack the "facilities". That includes the 2 buildings. Shoot them with the gun and you'll get the message.

Ah, now I understand. I missed the upper part of the hub. Some feat of engineering. This also poses some interesting limitations on the flight envelope. I figure that using rudder pedals could be quite dangerous in high-collective situations, as it could push one of the rotors to dangerously high AOA.

In my model helicopter, the collective moves the entire swashplate up and down and the swashplate is not fixed to the shaft. I would not see in what other way you could increase the pitch collectively. Differential torque, as I see it, could only be created by moving the swashplates up and down independant from one another. But looking at the picture on the frontpage of the manual, it looks like the swashplates are pretty much connected to eachother by rods. This would totally inhibit independant movement.

I love the complexity of this simulation. I just can't seem to find an answer to this generic coaxial rotor question. Given the fact that there is no tailrotor, I figured the only way that yaw could work would be to initiate some kind of differential torque in the rotors. However, looking at the pictures of the rotor hub, it seems that both swashplates are interconnected with bolts, which would make independant movement impossible. I might be mistaken, but the only way differential torque would work as far as I know, is to lower one swashplate and raise the other one. This would maintain the cyclic configuration and transfer weight from one rotor the other. Although the blade pitch is visible, it looks like the swashplates are not animated in the simulator, so I can't study the behaviour while moving the flight controls. What am I missing here?