There is a fix for this in JSBSim CVS. It should not be getting called in
FlightGear. It is used in the standalone version of JSBSim to generate a
"reset" file at a particular time, so that the aircraft can start at that
point in the same (roughly) state, later on in another run.
Jon
> -Orig
On Fri, 30 Jan 2009 21:25:48 +0100, Daan wrote in message
<4983624d.0702d00a.6d1c.2...@mx.google.com>:
> > This was a good day! Until someone reported once again how he ran
> > into this stupid ambiguity, and someone else posted a broken "fix".
> > And it won't be the last time that this happens.
Hi all,
I've just noticed that at least these jsbsim aircrafts create a file
named "initfile.xml", inside the directory I use to launch FG. Here is
the file content:
0
0
0
0
-0
0
0
0
0
that is not so disturbing as long as I don't have an important
Hi,
I am not so sure it is usefull to publish a package which is already
maintain by someone else. I am almost sure they won't integrated it.
The other point is debian 5.0 is about to bear, so the package list is quite
frozen right now. I think we have to wait a little in order to see new
packages
Ah, you're the one I got plib 1.8.5 from.
Thank you!
It would be nice to have it available, yes please :)
And maybe plib cvs/1.8.6 if you get a chance, too.
I'm kind of bummed it won't make it into debian lenny officially,
though.
Thanks again,
Ron
On Fri, 2009-01-30 at 23:27 +0100, Nicola
Hi,
I have already published the plib package 1.8.5 for debian.
I can publish again if you want.
Regards,
Nicolas
Le dimanche 25 janvier 2009 à 22:05 +0100, Laurent a écrit :
> Hi all,
>
>
> Here are some informations about plib 1.8.5 on debian, mandatory
> condition to add FG 1.9.0 to debia
On Fri, Jan 30, 2009 at 1:57 PM, Melchior FRANZ wrote:
> > A design goal of flightgear has always been to keep
> > itself contained in one area and be a good citizen of your hard drive.
>
> This assumption suggests a badly laid out file hierarchy.
No; it does not.
> It's tailored for FlightGea
* Daan -- Friday 30 January 2009:
> > This was a good day! Until someone reported once again how he ran into
> > this stupid ambiguity, and someone else posted a broken "fix". And it
> > won't be the last time that this happens.
>
> I hope this was not me,
It was you, but it wasn't your fault, no
> This was a good day! Until someone reported once again how he ran into
> this stupid ambiguity, and someone else posted a broken "fix". And it
> won't be the last time that this happens.
I hope this was not me, but I have a bad feeling that I did trigger this...
I just wanted to report a first u
* Curtis Olson -- Friday 30 January 2009:
> On Fri, Jan 30, 2009 at 12:59 PM, Melchior FRANZ wrote:
> Wow, I'm sorry if I caught you on a bad day.
This was a good day! Until someone reported once again how he ran into
this stupid ambiguity, and someone else posted a broken "fix". And it
won't be
On Fri, Jan 30, 2009 at 12:59 PM, Melchior FRANZ wrote:
> * someone off list, but IMHO this should be discussed openly:
>
> > [...] but the intent is for FG_ROOT to point to a top level
> > directory (i.e. the root) and beneath that would be bin/
> > data/ src/ lib/ include/ etc
>
Wow, I'm
* someone off list, but IMHO this should be discussed openly:
> [...] but the intent is for FG_ROOT to point to a top level
> directory (i.e. the root) and beneath that would be bin/
> data/ src/ lib/ include/ etc
There's only one reason why we need to point fgfs and associated
scripts and
> No. This is just a case of badly set FG_ROOT. The template file can
> be found under $FG_ROOT/Input/Joysticks/template.xml, just like the
> version file is $FG_ROOT/version. Set FG_ROOT accordingly!
>
If this is the case I think the windows based installed should set $FG_ROOT
correctly. I just
* Reagan Thomas -- Friday 30 January 2009:
> It looks like
>
> templatefile.append("Data");
>
> should be inserted before:
No. This is just a case of badly set FG_ROOT. The template file can
be found under $FG_ROOT/Input/Joysticks/template.xml, just like the
version file is $FG_ROOT/version. Set
Daan wrote:
>
> Hi,
>
> Let me shortly introduce myself. My name is Daan and I am located in
> the Netherlands. My interest in flying simulators goes way back, but
> so far I never ran into the FlightGear sim. Now I found it I am very
> keen on getting involved in the development and maintenance
Hi!
I thought one of the reasons for keeping the data package unchanged
was to have a small upgrade download available, with only the
executables inside.
I don't see it on the web page, has this idea been abandoned?
Not that I am personally interested in it, of course.
--
Csaba/Jester
-
Hi,
Let me shortly introduce myself. My name is Daan and I am located in the
Netherlands. My interest in flying simulators goes way back, but so far I
never ran into the FlightGear sim. Now I found it I am very keen on getting
involved in the development and maintenance of this system.
I wi
"Rob Shearman, Jr." wrote:
> The scenery is permanently installed. I do not run TerraSync.
>
> As stated in the original report, this occurred on two successive
> flights in two days.
Ah, ok, thanks for responding anyway.
Cheers,
Martin.
--
Unix _IS_ user friendly - it's just selecti
On 01/30/2009 03:44 AM, Tim Moore wrote:
> Give the new version a try please.
All better now. Thanks.
VIRT = 460 peak, 440 steady state.
Readers who aren't closely following the context should note
that we are referring to the "next" branch of _simgear_.
> Point of information: there are 2.6
John Denker wrote:
...
> Alas after doing that, the memory bloat remains, as bad as ever.
> I saw it peak at 905 megs at KASE before falling back to 888 megs.
>
> While were in the neighborhood: I did a fresh cvs update and the
> symptoms are the same, so we can't blame it on non-authoritative
20 matches
Mail list logo