Unsolved TD box in DTOS
-
the TD box moves freely when AG-DTOS is selected but once I attempt to attack a target the box can no longer be slewed !! is that a bug or a possibly hardware issue?
edit: not related to procedure of attacking a target, behaviour appears randomly
-
@Alfred I’ll let one of our “Avionics Experts” chime in for the final answer to this question, but once you TMS-Up the Target Designator box should be locked to that particular coordinate. Try TMS-Down to unlock, move to a new position and then TMS-Up again.
-
@JollyFE said in TD box in DTOS:
@Alfred I’ll let one of our “Avionics Experts” chime in for the final answer to this question, but once you TMS-Up the Target Designator box should be locked to that particular coordinate. Try TMS-Down to unlock, move to a new position and then TMS-Up again.
its not related to TMS up, once I select DTOS from AG menu the TD box appear and it can be slewed. If the anomaly appears I click AG off & on to make it go and it works that way back to normal.
-
What do you have selected as your Sensor of Interest (SOI)? Ground Radar? HUD? Or Targeting Pod?
-
I believe you are doing it wrong.
When entering DTOS, the TD box is caged/slaved with the fpm.
Put your FPM in the global area of what you want to attackFirst TMS UP -> you ground stabilize the TD box = it frees it from the FPM and makes it ground stable.
Once ground stable, you fine tune the position of your TD box with your slew cursor.
Final TMS up and you’re golden for a CCRP pass
-
Reference the Falcon manual TO 1F-16CMAM-34-1-1 BMS, Para. 2.5.6.3 (Pg 259).
-
The term is “ground-stabilized”. In the pre-designated state the TD can be slewed (relative to the FPM) and designated which causes it to be ground-stabilized. Once ground-stabilized it can be refined further by slewing. There is no “locked” where it’s not slewable.
Slewing in DTOS requires that the HUD be SOI. There’s little reason that HUD is not SOI but when in doubt refer to the “*” symbol on the HUD.
-
I have a similar issue. When trying to use DTOS mainly it won’t allow my HUD to be the SOI. Sometimes it will sometimes it won’t. I’ve been messing with it for hours trying to fix it in flight. It will DMS up and remove SOI from MFD but won’t actually goto the HUD. The asterisk will flicker for a split second. Then randomly down the road it will allow the HUD to be SOI. I’ve even turned off all the other sensors and it still won’t allow the HUD to become the SOI.
-
All – it’s important to write down detailed repro steps, if you can repro these bugs, or quirks.
I also sometimes struggle with SOI bugs or quirks, so I believe there may be lingering bugs. But it’s just not actionable to investigate, without some level of detail – what buttons you’re hitting… what block jet are you in… what weapons active, etc
-
@airtex2019 @airtex2019 This also affects all bomb release modes not just DTOS. So I spent all my trial runs in the 40 block. The hud sensor works fine after take off as long as I don’t touch anything else in regards to sensors. It seems to me most of the time the issue will arise if I use the fcr/tgp and setup a markpoint or target target track. Bore sighting mavs will also start this issue. I’ve tried only having the same type bomb on board to see if there was weapon interference but it still happens. Then when I switch to a/g it will sometimes make the hud SOI properly or completely blocks it. I’ve tried cancelling any cursor slews across all modes. Changing back to the STP where it was initially working doesn’t help once the error occurs. Turning off power to all other available sensors or running STBY whilst blanking out all OSBs across all modes doesn’t help. Switching to MRM/Dogfight and back. It sometimes will fix itself and allow Hud SOI on its own with no input on my end. I’ve done every combination of FCR/TGP modes/ OSB combinations on NAV/AG/AA master modes. I have also used TMS commands to break tracks as well as any other TMS combo just for trial and error in combination with the aforementioned.
-
@itsbobbaayy Tried the the Block 50 Tonight as well. Same issue as the 40 block.