Jump to content

Hummingbird

Members
  • Posts

    4336
  • Joined

  • Last visited

Posts posted by Hummingbird

  1. On 10/22/2023 at 10:36 PM, bkthunder said:

    G onset rate seems slower and the FLCS response to control input is sluggish. The FLCS often can't trim for 1g and will stay at 1.1 or 1.2 for for a number of seconds. 
    Also, when centering the stick after a pull, the aircraft keeps pulling Gs by itself, slowly going from e.g. 9G back to 1.0G. So it looks like both the onset rate as well as the "unload" rate are slower. 
    The input lag is still there too.

    One more strange thing is the elevons deflect upwards quite a bit during pulls at all speeds, which shouldn't be the case since this would defeat the purpose of a relaxed stability airframe, which is to reduce trim drag and drag that arises from the displacement of tail surfaces. The elevons are there to initiate the pitch moment and then should stay mostly neutral for the duration of the pull.

    IMO this is still not a good representation of the real aircraft FM/FLCS combination

    I can confirm that the G-onset rate (aka pitch rate)of the F-16C has been noticably reduced, it was a lot more responsive before. Not sure why this was done, and I'm not gonna lie, kinda feels like 1 step forward and then 2 steps back.

    • Like 3
  2. On 6/21/2023 at 7:47 PM, fat creason said:

    Guys, there is no bug here, there's nothing "look at". The aircraft is perfectly controllable above 25 units and behaves exactly as described in the manual AND our pilot SME agrees with the current behavior. See the attached video and the controls overly for proof. I guess it bears repeating: the Yaw SAS change has nothing to do with rudder authority or high AOA controllability. Perhaps you're getting so slow that none of the surfaces work effectively? You can't expect to maintain controllability down to zero airspeed, that's not how aircraft work. I recommend you practice high AOA flight if you're struggling, it's not a flight model issue, it's a PEBKAC error. 😛

     

     

    image.png

    image.png

     

     

    It's during high AoA in hard turns, not level flight, that I noticed a lot of wing rock when attempting to apply small corrections in roll / bank angle using rudder only (didn't apply any lateral stick). That's what I don't recall  being the case last I flew a little over a year ago. 

  3. Finally got back to flying in DCS after a long hiatus, and noticed something different about the F14 right away. Specifically it seems a lot more wobbly when maneuvering at higher than 15 units AoA, eventhough Im only using rudder for roll here and not applying any side stick movement. I recall previously being able to roll without wobble at high AoA when using just rudder. 

    To me this is a big change to the FM, and it strikes me as odd to come so late. Was it really all wrong before and is it supposed to handle this poorly at high AoA when using just rudder for roll? Asking as it appears borderline pointless to try maneuvering at high AoA atm due to the unavoidable wobble. 

     

    • Like 3
  4. @Aerges Devs

    Do you have available the real aircraft's EM charts to tune kinematic aspects of the FM with, or are you forced to extrapolate/estimate here? 

    Just curious 

    • Like 3
  5. The 54A Mk.60 goes over 500+ knots faster when launched from 33 kft at a co-alt target 80 nm away for me. Resulting in a speed of 1500 KTAS (Mk47 C) vs 2000 KTAS (Mk60 A) once withing 10 nm of the bogey. That's pretty extreme.

     

    Also noticed that the missile will go into a super high lofting arc even against targets at relatively close range of <20nm.

  6. 9 hours ago, myHelljumper said:

    As said above, the video is wrong the aircraft is not having 17 °/s turns at these speeds.......

    We know the aircraft is over-performing in STR by ~10% at worst, but we already have a reworked FM version in development that resolved this issue.

    As soon as the reworked FM and FBW are ready we will release them and then you guys can compare the turn rates :).

     

    Ok, that's good to know. 10% can afterall be crucial in a dogfight, as it can amount to several deg/sec in turn rate.

  7. 1 hour ago, Rudel_chw said:

     

    I'm calm .. just that is the type of thing that I would never do: speak before checking the facts.

     

    Speak? Like I said, I'm not declaring any overperformance, I'm stating I've heard rumors, which has made me curious. No reason to create drama out of nothing.

     

    1 hour ago, Ian Boys UK said:

    It's based on this video which is downright daft - he claims at one point a 17 d/s turnrate at the exact same time that tacview on the screen shows he averaged 11.6 throughout the turn. 

     

    That's not where I got it from, I got it from friends who had been BFM'ing it in the F-14 & F-16. That doesn't mean its true ofcourse, which is why I need to check it out.

     

     

  8. Planning on testing how all these changes have affected the STR of the aircraft soon. I've heard worrying rumors that the Mirage 2000 is now outrating every 4th gen jet in the sim, incl. the F-16, F-14, F-15, Su27, MiG29 & F/A-18. Which obviously it shouldn't be capable of.

  9. Yeah looks about right, although I measured it between 40 and 30 deg, to makes sure it was up to speed, where I got about 6 deg/sec. But most curious is in flight where the sweep is constantly lagging behind the CADC command indicator, even at slow accelerations and thus slow sweep change commands.

    The sweep is lagging behind even at sweep change commands no faster than 1-2 deg/sec. 

  10. A 1 G auto trimming aircraft will try to achieve 1 G perpendicular to the direction of flight. If the direction of flight is up (or down) in relation to level flight, then you're not at 1 G perpendicular to direction of flight anymore, and hence the FLCS will be commanding a slight pitch up to achieve said 1 G. 

    Hence its correct behavior. 

     

    EDIT: Dummycatz post explains it perfectly. 

  11. 20 hours ago, IronMike said:

    Same as near blind, sweeps and button work fine on my end on the ground as well. Sounds like the handle is not properly in the spider detent before hitting master reset maybe.

    What about the sweep rate? Seems abit slow and lags behind the CADC command even at low change rates, did something change? 

  12. Also noticed that the throttle wing sweep aft & forward buttons (wing sweep cover down) don't work on the ground anymore, even after pressing the master reset button. Used to be able to to adjust wing sweep on the ground using just the buttons on the throttle. 

     

    In addition to this the sweep indicator also no longer automatically switches to "auto" after take off when you've reached ~300 kts speed, eventhough the CADC appears to have actually taken control.

  13. @IronMike@fat creason

    Did something happen to wing sweep rate? Asking as I'm noticing the wings struggling to keep up with the CADC command even at rather low change rates. It doesn't seem like its achievning the 7.5-8 deg/sec sweep rate. This is at 1 G too btw, haven't checked if anything changed under G load yet, but you should be able to get 4 deg/sec @ 7.5 G (i.e. sweep rate only just about halfed at that G).

    • Like 1
  14. Decided to test the pitch stability today in terms of the aircraft's ability to return to 1.0 G flight after a positive or negative pitch command and then releasing the stick. What I found was that after commanding positive or negative G, and then releasing/centering the stick, the aircraft will oscillate in pitch around the 1.0 G attitude that it needs to return to by up to +- 0.8 G. 

    In other words if you e.g. pull 4-6 G and quickly release/center the stick (zero pitch command), the FLCS will attempt to reduce G's back down to 1.0 too rapidly by applying too much horizontal stab trailing edge down, resulting in the aircraft undershooting 1.0 G (by as much as -0.8 G, i.e. it hits 0.2 G) before getting back up to 1.0 G.

    Here's a video recording, as well as track file of it occuring:

     

    F16FLCS1Govercorrect.trk

     

    Seems to be a FLCS command filter issue for when you decrease pitch/G commands by a big amount in either direction. 

     

    • Like 4
×
×
  • Create New...