From: F. C. <fab...@go...> - 2009-01-19 10:16:20
|
Currently, there is no automatic set of the timezone when you choose a location from the location widget. This is in fact an important TODO item that I forgot to report! For this feature to work, the time zone info must be added to the base_locations.txt file. The second bug seems to be caused by the divergence of the moon position computation which return NaN, and makes the computation of earth moon barycenter also NaN, making the atmosphere rendering fail. Was this bug present in older version? Fabien On Mon, Jan 19, 2009 at 5:45 AM, Mike Storm <oop...@gm...> wrote: > Yes, it seems that there are two separate bugs here. There's the > rendering bug past year 80608, and then there's a general problem with > time and daylight. I would guess that these bugs have different > causes, or perhaps they're both rooted in buggy time code. Either way, > I vote that we fix them before the 0.10.1 release. > > Mike > > On Sun, Jan 18, 2009 at 10:23 PM, David Fox <dfo...@gm...> wrote: >> On Sun, Jan 18, 2009 at 4:08 PM, Mike Storm <oop...@gm...> wrote: >>> Does anybody else notice this? Stop time and set it to 0:48:14. >>> Advance the date to 80608/2/20, then either start time or manually >>> advance time by one second, to 0:48:15. On my machine, the sky goes >> >> I can replicate this as well (same svn revision) on ubuntu intrepid, >> using the nvidia driver (machine is a dual core Athlon/64 @3800 mhz). >> it doesn't go away while the time advances as normal. But if I revert >> to "now" it starts displaying at a normal rate as far as FPS's go (a >> little above 30fps is normal here). >> >> I'm confused about the precession in general. I know what it implies, >> of course, but for instance, take my normal location (San Jose, CA) >> and "now" being about 8pm. Now if I go into the date and time window, >> and cursor out the year to something around 2 AD or what have you, the >> sky is now daylight! I don't see how it would still be daylight in mid >> winter at my location. Or, keep the set time as per your example >> (0:48:14, IOW, after midnight) but cursor delete the year part >> gradually, and you're in daylight, or near twilight, at around 806 AD. >> Charlemagne must have had plenty of light for his parties :). Now, >> play with the location a bit (say move from San Jose, or your >> location, to Paris France, and there is no more daylight.) But if I >> move back it seems that it doesn't respect the local time any more if >> I'm viewing the sky at the year 800, for instance, just by increasing >> the time one hour at a time. >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by: >> SourcForge Community >> SourceForge wants to tell your story. >> http://p.sf.net/sfu/sf-spreadtheword >> _______________________________________________ >> Stellarium-pubdevel mailing list >> Ste...@li... >> https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel >> > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > _______________________________________________ > Stellarium-pubdevel mailing list > Ste...@li... > https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel > |