ThorstenB writes:
> On 16.04.2011 02:06, Pascal J. Bourguignon wrote:
>> The props data protocol ls command has a problem: there's no way to
>> determine that its output is complete (unless we use a timer, which
>> would mean that all ls commands would suspend the client for the time out
>> durat
But it's totally worth it (even with no sounds)
> > Merge commit 'refs/merge-requests/84' of
> git://gitorious.org/fg/fgdata into integration
> >
> > commit 4a25745ea96dac35a1069a2f85f0b6e72e38ed14
> > Author: Victor Slavutinsky
> > Date: Wed Apr 13 16:19:53 2011 +0400
>
> > 1) Initial a
> Merge commit 'refs/merge-requests/84' of
git://gitorious.org/fg/fgdata into integration
>
> commit 4a25745ea96dac35a1069a2f85f0b6e72e38ed14
> Author: Victor Slavutinsky
> Date: Wed Apr 13 16:19:53 2011 +0400
> 1) Initial adding of Vostok-1 spacecraft and carrier.
$ du -hs Vostok-1/
156M
On Saturday 16 April 2011 15:29:52 Arnt Karlsen wrote:
> ..more ways to skin this cat: IRL, flying or stalling like this
> into the grass, should bend metal or break wood propeller blades,
> but the engine should turn another 2/3 to 2 or 3 more revolutions
> plowing into the field. At high speed,
On Sat, 16 Apr 2011, ThorstenB wrote:
> Ok, thanks a lot Anders for these hints! I'll open a tracker issue for
> the particle issue - so we won't forget these details. Can you estimate
> on how bad this issue could get? Does it only mean a minor memory leak -
> or could it get really bad over time
On Sat, 16 Apr 2011 14:27:05 +0200, Arnt wrote in message
<20110416142705.0850290d@celsius.local>:
> On Fri, 15 Apr 2011 15:20:58 +0200, Geoff wrote in message
> <1302873658.8552.1.camel@DELL02>:
>
> > Hi Arnt,
> >
> > >> > >> http://geoffair.org/tmp/makefg
> > > ..idea for makefg-1.3.0: WE
On 16.04.2011 16:24, Anders Gidenstam wrote:
> On Sat, 16 Apr 2011, Anders Gidenstam wrote:
>
> Hmm.. I should have added that I looked at this in early September last
> year so it is not fresh in my memory.
>
> IIRC the current code already does the fundamentaly unsafe operation of
> adding items
On 16.04.2011 02:06, Pascal J. Bourguignon wrote:
> The props data protocol ls command has a problem: there's no way to
> determine that its output is complete (unless we use a timer, which
> would mean that all ls commands would suspend the client for the time out
> duration).
>
> I'm proposing to
On Sat, 16 Apr 2011, Anders Gidenstam wrote:
> My failed attempt to unlink the particle systems might provide some insight
> into that issue. The attempt is broken because the
> methods calls
>if (!Particles::getCommonRoot()->removeChild(item)) {
> or
>if (!Particles::getC
On Sat, 16 Apr 2011, Anders Gidenstam wrote:
I think that is a different leak from the effects. IIRC each particle
system is attached to the scene graph in (at least) two places: at the
emitter's location in the graph and in a global vector of particle system
updaters. IIRC they are never remove
On Sat, 16 Apr 2011, ThorstenB wrote:
> Another observation: I started an MP session at KSFO (lots of MP
> aircraft), then warped to the middle of nowhere (no MP aircraft).
> After about 30min I dumped the scene graph. Surprisingly, loads of
> osg::particles were still *in* the scene graph, referr
On 15.04.2011 22:22, Bertrand Coconnier wrote:
> Yes, a bug fix has been committed to fix instant replay with JSBSim
> aircraft (bug #294)
> https://gitorious.org/fg/flightgear/commit/11320e6b008eb85b8dff66a137f671743cc04580
>
> I think it should be applied to 2.2.0 as well.
Ok, thanks Betrand! Th
Hi,
had another look at memory consumption. The FG multiplayer (=AI)
aircraft classes seem fine - they are created/removed as expected. But
there are problems with some of our OSG-based simgear classes: they
are never removed at run-time - hence memory is eaten up.
Problems start at simgear::Effe
Mixing spaces and tabs is really ugly - I think cleaning up such a mess is good.
Many people like tabs, but disadvantage is that everyone uses a
different tab settings. Most editors I know use 4 or 8 spaces/tab as
the default. But since it's different for everyone, I personally
prefer spaces - at l
On Fri, 15 Apr 2011 18:07:42 +0300, Emilian wrote in message
<201104151807.42441.emili...@gmail.com>:
> On Friday 15 April 2011 17:36:12 syd adams wrote:
> > > Syd, about the fuselage contact points: they are internally
> > > represented as a gear object, only without the compression stuff
> > >
On Fri, 15 Apr 2011 15:20:58 +0200, Geoff wrote in message
<1302873658.8552.1.camel@DELL02>:
> Hi Arnt,
>
> >> > >> http://geoffair.org/tmp/makefg
> > ..idea for makefg-1.3.0: WEUSESYSTEMPLIB=1, WEUSESYSTEMOSG=1
>
> Already thought of, and done ;=))
..aha, I was in an hurry and wonderi
Well, at least it explains for me the many "whitespace errors" when updating my
datas
To be honest, I'm not happy about this.
And I never had probelms to read the files.
Heiko
> Datum: Samstag, 16. April, 2011 14:05 Uhr
>
>
> > -Original Message-
> > From: Frederic Bouvier [mailto:f
> -Original Message-
> From: Frederic Bouvier [mailto:fredfgf...@free.fr]
> Sent: 16 April 2011 11:52
> To: vivian meazza; FlightGear developers discussions
> Subject: Re: [Flightgear-devel] XML formating Was: [Flightgear-commitlogs]
> FlightGear Base Package branch, master
>
>
> -
Durk Talsma wrote:
> Hi All,
>
> As part of visualizing the AI ground networks from
within FlightGear, I've
> been trying to find out whether there is a simple way
of drawing them
> using a few OSG commands. As a start, for each of the
segments, I have a
> start and end position in latitude /
Hi All,
As part of visualizing the AI ground networks from within FlightGear, I've been
trying to find out whether there is a simple way of drawing them using a few
OSG commands. As a start, for each of the segments, I have a start and end
position in latitude / longitude coordinates, and I wou
- "Vivian Meazza" a écrit :
> Fred wrote
>
> >
> > Is it wise to reformat preferences.xml with a tab length set to 2 ?
>
> Well, it's better than the current mess of spaces and tabs. At least
> we can now read it.
*You* can read it with your own MSVC preferences
-Fred
--
Frédéric Bouv
On Fri, 2011-04-15 at 11:27 +0200, Erik Hofman wrote:
> On Fri, 2011-04-15 at 11:22 +0200, Durk Talsma wrote:
> > Like, Christian and Vivian stated earlier, I would also hate to see a patch
> > getting lost, especially when it contains promise. This is why I
> > originally suggested committing i
Fred wrote
>
> Is it wise to reformat preferences.xml with a tab length set to 2 ? see
> below :
>
> Le 15/04/2011 22:19, Flightgear-commitlogs a écrit :
> > - Diff
> >
> > diff --git a/preferences.xml b/preferences.xml
> > index 3
Is it wise to reformat preferences.xml with a tab length set to 2 ? see
below :
Le 15/04/2011 22:19, Flightgear-commitlogs a écrit :
> - Diff
>
> diff --git a/preferences.xml b/preferences.xml
> index 342734e..8612a78 100644
> --- a/
24 matches
Mail list logo
