Hi Thorsten,
Wherever I mentioned 2.12, it was because that's the logical follow up on 2.10.
If we didn't decide anything, we'd "automatically" end up with 2.12 instead of
3.0.
That's all. I wouldn't worry too much about someone who's telling what other
people think, without he himself taking
Referring to the version number discussion, I've been given to understand here
http://www.flightgear.org/forums/viewtopic.php?f=19&t=20137#p185619
that there have been already "core developers referring to the next release as
2.12" a while ago who would now be "obviously pretty annoyed about it
The hang glider is using the UIUC fdm, right? Perhaps that is using a
float (6-7 digits of precision) to represent it's initial conditions ... or
somewhere in the startup pipeline or the flightgear interface to the uiuc
model, the initial lon/lat is stored as a float?
On Sun, Jun 23, 2013 at 5:2
Hmm, everything is fine if I use a different plane. Seems to be a hang
glider specific problem.
Monitoring the latitude and longitude variabel from the very beginning
shows, that both variables have at first indeed the correct values. Then
the latitude value suddenly jumps from 47.306263 to 47.306
Hi Ashirwada,
this feature is implemented but disabled by default in FG's source code.
To enable it, if you really want that (think twice), edit file
"src/AIModel/AIMultiplayer.cxx" and alter the "false" to "true" in
FGAIMultiplayer::FGAIMultiplayer() :
FGAIBase(otMultiplayer, false)
This ac
Hi Tom,
> How have you checked these values? I've just tried it myself and in
> the property browser exactly the same values appear.
I started FG with
--lon=11.379070
--lat=47.306263
--heading=155
--units-meters
--on-ground
and found me at --lon=11.3791 -
Hi,
Am 2013-06-23 22:27, schrieb D-NXKT:
> I noticed that positioning an aircraft at FG startup with --lon= and
> lat= has only a limited accuracy. It seems that only the first 7
> digits are read. This leads to an uncertainty of several
> meters/feet! For example lon=11.379070 --lat=47.306263 is
Hello,
I noticed that positioning an aircraft at FG startup with --lon= and
lat= has only a limited accuracy. It seems that only the first 7 digits
are read. This leads to an uncertainty of several meters/feet!
For example lon=11.379070 --lat=47.306263 is needed to place our hang
glider directly i
Hi John:
I'm wondering if anyone has any suggestions on getting this data into
the system so users can start flying over it.
I maintain a mirror for flightgear. (ftp://ftp.kingmont.com and
http://kingmont.com)
You might try contacting Curtis and see how you would go about putting
some of y
Dear sir/madam
I am a great fan of flightgear. I would like to point out that crashes in
flightgear is not simulated. so add simulated crashes in the next
flightgear version.
--
ASHIRWADA WIJERATHNA
--
This SF.net email
10 matches
Mail list logo
