Razor18 Posted January 20, 2016 Posted January 20, 2016 (edited) Hi Guys, after watching Recon Stewarts excellent Maple Flag TTQ Mission 15 Deep Interdiction Strike video on Youtube (relevant part at around 6:40), I was wondering if there is a bit easier (?) way to point TGP to a „TAD object”. In the video I think (might be wrong) he selects the target waypoint, then makes TGP SOI and watching the diamond moving on the TAD screen, he puts the TGP diamond onto the waypoint, then makes TGP SOI and fine tunes the tracking on the TGP image and then makes SPI from TGP. My question: wouldn’t it be maybe a good alternative to make TAD SOI slew TAD cursor over TGT wayoint hook waypoint by TMS UP Short TMS Up Long to make the hooked object SPI China Hat FOWD Long to „slave all sensors to SPI” Should this sequence also resulting in the TGP pointing at the target/waypoint area (allowing further TGP fine tuning for point track)? Just asking, because when I simply select any waypoint (no TAD used), and China Hat AFT Long, then my TGP (with or without making TGP SOI) points in empty space in the air (meaning 3D waypoint "elevated" position) despite being in A/G mode. Sorry, if I missed something, very good learning material anyway, all of his videos! Thanks Edited January 20, 2016 by Razor18
Gliptal Posted January 20, 2016 Posted January 20, 2016 (edited) Your sequence is totally valid (and actually better than slewing the TGP on the TAD), but works with waypoints only if their elevation is 0. The TGP points in the air because waypoints are normally placed at a given altitude in 3D space. An easy workaround is: - make TAD SOI - slew TAD cursor over waypoint - create markpoint (TMS RIGHT SHORT) - set database to MARK - hook and make SPI the markpoint - slave all to SPI It sounds longer to do than it really is. This works because markpoint elevation always is the elevation of the ground at those coordinates. Edited January 20, 2016 by Gliptal
Aginor Posted January 20, 2016 Posted January 20, 2016 Your sequence is totally valid (and actually better than slewing the TGP on the TAD), but works with waypoints only if their elevation is 0. The TGP points in the air because waypoints are normally placed at a given altitude in 3D space. An easy workaround is: - make TAD SOI - slew TAD cursor over waypoint - create markpoint (TMS RIGHT SHORT) - set database to MARK - hook and make SPI the markpoint - slave all to SPI It sounds longer to do than it really is. This works because markpoint elevation always is the elevation of the ground at those coordinates. I do that quite often, too. Works well. It is also a great way to look at some place people refer to by its Bullseye coordinates. Put the TAD in "Bullseye -> Cursor mode", move cursor to coordinates of the Bullseye call, create mark point, slave TGP to it. DCSW weapons cheat sheet speed cheat sheet
Razor18 Posted January 20, 2016 Author Posted January 20, 2016 (edited) Your sequence is totally valid (and actually better than slewing the TGP on the TAD), but works with waypoints only if their elevation is 0. The TGP points in the air because waypoints are normally placed at a given altitude in 3D space. An easy workaround is: - make TAD SOI - slew TAD cursor over waypoint - create markpoint (TMS RIGHT SHORT) - set database to MARK - hook and make SPI the markpoint - slave all to SPI It sounds longer to do than it really is. This works because markpoint elevation always is the elevation of the ground at those coordinates. Actually in the heat of the sudden task saturation I tried to quickly overwrite WPT elevation to 0 for both Target waypoints, and tried to CHina Hat AFT Long, but at first look it didn’t seem working. either. Now that I think it over again (and meanwhile succeded with the TGP slewing method after all), I guess I just didn’t realise that the SPI on the ground was in fact obscured for a little period of time. BTW, after my apparent failure with WPT elevation set to 0, I also wanted to ask, if TGP has any „logic” in function, meaning that if I switch it to A/G mode, then maybe it would be logical for the TGP to look rather on the ground even if 3D WPT has any elevation set. But I know, nothing is perfect… Oh, and when I set elevation to 0, does it mean MSL 0 (that would be "inside" the hill or mountain), or it only means for the computer to look exactly on "ground level on a hilltop or valley", based on the elevation database? Thanks for confirmation guys! Edited January 20, 2016 by Razor18 1
Gliptal Posted January 20, 2016 Posted January 20, 2016 Elevation 0 means that if you're looking at a hill, the TGP actually points to the ground. You should be using LASTE elevation.
Razor18 Posted January 21, 2016 Author Posted January 21, 2016 By "ground" you mean the "flat base" of the hill instead of the elevated contour surface? How can I use LASTE elevation?
Gliptal Posted January 21, 2016 Posted January 21, 2016 By "ground" you mean the "flat base" of the hill instead of the elevated contour surface? How can I use LASTE elevation?Yes sorry, I meant into the ground. AFAIK it basically points to the 3D point at 0 feet MSL. Provided LASTE is on, simply create a new waypoint and LASTE ground elevation will automatically be set as the waypoint's height.
Recommended Posts