Page 1 of 1

SSC location file encoding

Posted: 09.08.2009, 01:35
by PlutonianEmpire
I decided to try to make my Apollo addon more realistic, so I copied all of the solar system data files into the extras directory, and when I tried to condense it all into one big ssc file, and mass-replaced "Sol" with "SSB2" using microsoft word, I discovered that there was encoding used for the solar system location files, and that ms word automatically used special characters for some of the location names, resulting in a significant percentage of the locations not displaying in celestia.

How should I fix it?

The reason I merged all the files into one big file is that sometimes out of three separate ssc files, only two will show up in celestia.

Re: SSC location file encoding

Posted: 09.08.2009, 13:51
by selden
Word modifies the contents of the files. You might try using COPY instead. In a CMD window, type

COPY name1.ssc/B + name2.ssc/B outputname.ssc/B

The /B switches are needed to prevent COPY from inserting a Ctrl-Z in the output file. Replace nameN by the actual names of your files.

If you have Cygwin installed, you can use cat.

When using separate SSC files, they have to be loaded in the correct order. SSC files containing objects used in other SSC files have to be loaded before the files which use them. If the files are loaded out of order, some objects will be ignored because their parent objects haven't been defined yet. Under Windows, Celestia loads SSC files in alphabetical order. That's not always the case under MacOS or Linux.

Re: SSC location file encoding

Posted: 30.08.2009, 22:36
by PlutonianEmpire
selden wrote:Word modifies the contents of the files. You might try using COPY instead. In a CMD window, type

COPY name1.ssc/B + name2.ssc/B outputname.ssc/B

The /B switches are needed to prevent COPY from inserting a Ctrl-Z in the output file. Replace nameN by the actual names of your files.

If you have Cygwin installed, you can use cat.

When using separate SSC files, they have to be loaded in the correct order. SSC files containing objects used in other SSC files have to be loaded before the files which use them. If the files are loaded out of order, some objects will be ignored because their parent objects haven't been defined yet. Under Windows, Celestia loads SSC files in alphabetical order. That's not always the case under MacOS or Linux.
I tried that, but realized that I'd still have to go into the files and change "Sol/..." to "SSB2/..." and I used word to do it en masse, because, to be honest, I do not have the patience to do each line individually, and using word would mean it would modify the content of the file(s) in question.

What should I do?

Re: SSC location file encoding

Posted: 30.08.2009, 22:50
by BobHegwood
PlutonianEmpire wrote:What should I do?

Use Notepad2 to replace the offending characters. :wink:

Thanks, Brain-Dead

Re: SSC location file encoding

Posted: 30.08.2009, 23:12
by PlutonianEmpire
Thank you very much! :D