Jump to content

RoxSy

Members
  • Posts

    128
  • Joined

  • Last visited

Posts posted by RoxSy

  1. Disregard my last post,

    I removed the ''read only'' option from every folder (Eagle Dynamics to Raven One Campaign)

    I couldn't save in ME but when I launched the mission in the campaign, the deck crew I removed was indeed gone.

    Strange ... but it worked as intended.

    I completed the mission. Got thumbleweed a couple of times but the work has been done.

    I did not have a ''Mission Complete'' message once I trapped on Mother (maybe because I boltered or maybe because I altered the mission).

    Anyway, score 190 / result 100.

    I'm a happy hunter.

    @baltic_dragon

    In this mission the Tomcats had a Jolly Roger liveries and did not seem to be very combative.

    I splashed one with the gun but the pilot did everything to make it easy though.

  2. That was the point, having a constant TOT at my descent entry point.

    I asked about that because I see a TACAN O/S informations on the HSI menus.

    I couldn't find a way to populate them though.

    Mobius708, if I'm not mistaken you are a RL Hornet driver.

    I guess this is not something you guys are doing anyway.

    Thank you guys for your input.

  3. 6 hours ago, QuiGon said:

    This! Changing the track mode of the TGP to SCENE or TRACK just lets the TGP track the object, but it does not designate it as a target! To designate it as a target you need to press TDC DEPRESS!
    I'm not sure though if it then starts to continiously update the target position if the tracked target is moving. I will have to test this, as I'm curious myself now.
    In the A-10C you just generally designate a sensor (like the TGP) as the SPI provider and it will contioniously generate a target (SPI) wherever the sensor is looking at.

    A potential way to check on this is to see if the coordinates are constantly changing on the JDAM TOO page while the target is moving.

  4. Hi guys !

    Is there away to put an offest to a TACAN beacon ?

    I would use it to make a reference point from Mother in Case III trap, that way I can use the timer to be just in time to commence my approach with Time on Target for example.

    Is it something like that possible ?

    Thx

  5. I think it is because you habe to make a TDC depress on the FLIR page first.

    Scene or track will focus on an object but the TDC depress will actually designate the coordinates to the system, like you'd do for the JDAM and JSOW.

    For a moving vehicule the best way is to indeed undesignate when you are running in and slew the Mav.

    For fixed targets, just do a TDC depress before uncaging the Mav.

  6. 2 hours ago, AstonMartinDBS said:

    I'm afraid that ED ignores this thread because it already has been marked as "cannot reproduce". 😔

    I'll do another one then ...

    To be fair they asked for a track and it took me quite a while to post one (not been on DCS for quite some time because of work)

  7. 20 hours ago, Hulkbust44 said:

    Yes, the ATFLIR should be able to predict the position of the target from the previous track if masked. I believe in DCS it is just tracking the target no matter what. But hey, if the target didn't change course or speed it's realistic.

    Mobius708
     

    That is nice.

    Actually I think the couple of times I noticed that the vehicules were going pretty much straight, one was a vehicule in the open and the second was a helicopter.

    Thank you all for your answers 🙂

  8. 7 hours ago, GazAce said:

    This is exactly why I dumped ATFLIR when using MAVs, it's woeful & virtually useless to moving Targets especially in built up urban environments. Just load up your Litening man, middle bay for nice AC balance, always reliable, can manual slew to your hearts content & able to lock up multiple targets in one pass. No brainer for me & saves so much frustration & grief.  Peace out  🙂

    The problem is exactly the same with the Litening and it doesn't solve problem with the HSI/SA waypoint designate.

    I suspect it is the same with AG Radar or even with a Helmet designation.

    Plus Litening wasn't used on Navy aircrafts, only ATFLIR.

    The solution is indeed to look for targets with the POD and undesignate when you are running in.

    Then BDA is difficult to achieve and it becomes very fiddly and you end up firing way closer to the target than you should.

    Now if it is a real life limitation, no problem.

    But nothing has been confirmed or infirmed on that matter yet ...

  9. There you go !

    See how I cannot slew the Maverick once the ATFLIR is in scene and pointed onto the vehicules. You'll see that I kept the TDC pressed and I have the realistic TC option boxed.
    If there were 2 vehicules nearby and the Mav was locking on the wrong vehicule I would habe been unable to reposition it.

     

    So ... is that supposed to be normal ?

    MavNoSlew.trk

  10. On 11/18/2021 at 11:04 AM, AstonMartinDBS said:

    That works great - as long as ATFLIR is in INR mode. But the MAV seeker isn't slewable when the ATFLIR is in SCENE or AUTO mode, because the MAV re-slaves continuously to the ATFLIR designation. It's impossible to brake this constant designation update/re-slave loop with undesignate, while ATFLIR is in SCENE or AUTO mode and sensor priority is on the MAV format page.

    I don't think, that this is as intended, because I don't see any reason for that behaviour.

     

    I get the logic of the never-ending slewing to the pod SPI.

    So ... the question is now whether it is supposed to be like that in the real plane or is that a DCS logic bug ?

    Because mashing the un/cage button until it locks the good signature looks a quite terrible process.

    But maybe those 2 sensors aren't meant to be used that way or maybe it is just a limitation of the RL sensors.

    I just can't believe, with all the people that have this thing, that ED guys cannot reproduce the situation.

    Lock a target with the ATFLIR in scene of track, switch SOI, uncage the Mav and try to slew.

    It won't move.

    • Like 1
  11. Hey there !

    Just to let you know that since the last update (2.7.8) some bindings have been deleted :

    Launch bar retract

    Launch bar extend

    Hook bypass Field

    Hook bypass Carrier

     

    The special on/off for momentary buttons are still present but the separate bindings for 2 positions switches are missing, so I can't use my fellow Winwing panel anymore on those bindings.

    A quick fix would be very welcome since I don't want to spend time to mess with the lua.

     

    Thx

×
×
  • Create New...