Jump to content

Whisper

Members
  • Posts

    691
  • Joined

  • Last visited

Posts posted by Whisper

  1. 21 hours ago, gulredrel said:

    My L wingman fired with command to engage ground targets. Looking with the L's periscope and tasking him to engage my target didn't work.

    SA-342_wingman_HOT3_engage.trk 1.04 MB · 2 downloads

    There's no lock on target through the periscope, the DCS engine has no way to know what is your target, so I'd guess the "attack my target" can't work with sensor that have no lock on ability

    • Like 1
  2. 16 hours ago, Get_Lo said:

    "New cyrano IVM"
    "Low fuel capacity"
    "slave the Magic"
    and worst of all "MULTIROLE"?!?!?!?!
    No INS tutorial what so ever, but instead a 10minute long AAR tutorial.
    and audio effects dubbed over to make it sound like a 1910s film.

    Good lord someone let me know when Redkite uploads his version of this, I cant go any further.
     

    Hu? I wonder what is presented from 2:50 to 7:40 then....

    • Like 1
  3. 48 minutes ago, Parameter said:

    I tried to use ILS at Larrnaca, and could not get it to work either. For some reason the tower gives me runway 04 no matter where the wind blows.

    I had success with ILS at Incirlik, and I recommend you try landing there instead. To me this seems like a problem with the ATC system rather than a problem with your procedure.

    All airports do not have ILS set up in both directions, in DCS. It may well be that Larnaca only has antennas set up for the 04.

  4. 55 minutes ago, imacken said:

    I find it almost impossible to line up the I beam when hovering. The precision required for the position of the beam makes if very difficult to move the aircraft into the correct azimuth. Especially when using George. Difficult to make the required degree of accuracy.

    AFAIK rockets are not intended to be fired from a hovering position

  5. On 4/10/2022 at 2:25 AM, RuskyV said:

    Why not have a trim system that just allows you to centre the stick separate to either of the current options, the bit I don’t get is why freeze the controls on one setting and on the other add in the extra deflection.

    Is there really any need for the added complexity of either systems? Why not trim and have neither side effects.

    im sure there is a deep rooted answer beyond my understanding otherwise it would already be an option no?

    Because it's inevitable if you model the behaviour like the real life counterpart : pressing trim up release the trim brake on the stick, release the trim re-grips the brake on the stick at the place the stick was when you released.

    This is the way ED wished to model it, true to IRL behaviour.

    Since our joysticks cannot stay at the position we commanded but will always return to center, we're stuck with either one the 2 drawbacks you mention.

     

    If you want to get rid of it, you need to model trim button behaviour differently from the real thing. I think you propose that when pushing trim up button, we actually indicate to the system that our expected trim position is the stick position when trim is pressed (unlike current behaviour where expected trim position is the position when trim is released), and that the trim button pressed neutralize input, which are given back when we release the trim?

    That way we could press trim up when in target stick position, place the stick back to center without impact on attitude, and release trim button when our stick is back at center.

     

    Is that so, or do you have something else in mind?

    On 4/10/2022 at 2:25 AM, RuskyV said:

     

     

  6. This looks kinda logical to me.

    Slave redirects your sensor (TADS) to your acquisition source , unslave gives you back control through the TEDAC .

    Your acquisition source is the laser seeker, so once the lasing is on, the seeker catches it, and slaving puts your TADS on point

    So that should work... provided the seeker finds the laser point, IE is looking in the general vincinity of it, that may be your issue

    Do you also have a 9 line from the JTAC? If so, maybe using a markpoint on coordinates and slaving to it would do the trick

    Edit : warning, many edits after initial post, I didn't properly read your post in the first place 🙂

  7. 22 hours ago, Swift. said:

    So I just tested this because I was curious about this assertation, compared UH-1H with AH-64D behaviour. What I saw was as you described: pretty much the same behaviour.

    However the big and critical difference between these two aircraft is the delay between button release and 'trim set' so to say. In the Apache you have microseconds to centre the stick before it adds the input onto the new trim. In Huey on the other hand there is a noticeable delay where the control freezes, which is key to allowing the pilot to recenter the stick before it comes alive again.

    So in summary, if we want the same trimming technique in apache as we have in huey, we need a slightly longer delay between button press and reactivation of the controls. Or even better, a slider option in the special menu.

     

     

     

    Exactly this!

    Add to this the fact that the Apache is FAR more reactive than the other helos and it makes the difference really noticeable, actually, even though it's technically minimal.

    Working on this delay and if feasible, Apache twitchiness would help far more than a "trim reset" option

    • Like 1
  8. To each his own, no pb with that 🙂

    Central trimmer bugs on me (DCS often do not recognise that the stick is back at center, leaving me with a dead stick).

    I just don't understand the hyperbole behind describing the apache trim as totally alien to the other DCS helicopters. Technically, the diff isn't that much (there's very short delay in Mi8 before the trim kicks in in default mode, and afaik that is all that differs, and yes, I think they could easily put it in the Apache, but I'm no DCS dev, so... ) between the trim implementations.

    Like you say, add it to the general Apache twitchness and the result can appear violent, and thus I'm not sure how a trimmer reset will solve issues. It's going to be a very violent reset, actually, seeing how reactive the Apache is to input.

    Wouldn't working on a delay and a more dampened input be better?

  9. 18 hours ago, Hammer1-1 said:

    No it's not, it's designed for FFB sticks as default. Was told by shagrat it was due in error to make it default, so it'll be changed next time around hopefully... but it's nothing like trim in other helicopters. That default is the exact same as the Ka50 with FFB joysticks.

    Changed to what default behavior? Because the current Apache "INSTANT TRIM (FFB Friendly)" behaves the same as all the other "Default" in the other choppers to me. What exactly makes the Apache ""INSTANT TRIM (FFB Friendly)"" different?

    I don't see the "it's nothing like trim in other helicopters" part AT ALL on my side. It took me zero second to adapt because it was behaving in the same way (only talking about cyclic trimming, here)

  10. 49 minutes ago, Smashy said:

    One example I can think of is an emergency autorotation.  Imagine being trimmed for forward flight and you lose power.  Being able to instantly find the center of cyclic and antitorque in a sprung joystick and pedals is pretty handy.  I used trim reset a lot in the Huey while learning autorotation.  I would create a mission where I would start in the air and cut fuel to the engine.  It took me a couple of crashes to figure out that when you airstart in the Huey, it's trimmed for forward flight and pulling the cyclic full aft doesn't give you enough pitch authority to enter a successful autorotation.

    Indeed, good point.

  11. I'm not here to prevent the request, if people feel that's a good addition to them, I've no issue with that.

     

    But just a genuine question : what is it helpful for, actually? In fact, what is that "neutral" position? I'd argue there's no such thing, you just need to place your stick in the position needed for your bird to be in the desired attitude, and then you trim, and voila....

    Each time I decide to use a "trimmer reset" button, it creates more problem than it solves, personally : either my current trim point is far from the "neutral" position, and the result is a violent change of attitude of the helicopter with potential catastrophic event incoming, or it's so close to the neutral position that an actual light manual re-trim in the desired attitude (because actually, the "neutral" position is never optimal) will achieve better result.

    Maybe, once on the ground, it's usefull ?

    • Like 2
  12. Quick question : any particular reason for USA to be of faction "Red" in the Cyprus Incident campaigns? And how could I switch them back to blue?

    This prevents me from quick-hacking a campaign to add Apache to it, because your apache needs to be in the same coalition as USA if you want to have access to GPS and make the initial alignment ....

  13. On 2/23/2022 at 10:31 AM, ebabil said:

    It is not a bug. Heatblur said that it is immpossible to switch seats during MP session due to system limitations. Same applies to UH1.

    If the current state will not change, mi8 will also be non-swichable. 

    I always find this very annoying. And hope it will change soon.

    Just from the latest patch :

    MP Seat Switching now possible due to changes to DCS codebase 🙂 Thank you ED!

    • Like 2
    • Thanks 1
×
×
  • Create New...