travists wrote:Updated status: Had successful test build.
All GUI.PY features are presently DOA and on hold, pending further research/examples
What exactly do you need?
You should have enough documentation within GUI.py itself, if documentation there isn't enough, let me know what isn't clear and I'll fill in the gaps.
Also, remember my earlier proposition: if you output an XML with the elements, I'll make an xgui.py function that loads it, then it's all about loading/saving XMLs.
travists wrote:Q1: are Q and R vectors math terms or internal labels? Anyone know how to convert XYZ rotations to Q and R vectors?
Orthonormal basis are usually specified in triplets: P, Q, R. When you know the base is orthonormal, you can omit one (say P) and the others imply it (ie: the engine can compute it). Usually Q is right, R is up. So all you have to do is send in Q the direction you want your model's "right" side to point to, and P the direction you want your model's "up" side to point to. It's too simple to be true right?
(PS: VS is renown not to follow standards and conventions, so it might depart a bit from the description given above - but the idea is the same)
travists wrote:Q2: will single mp3's work, or do even they need to be in a m3u list?
I think mp3's should work, but I'm not entirely sure.
Check main_menu.py, I seem to recall there's a credits room that plays a custom track.
travists wrote:Q3: Thoughts on decoding existing art? I know, gui.py klauss
Just can't get it to work right now.
Forget about existing art. Existing art should be re-coded to use gui.py and/or xgui.py, to make it editable with your editor. Otherwise it will be an unforgiving and endless job: existing base scripts are ad-hoc, hand-coded and completely unfriendly to an automated tool.