cannot repoduce and missing track file Waypoint designate doesn't slew the targeting pod

[Maolain]

Is there a bug or am I doing something wrong in the Hornet? I designate Air to Ground and select a laser or GPS guided weapon. I turn on the FLIR (either pod) and make it SOI. I dial in the waypoint where I know bad guys are. I click weapons designate and immediately the pod slews into the sky instead of at the waypoint. Thoughts as to what I'm doing wrong?

[Maverick806]

Is the waypoint elevation at ground level?

[Maolain]

I'm not sure if it's at ground level. Typically, I'll assign waypoints for my Hornet, placing a waypoint directly over the target. Perhaps this is where I've gone wrong.

[markom]

I think the default in mission editor is some 6000 ft for waypoints. Unless you set that to the ground level, you've made a WP in the air. In Hornet, waypoints are 3D. 

In the air, you can edit WPs coordinates (including altitude) from the UFC. In HSI, tap on DATA and edit there.

[rob10]

I'd agree that your waypoint elevation is almost guaranteed to be the problem.  As markom said, set it to zero in the HSI/DATA page and it will get you where you want.  HOWEVER, if you just set it as zero it might want to wander, so once you have the target in your pod, get the actual elevation from the pod and set the correct elevation based on that.

[markom]

That may be true, but 0 has mostly worked for me to get "close enough" to the area where I need to be, and then just manually adjust the actual targeting.

[rob10]

37 minutes ago, markom said:

That may be true, but 0 has mostly worked for me to get "close enough" to the area where I need to be, and then just manually adjust the actual targeting.

Totally agree.  It's generally more an issue if you want to linger on a spot.  If you're just getting the pod in the right area then selecting something right away just going to zero works.

[bfr]

10 hours ago, markom said:

That may be true, but 0 has mostly worked for me to get "close enough" to the area where I need to be, and then just manually adjust the actual targeting.

Only really an issue if you adjust to zero in HSI/DATA mid-mission. Setting a WP altitude to 0 ASL in the mission editor overrides it to the equivalent of 0 AGL automatically if I remember rightly from setting up my own training/quick & dirty missions.

[Lane]

On 3/9/2023 at 1:47 PM, bfr said:

Only really an issue if you adjust to zero in HSI/DATA mid-mission. Setting a WP altitude to 0 ASL in the mission editor overrides it to the equivalent of 0 AGL automatically if I remember rightly from setting up my own training/quick & dirty missions.

In mission editor yes, i think it is edited to the ground altitude value where is set the waypoint at the moment you enter a value under this level. 

However totally agree that the problem seems be the WP altitude for OP.  The only other case where it can seeems look as described is if the Designation point is too far for the pod to see it and i will say zoomed in

Edited March 10, 2023 by Lane