As Supporter I can say the Panel State Load/Save function works very good
As a casual browser of the Aerosoft forum, I can say the forum is littered with users reporting problems with that function. Just look at the forum for proof.
normally a Aircraft Feature should not affect GSX or your pirate protection
Of out all the possible urban legends about piracy protection, I find this the most imaginative one: how one could even think this would have anything to do with piracy protection, is really beyond me.
This thing that "Couatl is used for piracy protection", with users relate anything to the protection, sometimes borderlines superstition: do you realize the WHOLE GSX program, and it's a fairly complex one, is a program written entirely with the Python language, and Couatl.EXE is the language interpreter for it ?
Like any other program out there, it might have quirks and bugs, and considering what GSX does and how complex is and with how many different (and bugged too) airplanes and sceneries it has to deal with, it's reasonably stable, that doesn't mean that EVERY error you see coming out from it, should have anything to do with piracy protection "because it's happening in Couatl".
Just to make it even more clear: if it wasn't running inside the Couatl interpreter and, for example, we wrote it as a C++ DLL module, instead of that harmless and logged error message, we would have probably crashed the whole FSX with it. That's the main advantage of using Python, which is an interpreted language (Couatl.exe is the interpreter for it), it's usually very safe, even when a running program has an error, it's usually harmless and will not hard crash a PC, unlike C++ for example.
Yes, but on ground panel save state work without problems, only in the air I have the error and the CTD
So, it's ONLY happening when Saving the panel state, and it's ONLY happening when flying ? This is strange, because I would expect exactly the opposite: GSX is entirely disabled when the airplane is flying. But maybe this has something to do with the Save
NameError: global name 'logColor' is not defined
A different error today
It's still exactly the same error about the log color not defined, just happening in a different situation. Is still happening only when saving the panel state while in-flight ?