brodyagaaa Posted January 19, 2022 Share Posted January 19, 2022 Link to comment Share on other sites More sharing options...
Marten@Stairport Posted January 19, 2022 Share Posted January 19, 2022 Can you please upload your log from plugins/SAM/logs as well. Link to comment Share on other sites More sharing options...
brodyagaaa Posted January 19, 2022 Author Share Posted January 19, 2022 1 hour ago, Marten@Stairport said: Can you please upload your log from plugins/SAM/logs as well. For sure 2022.01.19-14.34.56-log.txt Link to comment Share on other sites More sharing options...
Marten@Stairport Posted January 19, 2022 Share Posted January 19, 2022 (edited) Does that happen all the time or under a specific trigger? And can you please try resizing the SAM window? maybe that helps. Edited January 19, 2022 by Marten@Stairport Link to comment Share on other sites More sharing options...
siavee Posted January 20, 2022 Share Posted January 20, 2022 This seems to be triggered by the calculation of the runway entry points that has the same name. It should've been handled in the code, but apparently not in this case. @brodyagaaa from the logs, I take it that you are located at UKBB when this happened, is that correct? Can you please share the information of the specific UKBB that you're using? In the current default UKBB, I couldn't find holding point 6 that is listed in the error. Link to comment Share on other sites More sharing options...
Recommended Posts