As mission developers test their code, it is often handy to know the value of the current "MissionChronoMilestone". All of the sample missions have an area of logic within their big "processTimer()" functions that gets executed exactly once per second. It's easy to find that block of code because of the comprehensive source-code commentary introducing it. Look for thislittle comment statement to find it:
//Gethereonceeverysecond.
Within that "once every second" code block, consider inserting the following pair of new lines of code:
I find it handy to insert those two new lines at the very end of that "once every second" code block. That will cause the three-line, scrolling, "SystemMessagePanel" instrument on LAC's cockpit to display the current value of "MissionChronoMilestone" with an updated value every second. Very handy for troubleshooting MissionChronoMilestone code. You can delete those two lines later, as your mission is completed.
Last edit: bbosen 2020-06-24
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As mission developers test their code, it is often handy to know the value of the current "MissionChronoMilestone". All of the sample missions have an area of logic within their big "processTimer()" functions that gets executed exactly once per second. It's easy to find that block of code because of the comprehensive source-code commentary introducing it. Look for thislittle comment statement to find it:
Within that "once every second" code block, consider inserting the following pair of new lines of code:
I find it handy to insert those two new lines at the very end of that "once every second" code block. That will cause the three-line, scrolling, "SystemMessagePanel" instrument on LAC's cockpit to display the current value of "MissionChronoMilestone" with an updated value every second. Very handy for troubleshooting MissionChronoMilestone code. You can delete those two lines later, as your mission is completed.
Last edit: bbosen 2020-06-24