Celestia Forums

Hi folks...

I'm making a new star for the OA Universe, and have an STC file ready to go. I can type in the name of the star, and it shows up, and I can even tab to it. However, I cannot get Celestia to select it, much less go to it. Any thoughts? here's the STC file, which is absolutely identical to others that I have used successfully (identical except for the star name and details, of course):



I'm using barycenters because it will be a double star as soon as I iron this out, but it is worth noting that I have easily used barycenter definitions for single stars before. in fact, this is essentially the standard format for stc's that I use when I make new stars....

...John...

It looks to me like it may be a bug in Celestia.

Note that "72 Aurigae A" is undefined, which means that there's something wrong in its definition.
If you turn on the console log, you'll find that it complains that it can't find "72 Aurigae".

If you replace the spaces in the names by underscores, then it works fine.

So... why would that one not work, and one that I had just made named "43 Ordinatus" be just fine?

Weird...

It's the nature of bugs to be weird

I'll move this to the Bug forum.

**laughs** That would be a great tag line, you know!

Anyway, a little addition: I left the underscore under the barycenter, but didn't use it for the star name, and both worked just fine. Weird indeed!

John, Selden,

Is it possible that Celestia requires Barycenter and/or star names to be unique in perhaps the first 8-10 characters? In which case "72 Aurigae A" would have the same name (in first 8-10 chars) as the Barycenter "72 Aurigae", so would probably be ignored.

Just a thought, that might provoke some experimentation. I hope I'm wrong.

Regards
CC

Even when the "star" is undefined, the Barycenter should still be selectable.

It isn't.

selden wrote:Even when the "star" is undefined, the Barycenter should still be selectable.

It isn't.

I see.
(and would have seen earlier, if I'd read your first answer more carefully )

Another case of inconsistent parsing at different points in the .stc file.

At one point, "72 Aurigae" gets converted to the abbreviated form "72 Aur", while at another it doesn't.

Therefore you end up with a Barycenter named "72 Aurigae", however everywhere else apart from the Barycenter definition the string gets converted to "72 Aur" (e.g. in the OrbitBarycenter parameter, or in the text input in Celestia).

Defining your barycenter as "72 Aur" will work.