[RESOLVED] BAD delta Lat/Long rejects West, is always off to the west

[LastRifleRound]

When setting up a PI profile, before if there was no wind, PI bombing with good designation was accurate enough.

 

Now, the delta Lat/Long option rejects any input to the west, and the bombing solution is always off to the west. Attached is a track of the PCN rejecting valid input. I tried this same mission with the waypoint name making it BAD and got the exact same bombing results.

 

Target is to the east, but bombing is off to the west. Testing if the input is inverse, I noticed I couldn't enter values to the west.

 

Will make another post showing the results of the bombing run. One for using waypoint name to make BAD, and another to use delta Lat/Long to make BAD. Both are the same.

mirage_PI.trk

[myHelljumper]

Hi, yes we didn't catch this bug when testing, sorry. It's already fixed internaly and it should be available next update.

 

Thanks for the report.

[LastRifleRound]

Are both the input being rejected and the bombing solution being off confirmed or just the input?

[myHelljumper]

Just the input, I didn't quite understand the bombing solution being off, is is a precision problem ?

[LastRifleRound]

Not precision, accuracy. Always off the same amount the same direction.

 

I need to do more testing and open a new thread when I have more information.

[LastRifleRound]

Finished my testing on the PI bombing accuracy, working great. Not sure if something changed with TAS, but it seems like you just need to be a bit more careful with the designation than I used to be. +20 deg dive and about 2500ft AGL gets great results when designating the IP. You get the symbology without having to overfly and you don't need to hit VAL. Good stuff! I use #CONVERT_TO_BAD to get around the delta Lat/Long issue.

[Galinette]

Also, rho/theta seems to work to the west (but it is not accurate to the meter)

Edited April 18, 2021 by Kercheiz

[myHelljumper]

Hi, this should have been fixed in the last update. I'm moving this to resolved, if you still have issues, you can post them here I'll reopen the report.

 

Thanks.