Hi Cameron, Yes, it has been a long time coming, but life doesn't always go as planned and you have to keep in mind that I do all this beside a busy full time day job, family, baby and other constraints. So I am happy to have reached this stage so far, even by changing directions from time to time. It is my first aircraft and I guess this is natural, if you learn along the way. You are right, I built my own C++ framework for development, as I usually prefer to code in this language and it was working fine. However, I didn't like the pain to compile for three different platforms. I even bought a Mac Mini, just to be able to compile my code for the Mac, but I didn't like the idea to also install Linux as well, even I like to provide the Beaver to Linux users. So like I said, it was painful and the code turn around times, when I did a single code change became annoying. I know there are workarounds like having two folders of the same aircraft, where you just swap .xpl files etc., but also this was annoying. Another developer suggested SASL to me and gave me a short intro and after trying it, I was hooked. I could implement my code within minutes and now I can re-load my plugin on the fly, without stopping a running simulation. This allows rapid development, prototyping and testing. I know that SASL has its limitations with respect to OpenGL, but since I am not into developing airliners or heavy avionics cockpits, there is absolutely no need for me. SASL also makes it very easy for me to implement GUIs and I just love it that way. Code encryption, if required, is a piece of cake and I can do it myself and the support for all three platforms is important for me as well, because I don't want to close the door for anybody, even Linux users might be a minority. So no stumbling blocks. It was more a question of ease of use, a more rapid and streamlined development process, which is just fitting my specific needs and my own customer support. I still prefer C++ over Lua, but I can easily live with it.