Bug Report: LoGetRoute() returns empty '.route' array if in NAV mode

[RvEYoda]

Summary

---------------

LoGetRoute() in export.lua returns empty array in the LoGetRoute().route field if you are in NAV mode. I only tested in F-15 so far - but the bug is probably global.

 

 

Steps to reproduce

---------------

Start a mission with navpoints (e.g. a campaign mission) with the F-15. Call LoGetRoute() (I have made a REST API to this but you can do it straight in lua or log to a file if you prefer that).

 

the .route field used to work.. (but last time I tried was 5+ years ago ;))

 

 

Broken data in nav mode:

 

   "route": {
       "route": [],
       "goto_point": {
           "world_point": {
               "y": 5486.3999023438,
               "x": -269634.84375,
               "z": 640402.5625
           },
           "speed_req": 250,
           "estimated_time": 160.32640176225,
           "this_point_num": 2,
           "next_point_num": 3,
           "point_action": "TURNPOINT"
       }
   }

 

 

Proper data in ils mode:

 

   "route": {
       "route": [
           {
               "world_point": {
                   "y": 1045,
                   "x": -279927.5,
                   "z": 701156.5625
               },
               "estimated_time": 1.6911933005115e-306,
               "speed_req": 98.140602111816,
               "next_point_num": 2,
               "point_action": "TURNPOINT",
               "this_point_num": 1
           },
           {
               "world_point": {
                   "y": 545,
                   "x": -282408.125,
                   "z": 692505.125
               },
               "estimated_time": 9.7910379792078e-307,
               "speed_req": 93.140602111816,
               "next_point_num": 3,
               "point_action": "TURNPOINT",
               "this_point_num": 2
           },
           {
               "world_point": {
                   "y": 45,
                   "x": -284888.71875,
                   "z": 683853.75
               },
               "estimated_time": 1.0013613270685e-307,
               "speed_req": 73.140602111816,
               "next_point_num": 4,
               "point_action": "TURNPOINT",
               "this_point_num": 3
           },
           {
               "world_point": {
                   "y": 45,
                   "x": -285204.40625,
                   "z": 682643.9375
               },
               "estimated_time": 0,
               "speed_req": 0,
               "next_point_num": -1,
               "point_action": "LANDING",
               "this_point_num": 4
           }
       ],
       "goto_point": {
           "world_point": {
               "y": 545,
               "x": -282408.125,
               "z": 692505.125
           },
           "estimated_time": 9.7910379792078e-307,
           "speed_req": 93.140602111816,
           "next_point_num": 3,
           "point_action": "TURNPOINT",
           "this_point_num": 2
       }
   }

Edited March 21, 2016 by =RvE=Yoda

[RvEYoda]

Has there been any update on this? Did you log the bug report in your internal systems?