Jump to content

lefty1117

Members
  • Posts

    160
  • Joined

  • Last visited

Posts posted by lefty1117

  1. 5 hours ago, frostycab said:

    The altitude thing is news to me. I've flown routes that I've quickly dropped into the mission editor, thus having all my waypoints up around 6500ft, but flown past them in NoE flight and the waypoint has cycled just fine. If you have to pass them within 100m of altitude (which is less than 330ft!) it would be a real pain.

    EDIT: I've just tested this, and altitude does NOT appear to be a factor, at least not for me. I placed a waypoint at sea level and overflew it at 4000ft. At 0.1km lateral range it sequenced to the next route waypoint. I also tried placing one at 4500ft and flew under it at almost sea level, with the same result.

     

    Thanks for testing.  I was sure that had happened to me, but must have been another factor in my case.  I immediately thought it was altitude.

    • Like 1
  2. If we're prioritizing things I think more stability at low speed/alt is needed.  The tail is way too squirrely for a twist rudder like a lot of us have.  I'm using an x-56 myself.  I don't know if there are more auto-hold options coming or if they are going to balance the effect a bit, but for me that's my biggest issue with control right now.  IN terms of the trimming, I think trim reset can cause an awful lot of trouble.  I barely if ever used it when I was flying the Ka50 for the reasons already described ... massive and immediate changes in orientation due to the "snap back" to default trim.  Better to quickly and incrementally retrim.

    • Like 1
  3. A follow up question on this topic - what's the best way to make use of the "fire at will" (long up) command.  Should he already have a target selected?  If not, will he search targets on his own?  If he has a target and destroys it, will he automatically move to another target on his own or do we have to direct him to select another?

  4. 40 minutes ago, dburne said:

     

    I think the rudder needs a bit of tweaking by ED, no matter the curves it has that jump to it.

    I agree with this ... or some accomodation made for twist rudder on sticks.

  5.  Maybe the alt hold will help when it's in but I think they're going to need to add a bit more forgiving parameters for the holds to take effect.  I don't remember the KA50 being so twitchy at low speeds.

  6. What are you guys doing for curves?  I'm using a Logi x-56.  The heli is really fcking difficult to control at low altitude and low speed, even trimming like mad.  It just feels oversensitive at that speed.  I imagine curves would help so wanted to get a feel for what people are doing.

  7. Click the COM button on the bottom right of one of the MPDs.  Then click the Manual button on the bottom row.  You can then select the channel you want to manually update by clicking it and then entering the value into the keypad on the left side of the cockpit.  Press Enter and you should see it updated on the MPD

    • Like 3
  8. I'm really pumped, I like what I've seen so far. I haven't gone this deep since I first got the A10 module a few years back and dedicated my entire 2 week christmas break to learning it!

     

    If the F15E ever comes to fruition, I'll finally have all of my favorite combat sim modules from my childhood represented here. Ok except for the Apache but I don't expect to ever see that one!

     

    Great work so far on the Viper

  9. LSS works... Hit UNCAGE on the throttle and it will start searching for the laser, same as in the Hornet. TGP screen will freeze and only the dot on TGP screen will be circling to find the laser.

     

    Have you confirmed this? Does it work in multiplayer?

×
×
  • Create New...