From: Canberra, Australia
You are a jem, mate!
First off, the error I have jut detected had absolutely nothing to do with what you did in the interface. Rather it had to do with the movement of an inf gun platoon a few kms away. What was happening was that the platoon was moving in formation with its boss. The boss had two waypoints and had in fact moved past the first waypoint but for some reason had not removed it as it should. I can't tell why because it happened before the start. So the platoon for some reason, maybe it had been retreating, had to recalc its route. In doing so it creates an offset of its boss's route and seeds its waypoints by finding the closest index along the offset route that coresponds to the boss waypoints. Alas it it could not find an index that corresponded to the waypoint that should have been removed. However, it wasn't checking to see if the temporary found index was null or not, which it was, before adding it. Then when it tried to calc the route for the next leg it ended up with a null start and that caused the crash. I have fixed this now by doing a check and not seeding a waypoint. This means that it will ignore any waypoint passed by the boss already. So we should not have a repeat of this CTD.
However, I also got another assert when I tried to place a waypoint for the 21st Arty Bty in some woods. It should have automatically assessed that this could not move there and find a passable nearby loc. I'm going to investigate why this failed.