FlightControl Senior Member



Join Date: Mar 2012 Location: Antwerp, Belgium Posts: 2,024

There is still a whole lot of things to sort out on this stuff...



1. Why is it that when white spaces are contained in folders, it results in strange path strings in the debugger.lua process? This kills the debugger.lua workings. I need to do research on this.



2. How to deal with "debug mode" and "run mode". It is very complicated. Loading a script dynamically from the .miz versus embedding a script in the .miz. This really needs to be given a big thought. There will be a change required in each test mission to allow for debug mode or test mode. Each mission designer will have to follow a process to accomodate this. So the process needs to be as simple as possible. Or 10000 questions will arise and the forums will be full of discussing people (again).



3. Documentation. Videos are nice, but the setup process should be written down. The LDT should be further explained. Q&A will come.



4. What about missions you get from somebody else, how to debug those... Needs to be thought about.



5. Is debug really working correctly? Are there no crashes?



The biggest challenge will be to EXPLAIN this to noob users who will really benefit from the debugger.



People see MOOSE as a wall of code and complexity. While in essence, it helps them to have more fun of the sim.



So, some homework is to be done to get this finished.



That being said, you are all welcome to "alpha" test with me this debugging capability. If you have questions, please ask.



The debugger is already helping me now to resolve issues of other people questions to give help.



FC