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.
>
> Erik
> But, an FDM interface needs to do more than shove a datastructure back
> and forth. There needs to be some higher level communication to tell
> the remote FDM when it should reset it self or when it should trim for
> in air or on the ground, and what trim conditions are requested (i.e.
> start i
Martin Spott wrote:
Well, I prefer you to understand it as well-meant lobbying, driven by
the strong feeling that FG needs this - not for me but for others who
could do much more by connecting an external FDM to FG than I ever
could.
Just have a look at the CIGI "Interface Control Document", the
Hi Curt,
"Curtis L. Olson" wrote:
> Martin Spott wrote:
>>Indeed this sounds interesting. Does it mean that FG will get a modern,
>>full-featured and stable interface for external FDM's ?
> Sounds like you probably have something more specific in mind than
> can be expressed in a single sentence
Hi Harald,
I'm compiling on Windows under Cygwin.
Where do I get winmm.lib from ? I can't see it within
my source, and all the goggle references suggest it is
included in a Microsoft or Borland IDE. I have a
winmm.dll though - should I link to that? If so, how?
Sorry if these questions seem a bi
Martin Spott wrote:
"Curtis L. Olson" wrote:
[...] However, it has only very basic out the window graphics. I'm
doing a (hopefully quick little) project to build an interface from
their software to FlightGear in order to use FlightGear as the visuals.
Indeed this sounds interestin
Erik Hofman wrote:
Buchanan, Stuart wrote:
SimGear installed OK (I think), so I don't know
whether I'm missing from timezone libraries or what.
Any idea?
/home/Stuart/SimGear/simgear/timing/timestamp.cxx:74:
undefined reference to [EMAIL PROTECTED]'
collect2: ld returned 1 exit status
Buchanan, Stuart wrote:
SimGear installed OK (I think), so I don't know
whether I'm missing from timezone libraries or what.
Any idea?
/home/Stuart/SimGear/simgear/timing/timestamp.cxx:74:
undefined reference to [EMAIL PROTECTED]'
collect2: ld returned 1 exit status
Are you running Window
"Curtis L. Olson" wrote:
> [...] However, it has only very basic out the window graphics. I'm
> doing a (hopefully quick little) project to build an interface from
> their software to FlightGear in order to use FlightGear as the visuals.
Indeed this sounds interesting. Does it mean that FG wi
"Curtis L. Olson" wrote:
> Update of /var/cvs/FlightGear-0.9/data/Aircraft/Citation/Panel
> In directory baron:/tmp/cvs-serv18501/Panel
> Added Files:
> Citation-II-panel.xml adf-radio.xml dme-40.xml radios.xml
> transparent-bg.rgb
> Log Message:
> Syd Adams:
>
> Changes to the Cita
Thanks Erik - I really appreciate your quick response.
I built the latest SimGear CVS snapshot, hit the same
problem, then realized my LIBRARY_PATH wasn't set.
Doh!
Running
export
LIBRARY_PATH=/usr/local/lib:/usr/local/include/simgear
got it to compile further, but hit the problem below.
SimGea
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.
Erik
___
Flightgear-
Buchanan, Stuart wrote:
So I can't just use Simgear 0.3.8?
I've successfully run make install,
You can try, but usually it requires the CVS version.
Erik
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/
So I can't just use Simgear 0.3.8?
I've successfully run make install,
--- Erik Hofman <[EMAIL PROTECTED]> wrote:
> Buchanan, Stuart wrote:
> > Thanks.
> >
> > I downloaded the latest "bleeding edge" snapshot
> from
> > the terragear.org website, which included the
> patch.
> >
> > I had to fi
Erik Hofman wrote:
double azimuth = -90 + 180.0*(0.5 + 0.5*daytime);
Oh, well, wrong again (but you get the point by now):
double azimuth = 90.0 - 180.0*fabs(1.0 - 2*daytime);
Erik
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
Buchanan, Stuart wrote:
Thanks.
I downloaded the latest "bleeding edge" snapshot from
the terragear.org website, which included the patch.
I had to fix acinclude.md4 for the latest automake,
but have hit a problem with ld. Is this another
version issue?
In a sense, You need SimGear (CVS versi
Thanks.
I downloaded the latest "bleeding edge" snapshot from
the terragear.org website, which included the patch.
I had to fix acinclude.md4 for the latest automake,
but have hit a problem with ld. Is this another
version issue?
Output below.
Thanks
-Stuart
Making all in e00
make[1]: Enterin
Erik Hofman wrote:
Given that 12.00 UTC is high noon and 0.00 is midnight it is now easy to
determine the sun azimuth for (0,0) by using the following formula:
double azimuth = -90.0 + 180 * daytime.
This should be:
double azimuth = -90 + 180.0*(0.5 + 0.5*daytime);
Erik
__
Hi,
I just tried an idea I had which was the following:
* Unix time represents the current time in seconds since 00:00:00 UTC,
January 1, 1970.
* There are 86400 seconds in a day
By combining these tow I can get the normalized UTC time-of-day (ranging
from 0.0 .. 1.0) at lat/lon (0.0 , 0.0)
Phil Cazzola wrote:
I haven't looked at this since I submitted the original message,
but will probably work on it again soon.
Ok. I will hold off committing this until you manage to get back to it.
Erik
___
Flightgear-devel mailing list
Flightgear
I haven't looked at this since I submitted the original message,
but will probably work on it again soon.
One note: I believe (but haven't verified) that because of where the
range selector is being placed in the scene graph, all the children
from the same tile are using the same range.
21 matches
Mail list logo
