[11/09/19 20:06:51.749][DEBUG] [Main Thread] Start time has altitude lock, calculating start time for -1
[11/09/19 20:06:51.749][DEBUG] [Main Thread] ConvertTargetAltitudeToTime -> Could not find time for altitude below 0
[11/09/19 20:06:51.749][DEBUG] [Main Thread] End time has altitude lock, calculating start time for -1
[11/09/19 20:06:51.749][DEBUG] [Main Thread] ConvertTargetAltitudeToTime -> Could not find time for altitude below 0
I think the problem is that all my targets have a start and end altitude of 0 now, whereas yesterday they didnāt, So what I can do is go through all my targets, set the correct time which will populate the altitude, save the sequence, make a backup of the sequence, then load SGPro again which will load up the sequence and then send the logs?
I used the planning tools, looked at when the transit time is, and added 5 minutes
Altitude lock was enabled before setting the time, so I have not clicked on the altitude lock at all since the original enabling
So to also verify I just went back in, did the left click and right click on the planning tools, disabled and re-enabled the lock, saved the sequence, closed SGPro, opened it back up, and same behaviour
wowā¦ that was terrible. There was no bug in SGPro, but rather a bug in the tool that secures the final exe before release. Took forever to figure out why I couldnt get it to fail like your screenshots