missions.create_flight_plans: a no-navigation zone in the way makes CMO ask the player to pathfind #30

New issue

Closed

opened 2026-10-13 23:15:33 -04:00 by vinny · 0 comments

vinny commented

2026-10-13 23:15:33 -04:00

Owner

Library rerun of 2026-10-14 (after #28's guard). Santa Clara AB was the target, inside the flow's no-navigation zone NO-NAV land E7A6QQ1V (a 1.6° ring around it). createFlightPlans made CMO stop the game with a modal question: "The strike planner could not generate a direct-path flightplan for HOLOLIVE #21 due to the presence of No-Navigation Zones. Do you want the pathfinder to attempt finding a route? ... the pathfinder will not allow aircraft to fly closer than 0.2 degrees (12nm at the equator) to any No-Navigation Zones." The operator answered Yes. The socket call timed out waiting (outcome_unknown), and the harness's unassign/remove were then correctly refused for the uncertain reservation. Its final sweep removed the mission.

Fix: the tester's tool (its 7f3bf9e) refuses, naming the zone, aircraft and target, when any active zone of the side lies on or within 0.2° of an aircraft's direct way to a target. It reads each zone through getnonavzone(guid), whose wrapper holds the corners (checked live). Also from this run: navigation.fly_pattern read back partial because the harness ordered 349 kn and CMO holds jets at 350 kn in an orbit; --pattern-speed now defaults to 350.

A library rerun needs a target outside every no-navigation zone: the flow draws zones over hostile bases and ships it isn't striking, and the guard now refuses a target inside one.

Library rerun of 2026-10-14 (after #28's guard). Santa Clara AB was the target, inside the flow's no-navigation zone `NO-NAV land E7A6QQ1V` (a 1.6° ring around it). `createFlightPlans` made CMO stop the game with a modal question: "The strike planner could not generate a direct-path flightplan for HOLOLIVE #21 due to the presence of No-Navigation Zones. Do you want the pathfinder to attempt finding a route? ... the pathfinder will not allow aircraft to fly closer than 0.2 degrees (12nm at the equator) to any No-Navigation Zones." The operator answered Yes. The socket call timed out waiting (`outcome_unknown`), and the harness's unassign/remove were then correctly refused for the uncertain reservation. Its final sweep removed the mission. Fix: the tester's tool (its 7f3bf9e) refuses, naming the zone, aircraft and target, when any active zone of the side lies on or within 0.2° of an aircraft's direct way to a target. It reads each zone through `getnonavzone(guid)`, whose wrapper holds the corners (checked live). Also from this run: `navigation.fly_pattern` read back partial because the harness ordered 349 kn and CMO holds jets at 350 kn in an orbit; `--pattern-speed` now defaults to 350. A library rerun needs a target outside every no-navigation zone: the flow draws zones over hostile bases and ships it isn't striking, and the guard now refuses a target inside one.

vinny referenced this issue from a pull request that will close it,

2026-10-13 23:18:58 -04:00

Flight plans refuse a no-navigation zone in the way (issue #30) #31

vinny referenced this issue from a commit

2026-10-13 23:19:50 -04:00

Flight plans refuse a no-navigation zone in the way (issue #30)

vinny closed this issue

2026-10-13 23:20:22 -04:00

vinny referenced this issue

2026-10-13 23:29:57 -04:00

Library harness: a flight plan target clear of no-navigation zones #32

vinny referenced this issue from a commit