I committed a change that removes the cache from property tree path lookups.
This cache causes significant thread safety and other headaches, and my
tests show a negligible speedup from the caching. If you notice a big
performance hit and you think it might be related to this change, let me
know
Hello Durk,
I'd like to start working on ATC and AI with you. Not today and probably not
this month, but soon. I currently don't have a lot of time so let me make this
short and quote from IRC (hope you could manage to get on there).
My actual point being the following - I know this sounds a
However, the (so far to me unknown) C++ subrouting actually bringing
clouds into the visibly rendered scenery is even way slower - I can read
the message that the property writing is over after the expected 2.5
seconds, but continue to see clouds appear in the scenery for 30 seconds
and more.
Sydney would be better for me (to go hunt this scumbag down) than somewhere in
the USA - its only an 8 hr drive to Sydney for me, although I'd prefer to
fly...
:-)
Who knows where he actually trades from, I suspect with the number of aliases
used and web domains registered for the same
Curtis Olson wrote:
Out of curiosity, has anyone been able to obtain a copy of their source
code? Could this be posted in a known location? Or is there a known link
for downloading their code? It might be useful for us to maintain a
reference copy ourselves somewhere. It should be no
But would it be possible to accept old data, just not time going
backwards. I feel any METAR data is better than none, so perhaps;
1. accept any any valid METAR data, log warning message if it is old,
2. don't update METAR data if the date is older than current METAR date,
log severe
On 17 Nov 2010, at 13:32, Stuart Buchanan wrote:
As Martin and others have pointed out numerous times, what we have is
basically
a marketing failure on our part. If people had put as much effort into
marketing
and evangelizing FG instead of griping about an unlikely GPL violation, we
On Wed, Nov 17, 2010 at 7:32 AM, Stuart Buchanan wrote:
Hi Curt,
Not entirely sure whether you are being sarcastic or not, but I was able to
get hold of the source code (without buying it I might add). It's not
particularly
easy to get hold off, or indeed to un-tar (various semi-corrupt
On 17 Nov 2010, at 15:36, James Turner wrote:
The wiki has an official statement, it would be good to improve that, and
then make it official.
Err, that sentence is silly, apologies. What I mean is, it would be good to
promote the wiki statement widely, eg, the newsletter, other flight sim
Curtis Olson wrote:
On Wed, Nov 17, 2010 at 7:32 AM, Stuart Buchanan wrote:
I drafted an FAQ on this subject last time it came around, which was
discussed
in detail, but never published on our website. Perhaps we should look at
that
again? It would certainly help to have a official statement
Curtis Olson wrote:
The wiki is a good place to put something like this I think were it can
easily be updated as the landscape changes.
The Wiki is hosting, among a lot of serious content, a huge pile of -
to put it mildly - 'disputable' stuff, simply because _everyone_ can
edit there, no
On Wed, Nov 17, 2010 at 10:37 AM, Martin Spott wrote:
Curtis Olson wrote:
The wiki is a good place to put something like this I think were it can
easily be updated as the landscape changes.
The Wiki is hosting, among a lot of serious content, a huge pile of -
to put it mildly -
Hm, some need to read
http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg29013.html
again.
Gijs wrote (a lot more, but this is an important passage):
Of course we don't want some of our important pages (main page, download etc.)
to be edited by just anyone
with a wiki
On Wed, 17 Nov 2010, Curtis Olson wrote:
On Wed, Nov 17, 2010 at 10:37 AM, Martin Spott wrote:
Curtis Olson wrote:
The wiki is a good place to put something like this I think were it can
easily be updated as the landscape changes.
The Wiki is hosting, among a lot of serious content, a
Gijs de Rooy wrote:
[...] Luckily, we can add usergroups at the wiki and assign permissions to
them. Thus, important
pages can be locked (on the edit part) for the ordinary users. We've been
doing this with all Newsletters, which
can be edited only by wiki-admins after their publicication.
On Wed, Nov 17, 2010 at 4:41 PM, Curtis Olson wrote:
Ok, Stuart and Martin make a fair point. Lets move forward with putting
something onto the main FlightGear page. Stuart, you mentioned a faq you
had drafted?
Thanks,
Curt.
Hi Curt,
The latest version of the FAQ (v1.4) is below. This was
Ok, Stuart and Martin make a fair point. Lets move forward with putting
something onto the main FlightGear page. Stuart, you mentioned a faq you
had drafted?
I think it's all here:
http://sourceforge.net/mailarchive/message.php?msg_name=206864.11472...@web26005.mail.ukl.yahoo.com
Torsten
Hi all
Stuart wrote:
There is a version on the wiki, but it has since been modified by
various people to something more emotional and prejorative,
which nicely illustrates the point Martin and I were making :)
The emotional sentences you are refereing to were written before we decided on
Hi all,
I buy a new laptop and I install FlightGear GIT version. But I run the
FG gives segment fault.
/usr/local/games/FlightGear/bin/fgfs
--fg-root=/usr/local/games/FlightGear/data/
--fg-scenery=/usr/local/games/FlightGear/data/Scenery/
--aircraft=Concorde --callsign=mueddib
Processing
On Wed, 17 Nov 2010, Ozgur Karatas wrote:
Hi all,
I buy a new laptop and I install FlightGear GIT version. But I run the
FG gives segment fault.
...
Aircraft system element has problems in file
/usr/local/games/FlightGear/data//Aircraft/Concorde/Concorde.xml
Unknown exception in the main
On Wed, 17 Nov 2010 19:06:42 +0100, Torsten wrote in message
201011171906.43001.tors...@t3r.de:
Ok, Stuart and Martin make a fair point. Lets move forward with
putting something onto the main FlightGear page. Stuart, you
mentioned a faq you had drafted?
I think it's all here:
Digging into this deeper I have used strace -o Main.err make from
src/Main directory and have viewed the output. About the only thing
that shows up is missing
../../src/Instrumentation/KLN89/libKLN89.a
Also missing in KLN89 is RCS and SCCS directories.
Hey Group;
This may not even be a
22 matches
Mail list logo
