Luke Brown (1116943) Posted June 10, 2023 Report Share Posted June 10, 2023 (edited) Hi Juha, I have the pictured MSAW area defined, working ok in 2.4, but 2.5b2 gives me an error for the definition. I can't see any reason why this is the case? Spoiler P:18:N054.53.57.000:W006.19.23.000:N054.52.26.000:W006.11.35.000:N054.46.25.000:W006.15.51.000:N054.39.40.000:W006.13.48.000:N054.26.23.000:W006.04.35.000:N054.23.33.000:W006.07.33.000:N054.24.44.000:W006.17.44.000:N054.25.22.466 W006.21.45.133:N054.26.28.283:W006.25.49.425:N054.27.57.657:W006.29.30.615:N054.29.47.912:W006.32.42.341:N054.31.55.742:W006.35.17.867:N054.34.17.301:W006.37.13.331:N054.37.23.000:W006.38.30.000:N054.48.21.000:W006.33.45.000:N054.50.11.911:W006.31.00.635:N054.51.50.933:W006.27.29.908:N054.53.57.000:W006.19.23.000:2000 2.4 2.5b2 Edited June 10, 2023 by Luke Brown (1116943) Link to comment Share on other sites More sharing options...
Bernardo Reis (1096507) Posted June 10, 2023 Report Share Posted June 10, 2023 I've had to edit my MSAW definitions too, because some were not being recognized. That said, I'm not using MSAW now until I recheck the settings because it was giving me MSAW alerts inside inhibition areas. Link to comment Share on other sites More sharing options...
Juha Holopainen Posted June 10, 2023 Report Share Posted June 10, 2023 There's at least a missing ":" between N054.25.22.466 and W006.21.45.133. That would cause a fault to be flagged. Link to comment Share on other sites More sharing options...
Bernardo Reis (1096507) Posted June 10, 2023 Report Share Posted June 10, 2023 2 hours ago, Juha Holopainen said: There's at least a missing ":" between N054.25.22.466 and W006.21.45.133. That would cause a fault to be flagged. That's what I found out too. Our 2.4 definition had some spaces instead of ":" and it was still recognized. Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now