Eclipse finder fails if "invisible" class definitions are us

Report bugs, bug fixes and workarounds here.
Topic author
DOJOMO
Posts: 49
Joined: 10.08.2005
With us: 19 years 3 months

Eclipse finder fails if "invisible" class definitions are us

Post #1by DOJOMO » 12.01.2011, 21:14

If "invisible" class definitions are used in ssc files for objects on or spacecraft orbiting a planet then the eclipse finder, in lunar mode, enters an endless loop and celestia has to aborted. It is not clear but "component" class may exhibit the same problem.
Celestia 1.6.0. and svn variarions up to 5063 (new stars and orbit render)

Regards, David.
Celestia svn 5178
Sony Vaio VPCF12c5E laptop Intel(R) Core(TM) i5 CPU M 450 @ 2.4GHz, 500gb hard drive, 1Gb nvidea GeForce GT 330M GPU Open GL 2.0, Windows 7 Professional 64 bit. Fully updated.

Avatar
selden
Developer
Posts: 10192
Joined: 04.09.2002
With us: 22 years 2 months
Location: NY, USA

Re: Eclipse finder fails if "invisible" class definitions ar

Post #2by selden » 12.01.2011, 21:50

Here's an SSC to demonstrate the problem.

Code: Select all

# This SSC demonstrates a bug in Celestia's Eclipse Finder
# when Class "invisible" or Class "component" is specified
# the Lunar Eclipse Finder hangs (or goes into an infinite loop, perhaps)
# The Lunar Eclipse Finder also hangs if no Class is specified for a
# SurfaceObject.

# When both Class statements are replaced by Class "spacecraft",
# the Lunar Eclipse Finder works fine.

SurfaceObject "efb1" "Sol/Earth"
{
#   Class "invisible"
   Class "spacecraft"

   Radius   0.0125
   Color [ 0 1 0 ]

    FixedPosition { Planetographic [ -107.6177275  34.0787492  2.124]}
   FixedRotation {}
}
SurfaceObject "efb2" "Sol/Earth"
{
#   Class "component"
   Class "spacecraft"

   Radius   0.0125
   Color [ 1 0 0 ]

    FixedPosition { Planetographic [ -107.6177275  34.0787492  2.15]}
   FixedRotation {}
}
Selden

Topic author
DOJOMO
Posts: 49
Joined: 10.08.2005
With us: 19 years 3 months

Re: Eclipse finder fails if "invisible" class definitions ar

Post #3by DOJOMO » 13.01.2011, 12:56

Thanks for the clearer explanation.

Regards, David
Celestia svn 5178
Sony Vaio VPCF12c5E laptop Intel(R) Core(TM) i5 CPU M 450 @ 2.4GHz, 500gb hard drive, 1Gb nvidea GeForce GT 330M GPU Open GL 2.0, Windows 7 Professional 64 bit. Fully updated.


Return to “Bugs”