@Mav-jp Hi, Mav. I can’t speak for W_F, and if you say BMS models it accurately, fine. So, are you saying that HAD does not give emitter status once Handoff has occurred? That would be interesting to me. I 've assumed, since HAD shows emitter status before Handoff, as per Dash-34 p.264, that it would show it afterwards. That would seem to be important , especially with HARM. If you shoot a HARM at a non-emitter, you’ve just wasted a weapon( in the strictly DEAD sense, anyway)
Assuming proved many times beeing a wrong thing to do.
Try to find a document which depicts the handoff symbology that is different depending on emitter status and we can talk again 🙂
That is always true, and I will take your suggestion. Meanwhile, does HAD display emittor-status after Handoff?
@Obi1 Exactly, yes. Even 1 ALQ is “working” … In case of EF111 , no need for ALQ-99, as it is “onboard” jammer.
But there’s that old video of @LorikEolmin duh 🙂 … but!, it explains this stuff with waypoints jamming activation …
You DONT change “starting jam loop” waypoint , …any stp different then first waypoint of jam loop, or … jamming will be “terminated” … - OFF.
End of story , can’t turn it on again.
Now, I had a thought bout this… what if you first went to a waypoint “above the loop” … eg … jam loop is stp5-6 … but you created more stps… eg 15-24 , so , you first go to 15 then … blablabla…
AND then you go to “jam-loop” 5 … and don’t move from there until you/allies are in safe zone…
Need testing… yeah… BUT, YOU DON’T “EXIT” STP5 (start of jam loop) UNTIL “feet wet” !!! 🙂
There is wokaround, if you need more stps in plan, you could insert stps , before loop , … so in essence move the loop further - to the stps12-13 … do your stuff in stps before … then do “the loop” 🙂
(of course, I was trying to make it work without the need of MC , editing waypoints … but , as Lorik said… didn’t work ,… all kind of crazy things starts happening… but that could be because of that “wait stp” … stp2or3 mostly. - as waypoints with “departure” time are in essence “end of the loop” waypoints for Falcon “logic” … so if you add , eg 2 jam-loops [5-(6-7)-8] - then there is that stp2 … and that is ODD number … so everything goes crazy… needed few more tests , but , as Lorik said … "it is a long time " 🙂 )
Hello drtbkj, thank you for your reply and the interesting info. Basically I was wondering why the resuply feature on campaign does not seem to happen on the planned time as scheduled on the squadron tab. I’ll wait a bit and if nothing changes, I will do what you suggested.
@Vespa depends if your goal is time on target or start time?
In MP, I use always take-off time as a reference
In SP, if you have multiple flights in the same package coming from different locations, I would go with TOT since you want to make sure you coordinate the time over target correctly…
I think this might be intended. The calculated pipper is lvl 5 and based on target acceleration. The EEGS funnel is a pure history device so may not have settled to current maneuvering parameters. You should be able to put the pipper on target and as long as parameters are constant the funnel should settle to agree in a time range of 0.5-1.5sec.