I would recommend either replacing this document with a simple set of links to my Steam guides or at least adding links to my Steam guides.
https://steamcommunity.com/sharedfiles/filedetails/?id=3247360849
Basic launch automation script, covering autostaging, launch to inclination, and a roll autopilot.
https://steamcommunity.com/sharedfiles/filedetails/?id=2944674093
Covers basics of vector math(especially defining and using reference frames), PID creation, and capturing user input in the context of a "hover and land at target" script.
I also have other guides on Steam, but they are not especially relevant to the subject of this document. While the Steam guides lack the comprehensive list of Vizzy blocks, they do document most of them (especially in the launch guide), and with the inclusion of screenshots and the like I would expect it to be more useful for people just getting started in Vizzy.
On the other hand, if people are looking at this project they probably don't don't want to get started in Vizzy, because Vizzy sucks for serious development work, but in that case the referenced document isn't especially helpful. A document that mapped Vizzy blocks to VizzyCode equivalents would be, but that would be a very different document.
I would recommend either replacing this document with a simple set of links to my Steam guides or at least adding links to my Steam guides.
https://steamcommunity.com/sharedfiles/filedetails/?id=3247360849
Basic launch automation script, covering autostaging, launch to inclination, and a roll autopilot.
https://steamcommunity.com/sharedfiles/filedetails/?id=2944674093
Covers basics of vector math(especially defining and using reference frames), PID creation, and capturing user input in the context of a "hover and land at target" script.
I also have other guides on Steam, but they are not especially relevant to the subject of this document. While the Steam guides lack the comprehensive list of Vizzy blocks, they do document most of them (especially in the launch guide), and with the inclusion of screenshots and the like I would expect it to be more useful for people just getting started in Vizzy.
On the other hand, if people are looking at this project they probably don't don't want to get started in Vizzy, because Vizzy sucks for serious development work, but in that case the referenced document isn't especially helpful. A document that mapped Vizzy blocks to VizzyCode equivalents would be, but that would be a very different document.