Jump to content

[NEED TRACK REPLAY]Entering waypoints manually produce incorrect coordinates


Recommended Posts

Posted

I agree with @Honey.

I can easily put JSOW rounds on target (either A or C) by using either (a) TOO + TPOD designations or (b) TOO + TPOD markpoints + waypoint designations.

 

But TOO + waypoints (LABORIOUSLY!) created off the F10 map and entered in the UFC, even in PRECISE mode (with elevation ASL in feet as well), send the round past the target doing nothing. Fuzing set in inst. So far only tried JSOW 154A.

 

Probably should get its own thread. If @Honey does not open one with tracks, I will later when I experiment more and get some tracks.

Posted
I agree with @Honey.

I can easily put JSOW rounds on target (either A or C) by using either (a) TOO + TPOD designations or (b) TOO + TPOD markpoints + waypoint designations.

 

But TOO + waypoints (LABORIOUSLY!) created off the F10 map and entered in the UFC, even in PRECISE mode (with elevation ASL in feet as well), send the round past the target doing nothing. Fuzing set in inst. So far only tried JSOW 154A.

 

Probably should get its own thread. If @Honey does not open one with tracks, I will later when I experiment more and get some tracks.

 

You AGL correct? If not, that could be your issue.

 

Cheers,

 

Ziptie

i7 6700 @4ghz, 32GB HyperX Fury ddr4-2133 ram, GTX980, Oculus Rift CV1, 2x1TB SSD drives (one solely for DCS OpenBeta standalone) Thrustmaster Warthog HOTAS, Thrustmaster Cougar MFDs

 

Airframes: A10C, A10CII, F/A-18C, F-14B, F-16C, UH=1H, FC3. Modules: Combined Arms, Supercarrier. Terrains: Persian Gulf, Nevada NTTR, Syria

Posted

 

You AGL correct? If not, that could be your issue.

 

Cheers,

 

Ziptie

 

That might indeed be the issue. The F10 map shows elevation in ASL. I assumed the elevation in the missile programming / waypoint designation would be ASL as well. Is that not the case?

Posted

 

That might indeed be the issue. The F10 map shows elevation in ASL. I assumed the elevation in the missile programming / waypoint designation would be ASL as well. Is that not the case?

 

I would think it would need to be AGL, other wise if you were in Nevada for example: 1500ft AGL would be a massive difference from 1500ft MSL. You know what I mean? some places in Nevada would be 3000 ASL at ground level.... Some places on other maps could actually be below 0 ASL.

 

 

You'd want the bomblet separation at 1500 AGL so they can disperse correctly, rather than driving all the way into the ground because ground level at that particular point could be 3000 MSL ......

 

 

Cheers,

 

Ziptie

i7 6700 @4ghz, 32GB HyperX Fury ddr4-2133 ram, GTX980, Oculus Rift CV1, 2x1TB SSD drives (one solely for DCS OpenBeta standalone) Thrustmaster Warthog HOTAS, Thrustmaster Cougar MFDs

 

Airframes: A10C, A10CII, F/A-18C, F-14B, F-16C, UH=1H, FC3. Modules: Combined Arms, Supercarrier. Terrains: Persian Gulf, Nevada NTTR, Syria

Posted

 

I would think it would need to be AGL, other wise if you were in Nevada for example: 1500ft AGL would be a massive difference from 1500ft MSL. You know what I mean? some places in Nevada would be 3000 ASL at ground level.... Some places on other maps could actually be below 0 ASL.

 

 

You'd want the bomblet separation at 1500 AGL so they can disperse correctly, rather than driving all the way into the ground because ground level at that particular point could be 3000 MSL ......

 

 

Cheers,

 

Ziptie

 

Sure, but it depends on what the weapon uses and expects -- AGL or ASL. Either would work. But if the weapon expects ASL and you give AGL it would be just as off as the other way around.

 

With (consumer) GPS you can easily get ASL based on the WGS spheroid. AGL is more complicated and requires terrain data to be available. No idea what the weapon uses or, more to the point, what the DCS implementation of the weapon.

Posted

 

Sure, but it depends on what the weapon uses and expects -- AGL or ASL. Either would work. But if the weapon expects ASL and you give AGL it would be just as off as the other way around.

 

With (consumer) GPS you can easily get ASL based on the WGS spheroid. AGL is more complicated and requires terrain data to be available. No idea what the weapon uses or, more to the point, what the DCS implementation of the weapon.

 

That is what I am wondering - if something in their recent update has switched the missile YT fusing to ASL rather than AGL. They used to work perfectly for me, and they've had some issues as of late with no separation (seem like they've not accepted the fusing I entered).

 

 

Cheers,

 

Ziptie

i7 6700 @4ghz, 32GB HyperX Fury ddr4-2133 ram, GTX980, Oculus Rift CV1, 2x1TB SSD drives (one solely for DCS OpenBeta standalone) Thrustmaster Warthog HOTAS, Thrustmaster Cougar MFDs

 

Airframes: A10C, A10CII, F/A-18C, F-14B, F-16C, UH=1H, FC3. Modules: Combined Arms, Supercarrier. Terrains: Persian Gulf, Nevada NTTR, Syria

Posted

Just've shot 8 154C's from max distance 36k feet in PP + manual coords. 7 hit, one fell short (likely entered wrong coords for that one). 154A's are totally random. Sometimes you hit 3 in a row, other times you miss 20 by a mile. Targets are on the shore (~20 meters ASL), so I don't think it should cause any issues. In the end, sometimes, A's properly pop and kill targets. I think, btw, in every guide out there people transferred target elevations from the F10 map as-is, directly, without any issues. Now it doesn't work for A's most of the time. And also a lot of time A's miss targets by a mile - neither AGL nor ASL should cause that to happen. Something is wrong.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...