Re: [Flightgear-devel] OT: Mojave, CA
"Curtis L. Olson" wrote: > The other issue to consider is we could create the worlds most super > whiz bang remote FDM interface, [...] I don't feel it's so much about whiz bang. To make those people happy (to whom I've been talking) I expect it would be sufficient to write down a bit pattern of the current version on your most preferred platform, declare this document as the 'official' FlightGear network FDM interface description and, this is actually the point, make sure that this doesn't change with the next version of FG or on another CPU. These people don't want to risk adjusting their FDM to a moving target. They'd like to see an interface that they can rely on - at least for a predictable amount of time instead of starting reverse-engineering with every new version. These people don't write their FDM in C, the way they generate FDM output probably differs significantly from the way the data is generated by FG itself (if used as a standalone FDM). That's all. This doesn't mean the interface has to be changeless for the next ten years. If the need arises to apply changes to the interface then you could simply update the interface description and point at the changes. Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Sun Azimuth [Was: licensing problems in SUSE Linux]
Erik Hofman wrote: But if you don't mind I'm still working on my own solution, I already have the code to compensate for lon and daylight saving time. Which is silly since daylight saving time isn't something nature provides for us, but which is man made. So that code is commented out again. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Sun Azimuth [Was: licensing problems in SUSE Linux]
Steve Hosgood wrote: Durk is quite right. It's non-trivial, but dealing with all these issues is not really a problem. I'm in the middle of doing it myself, but have just only just got back from a week on vacation. My main interest is in removing the use of Xearth's "find the point on the planet where the sun is overhead" routine and replacing it with the more obvious "what is the current altitude and azimuth of the sun seen from a given location". Doing that will make all the solar (and lunar) astronomy code use standard algorithms from Peter Duffett-Smith's books and thus make sure there can be no problems with Xearth's non-GPL code causing trouble for FlightGear. That would be great. But if you don't mind I'm still working on my own solution, I already have the code to compensate for lon and daylight saving time. Let's see what comes out of it ;-) Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Sun Azimuth [Was: licensing problems in SUSE Linux]
On Mon, 2005-08-08 at 06:31, Durk Talsma wrote: > On Sunday 07 August 2005 15:54, Erik Hofman wrote: > > Erik Hofman wrote: > > > Is this correct or am I missing something? > > > > I just realized that you also need to adjust for day-of-year to > > compensate for the out-of-center rotation that causes long days (and > > nights) for both polar areas. > > > Just looking through your mails quickly, it looks like you also need to > compensate for the fact the the earth's rotation axis is tilted by about 23 > degrees, [plus] the earth's orbit around the sun > is not a perfect sphere, but an ellipse. Durk is quite right. It's non-trivial, but dealing with all these issues is not really a problem. I'm in the middle of doing it myself, but have just only just got back from a week on vacation. My main interest is in removing the use of Xearth's "find the point on the planet where the sun is overhead" routine and replacing it with the more obvious "what is the current altitude and azimuth of the sun seen from a given location". Doing that will make all the solar (and lunar) astronomy code use standard algorithms from Peter Duffett-Smith's books and thus make sure there can be no problems with Xearth's non-GPL code causing trouble for FlightGear. Steve. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
