Edited Files not working

[climbingrog]

I've been doing some adding on and editing of some of my Celestia Files. I've got all the textures where they belong in the texture/medres folder, the .3ds files in the models folder, and the .ssc files in the extras folder, but while all the downloaded add-ons work fine. All the files I've edited with notepad don't work or are being ignored. This occurs even if I get the proper extensions right. Example: The minormoons.ssc file, or the extrasolar.ssc file which worked before, and not after I'd edited it. I had made the changes I'd wanted on that one, but then changed it back to the original way it had been. As a result I've lost all of my extra solar planets.

What am I doing wrong (Scratches head in bewilderment)

Roger

[selden]

Roger,

Even the slightest typographical error will cause an ssc not to work.
If you were to post one of the shorter ones that fails maybe someone might be able to help.

[Darkmiss]

im my experience of editing .ssc files
if you miss one } or { out of the text somehwere
then the rest of the code will not be read.

and its very easy to miss

also anything that is not code ie: info text
should have a # before it, too

I hope you find your problem.

if you say that none of your planets are showing
that would sugest that error, is early in the .ssc file.
post the first ten lines here to see if anyone can spot the error.

[chris]

I'm planning on having Celestia write all .ssc, texture, and model reading errors to a log file. To the average user, nothing will be different. But if you're creating worlds for Celestia, you'll be able to look at the file to get detailed information about anything that went wrong. The 'silent treatment' that you get now just isn't satisfactory . . .

--Chris

[Darkmiss]

That would be very helpfull

[ClimbingRog]

Thanks all of you! Thats what was wrong all right. I found mistakes in the coding on each case of my .ssc files not working. Paul it was in the top section on the minormoons.ssc file. I'd copied it over directly from the site without taking into account the top part was html. After editing those parts out it worked perfectly.