allow custom extension of activity area in landing challenge
I had a problem with creating a landing challenge based on a part of a star approach, that had way points further away than 10nm from the start.
When creating such a landing challenge with bushmissiongen, it always causes an error message generated right after starting into the landing challenge.
I finally found what caused this: What happens is, that bushmissiongen's generated xml file contains an entry, that makes the activity-area set to a 10nm radius to the destination by default.
The error is caused by the SubGoal "SGL_StayInLandingZone". For this SubGoal, there is a "CalculatorFormula" assigned to it, which is set to 10 (nautical miles). To fix this, put in a larger number, i tested with 30, and it worked.
The steps in detail: - have bushmissiongen generate the output, - then modify the generated XML file at the numerical value of CalculatorFormula for id "SGL_StayInLandingZone_aborted". - then compile
Suggestions: - Implement a field for the config text file that allows to set the value, i guess this doesnt need to be there by default, as most landing challenges are just right at 10nm. - Add this info into the documentation. Perhaps a second document could be usefull to explain possible manual modifications to the flt and xml files, which are not (yet) part of bushmissiongen's functionality? As there are probably many possible hacks like this, perhaps its best to collect them in some document for now, some of them might be very special so that they will not need implementation at all.
Feature will be available in v1.77 😊. Thanks for great input cptdev! BR, f99mlu