Re: [Flightgear-devel] condition/mixture control

On Sun, 27 Jan 2008 18:37:19 -0800 Syd&Sandy <[EMAIL PROTECTED]> wrote: > Does anyone have any objection to binding the mixture " M/m" control to the > Condition control , since they both are fuel controls on different engines ? > Here I have just set this in the controls.nas file ... > > var mi

[Flightgear-devel] condition/mixture control

Does anyone have any objection to binding the mixture " M/m" control to the Condition control , since they both are fuel controls on different engines ? Here I have just set this in the controls.nas file ... var mixtureAxis = func { var val = cmdarg().getNode("setting").getValue(); if(siz

Re: [Flightgear-devel] Air Traffic Control (ATC). Fixing bugs and adding new features.

* Daniyar Atadjanov -- Saturday 19 January 2008: > This (attached) diff fixes only two (little) bugs in Tower-ATC: Ah, great. (Will commit after testing.) > But this is a very little changes. What about other new feature to > make ATC more realistic? This whole subsystem isn't maintained at t

Re: [Flightgear-devel] trees

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Curtis Olson wrote: | On Jan 27, 2008 12:50 PM, Tim Moore <[EMAIL PROTECTED] | > wrote: | | You've got that right. The approach I'm taking in integrating | Stuart's work is to not | depth-sort the trees at all. Ins

Re: [Flightgear-devel] Environment build problems under Cygwin

> Hmm, this sounds very familiar. I can't give a solution right now, but > if all > is well I have some notes on my old laptop, regarding a fix for these > unqualified-id errors. IIRC, the solution is very very simple (adding a > conditional include, or something like it), but I will have do dig >

Re: [Flightgear-devel] Environment build problems under Cygwin

On Sunday 27 January 2008 16:28, Jon S. Berndt wrote: > I'm having a pretty bad time trying to get past this set of compile errors > when trying to build the latest FlightGear from CVS under cygwin: > > make[2]: Entering directory > `/cygdrive/d/jon/FlightGear-1.0/source/src/Environment' > g++ -DHA

Re: [Flightgear-devel] Compiling FlightGear under Cygwin

Hi Jon, On Sunday 27 January 2008 05:29, Jon S. Berndt wrote: > Is there anyone out there who has tried to compile FlightGear under Cygwin? > I've been running into an increasing number of compile errors. If anyone > else out there has gone through this before and knows what needs to be done > to

Re: [Flightgear-devel] trees

* Melchior FRANZ -- Sunday 27 January 2008: > The problem at the moment is that [...] This isn't really the cause for the long startup time, though, as this is also the case when that variable is unset. And, of course, OSG doesn't search the whole harddisk. :-} But it could be something related.

Re: [Flightgear-devel] trees

* Curtis Olson -- Sunday 27 January 2008: > Would this speed things up: > > find / -name '*.ac' -exec osgconv {} /`basename {} .ac`.osg \; > > (i.e. create a model.osg in / for every model.ac on your hard drive?) Could be, but I wouldn't want that. This has the potential to break a lot. The prob

Re: [Flightgear-devel] trees

On Jan 27, 2008 2:00 PM, Melchior FRANZ wrote: > One can show the view immediately with > > --prop:sim/sceneryloaded-override=true > > but still, OSG takes a lot longer to finish loading scenery objects. > Maybe that's because it scans the whole harddisk for instances of > cow.osg ... ;-) Woul

Re: [Flightgear-devel] trees

* Curtis Olson -- Sunday 27 January 2008: > One of the reasons (I think) that OSG start up times are so long is that the > loading is getting interleaved with the FDM and everything else, but we > aren't actually showing the view until the loader has loaded enough data. One can show the view immed

Re: [Flightgear-devel] trees

On Jan 27, 2008 1:21 PM, Norman Vine wrote: > < note I haven't dug into the code either > > > The standard way of doing this is to time limit the loader > Thread. Eg loading trees only a few per frame as time allows. > perhaps into a temporary data object. > > The OSG LOD loader thread is an exam

Re: [Flightgear-devel] trees

Curtis Olson writes: > > (I haven't dug much in the code for these trees, but ...) it > appears that the random locations are computed as areas come > into view (or come close enough to the viewer.) So each time > a new chunk of trees are added, I see a blip in the frame > rates. If there ar

Re: [Flightgear-devel] Log Stream patch

On Jan 27, 2008 3:51 AM, Frederic Bouvier wrote: > Stuart Buchanan a écrit : > > Hi All, > > > > One of the frustrations of using Windows for development is the lack of > a > > sensible way to re-direct stderr to a file. This is particularly > annoying if you > > want to use a --log-level=debug. >

Re: [Flightgear-devel] trees

On Jan 27, 2008 12:50 PM, Tim Moore <[EMAIL PROTECTED]> wrote: > You've got that right. The approach I'm taking in integrating Stuart's > work is to not > depth-sort the trees at all. Instead: > > crank the alpha test value up > draw the trees after the terrain so the sky doesn't appear to poke th

Re: [Flightgear-devel] trees

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Curtis Olson wrote: | On Jan 27, 2008 8:00 AM, Maik Justus wrote: | | Yes, that did it. There is a problem with the draw ordering leading to a | transparency bug. It seems, that the trees are done by only two | triangles, intersecting each

Re: [Flightgear-devel] Problem with compiling OSG

Hi, I had the same problem today: last week OSG compiled fine, but no more today. After several attempts to resolve this point I discovered that if I try to compile OSG with CMake 2.4.8 it works fine. If there is no real requirement to use the current CMake development dist, you can tell f

Re: [Flightgear-devel] trees

On Jan 27, 2008 8:00 AM, Maik Justus wrote: > Yes, that did it. There is a problem with the draw ordering leading to a > transparency bug. It seems, that the trees are done by only two > triangles, intersecting each other. Due to the intersecting none of the > two possible orderings are correct. A

[Flightgear-devel] Environment build problems under Cygwin

I'm having a pretty bad time trying to get past this set of compile errors when trying to build the latest FlightGear from CVS under cygwin: make[2]: Entering directory `/cygdrive/d/jon/FlightGear-1.0/source/src/Environment' g++ -DHAVE_CONFIG_H -I. -I../../src/Include -I../.. -I../../src -I/usr/lo

Re: [Flightgear-devel] Compiling FlightGear under Cygwin

Is there any level of g++ compiler that FlightGear depends on for successful compilation? Jon - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/

[Flightgear-devel] XML Particles patch

Hi Here's the patch to add particles by XML to the OSG branch (instructions inside): http://gusmao.home.sapo.pt/particlesv1.tar.gz (that page is not an error, you will have to click in "AQUI", because it doesn't like hotlinking much) There is a short document here: http://gusmao.home.sapo.pt/RE

Re: [Flightgear-devel] trees

Hi Stuart, Stuart Buchanan schrieb am 26.01.2008 22:18: > --- Stuart Buchanan wrote: > >> --- Stuart Buchanan wrote: >> >>> Hi All, >>> >>> Just a quick note to mention that I've now implemented random tree height, >>> >> and >> >>> multiple textures as suggested by Curt. Scre

Re: [Flightgear-devel] trees

Stuart > Sent: 27 January 2008 10:42 > To: FlightGear developers discussions > Subject: Re: [Flightgear-devel] trees > > > --- Vivian Meazza wrote: > > The patch is broken here - there is some corruption in > simgear.patch > > which causes the file to appear empty when it is read by the patch

Re: [Flightgear-devel] trees

--- Vivian Meazza wrote: > The patch is broken here - there is some corruption in simgear.patch which > causes the file to appear empty when it is read by the patch utility, or by > Vi etc. Csaba provided me with a complete patched Simgear source (thanks) so > I was able to compile and run fg. The

Re: [Flightgear-devel] trees

Stuart wrote > Sent: 26 January 2008 21:18 > To: FlightGear developers discussions > Subject: Re: [Flightgear-devel] trees > > > --- Stuart Buchanan wrote: > > > > --- Stuart Buchanan wrote: > > > Hi All, > > > > > > Just a quick note to mention that I've now implemented > random tree > > >

Re: [Flightgear-devel] Log Stream patch

Stuart Buchanan a écrit : > Hi All, > > One of the frustrations of using Windows for development is the lack of a > sensible way to re-direct stderr to a file. This is particularly annoying if > you > want to use a --log-level=debug. > > To fix this, I've changed the global_logstream to use stdout

[Flightgear-devel] Yet another attempt to fix the repeating message bug in MP Chat

Hi All, As Csaba (?) pointed out a while back, the apparent reason for the MP chat repetition bug is that we don't remove "dead" AI aircraft from the property tree, so that the radar continues to work. Instead we just mark them as invalid. This means that when a new aircraft joins as that index

[Flightgear-devel] Log Stream patch

Hi All, One of the frustrations of using Windows for development is the lack of a sensible way to re-direct stderr to a file. This is particularly annoying if you want to use a --log-level=debug. To fix this, I've changed the global_logstream to use stdout for windows only. The patch below does