Re: [Flightgear-devel] Simple atmospheric scattering shader for skydome

[Erik Hofman]

On Fri, 2011-04-15 at 00:16 +0200, Christian Schmitt wrote:
> I can only agee with Vivian here: lets get this change into GIT, so that it 
> doesn't get lost as so many others in the past. The shader is not perfect 
> yet, but that should not hurt, as it is disabled as a default. Those who 
> want to test and improve it are free to do so.
> Let me add that it's good to have people who work on things like shaders (we 
> need every single one of them).

I'm not opposed to adding the shaders but I want a good look at the code
to make sure that current functionality is not lost with the patch
before it gets committed.

Erik


--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] FlightGear GIT version 64bit problem

[Arnt Karlsen]

On Fri, 15 Apr 2011 02:11:46 +0300, Ozgur wrote in message 
:

> Hi all,
> 
> I install Debian squeeze 64 bit.
> 
> # uname -ar
> Linux laptop 2.6.32-5-amd64 #1 SMP Mon Mar 7 21:35:22 UTC 2011 x86_64
> GNU/Linux
> 
> I installed FG GIT version and I read wiki howtos:
> 
> http://wiki.flightgear.org/index.php?title=Building_FlightGear_-_Debian&oldid=30115
> 
> I compiled finished install openal, plib, osg and simgear 

..pls post output of; "for i in openal plib openscene simgear \ 
flightgear ; do dpkg -l |grep $i ;done |fmt -tu "

> but
> flightgear source is error:
> 
> /usr/bin/ld: i386 architecture of input file
> `/usr/local/games/FlightGear/lib/libsgbvh.a(BVHStaticNode.o)' is
> incompatible with i386:x86-64 output
> /usr/bin/ld: i386 architecture of input file
> `/usr/local/games/FlightGear/lib/libsgnasal.a(vector.o)' is
> incompatible with i386:x86-64 output
> collect2: ld returned 1 exit status
> make[2]: *** [fgfs] Error 1
> make[2]: Leaving directory
> `/home/mueddib/Desktop/flightgear/flightgear/src/Main'
> make[1]: *** [install-recursive] Error 1
> make[1]: Leaving directory
> `/home/mueddib/Desktop/flightgear/flightgear/src' make: ***
> [install-recursive] Error 1
> 
> What is the problem?
> 
> osg is install 64-bit:
> 
> # ls /usr/local/games/FlightGear/
> bin  include  lib  lib64  share
> 
> Help me please,
> 
> Regards
> 
> Ozgur Karatas
> mueddib


-- 
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.

--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] FlightGear GIT version 64bit problem

[Csaba Halász]

On Fri, Apr 15, 2011 at 1:11 AM, Ozgur  wrote:
> Hi all,
>
> I install Debian squeeze 64 bit.
>
> /usr/bin/ld: i386 architecture of input file
> `/usr/local/games/FlightGear/lib/libsgbvh.a(BVHStaticNode.o)' is
> incompatible with i386:x86-64 output

You somehow managed to build a 32 bit simgear. Make sure you build a
64 bit simgear for a 64 bit flightgear.

-- 
Csaba/Jester

--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] FlightGear GIT version 64bit problem

[Robert]

Did you compile simgear from git?


2011/4/15 Ozgur 

> Hi all,
>
> I install Debian squeeze 64 bit.
>
> # uname -ar
> Linux laptop 2.6.32-5-amd64 #1 SMP Mon Mar 7 21:35:22 UTC 2011 x86_64
> GNU/Linux
>
> I installed FG GIT version and I read wiki howtos:
>
>
> http://wiki.flightgear.org/index.php?title=Building_FlightGear_-_Debian&oldid=30115
>
> I compiled finished install openal, plib, osg and simgear but
> flightgear source is error:
>
> /usr/bin/ld: i386 architecture of input file
> `/usr/local/games/FlightGear/lib/libsgbvh.a(BVHStaticNode.o)' is
> incompatible with i386:x86-64 output
> /usr/bin/ld: i386 architecture of input file
> `/usr/local/games/FlightGear/lib/libsgnasal.a(vector.o)' is
> incompatible with i386:x86-64 output
> collect2: ld returned 1 exit status
> make[2]: *** [fgfs] Error 1
> make[2]: Leaving directory
> `/home/mueddib/Desktop/flightgear/flightgear/src/Main'
> make[1]: *** [install-recursive] Error 1
> make[1]: Leaving directory
> `/home/mueddib/Desktop/flightgear/flightgear/src'
> make: *** [install-recursive] Error 1
>
> What is the problem?
>
> osg is install 64-bit:
>
> # ls /usr/local/games/FlightGear/
> bin  include  lib  lib64  share
>
> Help me please,
>
> Regards
>
> Ozgur Karatas
> mueddib
>
>
> --
> Benefiting from Server Virtualization: Beyond Initial Workload
> Consolidation -- Increasing the use of server virtualization is a top
> priority.Virtualization can reduce costs, simplify management, and improve
> application availability and disaster protection. Learn more about boosting
> the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
> ___
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] release discussion (was: Simple atmospheric

[Martin Spott]

ThorstenB wrote:

> The 2.2 release itself was branched in January (first sg+fg and a few 
> weeks later also fgdata).

Note that there are a couple of updates/additions (and removals) to the
Base Package which have, as far a I can tell, not yet been migrated to
the release branch. At least the stuff Jon Stockill and I have
committed to the Models/ subdirectory is affected.

Cheers,
Martin.
-- 
 Unix _IS_ user friendly - it's just selective about who its friends are !
--

--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

[Flightgear-devel] FlightGear GIT version 64bit problem

[Ozgur]

Hi all,

I install Debian squeeze 64 bit.

# uname -ar
Linux laptop 2.6.32-5-amd64 #1 SMP Mon Mar 7 21:35:22 UTC 2011 x86_64 GNU/Linux

I installed FG GIT version and I read wiki howtos:

http://wiki.flightgear.org/index.php?title=Building_FlightGear_-_Debian&oldid=30115

I compiled finished install openal, plib, osg and simgear but
flightgear source is error:

/usr/bin/ld: i386 architecture of input file
`/usr/local/games/FlightGear/lib/libsgbvh.a(BVHStaticNode.o)' is
incompatible with i386:x86-64 output
/usr/bin/ld: i386 architecture of input file
`/usr/local/games/FlightGear/lib/libsgnasal.a(vector.o)' is
incompatible with i386:x86-64 output
collect2: ld returned 1 exit status
make[2]: *** [fgfs] Error 1
make[2]: Leaving directory
`/home/mueddib/Desktop/flightgear/flightgear/src/Main'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/home/mueddib/Desktop/flightgear/flightgear/src'
make: *** [install-recursive] Error 1

What is the problem?

osg is install 64-bit:

# ls /usr/local/games/FlightGear/
bin  include  lib  lib64  share

Help me please,

Regards

Ozgur Karatas
mueddib

--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

[Flightgear-devel] release discussion (was: Simple atmospheric scattering shader)

[ThorstenB]

On 14.04.2011 18:22, Curtis Olson wrote:
> Yeah, we should get back to that. What is the current status? I have
> spend a lot of time doing the prepatory work for an eventual release
> during my holiday, but apparently no release has happened during my
> absence. Are there still any showstoppers?
>
>
> I seem to recall James mentioned the a couple issues remained, but I
> don't recall ever hearing specifically what those issues where.  He has
> been buried by real life lately so he hasn't had the chance to jump in
> much lately.  I haven't heard much from Tim either.

The remaining issues James was working on were concerning the automatic 
build process. He was close to finishing and make Hudson provide 
_complete_ (that is including _basic_ fgdata) installers for 
Mac/Windows. There were remaining issues due to the huge size of the 
installers though - since data gets copied over the network. And then he 
got buried under a pile of RL work for a while.

The 2.2 release itself was branched in January (first sg+fg and a few 
weeks later also fgdata). And I think we've fixed all the show stoppers 
for the 2.2 branch. We've had a few more fixes on the "next" branch 
since, but these mainly affected new code issues, which were not yet 
part of 2.2. I think the release branch got a fair amount of testing - 
and is very stable (feels much more stable than 2.0 to me, if I may say 
:) ).

So, as far as I'm concerned, if we can manually provide Mac/Windows 
installers, we could just tag and release now (come on, let's have a new 
release to show off at LinuxTag! :) ).
The 2.2 branch may look a little outdated to git/next users by now. But 
I'd still stick with releasing the existing branch as 2.2. We've already 
committed lot's of new code to "next" since, so that would take more 
work/time to be ready. And we can still have another release (2.3/2.4) 
in a few months - and don't need to wait for another year again...

cheers,
Thorsten

--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

[Flightgear-devel] ..another 3-letter inspiration, was: Heads up: AI/ATC interactions

[Arnt Karlsen]

On Thu, 14 Apr 2011 18:50:18 +0700, Harry wrote in message 
:

> Thanks for the links Torsten,
> 
> I need to upgrade from git 2.2 release to current to play with this,
> I have spend the last few hours since your post digging into HLA.

..another 3-letter inspiration: TLD, multimedia intro: ;o)  
http://info.ee.surrey.ac.uk/Personal/Z.Kalal/tld.html

-- 
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.

--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Simple atmospheric scattering shader for skydome

[Christian Schmitt]

Erik Hofman wrote:

> I'm not sure, it needs time to look after some things. For one it should
> be made possible for the shader to adjust the fog color located
> under /rendering/fog but at this time values written to it will be
> overwritten by the current code.
> 
> Erik
> 

I can only agee with Vivian here: lets get this change into GIT, so that it 
doesn't get lost as so many others in the past. The shader is not perfect 
yet, but that should not hurt, as it is disabled as a default. Those who 
want to test and improve it are free to do so.
Let me add that it's good to have people who work on things like shaders (we 
need every single one of them).

Chris
papillon81

--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Simple atmospheric scattering shader for skydome

[Vivian Meazza]

Erik wrote

> 
> On Thu, 2011-04-14 at 18:15 +0200, Durk Talsma wrote:
> 
> >
> > Okay, thanks for the comments. I'll be holding back on committing. Is
> > there any perspective that this patch can be brought to production
> > quality?
> 
> I'm not sure, it needs time to look after some things. For one it should
> be made possible for the shader to adjust the fog color located
> under /rendering/fog but at this time values written to it will be
> overwritten by the current code.
> 

I added some sliders in the rendering dialog here as suggested by Fred and
did some adjustments at runtime. There do seem to be some issues that I was
unable to tune out - at least so far:

ftp://abbeytheatre2.org.uk:2121/flightgear/Skydome/

However, I am concerned that if we do not get this into git, it will get
forgotten, and we will not get the potential improvements. That said, there
do seem to be some pretty fundamental problems here, as the screenshots
indicate.

I can't see any downside here - if the shader is disabled - so far as I can
see the existing skydome is unaffected. 

Vivian



--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] download_and_compile.sh script link

[Arnt Karlsen]

On Thu, 14 Apr 2011 20:24:50 +0200, Geoff wrote in message 
<1302805490.6456.10.camel@DELL02>:

> Hi Arnt,
> 
> > >>  http://geoffair.org/tmp/makefg 
> This is 'now' 1.2.5, since I am quite happy with
> it so far... but still testing...
> 
> But specific version are usually also available 
> under their version numbers -
>  http://geoffair.org/tmp/makefg-1.2.5
>  http://geoffair.org/tmp/makefg-1.2.4
>  http://geoffair.org/tmp/makefg-1.2.3
>  etc...
> 
> Have not specifically checked Brisa's script,
> but yes, in the main I use the 'same' directory
> structure, as per his 'original' script. But you
> could check, and adjust that...
> 
> And yes, with the ever growing size of fgdata
> I too am coming in for a bit of disk squeeze ;=))
> Normally I keep the previous say ~/fg/fg14, and
> move to a new folder, ~/fg/fg15, but...
> 
> > ..both 2.9.10 and 2.9.11 fails for you?
> Never tried 2.9.10, but had trouble with
> 2.9.11 last time I tried, months ago, both in Ubuntu,
> and WIN32 XP...
> 
> My re-build of sg/sg back with OSG 2.8.3 just complete,
> grace of a simple script command -
> ~/fg/fg14$ makefg OSG283 FGCONF FGCLEAN SGCONF SGCLEAN NOPAUSE NO_CONF
> and so far it RUNS JUST FINE ;=)) Phew, the
> 'shakes' were starting...
> 
> The script also supports OSG299, but think I have

..idea for makefg-1.3.0: WEUSESYSTEMPLIB=1, WEUSESYSTEMOSG=1 
etc, printing the warning to standard output and pointing the
build to whatever is installed on the box, I did something 
similar on my last building on Francesco's former script:
https://github.com/gasguru/flightgearthings/blob/master/download_and_compile.sh-1.2.0-sysOSG
he has since released a newer version.

> had enough of a 'fright' for a while ;=)) Need
> some quiet flying time...

..aaaye, I'd like that kinda boredom too. :o)


-- 
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.

--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Valgrind logs

[Torsten Dreyer]

> 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 example

class MyReferenced : public SGReferenced {
public:
  MyReferenced( int id );
  virtual ~ MyReferenced();
private:
  int _id;
};

MyReferenced::MyReferenced( int id ) :
  _id(id)
{
  std::cerr << "MyReferenced(" << _id << ") constructed" << std::endl;
}

MyReferenced::~MyReferenced()
{
  std::cerr << "MyReferenced(" << _id << ") destructed" << std::endl;
}

int main(int argc, char **argv )
{
  std::vector > v;
  std::cerr << "Adding first" << std::endl;
  v.push_back(new MyReferenced(1));
  std::cerr << "Adding second" << std::endl;
  v.push_back(new MyReferenced(2));
  std::cerr << "Clearing Vector" << std::endl;
  v.clear();
  std::cerr << "Exiting" << std::endl;
  return 0;
}

Creates output as expected:
Adding first
MyReferenced(1) constructed
Adding second
MyReferenced(2) constructed
Clearing Vector
MyReferenced(1) destructed
MyReferenced(2) destructed
Exiting

And without the explicit clear(), it looks right, too:
Adding first
MyReferenced(1) constructed
Adding second
MyReferenced(2) constructed
Exiting
MyReferenced(1) destructed
MyReferenced(2) destructed


> In any case, the static variables and probably the complete autopilot
> are only destroyed at program end, so fixing these leaks won't have an
> influence on the growing memory footprint at runtime. I just mentioned
> them because they were the only ones where I thought an easy fix to be
> possible.
Which is very much appreciated. It's just to easy to overlook something.

Torsten

--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] YASim issues

[Gary Neely]

Adrian,

Great catch on the fuel and glideslope issues. You're right-- despite
parsing the fuel attributes and supplying defaults if necessary, it
has the defaults hard-coded right in the Airplane::compile block. It
seems to consider the user-supplied values for aircraft mass, but not
elsewhere. Makes me feel dumb that I'd not noticed this before. I hope
this one makes it in the new build!

-Gary


On Thu, Apr 14, 2011 at 9:06 AM, Adrian Musceac  wrote:
> Hello,
> I have found a couple of YASim issues, more details here:
> https://code.google.com/p/flightgear-bugs/issues/detail?id=302
> https://code.google.com/p/flightgear-bugs/issues/detail?id=303
>
> Would anyone still maintaining YASim please have a look and provide
> some feedback?
>
> Cheers,
> Adrian
>
> --
> Benefiting from Server Virtualization: Beyond Initial Workload
> Consolidation -- Increasing the use of server virtualization is a top
> priority.Virtualization can reduce costs, simplify management, and improve
> application availability and disaster protection. Learn more about boosting
> the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
> ___
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>

--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Simple atmospheric scattering shader for skydome

[Erik Hofman]

On Thu, 2011-04-14 at 18:15 +0200, Durk Talsma wrote:

> 
> Okay, thanks for the comments. I'll be holding back on committing. Is
> there any perspective that this patch can be brought to production
> quality?

I'm not sure, it needs time to look after some things. For one it should
be made possible for the shader to adjust the fog color located
under /rendering/fog but at this time values written to it will be
overwritten by the current code.

Erik



--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] download_and_compile.sh script link

[Geoff McLane]

Hi Arnt,

> >>  http://geoffair.org/tmp/makefg 
This is 'now' 1.2.5, since I am quite happy with
it so far... but still testing...

But specific version are usually also available 
under their version numbers -
 http://geoffair.org/tmp/makefg-1.2.5
 http://geoffair.org/tmp/makefg-1.2.4
 http://geoffair.org/tmp/makefg-1.2.3
 etc...

Have not specifically checked Brisa's script,
but yes, in the main I use the 'same' directory
structure, as per his 'original' script. But you
could check, and adjust that...

And yes, with the ever growing size of fgdata
I too am coming in for a bit of disk squeeze ;=))
Normally I keep the previous say ~/fg/fg14, and
move to a new folder, ~/fg/fg15, but...

> ..both 2.9.10 and 2.9.11 fails for you?
Never tried 2.9.10, but had trouble with
2.9.11 last time I tried, months ago, both in Ubuntu,
and WIN32 XP...

My re-build of sg/sg back with OSG 2.8.3 just complete,
grace of a simple script command -
~/fg/fg14$ makefg OSG283 FGCONF FGCLEAN SGCONF SGCLEAN NOPAUSE NO_CONF
and so far it RUNS JUST FINE ;=)) Phew, the
'shakes' were starting...

The script also supports OSG299, but think I have
had enough of a 'fright' for a while ;=)) Need
some quiet flying time...

Regards,
Geoff.



--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] ..now it's "Submodels: Unable to read AI submodel list", was:..now, running it...

[Arnt Karlsen]

On Thu, 14 Apr 2011 19:18:26 +0200, Geoff wrote in message 
<1302801506.6456.7.camel@DELL02>:

> Hi Arnt,
> 
> I got the SAME message and an abort when I
> tried to comment out the nimitz_demo in
> preference.xml?
> 
> Submodels: Unable to read AI submodel list
> 
> so put back the original preferences.xml.
> 
> And have now had a chance to run under gdb, and
> got :-
> 
> ~/fg/fg14$ ./run_fgfs_gdb.sh
> run_fgfs_gdb.sh: Running: gdb --args ./fgfs
> --fg-root=/home/geoff/fg/fg14/fgfs/data --timeofday=noon
> --disable-ai-traffic  --disable-ai-models 
> GNU gdb 6.8-debian
> Copyright (C) 2008 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> 
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show
> copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64-linux-gnu"...
> (gdb) run
> Starting program: /home/geoff/fg/fg14/install/fgfs/bin/fgfs
> --fg-root=/home/geoff/fg/fg14/fgfs/data --timeofday=noon
> --disable-ai-traffic --disable-ai-models
> [Thread debugging using libthread_db enabled]
> Processing command line arguments
> [New Thread 0x7ff7a9544700 (LWP 8831)]
> [New Thread 0x4265c950 (LWP 8834)]
> Compatibility layer: testing for hard coded support
> * can set light saturation:yes
> * hard coded terrain presampling:  yes
> * can disable global weather:  yes
> Compatibility layer: tests done.
> Loading local weather routines...
> KI266 dme indicator #0 initialized
> loading scenario 'nimitz_demo'
> 
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7ff7a9544700 (LWP 8831)]
> 0x21a1 in ?? ()
> (gdb) bt
> #0  0x21a1 in ?? ()
> #1  0x7ff7a5768ee8 in osg::FrameBufferObject::apply ()
>from /home/geoff/fg/fg14/install/OSGtrunk/lib/libosg.so.72
> #2  0x7ff7a5c8eefb in osgUtil::RenderStage::runCameraSetUp ()
>from /home/geoff/fg/fg14/install/OSGtrunk/lib/libosgUtil.so.72
> #3  0x7ff7a5c902d0 in osgUtil::RenderStage::draw ()
>from /home/geoff/fg/fg14/install/OSGtrunk/lib/libosgUtil.so.72
> #4  0x7ff7a5c8c076 in osgUtil::RenderStage::drawPreRenderStages ()
>from /home/geoff/fg/fg14/install/OSGtrunk/lib/libosgUtil.so.72
> #5  0x7ff7a5c9da05 in osgUtil::SceneView::draw ()
>from /home/geoff/fg/fg14/install/OSGtrunk/lib/libosgUtil.so.72
> #6  0x7ff7a67860c0 in osgViewer::Renderer::cull_draw ()
>from /home/geoff/fg/fg14/install/OSGtrunk/lib/libosgViewer.so.72
> #7  0x7ff7a57a5128 in osg::GraphicsContext::runOperations ()
>from /home/geoff/fg/fg14/install/OSGtrunk/lib/libosg.so.72
> #8  0x7ff7a67d39f8 in osgViewer::ViewerBase::renderingTraversals
> () from /home/geoff/fg/fg14/install/OSGtrunk/lib/libosgViewer.so.72
> #9  0x0048ae17 in fgOSMainLoop () at fg_os_osgviewer.cxx:287
> #10 0x0042c8c6 in fgMainInit (argc=5, argv=0x7fff2ff05c58) at
> main.cxx:662
> #11 0x0042aea9 in main (argc=5, argv=0x7fff2ff05c58) at
> bootstrap.cxx:243
> (gdb) q
> The program is running.  Exit anyway? (y or n) y
> ~/fg/fg14$ 
> 
> Which I think indicates a 'problem' in OSG-trunk, so
> will tomorrow revert to 2.8.3

..if you have Debian Sid+Experimental, try osg-2.9.11-1 too.

> 
> Regards,
> Geoff.
> 
> 
> 
> --
> Benefiting from Server Virtualization: Beyond Initial Workload 
> Consolidation -- Increasing the use of server virtualization is a top
> priority.Virtualization can reduce costs, simplify management, and
> improve application availability and disaster protection. Learn more
> about boosting the value of server virtualization.
> http://p.sf.net/sfu/vmware-sfdev2dev
> ___ Flightgear-devel
> mailing list Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
> 


-- 
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.

--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] download_and_compile.sh script link

[Arnt Karlsen]

On Thu, 14 Apr 2011 18:51:45 +0200, Geoff wrote in message 
<1302799905.6456.2.camel@DELL02>:

> Hi Arnt,
> 
> >>  http://geoffair.org/tmp/makefg 
> > ..your makef|tg is still version 1.2.3, Geoff?
> That link should be to 1.2.4 IIRC. And have not
> used/changed the 'tg' version for _MANY_ months,
> but also think it should be 1.2.4...
> 
> Am presently testing a makefg 1.2.5, especially using
> an OSGTRUNK switch, and while SG/FG compiled and linked
> fine, I can not get fgfs to run -

..url to makefg-1.2.5RC0?

..this still fits in dropping the data into the same 
places as Francesco's download_and_compile.sh? 
(I'm tight on disk space and funding.)

> (a) The status text on the splash is 'broken', and
> (b) it 'aborts' some short time after the output -
> loading scenario 'nimitz_demo'
> 
> sg/fg/fgdata are a git pull of today... and naturally
> include SGCLEAN and FGCLEAN to do a FULL re-build...
> 
> Still researching the cause(s) ;=(( like add log debug,
> and running under gdb, but may revert to OSG 283 or 299 

..both 2.9.10 and 2.9.11 fails for you?

> soon, to see if that gets me back to a 'working' 
> version before withdrawal sets in ;=))

..can't have that happening. ;o)

-- 
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.

--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Valgrind logs

[Andreas Gaeb]

Am 14.04.2011 16:58, schrieb Torsten Dreyer:
> Thanks for looking into this.
> A few comments on the autopilot objects:
> InputValueLists are vectors of InputValue, a subclass of SGReferenced, so 
> they 
> should be automatically deleted, once the last reference is gone?
> 
> The componentForge is a static vector, initialized only once at startup. It's 
> intention is to live during the entire session. It's never dropped, never 
> recreated and never cleared. 
The thing with maps and vectors of pointers to heap objects is that --
according to valgrind -- the heap objects are not deleted when the
parent vector is. Minimal example:
#include 
int main() {
  std::vector v;
  v.push_back(new int(1));
  v.clear();
  return 0;
}
leaks 4 bytes in spite of the clear() call. It is necessary to delete
the heap objects explicitly, e.g.
  std::vector::iterator i;
  for (i=v.begin(); i != v.end(); ++i)
delete (*i);
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.
In any case, the static variables and probably the complete autopilot
are only destroyed at program end, so fixing these leaks won't have an
influence on the growing memory footprint at runtime. I just mentioned
them because they were the only ones where I thought an easy fix to be
possible.

Best regards,
Andreas

--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] ..now it's "Submodels: Unable to read AI submodel list", was:..now, running it...

[Geoff McLane]

Hi Arnt,

I got the SAME message and an abort when I
tried to comment out the nimitz_demo in
preference.xml?

Submodels: Unable to read AI submodel list

so put back the original preferences.xml.

And have now had a chance to run under gdb, and
got :-

~/fg/fg14$ ./run_fgfs_gdb.sh
run_fgfs_gdb.sh: Running: gdb --args ./fgfs
--fg-root=/home/geoff/fg/fg14/fgfs/data --timeofday=noon
--disable-ai-traffic  --disable-ai-models 
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show
copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...
(gdb) run
Starting program: /home/geoff/fg/fg14/install/fgfs/bin/fgfs
--fg-root=/home/geoff/fg/fg14/fgfs/data --timeofday=noon
--disable-ai-traffic --disable-ai-models
[Thread debugging using libthread_db enabled]
Processing command line arguments
[New Thread 0x7ff7a9544700 (LWP 8831)]
[New Thread 0x4265c950 (LWP 8834)]
Compatibility layer: testing for hard coded support
* can set light saturation:yes
* hard coded terrain presampling:  yes
* can disable global weather:  yes
Compatibility layer: tests done.
Loading local weather routines...
KI266 dme indicator #0 initialized
loading scenario 'nimitz_demo'

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ff7a9544700 (LWP 8831)]
0x21a1 in ?? ()
(gdb) bt
#0  0x21a1 in ?? ()
#1  0x7ff7a5768ee8 in osg::FrameBufferObject::apply ()
   from /home/geoff/fg/fg14/install/OSGtrunk/lib/libosg.so.72
#2  0x7ff7a5c8eefb in osgUtil::RenderStage::runCameraSetUp ()
   from /home/geoff/fg/fg14/install/OSGtrunk/lib/libosgUtil.so.72
#3  0x7ff7a5c902d0 in osgUtil::RenderStage::draw ()
   from /home/geoff/fg/fg14/install/OSGtrunk/lib/libosgUtil.so.72
#4  0x7ff7a5c8c076 in osgUtil::RenderStage::drawPreRenderStages ()
   from /home/geoff/fg/fg14/install/OSGtrunk/lib/libosgUtil.so.72
#5  0x7ff7a5c9da05 in osgUtil::SceneView::draw ()
   from /home/geoff/fg/fg14/install/OSGtrunk/lib/libosgUtil.so.72
#6  0x7ff7a67860c0 in osgViewer::Renderer::cull_draw ()
   from /home/geoff/fg/fg14/install/OSGtrunk/lib/libosgViewer.so.72
#7  0x7ff7a57a5128 in osg::GraphicsContext::runOperations ()
   from /home/geoff/fg/fg14/install/OSGtrunk/lib/libosg.so.72
#8  0x7ff7a67d39f8 in osgViewer::ViewerBase::renderingTraversals ()
   from /home/geoff/fg/fg14/install/OSGtrunk/lib/libosgViewer.so.72
#9  0x0048ae17 in fgOSMainLoop () at fg_os_osgviewer.cxx:287
#10 0x0042c8c6 in fgMainInit (argc=5, argv=0x7fff2ff05c58) at
main.cxx:662
#11 0x0042aea9 in main (argc=5, argv=0x7fff2ff05c58) at
bootstrap.cxx:243
(gdb) q
The program is running.  Exit anyway? (y or n) y
~/fg/fg14$ 

Which I think indicates a 'problem' in OSG-trunk, so
will tomorrow revert to 2.8.3

Regards,
Geoff.



--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] download_and_compile.sh script link

[Geoff McLane]

Hi Arnt,

>>  http://geoffair.org/tmp/makefg 
> ..your makef|tg is still version 1.2.3, Geoff?
That link should be to 1.2.4 IIRC. And have not
used/changed the 'tg' version for _MANY_ months,
but also think it should be 1.2.4...

Am presently testing a makefg 1.2.5, especially using
an OSGTRUNK switch, and while SG/FG compiled and linked
fine, I can not get fgfs to run -

(a) The status text on the splash is 'broken', and
(b) it 'aborts' some short time after the output -
loading scenario 'nimitz_demo'

sg/fg/fgdata are a git pull of today... and naturally
include SGCLEAN and FGCLEAN to do a FULL re-build...

Still researching the cause(s) ;=(( like add log debug,
and running under gdb, but may revert to OSG 283 or 299 
soon, to see if that gets me back to a 'working' 
version before withdrawal sets in ;=))

Regards,
Geoff.



--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Simple atmospheric scattering shader for skydome

[Curtis Olson]

On Thu, Apr 14, 2011 at 11:15 AM, Durk Talsma  wrote:

> PS: what about the 2.2 release first ? I see plans for lots of code.
>
> Yeah, we should get back to that. What is the current status? I have spend
> a lot of time doing the prepatory work for an eventual release during my
> holiday, but apparently no release has happened during my absence. Are there
> still any showstoppers?
>

I seem to recall James mentioned the a couple issues remained, but I don't
recall ever hearing specifically what those issues where.  He has been
buried by real life lately so he hasn't had the chance to jump in much
lately.  I haven't heard much from Tim either.

On my end I have been packaging and uploading the cutting edge executables
from the hudson build server along with the current data package from git.
 That is pushing about 400Mb as a single setup.exe right now.  When we do a
real release, we should be able to do bittorrent seeded through ibiblio.org.

Curt.
-- 
Curtis Olson:
http://www.atiak.com - http://aem.umn.edu/~uav/
http://www.flightgear.org -
http://gallinazo.flightgear.org
--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Simple atmospheric scattering shader for skydome

[Durk Talsma]

On 14 Apr 2011, at 10:30, Frederic Bouvier wrote:

> Erik Hofman wrote:
> 
>> 
>> It's not production ready yet, and it even removes some of the features
>> form the old code. I don't seem to see any difference with different
>> humidity levels for example.
> 
> 
> I guess one would have to play with the Mie and Rayleigh factor to 
> achieve that. A debug window with 2 sliders would be handy to experiment.
> 
> It also would be nice if Lauri could publish how he computed the 
> factor used in the outscatterscale function.

Okay, thanks for the comments. I'll be holding back on committing. Is there any 
perspective that this patch can be brought to production quality?

> 
> Regards,
> -Fred
> 
> PS: what about the 2.2 release first ? I see plans for lots of code.
> 
> 


Yeah, we should get back to that. What is the current status? I have spend a 
lot of time doing the prepatory work for an eventual release during my holiday, 
but apparently no release has happened during my absence. Are there still any 
showstoppers?

cheers,
Durk

--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] YASim issues

[syd adams]

Just a note about the belly landing ... you can use fuselage objects
instead of fake gear  each end of a 'fuselage' is a contact point
, and like the doc says you can have as many and in any orientation
you like ... though most people seem to be under the impression that
you can only model the main fuselage this way.
Works great for me , and Ive never noticed this retracted gear problem
... I'll try some tests here.

On Thu, Apr 14, 2011 at 7:06 AM, Adrian Musceac  wrote:
> Hello,
> I have found a couple of YASim issues, more details here:
> https://code.google.com/p/flightgear-bugs/issues/detail?id=302
> https://code.google.com/p/flightgear-bugs/issues/detail?id=303
>
> Would anyone still maintaining YASim please have a look and provide
> some feedback?
>
> Cheers,
> Adrian
>
> --
> Benefiting from Server Virtualization: Beyond Initial Workload
> Consolidation -- Increasing the use of server virtualization is a top
> priority.Virtualization can reduce costs, simplify management, and improve
> application availability and disaster protection. Learn more about boosting
> the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
> ___
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>

--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Valgrind logs

[Torsten Dreyer]

> 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 entry stems from the TrafficMgr code. It is fixed by
> the attached patch, which deletes all scheduled flights.
> 
> However, as I quit the program as soon as the 3D clouds showed up, I
> suspect that with increased run time other leaks might become more
> important, possibly the ones regarding
> simgear/scene/model/SGReaderWriterXML.cxx:289.
> 
> Some things that might be fixed relatively easy:
> FG/src/Autopilot/digitalfilter.cxx: all InputValues pushed_back to one
> of the InputValueLists need to be deleted
> FG/src/Autopilot/digitalfilter.cxx:316: members of componentForge need
> to be deleted
> FG/src/Autopilot/autopilot.cxx:46: the same
> FG/src/Instrumentation/gps.cxx:1575: _currentWaypt needs to be deleted
> FG/src/AIModel/performancedb.cxx:88 members of _db need to be deleted
> 
> Hope this helps a little in stuffing the sieve,
> best regards,
>   Andreas
> 
Thanks for looking into this.
A few comments on the autopilot objects:
InputValueLists are vectors of InputValue, a subclass of SGReferenced, so they 
should be automatically deleted, once the last reference is gone?

The componentForge is a static vector, initialized only once at startup. It's 
intention is to live during the entire session. It's never dropped, never 
recreated and never cleared. 

Torsten

--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

[Flightgear-devel] Valgrind logs

[Andreas Gaeb]

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 entry stems from the TrafficMgr code. It is fixed by
the attached patch, which deletes all scheduled flights.

However, as I quit the program as soon as the 3D clouds showed up, I
suspect that with increased run time other leaks might become more
important, possibly the ones regarding
simgear/scene/model/SGReaderWriterXML.cxx:289.

Some things that might be fixed relatively easy:
FG/src/Autopilot/digitalfilter.cxx: all InputValues pushed_back to one
of the InputValueLists need to be deleted
FG/src/Autopilot/digitalfilter.cxx:316: members of componentForge need
to be deleted
FG/src/Autopilot/autopilot.cxx:46: the same
FG/src/Instrumentation/gps.cxx:1575: _currentWaypt needs to be deleted
FG/src/AIModel/performancedb.cxx:88 members of _db need to be deleted

Hope this helps a little in stuffing the sieve,
best regards,
Andreas
diff --git a/src/Traffic/SchedFlight.hxx b/src/Traffic/SchedFlight.hxx
index 0ee3eb6..5d2f3fd 100644
--- a/src/Traffic/SchedFlight.hxx
+++ b/src/Traffic/SchedFlight.hxx
@@ -115,6 +115,7 @@ typedef vector   FGScheduledFlightVec;
 typedef vector::iterator FGScheduledFlightVecIterator;
 
 typedef std::map < std::string, FGScheduledFlightVec > FGScheduledFlightMap;
+typedef std::map < std::string, FGScheduledFlightVec >::iterator FGScheduledFlightMapIterator;
 
 bool compareScheduledFlights(FGScheduledFlight *a, FGScheduledFlight *b);
 
diff --git a/src/Traffic/TrafficMgr.cxx b/src/Traffic/TrafficMgr.cxx
index 4abbc1a..7213175 100644
--- a/src/Traffic/TrafficMgr.cxx
+++ b/src/Traffic/TrafficMgr.cxx
@@ -66,7 +66,7 @@
 #include 
 
 
-
+#include "SchedFlight.hxx"
 #include "TrafficMgr.hxx"
 
 using std::sort;
@@ -124,6 +124,12 @@ FGTrafficManager::~FGTrafficManager()
 cachefile.close();
 }
 scheduledAircraft.clear();
+FGScheduledFlightMapIterator itm;
+FGScheduledFlightVecIterator itv;
+for (itm = flights.begin(); itm != flights.end(); ++itm) {
+  for (itv = itm->second.begin(); itv != itm->second.end(); ++itv)
+delete (*itv);
+}
 flights.clear();
 }
 
diff --git a/src/ATCDCL/ATCmgr.cxx b/src/ATCDCL/ATCmgr.cxx
index 537bfdd..2da7e53 100644
--- a/src/ATCDCL/ATCmgr.cxx
+++ b/src/ATCDCL/ATCmgr.cxx
@@ -63,6 +63,10 @@ FGATCMgr::FGATCMgr() :
 
 FGATCMgr::~FGATCMgr() {
 delete v1;
+for (airport_atc_map_itr = airport_atc_map.begin();
+ airport_atc_map_itr != airport_atc_map.end();
+ ++airport_atc_map_itr)
+  delete airport_atc_map_itr->second;
 }
 
 void FGATCMgr::bind() {
--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Joystick axis issues

[TDO_Brandano -]

Hi Thorsten,
I suspect I know what is actually happening, at least it also happend on my 
Thrustmaster Cougar.
Just try this: move all axes on the joystick to all extremes before starting 
FG. 
I think you are hitting on an autocalibration issue. It might be the OS or even 
the joystick's own hardware.
If this is the issue you should need to do this only once per session or every 
time the controller is unlpugged and replugged.

Ciao,
Alessandro

> Date: Wed, 13 Apr 2011 21:55:13 +0200
> From: bre...@gmail.com
> To: flightgear-devel@lists.sourceforge.net
> Subject: [Flightgear-devel] Joystick axis issues
> 
> Hi,
> 
> I'm having joystick issues: on start-up, all axis are in 
> left-most/lower-most position (reporting "-1"). Only once I have moved 
> each axis for the first time, do I get valid positions. Hardly 
> noticeable with most planes, since "-1" means throttle is idle - so full 
> left-rudder/pushed-aileron has no effect. But starting the UFO is 
> annoying, as it's spinning around all three axis at full speed by 
> default - until I have moved all joysticks. Wasn't like this maybe a 
> month or two ago. And I have tested different joysticks.
> 
> Anyone else seeing this? Test: start the UFO, keep away from joysticks, 
> see what happens...
> 
> I have a local patch which fixes things for me - but I may be fixing 
> local/system issues here.
> 
> cheers,
> Thorsten
> 
> --
> Benefiting from Server Virtualization: Beyond Initial Workload 
> Consolidation -- Increasing the use of server virtualization is a top
> priority.Virtualization can reduce costs, simplify management, and improve 
> application availability and disaster protection. Learn more about boosting 
> the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
> ___
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
  --
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

[Flightgear-devel] YASim issues

[Adrian Musceac]

Hello,
I have found a couple of YASim issues, more details here:
https://code.google.com/p/flightgear-bugs/issues/detail?id=302
https://code.google.com/p/flightgear-bugs/issues/detail?id=303

Would anyone still maintaining YASim please have a look and provide 
some feedback?

Cheers,
Adrian

--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Heads up: AI/ATC interactions

[Harry Campigli]

Thanks for the links Torsten,

I need to upgrade from git 2.2 release to current to play with this, I have
spend the last few hours since your post digging into HLA.

As there is so much on the move here I was unaware of, best for now i
confine myself to a routine to parse ads-b data.

Harry







On Thu, Apr 14, 2011 at 3:38 PM, Torsten Dreyer  wrote:

> > 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 added HLA/RTI support last year in these commits:
>
> http://gitorious.org/fg/flightgear/commit/70dd6279a742030271b5b0927501f59bc9aecb98
>
> http://gitorious.org/fg/simgear/commit/44ff23b227dcc1f3efbd10a4df4d8b723165c11c
>
> I hope we have some time to test it during this year's LinuxTag...
>
> Torsten
>
>
> --
> Benefiting from Server Virtualization: Beyond Initial Workload
> Consolidation -- Increasing the use of server virtualization is a top
> priority.Virtualization can reduce costs, simplify management, and improve
> application availability and disaster protection. Learn more about boosting
> the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
> ___
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Heads up: AI/ATC interactions

[Torsten Dreyer]

> 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 added HLA/RTI support last year in these commits:
http://gitorious.org/fg/flightgear/commit/70dd6279a742030271b5b0927501f59bc9aecb98
http://gitorious.org/fg/simgear/commit/44ff23b227dcc1f3efbd10a4df4d8b723165c11c

I hope we have some time to test it during this year's LinuxTag...

Torsten

--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Simple atmospheric scattering shader for skydome

[Frederic Bouvier]

> On Wed, 2011-04-13 at 19:37 +0200, Durk Talsma wrote:
> 
> > Admittedly, I only looked at the corresponding forum topic very
> briefly, but the screenshots certainly looked promising. I'd be happy
> to commit the corresponding simgear and flightgear patches.
> > 
> > I did see some comments from Fred in the forum thread and I can't
> > tell for sure whether these have been addressed or not. Therefore, I'd
> > like to give others a few days to comment. If I don't hear any
> > objections by the weekend (and if I don't see any negative side
> > effects myself). I'm might go ahead and commit these patches by
> > Saturday. So, just drop a note here if there are problems I should be
> > aware of.

I think Lauri already mentioned he left these issue for the future/other
developers. I am afraid that if it is not sufficiently documented and 
understood by others, it will remain as it is a long time.

> 
> It's not production ready yet, and it even removes some of the features
> form the old code. I don't seem to see any difference with different
> humidity levels for example.


I guess one would have to play with the Mie and Rayleigh factor to 
achieve that. A debug window with 2 sliders would be handy to experiment.

It also would be nice if Lauri could publish how he computed the 
factor used in the outscatterscale function.

Regards,
-Fred

PS: what about the 2.2 release first ? I see plans for lots of code.



-- 
Frédéric Bouvier
http://www.youtube.com/user/fgfred64   Videos


--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Simple atmospheric scattering shader for skydome

[Erik Hofman]

On Wed, 2011-04-13 at 19:37 +0200, Durk Talsma wrote:

> Admittedly, I only looked at the corresponding forum topic very briefly, but 
> the screenshots certainly looked promising. I'd be happy to commit the 
> corresponding simgear and flightgear patches.
> 
> I did see some comments from Fred in the forum thread and I can't tell for 
> sure whether these have been addressed or not. Therefore, I'd like to give 
> others a few days to comment. If I don't hear any objections by the weekend 
> (and if I don't see any negative side effects myself). I'm might go ahead and 
> commit these patches by Saturday. So, just drop a note here if there are 
> problems I should be aware of.

It's not production ready yet, and it even removes some of the features
form the old code. I don't seem to see any difference with different
humidity levels for example.

Erik


--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel