Jump to content

Topper81

Members
  • Posts

    235
  • Joined

  • Last visited

Posts posted by Topper81

  1. Hello BIGNEWY,

    the azimuth is not more that 5° on the launch of the second harm or what do you mean?

    grafik.png

    I tried it in all other PB modes: It's not possible to launch the missile correct when the target is masked by terrain.

    If target is not masked and I have an RWR Icon, it always worked fine for me.

    [Edit]

    harm crash3.trk is another trackfile. Here I fired 4 Harms, on the first two, the waypoint is mask by terrain, they crash into ground without climbing. On the shoot of the 3rd and 4th harm, the wp is not masked, they will climb and hit.

    I also changed the waypoint to be at 30 feet above the ground, so this seems not to be the reason.

    From my point of view this is definitely a bug.

    I never get the Harm on target in PB mode when the waypoint is masked, so I maybe belive that it's no bug when somebody shows me a scenario where the harm hits in PB mode and the designated waypoint is masked by terrain when launching the harm.

     

    • Like 2
  2. I observed that the Harm in POS - PB mode will not aim the designated waypoint if the there is no line of sight to the designated waypoint.

    Istead the missile seems to aim the point where the line of sight intersects the terrain.

    I expect that the harm will climb for lofting because it knows the distance to the selected waypoint as I understood.

    Note in the track file that the first both harms will not climb and instead they'll aim the a point before the waypoint and crash into the ground.

    After the waypoint is not masked by terrain anymore, the 3rd and 4th harm will climb and aim the waypoint as expected.

    This behaviour is reproducable for the Hornet as well.

    If it's no bug, please explain me how the harm knows if the target waypoint is masked by terrain or not, and why it's commanded to crash into the ground in this case. 😉

    Sketch for explainaition:

    First Case: Harm always crashes near the intersection point

    Second Case: Harm is lofting as expected (because it knows the corect distance?)

    grafik.png

     

    Thank you

    harm crash3.trk

    • Thanks 2
  3. Hello,

    I tried arround with this function using this scipt repetitive action, so in general it works so far.

    The issue with the first script is that it isn't working for group level for "air units" (source: https://wiki.hoggitworld.com/view/DCS_func_isTargetDetected)

    Quote

    Function is available at the unit level for all unit types.

    When used with a Group Controller the function will return expected values only with Ground and Ship groups.

     

    However, I never get the case that the distance is known

    local player = Unit.getByName('Player1')
    local badguy = Unit.getByName('Badguys1')
    if badguy ~= nil and player ~=nil and badguy:isExist() and player:isExist() then
       local detections = Controller.Detection
       local controller = badguy:getController()
       local detected , visible , lastTime , type , distance , lastPos , lastVel = controller:isTargetDetected(player) 
       trigger.action.outText('Detections: ' 
       .. (controller:isTargetDetected(player, detections.VISUAL) and 'Visual ' or ' - ')  
       .. (controller:isTargetDetected(player, detections.OPTIC) and 'Optic ' or ' - ') 
       .. (controller:isTargetDetected(player, detections.RADAR) and 'Radar ' or ' - ') 
       .. (controller:isTargetDetected(player, detections.IRST) and 'IRST ' or ' - ')  
       .. (controller:isTargetDetected(player, detections.RWR) and 'RWR ' or ' - ')  
       .. (controller:isTargetDetected(player, detections.DLINK) and 'DLINK ' or ' - '), 1)
    
       if detected then
          trigger.action.outText('You have been detected somehow ' .. (distance and 'and your distance is known.' or 'but your distance is not known.') , 1 )
       else
          trigger.action.outText('You havn\'t been detected so far', 1 )
       end
    end

    My expactation is if the detection is done by radar the range should be known but thats not the case or is there any mistake?

    Best Regards

    Topper

     

    detection.miz

    • Like 1
  4. Hello,

    is it possible somehow to run a "COCKPIT PERFORM CLICKABLE ACTION" from lua script? Or is there another way to get a Device on misson startup?

    When I use "DO SCRIPT" and I put "local dev = GetDevice(9)" in the box, I get this error message:

    grafik.png

    I want to create a script to change the cockpit configuration on startup and I prefere to use one script insted of multiple actions in the ME like here...

    grafik.png

    Thank you!

  5. When EWR / dispenser is in S/A (sequence maual started) or (even in automatic mode?), the sequence stops before it's defined end when evading and the EWR is not recieving radar signals anymore (regarding aircrafts orientation).

    Example: In the attached track file, the sequence is set to dispense 24 chaffs and flares. However, because the signal is lost on evading it's dispensing only till the radar signal has been lost by the EWR, but the missle is still on track...

    So my expactiation is that dispensing will stop after dispensing all 24 chaffs and flares because on evading manouevers it could be possible that only the signal is lost but the missile is still on track.

    Dispenser.trk

  6. Hello, no matter which mode, my feeling is that the rockeye is falling always short.

    I set HT to 1.500 (which is mandatory as I understood)

    In the track file I started bombing when TGP center is in the middle of the runways, however, the beginning of the runway is also hit.

    I tested also in CCRP and the effect is the same: It's not accurate.

    rockeye_short.trk

  7. Steps to reproduce:

    - Select a target in the HAD

    - Activate markoint mode (TGP mode)

    - Set TGP SOI

    - Set a markpoint with TGP

    - Fire Harm

    - Set HAD SOI

    - Try to select the target again when HAD is SOI (Not working)

    Expected:

    - It's possible to select a target because HAD is SOI and not TGP

    Observed:

    - It's not possible to select a target with the HAD (TMS Forward is stil "reserved" to create markpoints with TGP? But TGP is not SOI...)

    HAD_Markoint.trk

  8. 2 hours ago, Carbon715 said:

    You need to undesignate the had target via the had, then tgp cz if matkpoint is stpt...then you are good to go....unless your had/hts bugs out and you can't unlock...then you are SoL

    Got to remember while you have an emitter locked, hts is going to triangulate the emitter position and keep updating a better position slaving the tgp all the while until you create the mark and undesignate that emmiter

    No it does not work, I have unlocked the had as you can see in the trackfile.

  9. I sometimes noticed that it was not possible to undesignate the TGP after having a look with the HAD.

    So from my point of view the TGP is absolute useless this happent.

    The issue occures in the trackfile after 9:50. I cannot move the TGP anymore afterwards...

    I have used Mavericks with FCR GMT mode previously, but I don't know if this is related.

    I have created mark points on the SAM poisiton on the TGP after HAD Lock and choosen the markpoint as steerpoint.

    When I started the mission from runway, this happent multiple times.

    I had no success to reproduce this issue by starting the mission in the air.

    undes2.trk

  10. When I use point track of the TGP, acquire a moving target and then press Waypoint Increment long, I can create the target of oppertuinity which can be used for the Laser JDAM. However, the TO will not be updated if the target moves. The only way to update the TO is to move the TGP away from the Target and acquire  the target again. Is this a bug or is there any other solution to update the TO in point track mode?

  11. - Activate A/G mode

    - Goto Weapon page of the maverick

    - Activate PRE mode (OSB 2) or any other mode

    - Change the FOV of the maverick

    - Go to the next maverick (OSB 16)

    - Change the FOV

    - Repeat this for all mavericks to have them all in near FOV

    - Note that pressing OSB 2 will not circle through this modes (VIS, BORE, PRE) anymore

    fov_pre_not_working.trk

    • Like 1
  12. Hello, I saw some users at youtube who said they had created target points in the mission editor. So I'm able to create initial points in the ME and I can find them on the abris, but is it true that it's also possible to create them as target points for the PVI and if yes how?

  13. Hi I thought about this and for me it's not "correct as is"

    Ground stabilisation is for the MAV page but I don't change the target with TDC@MAV page.

    Or is it also a feature of the TGP? Becasue I guess when I'm in area track mode on the TGP, it's always "ground stabilised".

     

    I'm talking about changing the target with the TGP first and then switching the TDC to the MAV Page.

    Sometimes, the MAV will try to lock the target which is focused by the TGP as expected (because it's slaved to the TGP), but sometimes it's not and it keeps it's old target (Bug?).

    Which behaviour is correct here in which case?

    Thank you!

×
×
  • Create New...