Hi,
Also, if we have two consistent time_t, why not simply subtract one from
the other, ABS it, and voila you have the time difference ? Or am I
missing something regarding usage of difftime ?
yes. there is no _standard_ mapping of the data type time_t to any
standard C/C++ data type.
Hi,
On Thursday 08 October 2009 17:29:21 James Turner wrote:
Related to the new route-manager: I could very easily define a string
property which contains a plain text summary of the filed flight-plan.
What is the magic required to expose that string (which be 200 or 400
bytes, I guess,
Hi,
On Thursday 08 October 2009 22:09:40 Martin Spott wrote:
If bandwidth is not a matter, then you'd probably want to jump on the
HLA train and join the CERTI/VirtualAir effort. They're offering
everything like subscribing to attributes and the such yet I have
to state that reduced
With today's SimGear CVS, I am getting the following compile error
Making all in props
make[3]: Entering directory `/home/dad/source-osg/SimGear/simgear/props'
g++ -g -O2 -D_REENTRANT -lOpenThreads -o props_test props_test.o
libsgprops.a ../../simgear/xml/libsgxml.a
On Sat, 10 Oct 2009, dave perry wrote:
With today's SimGear CVS, I am getting the following compile error
Making all in props
make[3]: Entering directory `/home/dad/source-osg/SimGear/simgear/props'
g++ -g -O2 -D_REENTRANT -lOpenThreads -o props_test props_test.o
libsgprops.a
Hi,
A recent checkin into SGAtomic.cxx brakes that.
Either provide a -march= option higher than i386 to your compile, or revert to
rev 1.3 of SGAtomic.cxx.
I am currently asking the author of that change what this patch should fix.
Greetings
Mathias
On Sat, 10 Oct 2009, dave perry wrote:
I have --build=i686 as a switch to configure. Where do I supply -march=?
You set CXXFLAGS and CFLAGS (but the latter might not be needed). My
configure line starts with:
configure CFLAGS=-O2 -g -march=core2 -mfpmath=sse -Wall CXXFLAGS=-O2 -g
-pipe
I'm working on my motion sim for xmas. Its powered by a vacum cleaner atmo..
One BIG BIG problem - am basicng the cockpit on Bravo and 787
The autopilot heading bug is very violent and JERKS to direction..
How can we solve that problem please because on my motion platform, I
cant keep up with
I haven't looked at these autopilot configurations (at least not for a long
time) but off the top of my head, I think this can all be fixed by tuning
the autopilot.
For instance, lowering the max aileron deflection from (-1 ... 1) down to
maybe (-0.1 ... 0.1) might be an interesting thing to
Actually my motion platform is at the momnet I am taking it one step at
a time.. ie so far its banking left to right by around 10 degree's which
kinda exagarrated the sim and is useful..
Anyone as a pilot at the moment can tip the aircfaft to lbank.. However
this jerk needs solving.. SO what
Do you really expect much help after that stuff you lot remark?
As a former autopilot designer I would suggest that what is needed is a rate
limit on roll angle demand within the autopilot. You could also try to add
some roll damping within the autopilot. It is possible that the FDM for your
We need to define the autopilot properly and define its behaviour.
At it's most basic I expect the autpoilot to fullfil the following
functions.
1) maintain a heading - ie go that way direction - this jerks
violently in the sim
2) Altitude hold - this works, and on the motion platform it works
Alan Teeder wrote:
Do you really expect much help after that stuff you lot remark?
Sorry.. guess it my frustration...
As a former autopilot designer I would suggest that what is needed is a rate
limit on roll angle demand within the autopilot. You could also try to add
some roll damping
This is a problem across the whole system and a mega
fault.
If you mean this sudden banking when after reaching a new wayoint: yes. It is
known and is still on the bug-list on flightgear.org anywhere.
There were some aircraft authors who had a workaround with nasal- to my
knowledge the
On Sat, Oct 10, 2009 at 3:23 PM, Heiko Schulz aeitsch...@yahoo.de wrote:
If you mean this sudden banking when after reaching a new wayoint: yes. It
is known and is still on the bug-list on flightgear.org anywhere.
There were some aircraft authors who had a workaround with nasal- to my
On Saturday 10 October 2009 22:33:01 Curtis Olson wrote:
Really, this is all in how the autopilot is tuned and configured.
FlightGear doesn't model realistic control surface deflection rates so it's
possible to command an instantaneous deflection of the control surfaces.
Control surface
Roy Vegard Ovesen wrote:
On Saturday 10 October 2009 22:33:01 Curtis Olson wrote:
Really, this is all in how the autopilot is tuned and configured.
FlightGear doesn't model realistic control surface deflection rates so it's
possible to command an instantaneous deflection of the control
From: Roy Vegard Ovesen [mailto:roy.v.ove...@haugnett.no]
Control surface deflection rate can be limited by inserting a low-pass
filter
between the output of the final PID-controller and the control surface.
THis
is done in the autopilot config file.
For JSBSim aircraft, you also have
On 10 Oct 2009, at 08:56, Olaf Flebbe wrote:
Also, if we have two consistent time_t, why not simply subtract one
from
the other, ABS it, and voila you have the time difference ? Or am I
missing something regarding usage of difftime ?
yes. there is no _standard_ mapping of the data type
19 matches
Mail list logo
