Feature Request: Splitting Class

[ajtribick]

In a Solar System Catalog (.ssc) file, there is the attribute "Class" which changes the object's behaviour. However it seems that the "Class" attribute does two different things.

Sometimes the Class attribute affects the rendering of the object, i.e. the "invisible" and "comet" class. All "Class" attributes affect the rendering of the object's orbit.

However if I wanted to set up a system with a binary planet orbiting the centre of mass and I model the centre of mass as an "invisible" object, the orbit of the centre of mass is invisible unless selected.

Would it be possible to include OrbitClass and RenderClass as subdivisions of Class: changing the OrbitClass would have the orbit treated as planet, moon, asteroid, comet etc, changing the RenderClass would cause the rendering of a cometary tail or invisible objects.

The original "Class" attribute could then be retained as a synonym for setting both, e.g. setting "Class" to comet would set both OrbitClass and RenderClass to comet.

So to set up my barycentre object I could set OrbitClass to planet and RenderClass to invisible.

Or would this be too difficult to implement at the moment?

[JackHiggins]

Why not just set the center-of-mass to be class "planet" ,but set the mesh of it as "invisible.3ds" so you can't see it? (theres an invisible.3ds available somewhere on the forum)

[granthutchison]

(theres an invisible.3ds available somewhere on the forum)

Tut, Jack, you have no memory for anything I do ...
It's here: http://www.lns.cornell.edu/~seb/celestia/hutchison/empty.html
Grant

[JackHiggins]

Sorry Grant

Next time i'll do a search first...

Is that the kind of thing you're looking for anyway chaos?

[ajtribick]

Thanks for the tip. Zavijava is now getting a binary planet...

[JackHiggins]

hehe Grant- just noticed your post count is currently "the number of the beast"...

666!!