Jump to content

Blindspot

Members
  • Posts

    97
  • Joined

  • Last visited

Everything posted by Blindspot

  1. You now should be able to simply create copies of your 1st group. This MOD should work for FC2 too.
  2. Got the same problem, but only when cockpit door is closed!
  3. In my experience in BS Hinds are best attacked from above "WW2 style". To get there ist the difficult part. You have to go in as fast as you can. If you are head to head try to lock one Hind and fire a Vikhr, so at least this one turns away from you for a short while. Fly around shells, do not fly constantly in one direction. If you are close enough use all your kinetic energy to gain altitude and fly something like a hammer head turn. While looking down on them, use your cannon and begin to speed up. In case you miss one, try to stay above turn around and never get too slow. This was the most successful tactic to me against AI Hinds in BS.
  4. You're right. I don't use it this way. S5 is "trim" and "lock target", depending on the Mode switch (throttle)... maybe I'll try.
  5. I've got an G940 and Win7 64 and I have no driver problems. I'm normally not a real friend of Logitech products (especially because of their software and drivers), but the G940 does not make any problem. To be able to fly the BlackShark, I had to remove the spring off the pedal unit because I didn't want to buy a fitness trainer. Beside this little modification I deactivated the "hand on stick" sensor with a small tape and found out that the best FF device settings for the stick to me are: - intensity: 100% - spring: 60% - damper: 150% - activate spring in FF games: no (change these settings within the settings dialog of the joystick device, they are not available within the game settings) Try this, maybe it helps you.
  6. So, I tested again today and ... wasn't able to reproduce it either. :doh: What happend? I could swear that no wind setting or realism setting was the cause when I detected the "problem"! What I am sure I did was to misleadingly assume, that the speed in the HUD would never be ground speed. But ok, that's no fixed wing aircraft, maybe it's because of that. So, I'm sorry and I thank you for your answers and warm welcome!
  7. Dear ED and forum audience, the airspeed gauge, the hud and the ground speed output in the ABRIS are always showing the same speed, regardless which altitude flying. This is not possible in real and therefore I think is is a bug. On the other hand, the higher you fly, the earlier you get the over speed warning. So, there must be any indicated-/true airspeed/groundspeed calculation internally. But why is it obviously not shown on the instruments? At third, (and maybe this could be my own misunderstanding) why the hell do you get the overspeed warning at lower "indicated" airspeed when flying at higher altidudes? Isn't overspeed because of a possible rotor clash or stall situation and isn't this subject to the forces of the flowing air?? So, if the impact of the flowing air on the rotors falls when the air getting thinner (relative to real or ground speed) so why are the rotor blades bending like in "thicker" air? Kind regards, Blindspot
×
×
  • Create New...