> As for the Dragonfly, the performance just seems unreal, thought I've
> never flown on myself. I think we could replace it with the Dromader,
> a much higher detail aircraft with a pretty extensively detailed FDM.
>
What part of the FDM do you think is unreal? Having flown the Dragonfly
mys
> Should we now track the paternity of every single file and humbly cry
> for permission from the *main Developer* (with a capital 'D') of the
> aforementioned file for every single commit ? Or do we want to be
> pragmatic and accept that once a file is committed under GPL in git,
> any contributor
> I'll jump in with some quick background.
>
> Originally I developed a system where you defined your electrical system
> components and all the connections in a complex xml file. Then a C++
> module loaded this configuration at run time and used a simplistic
> approach to propagate the "juice"
> After some more grey hair,
Lucky man - at least you still have some hair left!
>
> 2) What are the rules for loading live METAR?
The metar realwx controller checks every 60 seconds for a station reporting
metar and loads that data if the station id has changed since the last check.
It also rech
I changed the fuel.nas recently to reflect the changes in the core code.
The /consumables/fuel/tank[n]/* properties for level, density and mass should
now automatically be set to reasonable values. I removed the code from
fuel.nas duplicating that (converting from gal_us to lbs to ltr to kg etc
> I am looking to time sync 3 machines running FG over the network and would
> like to sync the sim times to one master machine.
> I have them all on nfs but it seems thats not quite the trick.
>
> So what ever time the master is working on, be it from command at start, or
> selecting for example
> I'm currently busy with other stuff. But checking on what's going wrong
> with loading/unloading clouds and MP models may be worth a closer look.
There was a fix for a MP memory leak approx. two weeks ago:
http://gitorious.org/fg/flightgear/commit/8962477cfa10850cb459d7de754c9a435cc91293
Torste
> So, I am wondering:
>
> 1) Am I seeing something unrelated, which just by a funny coincidence
> obscures an error message from the Nasal code that it relevant for me by
> generating tons of warnings?
>
> 2) Am I seeing something related to what I do, e.g. am I using an
> ill-formed model somewh
>
> So can anyone advise what is the story here and how the *fuel-flow_pph *is
> defined? I assumed it was just a function on the engine in jbsim I need bit
> of a primer here.
>
There is Nasal/system.nas in the 737-300 directory. Around line 200 of that
file the code
pph1=getprop("/engines/eng
> Hallo everybody,
> I purchased a few rotary encoder and a bunch of 7segment displays to build
> a physical replacement of the Bendix KX165. I'm using Arduino which feeds
> data to FGFS on a serial connection. I'd like to update
> "instrumentation/comm[0]/frequencies/standby-mhz" property usin
For those who use Linux, this might be the most interesting news today:
http://www.debian.org/
http://www.archlinux.org/
http://www.opensuse.org/
http://www.gentoo.org/
http://grml.org/
All unified in a joint project.
Torsten
-
>
> "Others"? Who? Where in the code should I look for it? What should I search
> for?
>
Me ;-)
But even simpler for the microcontroller: the internal representation neither
khz nor mhz but channel. For the COMM, channel 0 is 118.000 Mhz and channel
759 equals 136.975 MHz. The formula to conve
> I've also been using CACHE_ALL since then - not seeing any problems. But
> I haven't checked memory consumption. So, what's the status about the
> OSG caching options, should we enable these? Tim?
Me, too. I had a few coredumps with the 4-nvidia-cards, 8 monitors
(multithreading=automatic) setup
> int
>
that's the nature of an INT: no fractions at all :-P
Torsten
--
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself;
WebMatrix provides all the features you nee
> HLA is a follow-on to DIS and SimNet developed by DARPA and would require
> either an extensive rewrite of FG to be HLA (Stanag 4603)
> compliant or a wrapper function, In addition, there is a thing called
> Run-Time Infrastructure (RTI) that handles the federates interfaces
Matthias Fröhlich ad
> Hello everybody,
>
> a valgrind log of recent FlightGear is available from
> http://dl.dropbox.com/u/15761796/valgrind.log
> (13 MB). A short version containing only the "definitely lost"
> backtraces is at
> http://dl.dropbox.com/u/15761796/definitely_lost.log
> (59 kB).
>
> The largest single
> This doesn't happen for static variables nor for data members. I'd
> assume that in case of SGReferenced objects, the same explicit delete is
> necessary to decrement the reference counter.
Isn't that what SGReferenced objects were made for? Automatic deletion?
Minimal but slight more complex exa
> 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
> To compensate the lack of feel and indirect visual indicators of the
> wind conditions in the simulator I am monitoring the
> properties /environment/wind-from-heading-deg and wind-speed-kt. This
> worked out pretty good the past two years. I cannot tell when it
> stopped working but last night I
ies [1] and you'll find the xml code
> enclosed.
>
> [1] http://fgfs.beggabaur.de/daten/fgfs-metar03.jpg
>
>
> Am Sat, 23 Apr 2011 21:25:17 +0200
>
> schrieb Torsten Dreyer :
> > > To compensate the lack of feel and indirect visual indicators of the
> &
> Yes, the booth was confirmed.
And this is a preview of what will be seen at the booth:
http://www.flightgear.org/forums/viewtopic.php?f=42&t=11881
don't miss it!
Torsten
--
WhatsUp Gold - Download Free Network Manageme
> [4] http://fgfs.beggabaur.de/daten/fgfs-metar04.jpg
> [5] http://fgfs.beggabaur.de/daten/fgfs-metar05.jpg
There is a little checkbox in the global weather dialog telling you if
you entered metar is valid and could be parsed by the metar parser. The
data in image #4 is valid, the data in image
Hi,
I just commited a patch to make the JSBSim turbulence models selectable at
runtime.
The turbulence model can be selected by setting
/environment/params/jsbsim-turbulence-model to either "ttNone", "ttStandard",
"ttBerndt", "ttCulp", "ttMilspec" or "ttTustin". The Milspec model is selected
by
> Just a heads up for today´s Git update.
>
> JSBSim.cxx(732): error C3861: 'round': identifier not found
>
> Atmosphere->SetProbabilityOfExceedence(
> round(TurbulenceSeverityTable.GetValue( tmp ) )
>
> Something else that is not in the MS version of the standard. ;-)
> Great! Thank you! I really like the turbulence model of JSBSim- feels much
> more realistic than the one from YASim.
All the credit for the model goes to the excellent JSBSim devs. I just built
the bridge that linked it into FG.
Torsten
-
I would assume that random-wind is there by intention and I wouldn't remove it
just to prevent user-error ;-)
Good to hear realwx is working now for you.
Torsten
> Ahoy Torsten,
>
> I think I figured out what bugged me here. Last night I ran FG 2.2.0
> and it still had the issue with the non wo
> Ok, thanks. We'll probably have to narrow it down to the exact OSG
> commit to see what changed there. If anyone else has a
> working/non-working OSG revision in between 11900 and 12419, you're
> welcome to let us know. Also, maybe someone has an extremely powerful
> machine and could help with
Am 18.05.2011 14:32, schrieb Ron Jensen:
> On Tuesday 17 May 2011 21:35:59 Jon S. Berndt wrote:
>>> What is the requirement from the FlightGear side for an atmosphere
>>> model?
>>> I'd like to remove the capability to drive the JSBSim standard
>>> atmosphere
>>> model from FlightGear, but first I'
Hi everybody,
during this year's LinuxTag, Martin Spott, Mathias Fröhlich, Thorsten Brehm
and myself developed a strategy and a concept about how to kick out new
releases of FlightGear on a regular schedule.
Please find our first draft here: http://wiki.flightgear.org/Release_Plan
For the imp
> It's as good a plan as any other.
There was another release plan? Wasn't aware of it ;-)
> However we missed the last planned
> release (2.2.0). I'm unaware of the reason(s), but I assume that release
> is dead.
Yes, we simply declare it dead. To much has changed since the day we branched.
> So
Hi Curt,
> I have an android phone myself, but everyone else involved in this
> UAS project is mac so I'll probably get out voted. :-)
but remember: iPxxx needs the app store do install software unless you
jailbreaked your device. App store is more or less incompatible with GPL
software.
I onc
> On Sat, May 28, 2011 at 2:09 AM, Roland Häder wrote:
> > maybe ThorstenB's commit ca668f8a373190093738a69a5b700d6fcc086c7c does
> > cause this? He wrote there:
> > Fix bug #285 textranslate and scroll animation with negative numbers
>
> Yes, the commit indeed breaks textranslate for many aircraf
> Thanks, will test it once I have safely landed in Palma De Mallorca
> (LEPA).
Hope you maintain VMC without a working attitude indicator!
>
> Okay, okay. Two T(h)orsten in one mailing list ...
Three, actually ;-)
Torsten (who was the first)
-
Am 31.05.11 20:00, schrieb Curtis Olson:
Are there any other options or ideas that I'm missing?
Can you spawn an external application and render it's output window on
top of FlightGear? If so, fgpanel might be worth looking at. You find it
in utils/fgpanel and an example how to use it is in
Ai
> Can you please update http://wiki.flightgear.org/Release_Plan with this
> very important information ? Something like a short description of
> current state ?
>
> Thanks a lot, Yves
Hi Yves,
this particular wiki page was written (mostly by myself) to document our
release plan. I tried to make
> we need to sit on this as
> 2.2.freeflightsim.org.. We need a marketing plam somwhat.. I hope we stick
> to release schedule..
We are currently well on track. We fixed many bugs from the tracker and now
that June has arrived, there are just roughly two weeks until we freeze 'next'
for the final
> Hi Torsten
>
> I only missed the statements from your message here in the list, which
> is very important to see current progress. Because i.e. Text on
> gitorious does not reflect the new plan. Sorry, I was away for some
> weeks ... Maybe I will add a "box" or something on top of the wiki page
>
> May is over, June is well on its way: time for another newsletter! Looks
> like summer already started accross the globe, given the slightly
> dissapointing number of contributions. I guess being outside is in favour
> of sitting behind a desk for must of us. :)
>
> Still, a small group of peopl
> I've pushed a code change to be able to control the amount of light
> scattering (or absorption) of the fog by adjusting
> the /rendering/scene/scattering property. A value of 1.0 is full
> scattering and a value of 0.0 is full absorption (unrealistic). The
> default is set to 0.8 now.
Erik,
pr
Hi all,
reaching our first milestone for 2.4.0, the code freeze of the main
development stream on June, 17th, I just increased the version number for
fgdata to match the version of simgear/flightgear which is currently 2.3.0.
If you get a version mismatch upon start of fg, please git-pull fgdat
Am 16.06.11 22:09, schrieb Ron Jensen:
> There are some valuable features in JSBSim now it would be nice to have in the
> release. Could someone please sync the latest JSBSim into the flightgear code
> please?
Does the new atmosphere code work well with FlightGear's atmosphere?
I remember we had so
Short version for the impatient reader:
Please do _NOT_ push any major changes or new features to simgear,
flightgear, fgdata until further advice!
Long version:
Anticipating the release 2.4.0, we reached our first milestone today.
The development streams for flightgear, simgear and fgdata on git
> I'm working on modifying the interface between JSBSim and FlightGear to
> work with the new JSBSim standard atmosphere model. There are two or three
> ways that the atmosphere model can be modified by the calling application:
Hi Jon,
since FlightGear has it's own atmosphere model, how will this
I also know that quoting white-space paths works well in "command.com"
Windows shells. But apparently it didn't work when terrasync called the
"system" function to call "svn". Unfortunately I have no means to test
any of this on Windows.
The following patch seem to do the trick for me, it allow
Am 24.06.11 11:09, schrieb Vivian Meazza:
> Looks to me as if the command has to include no white space, and that's it.
No, it may contain white space. It's just that we mix backslash and
forward slash in the local path.
This:
D:/terrasync test\Terrain/w130n30/w122n37
Is a complete mess (from Win
Am 24.06.11 09:22, schrieb xsaint:
> Good day,
>
> I am attempting to create a new node via nasal
> I will like to call the node as "TempNode" with a int value of 50 and i
> will like to create it at /sim[0]/temp/.
>
> If the node was created, it will look like /sim[0]/temp/TempNode with a
> value
>> Is this built-in function:
>>
>> svn_path_uri_encode()
>>
>> any help?
>>
> Yup, does the trick - no need for fancy formatting.
>
> I'll see if I can do a damned merge request this side of Monday.
>
> Vivian
>
>
But isn't this a function of libsvn and we are talking about external
svn and libs
Am 24.06.11 23:59, schrieb Torsten Dreyer:
>>> Is this built-in function:
>>>
>>> svn_path_uri_encode()
>>>
>>> any help?
>>>
>> Yup, does the trick - no need for fancy formatting.
>>
>> I'll see if I can do a damned merg
Am 26.06.11 19:52, schrieb ecro...@aerolineas.com.ar:
Dear All,
I am very sorry for bothering, but we need your help in order to learn
how to do an specifical configuration of Flightgear.-
We are developing a new flight dynamics model in Aeronautical
Engineering University of Argentina, and w
Am 26.06.11 21:59, schrieb Alan Teeder:
> I have some questions regarding how data gets from the joystick, keypad etc
> to the fdm. No doubt I will feel foolish when it is pointed out that it is
> documented somewhere, but to date I have had to rely on experimentation and
> copying of XML/Nasal cod
> over ambitious to expected a working and tested solution by release 2.5?.
Just to clear the everybodies understanding of release numbers: 2.5.0 is the
version number of the development stream after the release branch 2.4.0 has
been created. The version number of the release following 2.4.(n) wi
Hi all,
some time ago, Martin announced some special hardware for our FlightGear
presentations at FSweekend and LinuxTag. Today, after several month of mostly
bureaucratic adventures, he managed to ferry our new toy across roughly half
of Germany. This is even more noticeable given the fact, th
> Have you considered using something like this:
>
> http://www.simkits.com/products.php?groupid=54
>
>
Hell, No!
Isn't buying a complete plug'n play panel contrary to the spirit of an
open-source project? Despite the fact that it it goes way beyond the
limits of our budget, our own tool fgpanel
>
> ATC Flight Sim does exactly what Torsten does ... draw the
> instrument gauges in 2D on an LCD display and then put a flat panel
> over the top with holes cut out for the instruments to show through.
> ATC goes a step further and machines bezels to go around the
> perimeter of the opening
Let's start our traditional discussion about what aircraft should be in the
base package of the next release (2.4.0).
We currently have
- 777-200
- A6M2
- b1900d
- bo105
- c172p
- CitationX
- Dragonfly
- dhc2
- f-14b
- Cub
- SenecaII
- sopwithCamel
- ufo
- ZLT-NT
Should we change this setup?
T
> Anyone got any ideas?
Hi Stuart,
The correct usage would be
textranslate
vs-digit5
/autopilot/KAP140/settings/target-pressure-rate-fpm
0.1
1
1
0
0
textranslate
vs-digit4
/autopilot/KAP140/settings/target-pressure-rate-fpm
0
Typo!!! (see inline)
> Why?
> The order of computation is (example for digit2, propertyvalue=500):
> 1. get property value (500)
> 2. apply stepping ( 500 step 1000 = 0)
> 3. apply factor (0 * 0.0001 = 0 --> don't shift texture)
> or for propertyvalue=5500
> 1. get property value (500)
1. get prope
> Thanks!
>
> No idea how it could have worked before. I've committed an update as
> described above.
>
> However, I'm still seeing some strangeness:
>
> 1) Sometimes I'm seeing "99" rather than "100"
> 2) Even with these changes, the -1000 value is incorrect.
>
> I suspect that there's some fl
Am 06.07.2011 08:56, schrieb thorsten.i.r...@jyu.fi:
> I keep asking in the forum if anyone knows a plane that reliably
> intercepts glideslope when under AP control - so far no one has been able
> to come up with one. If someone here knows a plane, please let me know and
> I give it a try.
>
I spe
> Sorry, I should have been more clear. My original comment was about
> airliners and that's what I was still referring to. I fly the SenecaII
> quite frequently and have indeed never had any problems with its AP.
Ah - ok. I obviously missed you were mentioning airliners. Glad, that
it's working f
Hi,
I have two tasks for the next release to give away:
1) is anybody willing to donate some time browsing through the
commitlogs of SimGear, FlightGear and FGDATA to provide a changelog for
the release?
It certainly should not contain every single "new aircraft" but an
abstract of what cool
Am 06.07.2011 18:23, schrieb Gijs de Rooy:
> > Torsten wrote:
> > 1) is anybody willing to donate some time browsing through the
> > commitlogs of SimGear, FlightGear and FGDATA to provide a changelog for
> > the release?
>
> Durk started with one for 2.3.0. I hope we didn't loose any features
Hi,
one week to go, before we create the release-branch for 2.4.0.
We still have some 80 bugs in out bug tracker at
http://code.google.com/p/flightgear-bugs/issues/list
I'd really love to get this number significantly down before we branch.
Please browse to
http://code.google.com/p/flightgear-b
Am 11.07.2011 14:47, schrieb Jon S. Berndt:
>> Note that the JSBSim environment model is in the middle of a major
>> overhaul so I wouldn't make too much of it at this point. It would be
>> more interesting to see how it compares after the rewrite.
>>
>> Erik
>
> The architecture is, but it should
Am 11.07.2011 14:37, schrieb Stuart Buchanan:
> Hi Thorsten,
>
> I think we've gone beyond what can be done for the upcoming
> release, but comments below.
What I'd really love to see in the mid-to-long-term range is some kind
of unified weather system. It does not really make sense for an average
Hi,
I have a discussion with the current maintainers of the Catalina which
is going completely into the wrong direction.
I think they feel offended by our current feature-freeze state of the
fgdata tree and I fail to explain that to them.
They are French, I am German and we communicate in Englis
Hi all,
our first phase of the release progress will end this Sunday with the
creation of the release branch.
Because pilots are unable to perform tasks with more than one step
without having a checklist, I have created one for the branching process at
http://wiki.flightgear.org/index.php/Relea
Am 11.07.2011 22:05, schrieb Stuart Buchanan:
> [For a moment I thought this post was from Thorsten Renk, and got _really_
> worried ;) ]
Hehe - apologies for having so many T(h)orstens around here. The parents
of the mid 60s were not very creative with names...
>
> Do you see this as a problem wi
Am 12.07.2011 10:18, schrieb thorsten.i.r...@jyu.fi:
>
> Well, there's also a reason - the different design philosophy - and at
> some point you may want to consider that before you merge.
Rest assured, there won't be any merge of the weather system without you ;-)
>
> If you compare a system that
Am 13.07.2011 19:00, schrieb Curtis Olson:
> I think Gene put it well. We need to give them the benefit of the doubt
> and cut them some slack due to potential language/translation issues and
> if they are newer to the project they need some time to figure out our
> project culture and how things
> Also, as we are so often told that git can do everything, why can a
> post-release branch not be set up for new source code developments, or a new
> release/freeze branch specifically for the new release? I thought that was
> the whole raison-d´etre of the devel branch.
You certainly can do that
> I think the one reason for this view is the level of integration with the FG
> core, where you've had to work hard to override the global weather system
> through no fault of your own. I think with better integration, the
> local weather
> package will feel much more part of the whole.
I moved m
Am 14.07.2011 23:22, schrieb Gijs de Rooy:
> Feel free to add/edit/remove http://wiki.flightgear.org/Changelog_2.4.0
Well done - thanks.
I changed a few lines after browsing through the commitlogs until I hit
the tag for 2.2.0-RC1
Torsten
> ..how about historical weather from e.g. air crash reports?
>
fgfs --metar="add any metar you want here"
--
AppSumo Presents a FREE Video for the SourceForge Community by Eric
Ries, the creator of the Lean Startup Metho
Following our release schedule, I'll be performing some git operations
on our simgear, flightgear and fgdata repositories to finally create the
branches for the release.
I am planning to start tomorrow on Sunday, July 17th at 08:00 UTC and
hope to be ready in less than an hour.
The tasked to be
Am 16.07.2011 17:37, schrieb Arnt Karlsen:
> On Sat, 16 Jul 2011 10:34:33 +0200, Torsten wrote in message
> <4e214d19.20...@t3r.de>:
>
>>> ..how about historical weather from e.g. air crash reports?
>>>
>> fgfs --metar="add any metar you want here"
>
> ..replacing METAR IDs with a data file that FG
Am 16.07.2011 13:04, schrieb Torsten Dreyer:
> Following our release schedule, I'll be performing some git operations
> on our simgear, flightgear and fgdata repositories to finally create the
> branches for the release.
This will start _NO
Am 17.07.2011 10:05, schrieb Torsten Dreyer:
> Am 16.07.2011 13:04, schrieb Torsten Dreyer:
>> Following our release schedule, I'll be performing some git operations
>> on our simgear, flightgear and fgdata repositories to finally create the
>> branches for the releas
We just turned into the final approach to our release 2.4.0!
I have just created the branches release/2.4.0 for fgdata, simgear and
flightgear and created tags version/2.4.0 and version/2.5.0 for the
commits containing the version changes.
The master branch of fgdata and the next branches of si
Hi,
we now have a mailinglist for all those, interested in the activity of
the bugtracker. The name is - guess what - flightgear-bugs.
You may subscribe here
http://lists.sourceforge.net/mailman/listinfo/flightgear-bugs
to receive a message for any new or updated issue.
Please do not post bugs
> Okay, I wish I could do that myself, but I'm a little rusty on the windows
> build environment. If anybody could enlighten me which build files should be
> changed, I'd be happy to do so (last year I touched the windows build files,
> in response to James' Hudson server, but the results were s
> Looks like I missed pushing part of my local changes onto gitorious. It
> should be working now (apart from updating hte MSVC build files).
Hi Durk,
starting at KSFO without a parkpos define, I get a segfault in
AIFlightPlanCreate::createTakeOff()
because firstFlight is set to false and the
Am 25.07.2011 20:35, schrieb Torsten Dreyer:
>> Okay, I wish I could do that myself, but I'm a little rusty on the windows
>> build environment. If anybody could enlighten me which build files should be
>> changed, I'd be happy to do so (last year I touched the
> Okay, I'll have a look. I *thought* that I had fixed all initialization
> issues this morning, but maybe I introduced a related problem. I expect to
> find a solution later this evening. Thanks for reporting!
It's probably a good idea to initialize properties in the constructor to
NULL and ch
>
> Sounds like a good idea. In any case, I have just commited a fix that should
> solve the runway initialization problem.
OK - that fixed the initialization issue.
looking at the code, there is still one rwy initialization on line 517
in createClimb() like those you just moved.
And I now get a
Am 25.07.2011 23:19, schrieb Durk Talsma:
>
> On 25 Jul 2011, at 22:54, Torsten Dreyer wrote:
>
>>>
>>> Sounds like a good idea. In any case, I have just commited a fix that
>>> should solve the runway initialization problem.
>> OK - that fixed the in
Am 26.07.2011 18:35, schrieb Durk Talsma:
>
> On 26 Jul 2011, at 07:43, Torsten Dreyer wrote:
>
>> Am 25.07.2011 23:19, schrieb Durk Talsma:
>>> Okay, I'll have a look. Just to make sure: This is a problem that only
>>> shows up during program shutdown?
&
Am 26.07.2011 22:00, schrieb Torsten Dreyer:
> Am 26.07.2011 18:35, schrieb Durk Talsma:
>>
>> On 26 Jul 2011, at 07:43, Torsten Dreyer wrote:
>>
>>> Am 25.07.2011 23:19, schrieb Durk Talsma:
>>>> Okay, I'll have a look. Just to make sure: This is a
Am 26.07.2011 22:26, schrieb Durk Talsma:
> Hi Torsten,
>
> Thanks for the report. I can confirm the crash, which means that I'm
> optimistic that I find a solution tomorrow. I've just seen a similar report
> at the forum, so I should have at least two test cases for this.
Just noticed: happens a
Am 27.07.2011 11:04, schrieb Durk Talsma:
>>
>> This one happen also at KNID with 87bd2bf, AFAIK, KNID doesn't have any
>> ground network. In the meantime I reverted to friday evening FG
>> (3723de5) and then it was OK again.
>>
>
> I'm currently committing a fix for this problem. As I already susp
Am 27.07.2011 11:58, schrieb Durk Talsma:
>
> On 27 Jul 2011, at 11:54, Torsten Dreyer wrote:
>>
>> Here is another one to chew on: How to I close the ATC Dialog?
>> It pops up again every time I hit the Cancel button or press Escape.
>>
>
> Great that it work
> > TreeBin* treebin;
>
> > SGTreeBinList::iterator j;
>
> > bool found = false;
>
> >
>
> > for (j = randomForest.begin(); (j != randomForest.end()) && (!found);
>
> > j++) {
>
> > if (((*j)->texture == mat->get_tree_texture() ) &&
>
> > ((*j)->texture_varieties == mat->get_tree_varieties(
> However, I don't think my change will have affected this.
>
> While the number of trees displayed is increased, the total number
> of trees in the scenery is unaffected, it's just that more of those
> trees are visible at any given time.
>
> I'm also not sure if the tree model is shared in this w
FlightGear 2.4.0 will be released in a bit more than two weeks from now.
To reach a broad audience, I am looking for someone to write an
announcement, initially in English.
Also, very welcome are people able to translate this into their native
language and distribute it to their local press/fligh
Am 01.08.2011 20:18, schrieb ThorstenB:
> Hi,
>
> I checked the FG base package contents. It seems our build rule hasn't
> been updated in a while. The following directories / files aren't
> packed, though it would seem reasonable to include these:
>
> data/MP
> data/HLA
> data/runfgfs.bat
>
> Not
Am 02.08.2011 14:41, schrieb thorsten.i.r...@jyu.fi:
> Following the report of a Forum user, I've just tested ridge lift near
> Innsbruck with the ASK-13 with a recent (yesterday) GIT binary. It appears
> to me that ridge lift is indeed broken in the sense that the number
> computed and visible und
Am 02.08.2011 15:15, schrieb Torsten Dreyer:
> Am 02.08.2011 14:41, schrieb thorsten.i.r...@jyu.fi:
>> Following the report of a Forum user, I've just tested ridge lift near
>> Innsbruck with the ASK-13 with a recent (yesterday) GIT binary. It appears
>> to me that ridg
Am 02.08.2011 16:37, schrieb Torsten Dreyer:
> Am 02.08.2011 15:15, schrieb Torsten Dreyer:
>> Am 02.08.2011 14:41, schrieb thorsten.i.r...@jyu.fi:
>>> Following the report of a Forum user, I've just tested ridge lift near
>>> Innsbruck with the ASK-13 with a r
Hi,
with help of many talented people, we are now able to present FlightGear
2.4.0 RC4 for Windows. Please download your copy here
http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Win32/Setup%20FlightGear%202.4.0rc4.exe
Bugreports to this list or the tracker
http://code.google.com/p/flight
> It's quite possible that it's broken for a while - there are not so many
> glider enthusiasts around, I usually prefer to rely on thermals when I
> have time to do some soaring, and the last time I distinctly remember
> having used ridge lift is before September 2010... Good we caught it
> before
1 - 100 of 826 matches
Mail list logo
