Celestia Forums

I've written some paragraphs on how to use ScriptedOrbits and ScriptedRotations in Celestia 1.5.0:

http://en.wikibooks.org/wiki/Celestia/T ... iptedOrbit

http://en.wikibooks.org/wiki/Celestia/R ... edRotation

Some familiarity with Lua programming (celx scripting) is assumed. If you have suggestions for improving this documentation, please respond in this thread.

--Chris

The major item that's missing is a description of how one sets up the initial environment:

What does one put in celestia.cfg, if anything, and why?

What does one put in whatever file is mentioned in celestia.cfg, and why?

Where does Celestia look for the initial Lua files and why would one choose one location over another?

None of these items are described in a coherent manner anywhere that I've been able to find.

Problem:
ScriptedOrbit error messages spew too fast to read.

If there's a bug in a ScriptedOrbit somewhere, Celestia writes an error message to its console log every time it refreshes its window. As a result, these messages scroll faster than one can read and push the original messages out of the buffer, making it impossible to determine the mistake.

Suggestion: emit only the first and every 30th (or so) message when it's the same as the previous message, plus a counter to indicate how many times it has been generated.