Need help with MARKPOINT.
-
MARK is a button on the ICP keypad (7?) which will start ready to make a mark point based on current sensor. It’s possible to change from this initial selection if needed. So above advice to make TGP SOI and tracking (AREA or POINT) before selecting mark mode with ICP button is helpful. If needed you can press DCS right to SEQuence through available options.
For the most accurate TGP marks ensure that laser is emitting at the moment of record. This will provide the best slant range data to calculate position under crosshairs. There is also some maximum practical distance for laser rangefinder.
TGP SOI, POINT or AREA
ICP MARK_7
DCS SEQuence to change sensor (if needed)
Laser arm, Pinky switch hold to emit laser for rangefinding
TMS forward to record mark point
ICP M-SEL_0 to switch steerpoint to last made mark (if needed)
CZ to remove system deltas -
Hi,
so select, have TPG locked in Area or point, hit 7 to call up MARKPOINT, hit CZ and then TMS up?
Thanks
-
Sorry, edited my post to add tms up
-
I always have the created steerpoints that are not collocated with the intended spot.
If you have slewed your SPI (System Point of Interest) to the intended spot before you TMS Up to create a markpoint you will have introduced a system delta. System deltas reflect the horizontal difference between the SPI position and the currently selected steerpoint’s original position. If you then switch to that markpoint without clearing the system delta your SPI will be pointing to the markpoint + the system delta.
This is all explained in the -34 manual in the SPI MANAGEMENT chapter, starting page 171.
-
Hi,
so select, have TPG locked in Area or point, hit 7 to call up MARKPOINT, hit CZ and then TMS up?
Thanks
CZ last. CZ is Cursor Zero; it removes the slew, (delta), from the current STPT. If you hit CZ before you TMS you will simply reset the TGP view to the STPT and away from thing you’re MARKing. Please see Frederf’s; he explains the sequence neatly and accurately.
Remember, CZ is applied to all STPTs, including markpoints be it ones you’ve set, or ones you send via datalink (if you mark somewhere but do not remove the CZ before sending it via datalink, the recipient will see the offset too and there fore not see the accurate markpoint). If you slew the TGP or FCR etc. 5nm south of STPT 5 (CZ will be lit) and the switch to STPT 6, STPT 6 will be selected but sensors will be referencing 5nm south of STPT6. This is why its in many SOPs to CZ at the end of an event
Also, the current SOI dictates which MARKpoint is the default option upon press ICP 7 MARK. TGP SOI = TGP. FCR SOI = FCR. You also have HUD and OFLY available too.
Page 70 of TO-BMS1F-16CM-1.pdf explains it all for you.
-
B̶T̶W̶ ̶a̶ ̶n̶o̶t̶e̶ ̶a̶b̶o̶u̶t̶ ̶c̶u̶r̶s̶o̶r̶ ̶z̶e̶r̶o̶:̶ ̶I̶’̶v̶e̶ ̶b̶e̶e̶n̶ ̶s̶u̶r̶p̶r̶i̶s̶e̶d̶ ̶t̶o̶ ̶e̶n̶c̶o̶u̶n̶t̶e̶r̶ ̶g̶u̶y̶s̶ ̶w̶h̶o̶ ̶o̶n̶l̶y̶ ̶k̶n̶o̶w̶ ̶h̶o̶w̶ ̶t̶o̶ ̶C̶Z̶ ̶b̶y̶ ̶p̶r̶e̶s̶s̶i̶n̶g̶ ̶t̶h̶e̶ ̶O̶S̶B̶ ̶b̶u̶t̶t̶o̶n̶ ̶o̶n̶ ̶t̶h̶e̶ ̶F̶C̶R̶.̶ ̶C̶Z̶ ̶h̶a̶s̶ ̶i̶t̶s̶ ̶o̶w̶n̶ ̶H̶O̶T̶A̶S̶ ̶b̶u̶t̶t̶o̶n̶ ̶o̶n̶ ̶t̶h̶e̶ ̶t̶h̶r̶o̶t̶t̶l̶e̶.̶ ̶I̶ ̶b̶e̶l̶i̶e̶v̶e̶ ̶t̶h̶e̶ ̶p̶i̶l̶o̶t̶s̶ ̶h̶i̶t̶ ̶i̶t̶ ̶w̶i̶t̶h̶ ̶t̶h̶e̶i̶r̶ ̶t̶h̶u̶m̶b̶.̶ ̶S̶o̶ ̶i̶t̶’̶s̶ ̶r̶e̶a̶l̶ ̶i̶m̶p̶o̶r̶t̶a̶n̶t̶ ̶t̶o̶ ̶h̶a̶v̶e̶ ̶t̶h̶a̶t̶ ̶b̶o̶u̶n̶d̶,̶ ̶y̶o̶u̶’̶l̶l̶ ̶b̶e̶ ̶u̶s̶i̶n̶g̶ ̶i̶t̶ ̶a̶l̶l̶ ̶t̶h̶e̶ ̶t̶i̶m̶e̶.̶
edit: wrong, wrong, wrong!
-
BTW a note about cursor zero:
I’ve been surprised to encounter guys who only know how to CZ by pressing the OSB button on the FCR.
CZ has its own HOTAS button on the throttle. I believe the pilots hit it with their thumb. So it’s real important to have that bound, you’ll be using it all the time.I’ve heard of CZ doable with a HOTAS command, but never on the throttle though (I believe on some tapes it is TMS Aft long, or short with TGP as SOI and not in track). Do you have a source ?
-
short TMS aft with TGP as SOI and not tracking is CZ. HSD OSB 10, FCD OSB 9 in some modes, are CZ. I will have to see if this works in BMS!
1.3.3.1.4.2.1.4 A hands-on capability to perform cursor zero, if the TGP is SOI, is also available. This capability resets the cursor by removing any existing cursor slews. It delivers the same results as pressing OSB 9 “CZ” on the TGP base page.
1.3.3.1.4.2.1.4.1 Short TMS aft (< 0.5 sec) performs cursor zero if the TGP is the SOI and the following modes are not selected: Area Track, Point Track, Computed Rates/INR Track, Multi-Target Track (MTT), or Combat Identification (CID) mode. When cursor slews are present, “CZ” is constantly highlighted. “CZ” de-highlights after cursor zero occurs.
There is no dedicated HOTAS button which is cursor zero in the real jet. Of course, you are free to map your own controls however you like for BMS!
EDIT: Sniped!
-
BTW a note about cursor zero:
I’ve been surprised to encounter guys who only know how to CZ by pressing the OSB button on the FCR.
CZ has its own HOTAS button on the throttle. I believe the pilots hit it with their thumb. So it’s real important to have that bound, you’ll be using it all the time.Are you getting mixed up with Cursor Enable?
-
short TMS aft with TGP as SOI and not tracking is CZ. HSD OSB 10, FCD OSB 9 in some modes, are CZ. I will have to see if this works in BMS!
There is no dedicated HOTAS button which is cursor zero in the real jet. Of course, you are free to map your own controls however you like for BMS!
EDIT: Sniped!
I’m pretty sure I tried this the other night after having read about it on here a while back during 4.33. It didn’t reset CZ, but I haven’t searched the 4.34 docs for this feature yet, either.
-
CZ through HOTAS undocumented in BMS, from what I’ve seen - unless you bind it somewhere.
-
CZ through HOTAS undocumented in BMS, from what I’ve seen - unless you bind it somewhere.
You could bind the callback, or even (crudely) the relevant MFD OSB to a button, but ideally it needs to be coded in so that it works correctly with TMS aft
-
Are you getting mixed up with Cursor Enable?
No, I did not mix it up with Cursor Enable.
It’s a callback in the default keyfile, in the Throttle Quadrant System section, with all the other real buttons.
So I’ve made an OOPSIE :lol: It’s not in the real jet. I’ve been ARCADE all this time. Thanks for clearing that up for me guys.
-
No, I did not mix it up with Cursor Enable.
It’s a callback in the default keyfile, in the Throttle Quadrant System section, with all the other real buttons.
https://i.gyazo.com/e991b4c85897424ec836699381de6c26.png
So I’ve made an OOPSIE :lol: It’s not in the real jet. I’ve been ARCADE all this time. Thanks for clearing that up for me guys.
Filthy casual
-
No, I did not mix it up with Cursor Enable.
It’s a callback in the default keyfile, in the Throttle Quadrant System section, with all the other real buttons.
https://i.gyazo.com/e991b4c85897424ec836699381de6c26.png
So I’ve made an OOPSIE :lol: It’s not in the real jet. I’ve been ARCADE all this time. Thanks for clearing that up for me guys.
Intersting, thanks. Reason for my asking about the mixup is because you mentioned the throttle in your previous post. I might add that call back to my shifted layer on the TMS switch.
-
Real F-16 has hands on CZ (TMS aft double tap I think) but only in later software versions. I have heard this please don’t be mad if I’m repeating a mistake
But yes it’s important to CZ after making a mark point because if you introduced system delta when moving TGP (or other sensor) around then they will still exist when mark point is selected as steerpoint. Naturally TGP will initially point at this wrong position but after CZ it will resume facing toward the correct place.
You might ask why doesn’t F-16 automatically CZ when selection mark point… well maybe you get that coordinate from DL and you need your system deltas because your INS has drifted (no GPS) and those system deltas were what was making your INS accurate again. Maybe real F-16 has special super-sekret programming to recognize when M-SEL own markpoint and realize you probably want CZ and does it for you. You never know with those sneaky engineers.