strange issue with a ssc file

doctrellor · Post #1by **doctrellor** » 13.08.2006, 21:35

This is my first planet so bear with me..:)

after a few tries, I got my M3V star to work.. Celestia being picky about adding an extra line at the bottom of the .stc file...

So I tried my .ssc file, and I have tried now for about 6 hours, and I can't seem to get the orbit where the habitable zone is, about .112 AU, I even tried .5 AU, but nothing

Yet...

when I try farther out, say 2.5 AU, the orbit and planet show up fine...

so has anybody else found this issue? BTW, I am using 1.41 for the version

bdm · Post #2by **bdm** » 13.08.2006, 23:39

Can you post the SSC file so others can have a look at it?

Post #3by **selden** » 14.08.2006, 11:34

about .112 AU, I even tried .5 AU, but nothing

Celestia's input scanner is quite picky and doesn't generate enough error messages

Fractional values must start with a leading 0.
e.g. 0.15 works but .15 does not.
Also, positive values must not include a leading +, but negative values must include a leading -.

doctrellor · Post #4by **doctrellor** » 14.08.2006, 19:53

ahhh, ok cool, that leading zero might do the trick

thx...

if that doesn't work, I'll post my .ssc

doctrellor · Post #5by **doctrellor** » 14.08.2006, 23:42

sure enough, it's the leading zero

thx ..:)

Post #6by **chris** » 14.08.2006, 23:50

selden wrote:
about .112 AU, I even tried .5 AU, but nothing

Celestia's input scanner is quite picky and doesn't generate enough error messages

Fractional values must start with a leading 0.
e.g. 0.15 works but .15 does not.
Also, positive values must not include a leading +, but negative values must include a leading -.

It should be easy to fix the parser to allow both a leading plus sign and a decimal point without a preceding 0.

--Chris

Post #7by **chris** » 16.08.2006, 18:36

chris wrote:
selden wrote:
about .112 AU, I even tried .5 AU, but nothing

Celestia's input scanner is quite picky and doesn't generate enough error messages

Fractional values must start with a leading 0.
e.g. 0.15 works but .15 does not.
Also, positive values must not include a leading +, but negative values must include a leading -.

It should be easy to fix the parser to allow both a leading plus sign and a decimal point without a preceding 0.

The fix is now in CVS: both the leading plus sign and decimal point without preceding zero are now permitted.

This should help prevent some ssc editing frustration in the future.

--Chris

Post #8by **selden** » 16.08.2006, 18:38

Chris,

Thanks!

Adirondack · Post #9by **Adirondack** » 19.08.2006, 22:40

Code: Select all

The fix is now in CVS: both the leading plus sign and decimal point without preceding zero are now permitted.

Chris,

will this work in cel-scripts too?

Adirondack

doctrellor · Post #10by **doctrellor** » 19.08.2006, 23:31

Thanks Chris

Post #11by **chris** » 19.08.2006, 23:44

Adirondack wrote:
Code: Select all
The fix is now in CVS: both the leading plus sign and decimal point without preceding zero are now permitted.

Chris,

will this work in cel-scripts too?

Adirondack

Yes. Cel scripts share the tokenizer (the part of code that I fixed) with the ssc parser.

--Chris

doctrellor · Post #12by **doctrellor** » 20.08.2006, 21:14

OK, I finally got 1 thing thru my thick skull..

use multiple .ssc files for each "group" of objects in the system

so I am finally going with 5 .ssc per star

1) asteroid belt
2) Comets
3) planets
4) Kuiper Belt stuff/Oort cloud stuff
5) Misc stuff

I finally 'saw the light' after going thru the "solar system" sscs and seeing what was going on...

I know you guys must think I am a total pain for asking all my questions, but hey, I'm learning..lol