Is Lat/Long ok?

[GazAce]

Hey good folk,

Just wondering if there is a prob with Lat/Long co ords once loaded giving accurate position in TGP. I created a winter mission with heaps of snow and when I entered lat/long coordinates of a target from F10 map or F7 I was scoping around for ages and couldn't see anything. Dble checked CDU and re entered them, same thing, no luck except when I had to zoom out quite a lot. I know there are variances and I'm used to it being off a little ways but this was quite far. I threw the ruler on it and measured from tgt to original slaved diamond and it was like over 1.2 kms. Does the snow make a difference? I quickly loaded up another inbuilt mission in summer and it wasn't as bad. Just wondering if anyone else has this problem and maybe this is something that needs attention as part of Beta? Couldn't keep experimenting as it got too late.

Cheers G

[Frederf]

Perhaps you make an error with L/L format DD.DDDD° vs DD°MM.MM' vs DD°MM'SS'' or with altitude.

 

With what airplane or helicopter module did you have this error?

[GazAce]

Lat/Long query

 

Perhaps you make an error with L/L format DD.DDDD° vs DD°MM.MM' vs DD°MM'SS'' or with altitude.

 

With what airplane or helicopter module did you have this error?

 

 

 

Thanks for reply Frederf,

I fly A-10C, not sure what difference altitude has or the specifics relating to logging in co ordinates into my CDU has got to do with that but after I went thru the four different co ordinates or readings if you like. I may have found the problem or maybe you could advise me on this. Quite clearly there are two which I cannot load into my CDU but there are two definite Lat/Long. I'm thinking screen shot ending in 220833 would be the one to load yes? Or is it 220820? I usually have no dramas with this but last night seem to have a problem. Anyway, any help much appreciated.

Cheers Gaz

[Shadow KT]

Don't know if this is the case with you, but elevation does play a big part.

 

If you put in the coordinates of something which has an elevation of 2000 feet and you do not take that in mind, when you slay your TGP, it will try to look through the ground. If you imagine that in your head, you can see that, it might lead to quite the distance variation from the actual coordinates on the ground.

 

This is the case for shared SPI targets, but generally you should have no issues, if you are directly inputting the cords in the CDU

[GazAce]

Lat/Long all good but UTM quite awesome!

 

Don't know if this is the case with you, but elevation does play a big part.

 

If you put in the coordinates of something which has an elevation of 2000 feet and you do not take that in mind, when you slay your TGP, it will try to look through the ground. If you imagine that in your head, you can see that, it might lead to quite the distance variation from the actual coordinates on the ground.

 

This is the case for shared SPI targets, but generally you should have no issues, if you are directly inputting the cords in the CDU

 

 

 

Hey thanks a bunch Shadow I'll take that on board man. And just a few min ago I took a test flight and found that the 10 digit UTM co ordinates were more accurate but admittedly I was over the target but it directly locked my TGP right on it, I was around angels 11. I've used UTM before but only in ingame campaigns and not opting to choose myself because I wasn't entirely sure it was the right one but now I'll def use UTM more often in my own missions. Thanks again folks, cheers G