Just came across the strangest bug I've ever seen. Please tell me someone else has seen this and knows what's going on.
Created an extrasolar system and marked a location on the surface of the planet. (Put that in a file I called Location.ssc) While I was working on it, I called the file containing the planet data Csys.ssc Works fine. Fly to that planet, look on the surface, and there's the label right where it's supposed to be.
I close out Celestia and decide to rename Csys.ssc (the planet data file) to Planets.ssc (a more descriptive name.) I don't rename the location file.
Next time I open Celestia, the location no longer shows up! Didn't change a thing IN the file itself, only the name of the file. Tried renaming it System.ssc, Temp.ssc, and a few other things, and it still didn't work. Rename it back to Csys.ssc, and it's there again. I close Celestia before I rename the file and restart it afterwards. (I even rebooted my computer at one point.)
Is there something hanging on to the old filename somewhere? Is there some glitch I'm unaware of?
FYI --
I'm running Celestia version 1.4.1
Doesn't appear to be an OS issue or a Video Card issue. Tried this on my Windows XP (SP2) machine and on my Vista machine and had the same results both places. My XP machine has an on-board graphics connection (Intel 82865G, I believe) and the Vista machine has an NVIDIA Quadro NVS 210S graphics card.
Any thoughts?
Thanks!
Location label disappears when ssc file renamed
-
Topic authorstarforce84
- Posts: 9
- Joined: 02.04.2007
- With us: 17 years 7 months
Celestia loads SSC catalog files in alphabetical order.
An object has to be defined before you can define locations on it.
Locations.ssc is alphabetically before
Planets.ssc
When Celestia loads Locations.ssc, Planets.ssc has not yet been loaded, so your planet is not yet defined, so the locations definition(s) fail.
When I need to have catalog files loaded in a particular order, I usually name them so they start with numbers:
001_planets.ssc
002_locations.ssc
etc.
001 is alphabetically before 002.
An object has to be defined before you can define locations on it.
Locations.ssc is alphabetically before
Planets.ssc
When Celestia loads Locations.ssc, Planets.ssc has not yet been loaded, so your planet is not yet defined, so the locations definition(s) fail.
When I need to have catalog files loaded in a particular order, I usually name them so they start with numbers:
001_planets.ssc
002_locations.ssc
etc.
001 is alphabetically before 002.
Selden
-
Topic authorstarforce84
- Posts: 9
- Joined: 02.04.2007
- With us: 17 years 7 months