Jump to content

GafferDCS

Members
  • Posts

    85
  • Joined

  • Last visited

Posts posted by GafferDCS

  1. On 2/20/2023 at 9:39 AM, LowGlow said:

    Interesting, for me the HARM did not self loft, and I was somewhere between 5..3 nm away from target. I was very low, and in Tacview I later saw that the HARM retained the same low altitude and finally simply overshot the target and impacted behind target. That's why I changed my tactic in another attempt and made a pull up attack instead, which finally succeeded.

     


    Thanks! 5mi is too close for the HARM to loft. 7.5 miles is about the closest you can be. You can loft it yourself by pulling the nose up. If it does not get some altitude, the chances of it hitting the target are low.

  2. On 10/17/2022 at 8:14 AM, Lace said:

    Just curious really, I know it trims in pitch for 1G, why doesn't it trim for roll?  Surely with zero roll demand from the pilot (via the stick), the aircraft FLCS should be able to provide any required roll trim to give a zero-roll rate condition.  Is there a deliberate reason they* didn't code this in?

    * I don't mean ED, I mean General Dynamics/Lockheed Martin.  I'm referring to the real-life Viper.


    I’m going to hazard a guess here, they don’t have the FLCS auto trim for roll because they want the pilot to have some “feel” when they are operating with an asymmetric load. So it’s designed to make the pilot trim it out. 

  3. 3 hours ago, Dermax1 said:

    I've really enjoyed all the videos that you've done so far. To me they're an excellent middle ground between some of the hour long, super in-depth tutorials out there and the short, bare-bones "this is how you do it". There's a place for all three in DCS training videos.

    There's something wholesome about being able to find a new YouTube channel in 2022 - I was subscriber 300 or something. Keep up the good work!

    Thank you! Now I just need to find time to record a few more. I've seen some good suggestions in the comments and I have a few ideas of my own.

    • Like 1
  4. 3 hours ago, kotor633 said:

    I just watched the video about FBW and Trim. Question: If you pull such a high AOA on the F-16C (25 - 30 AOA), shouldn't the wings break at some point? Or the wing mounts? It's the same with the Mi-21 and JF-17. Or is that related to the G-forces? I'm no expert so I'm asking.


    Stress on the airframe is tied to G forces, not AOA. I’m not aware of anything for the Mirage. 
     

    Thanks for watching

     

  5. Hi everyone. I put together several tutorials for the DCS F-16C over the last few weeks. I have around a dozen on my YouTube channel covering everything from the the Fly-By-Wire system, SEAD using a variety of weapons against different SAM systems (including the Grumble) and how to get a great approach and landing. 
     

    Enjoy!

     

     

     

     

    • Like 2
    • Thanks 2
  6. Cage/Uncage is supposed to command the pod into LSS, it's currently bugged at the moment. You can unstick it by designating and undesignating to return to Snowplow mode, or entering VVSLV by double-pressing Undesignate.

     

    Thanks!

  7. The Hornet doesn't have a boresight command for the pod, you can either slave it to the velocity vector (VVSLV) or put it in Snowplow (default aiming mode at power-up, returns to this mode after Undesignate).

     

    Thanks, how do you slave to the velocity vector? Cage/Uncage used to work..

  8. Is there a guide or can any of you share tips on Jester working the radar. At long range employing the AIM-54 he seems pretty good at finding, sorting contacts and stuff. At short to medium range, (15-30 miles) he does not seem to be able to find much on his own.

     

    For example I get a BRA call from AWACS 15 miles, 10,000 feet below me I turn on the heading, see nothing on TID. I tell Jester to search low, middle.. nothing. I'm pretty good at working the radar on the Hornet so I understand what he should be doing back there.

     

    Would love to hear some tips on how you use Jester.

  9. Without using waypoints at all (only selecting sequence to see the route on the SA page), I am able to get consistent hits with LGB's. As others have mentioned, it appears very likely that the auto delivery erroneous delivery cues are cause by some conflict to the waypoint system. Even if the designation appears to be exactly on target, the release queue is way too late resulting in an overshoot release point.

    I can reproduce this consistently.

    To summarise, in my experience, in order to induce the inaccuracy:

    1.) On the lower display, box the Waypoint in the top right.

    2.) Set the waypoint to 1.

    3.) Box the sequence option (don't think this has an actual impact)

     

    I have tried deselecting (switch the box off) on the Waypoint button top right mid flight and then designate the target, but once it has been selected it breaks the delivery queue for me. I hope this helps whoever is trying to troubleshoot the issue.

     

    I had the same issue. Using wpsdg will keep the GBU 12’s from picking up a laser. Even after deselecting everything to do with the waypoint system. I get a good drop on target, but the bomb never sees the laser. Also it does a weird thing where the LTD/R toggles on and off with the trigger press, instead of holding down the trigger to fire the laser.

  10. Thanks for the help

     

    This was a binding issue. The bindings appeared correct, when I pressed the button on my HOTAS, the sensor select left was immediately highlighted in my control assignments page, leading me to believe that the bindings were all good. (same with right, fwd, aft etc..) However, I decided to clear those bindings and re-do them, just for the hell of it, and wham, all is good now!

  11. You're right. Sensor Control Switch - Left, - Right etc.

    Let's check (assuming you are using the left DDI):

    1. In Options/Controls, when you push the sensor control switch left, the cursor jumps to that command.

    2. In flight, when you have switched to A/G mode, "MAVG" or MAVD" is displayed in the upper left of the DDI

    3. After the 3-minute countdown, when you push the sensor select switch left, there should be a little caret in the upper right of the left DDI. At that point you should be able to uncage.

     

     

    I typed a detailed response to this and somehow lost it after I hit reply.

     

    Long story short, I am doing all the things right, my keybind is correct, and it don't work. I'm going to make a video of the issue this evening and post to the bugs section. I'll link it here as well.

×
×
  • Create New...