I certainly agree that the documentation is important, and it will be available soon. But I must say I think sometimes people expect too much documentation, as if it will be able to tell them how to do everything they want to do. Just knowing what a particular setting controls obviously does not tell you that, and with the nearly infinite possibilities in TG2, it would be impossible to document even a fraction of what you can do, let alone how to do it.
I think those people who already have a sense of how TG2 works will be empowered by more node documentation (which is coming), but the people that really need help are those at a more basic level. The User Guide will hopefully provide that. We expect to get a lot of people new to TG2 now that the product is finalized and being marketed more widely, so that is our short-term focus.
The other challenging aspect is simply one of time. I have been the primary author of TG2 documentation to date, aside the function nodes which Jo Meder has mostly written. While I do have a pretty good understanding of most nodes and settings, there are some key areas that even I don't know enough about to write authoritatively - Intersect Underlying, for example. This is an area of functionality that really only Matt can fully describe, as he wrote the systems that control it. Matt has obviously been busy with the critical elements of core development for a long time, and hasn't had much time to contribute to the documentation. Even now he and Jo both are dedicating time to post-release bug fixes, so time for other things is still limited. In the near future he will be able to put some time into those more complicated or obscure areas of TG2 settings, and this will complete the node reference and other documentation. But obviously there is a lot more to be filled-in in the meantime (most of it simply needing to be converted, which has been delayed due to the laptop issues I mentioned), and as I have said that is coming soon.
- Oshyan
