2.19.1: WindSock(?) now takes geo coordinates instead of XYZ

[Amerio.Stephane]

Hello,

In our main terrain migrated from 2.19.0 to 2.19.1, we have this new error message:

ERROR 1: latitude or longitude exceeded limits
ERROR 1: latitude or longitude exceeded limits
ERROR 1: latitude or longitude exceeded limits
ERROR 1: latitude or longitude exceeded limits
ERROR 1: latitude or longitude exceeded limits
ERROR 1: latitude or longitude exceeded limits
ERROR 1: latitude or longitude exceeded limits
ERROR 1: latitude or longitude exceeded limits
ERROR 1: latitude or longitude exceeded limits
ERROR 1: latitude or longitude exceeded limits
ERROR 1: latitude or longitude exceeded limits
ERROR 1: latitude or longitude exceeded limits
ERROR 1: latitude or longitude exceeded limits
ERROR 1: Reprojection failed, err = -14, further errors will be suppressed on the transform object.

So far, I couldn't isolate its source cause. What could it be? It doesn't appear on other terrains, so I suppose it comes from one or many nodes in this specific terrain, maybe broken during the migration?

Thanks

[silent]

Hi Stephane,

It appears that there are errors related to GDAL/Proj. To my knowledge, there have been no changes to the GDAL/Proj versions in use, so the behavior should remain consistent in version 2.19.1.

Do you see these messages only in the editor, or do you see them during runtime as well?

Could you please send us a .world file (just single XML) without any additional content where you see these messages? It would be nice have the same file from 2.19 version as well (not migrated). This will help us better understand the situation.

Thanks!

[Amerio.Stephane]

Found it!

It was in our FlagComponent, where getMeteo()->getMeanWindSpeed() now takes geo coordinates instead of XYZ coords.

The issue is also present in IG Aviation add on, in EffectAircraft.cpp (lines 59 & 192). It probably also exists in your WindSock component.

Fix is simple, just a call to ig Converter()->worldToGeodetic().

Sidenote: I thought FlagComponent add been added to the engine (or an addon) but couldn't find it anywhere.

Sidenote bis: feel free to rename this post title, I clicked "Submit" a bit too early and forgot to set a meaningfull title. Sorry.

 

[cash-metall]

Yes, you are right! 
It was an error in the FlagComponent, which mistakenly passed world coordinates instead of geocoordinates.
The getMeanWindSpeed method has always expected geocoordinates. Apparently, we were lucky that the world coordinates didn’t exceed the geographic ones on smaller scenes, and there were no weather regions to notice incorrect readings.

 

[Amerio.Stephane]

Hi,

The issue is still present in ig_aviation add-on in version 2.20: getMeteo()->getMeanWindSpeed() now takes geo coordinates instead of XYZ coords.

(two instances in EffectAircraft.cpp)

 

[bmyagkov]

Hello Stéphane,

17 hours ago, Amerio.Stephane said:

The issue is still present in ig_aviation add-on in version 2.20: getMeteo()->getMeanWindSpeed() now takes geo coordinates instead of XYZ coords.

It seems there was a small mix-up between internal commits related to this fix. Fortunately, the issue has already been addressed. Please find the updated source file attached. Once it is replaced and rebuilt everything should work as expected.

We sincerely apologize for any inconvenience this may have caused.

Thank you for your understanding!

EffectAircraft.cpp