Re: [Flightgear-devel] new fedora

[Peter Sadrozinski]

ugh,

Sorry for the noise.  For some reason, the new Fedora 16 isn't using my
swap partition.  I am actually running out of memory!

I have a 2 GB swap partition.  Need to do some googling to see why it isn't
being used.

Pete

On Sat, Jan 14, 2012 at 3:28 PM, Stefan Seifert  wrote:

> On Saturday 14 January 2012 00:20:33 Peter Sadrozinski wrote:
> > Hello,
> >
> > I'm hitting an 'interesting' problem with the new fedora.  For some
> reason,
> > it's installing the PAE kernel (I guess I should have installed the 64
> bit
> > version).  The problem is, when the system() is called - for instance, to
> > copy an airport btg file from work to output, I get an error.
> >
> > Here's debug from copying of said airport:
> >
> > running cp ./work/AirportObj/w090n30/w085n33/KATL.btg.gz
> > ./output/w090n30/w085n33
> > system: : Cannot allocate memory
> > returned -1
> >
> > I'm not buying the out of memory error.
>
> Please beware that while PAE allows a 32 Bit OS to use more than 4GB of
> RAM,
> it does not change an individual processes limit. Maybe this is what bites
> you
> here?
>
> Stefan
>
>
> --
> RSA(R) Conference 2012
> Mar 27 - Feb 2
> Save $400 by Jan. 27
> Register now!
> http://p.sf.net/sfu/rsa-sfdev2dev2
> ___
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
--
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Flightgear-devel Digest, Vol 69, Issue 8

[Pierre Mueller]

Hello,

>But the central point in Pierre's posting is a different one: If there
>are copyright violations in the Base Package, then it's valid to
>express concerns about these violations.

>You're always well advised to read the copyright clauses really
>carefully before copying content from 3rd party sites, anyhow I know
>that accidental violations still may happen.
>But if they really happen, it's time to head out for a solution instead
>of ciriticizing people for pointing at the violations in question. 

Well said.


Pierre Mueller

Switzerland--
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Flightgear-devel Digest, Vol 69, Issue 9

[Pierre Mueller]

Dear Mr. BARANGER,

>I am sorry to contradict you, but it's totally false. I admit that I 
>sometimes use images (usually reduced compared to the original) in my 
>planes (rarely, but it happens). But only for development purposes. And 
>I recall the GIT is not a great public venue but a place of development. 
>I am not responsible for the misuse of GIT by everyone.

Some facts:
-It is o.k. to use such images as reference- when they aren't redistributed! 

-GIT ( www.gitorious.org) is publicy open for everyone- with pushing to it you 
made them available for everyone and with that you have already redistributed 
it!

-And still to my knowledge all things are frozen from FGdata at 
www.gitorious.org and redistributed as new FGFS-Release! FGFS-developers, 
please correct me when I'm wrong.

-Copyrights doesn't make any difference between being in "developement" or not!

-Sounds are copyrighted as well. Fact is, that you used a a part of a 
soundtrack from a famous movie (Apocalypse now) and a TV-serie, (Airwolf) which 
still are copyrighted- though in the forum you wanted me and all other members 
make to believe that for the "Ride for the Valkyrie" you used a public domain 
track.

Nice try, but false pretenses, which might could be seen as criminal act at 
court. 

>Now I have always responded positively to changes and improvements that 
>I have been asked by email. I even made ​​a point of honor. There is no 
>need to come crying wolf on the forums and lists. A simple mail and I do 
>the right thing !

>My email address is present in all of my airplanes and my site is very 
>easy to find on the net.

 >Criticism is good when it done intelligently. My few mistakes certainly 
>less cause to discredit FG that people who cry foul without even trying 
>to correct or think 5 minutes before!

I have made you already aware in the forum- even it was not per Email, it 
should have been already enough for you to remove those files. 
But I don't think that even per Email it had been more successfull- In the 
moment I can only see excuses and other red herring from you. 

Why don't you just remove the files and stop talking?


Pierre Mueller
Switzerland--
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Flightgear-devel Digest, Vol 69, Issue 9

[BARANGER Emmanuel]

Le 14/01/2012 22:00, flightgear-devel-requ...@lists.sourceforge.net a 
écrit :

> --
>
> Message: 15
> Date: Sat, 14 Jan 2012 20:52:38 + (UTC)
> From: Martin Spott
> Subject: Re: [Flightgear-devel] Flightgear-devel Digest, Vol 69, Issue
>   8
> To:flightgear-devel@lists.sourceforge.net
> Message-ID:
>
> BARANGER Emmanuel wrote:
>
>> First point, when you want to criticize and criticize only, it is best =
>> to write correctly. My name is Emmanuel BARANGER.
> Personally I wouldn't be happy if someone misspelled my name, but I'm
> old enough to know that these things happen every now and then without
> any bad intention.
>
> But the central point in Pierre's posting is a different one: If there
> are copyright violations in the Base Package, then it's valid to
> express concerns about these violations.
>
> You're always well advised to read the copyright clauses really
> carefully before copying content from 3rd party sites, anyhow I know
> that accidental violations still may happen.
> But if they really happen, it's time to head out for a solution instead
> of ciriticizing people for pointing at the violations in question.
> That's primarily_your_  reponsibility because, if Pierre's claims are
> true, you've been the one who has been commiting the violation - and,
> finally,_you_  are the one who brings the OpenSouce project named
> FlightGear into discredit.
>
> Cheers,
>   Martin.
> -- 
Hey Martin,

I am sorry to contradict you, but it's totally false. I admit that I 
sometimes use images (usually reduced compared to the original) in my 
planes (rarely, but it happens). But only for development purposes. And 
I recall the GIT is not a great public venue but a place of development. 
I am not responsible for the misuse of GIT by everyone.

Now I have always responded positively to changes and improvements that 
I have been asked by email. I even made ​​a point of honor. There is no 
need to come crying wolf on the forums and lists. A simple mail and I do 
the right thing !

My email address is present in all of my airplanes and my site is very 
easy to find on the net.

Criticism is good when it done intelligently. My few mistakes certainly 
less cause to discredit FG that people who cry foul without even trying 
to correct or think 5 minutes before!


-- 
BARANGER Emmanuel

http://helijah.free.fr


--
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

flightgear-devel@lists.sourceforge.net

[Martin Spott]

Gijs de Rooy wrote:

> How about moving these messages to --log-level=warn or the like?

I strongly object: People are willfully committing proprietary stuff
into FlightGear.  As long as we can't stop this, writing a warning is
one of the best things "we" (The FlightGear Project) can do.

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

--
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Flightgear-devel Digest, Vol 69, Issue 8

[Martin Spott]

BARANGER Emmanuel wrote:

> First point, when you want to criticize and criticize only, it is best =
> to write correctly. My name is Emmanuel BARANGER.

Personally I wouldn't be happy if someone misspelled my name, but I'm
old enough to know that these things happen every now and then without
any bad intention.

But the central point in Pierre's posting is a different one: If there
are copyright violations in the Base Package, then it's valid to
express concerns about these violations.

You're always well advised to read the copyright clauses really
carefully before copying content from 3rd party sites, anyhow I know
that accidental violations still may happen.
But if they really happen, it's time to head out for a solution instead
of ciriticizing people for pointing at the violations in question. 
That's primarily _your_ reponsibility because, if Pierre's claims are
true, you've been the one who has been commiting the violation - and,
finally, _you_ are the one who brings the OpenSouce project named
FlightGear into discredit.

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

--
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] new fedora

[Stefan Seifert]

On Saturday 14 January 2012 00:20:33 Peter Sadrozinski wrote:
> Hello,
> 
> I'm hitting an 'interesting' problem with the new fedora.  For some reason,
> it's installing the PAE kernel (I guess I should have installed the 64 bit
> version).  The problem is, when the system() is called - for instance, to
> copy an airport btg file from work to output, I get an error.
> 
> Here's debug from copying of said airport:
> 
> running cp ./work/AirportObj/w090n30/w085n33/KATL.btg.gz
> ./output/w090n30/w085n33
> system: : Cannot allocate memory
> returned -1
> 
> I'm not buying the out of memory error.

Please beware that while PAE allows a 32 Bit OS to use more than 4GB of RAM, 
it does not change an individual processes limit. Maybe this is what bites you 
here?

Stefan 

--
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

[Flightgear-devel] Using pixel colors for hot spots

[castle]

Hi,

Browsing the panel.cxx source to understand how "hotspots" are 
implemented; looks like we're still using the x & y coordinates of the 
mouse click to determine which insrument, switch, knob, whatever is 
activated.

If so, has anyone consider an alternative approach to use pixel colors 
to identify the mouse region selected?

The idea is to create a texture mask with unique RGB color regions that 
define the hot spots, overlay the texture mask with the visible texture 
showing the panel.  When a mouse click is detected, read the pixel value 
of the sub-texture in the FBO, decode the color value, and take the 
appropriate acion as in the following code snippet,

void Electrical_Panel::ReadPixel( int x, int y)
{
int pict;
GLRGBQUAD *color;
button = 0x;
unsigned char red, green, blue;

//  glReadPixels(x,y, 1, 1, GL_RGBA, GL_UNSIGNED_BYTE, &pixelColor[0]);
//  printf("Frame Color:%d %d 
%d\n",pixelColor[0],pixelColor[1],pixelColor[2]);
int xpic = x;
int ypic = (1000-y) * 400; // determine location of the pixel
pict = (xpic + ypic);
//  color = frame.GetPixel( pict );
//  printf("Frame Color:%d %d %d %d\n", pict, color->red, color->green, 
color->blue);
color = mask.GetPixel( pict );
blue = color->blue; green = color->green; red = color->red;
button = ((blue << 16) & 0xFF) | ((green << 8) & 0x00FF00) | red;
//  printf("Mask Color: %2x %2x %2x\n",  blue, green, red );
//  printf("Button = 0x%x\n\n" );
int knob = button;
if ( (button & 0x0000) == 0 ) {
pElec->Display_DC( knob );
return;
}

if ( (button & 0x00FF00FF) == 0) {
//  printf("AC rotary\n");
pElec->Display_AC( button );
return;
}

switch (button) {
case 0x00A5CF33:
printf("Maintenance key pressed\n");
break;
case 0x00C4EC0A:
pElec->AutoBusXfer( 1, ON );
//  pElec->Process();
break;
case 0x0033B3CF:
pElec->AutoBusXfer( 1, OFF );
break;
case 0x00E74761:
pElec->AutoBusXfer( 5, ON );
break;

//  and so forth

Logic bit masks can be used to direct program execution and segment the 
panel(s) based on color values and ranges.  Not having worked with panel 
code just wondering if this would be easier to implement and maintain 
than the existing code?  Advantages? Drawbacks? Comments? Questions?

We've been using this approach to design and create complex subsystems 
( such as the 737 electrical ) , implement virtual control panels, and 
test the supporting control and interface logic prior to building and 
installing the actual hardware panel(s).  Also allows further software 
development and testing without having to fire up the entire sim after 
the panels are installed.

Just a thought

John W.

--
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

[Flightgear-devel] [FWD: Using pixel colors for hot spots]

[john.w]

 Original Message 
Subject: Fwd: Using pixel colors for hot spots
From: castle 
Date: Sat, January 14, 2012 2:13 pm
To: 



 Original Message 
Subject: Using pixel colors for hot spots
Date: Sat, 14 Jan 2012 12:12:40 -0800
 From: castle 
To: 

Hi,

Browsing the panel.cxx source to understand how "hotspots" are 
implemented; looks like we're still using the x & y coordinates of the 
mouse click to determine which insrument, switch, knob, whatever is 
activated.

If so, has anyone consider an alternative approach to use pixel colors 
to identify the mouse region selected?

The idea is to create a texture mask with unique RGB color regions that 
define the hot spots, overlay the texture mask with the visible texture 
showing the panel.  When a mouse click is detected, read the pixel value 
of the sub-texture in the FBO, decode the color value, and take the 
appropriate acion as in the following code snippet,

void Electrical_Panel::ReadPixel( int x, int y)
{
int pict;
GLRGBQUAD *color;
button = 0x;
unsigned char red, green, blue;

//	glReadPixels(x,y, 1, 1, GL_RGBA, GL_UNSIGNED_BYTE, &pixelColor[0]);
//	printf("Frame Color:%d %d 
%d\n",pixelColor[0],pixelColor[1],pixelColor[2]);
int xpic = x;
int ypic = (1000-y) * 400; // determine location of the pixel
pict = (xpic + ypic);
//	color = frame.GetPixel( pict );
//	printf("Frame Color:%d %d %d %d\n", pict, color->red, color->green, 
color->blue);
color = mask.GetPixel( pict );
blue = color->blue; green = color->green; red = color->red;
button = ((blue << 16) & 0xFF) | ((green ><< 8) & 0x00FF00) | red;
//	printf("Mask Color: %2x %2x %2x\n",  blue, green, red );
//	printf("Button = 0x%x\n\n" );
int knob = button;
if ( (button & 0x0000) == 0 ) {
	pElec->Display_DC( knob );
	return;
	}

if ( (button & 0x00FF00FF) == 0) {
//		printf("AC rotary\n");
	pElec->Display_AC( button );
	return;
	}

switch (button) {
	case 0x00A5CF33:
			printf("Maintenance key pressed\n");
			break;
	case 0x00C4EC0A:
			pElec->AutoBusXfer( 1, ON );
//pElec->Process();
			break;
	case 0x0033B3CF:
			pElec->AutoBusXfer( 1, OFF );
			break;
	case 0x00E74761:
			pElec->AutoBusXfer( 5, ON );
			break;

//  and so forth

Logic bit masks can be used to direct program execution and segment the 
panel(s) based on color values and ranges.  Not having worked with panel 
code just wondering if this would be easier to implement and maintain 
than the existing code?  Advantages? Drawbacks? Comments? Questions?

We've been using this approach to design and create complex subsystems 
( such as the 737 electrical ) , implement virtual control panels, and 
test the supporting control and interface logic prior to building and 
installing the actual hardware panel(s).  Also allows further software 
development and testing without having to fire up the entire sim after 
the panels are installed.

Just a thought

John W.





--
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

flightgear-devel@lists.sourceforge.net

[Gijs de Rooy]

> is there an easy way to disable this message?
> since i'm using dds texture, it's flooding the console...

+1

Every single texture of --material=materials-dds.xml seems gives an error...
How about moving these messages to --log-level=warn or the like?
  --
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] new fedora

[Martin Spott]

Peter Sadrozinski wrote:

> [...] Is anyone else running a PAE kernel on a 64 bit
> machine?  Has anyone seen this issue?

Yes. No.  ;-)

I'm sorry, I can't help here.  I'm running machines with many processes
on large machines (up to 60 simultaneous users with GNOME/KDE, Firefox,
OpenOffice and the like on a single server) on PAE, but not just one
single, large process.

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

--
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

[Flightgear-devel] Jenkins TerraGear builds include hardcoded paths

[Gijs de Rooy]

Hi,

the TerraGear-Win64-Cmake build from Jenkins seems to include some hardcode 
paths. I get the following error running fgfs-construct:

Failed to load priorities file 
D:/FGFSHudsonCMake/TerraGear_64/install/msvc100-64/TerraGear/share/TerraGear/default_priorities.txt

And this one with the TerraGear-Win-Cmake build:

Failed to load priorities file 
D:/FGFSHudsonCMake/TerraGear/install/msvc100/TerraGear/share/TerraGear/default_priorities.txt

I don't have a D:/ drive on this machine, so I'm unable to generate scenery :-(

Cheers,
Gijs
  --
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] new fedora

[Peter Sadrozinski]

I am hitting the error in both fgfs-construct (when copying airport.btg.gz
from ./work to ./output) and simger write_ascii when gzipping the file.

Both are using system( cmd ).  System returns -1 and perror is printing out
of memory.

I doubt I am out of memory, as the command I'm running is just cp x y for
fgfs-construct.

I've never run the pae kernel before.  The new anaconda picked it for me
without asking.

I've backed up all my dev directory to NAS, and I'm buring the 64 bit
fedora DVD now.

This has been the worst upgrade experience by far for me.  I've been on
fedora since fedora core 2, and usually update every year or so.

Pete
 On Jan 14, 2012 10:42 AM, "Curtis Olson"  wrote:

> On Fri, Jan 13, 2012 at 11:20 PM, Peter Sadrozinski <
> psadrozin...@gmail.com> wrote:
>
>> Hello,
>>
>> I'm hitting an 'interesting' problem with the new fedora.  For some
>> reason, it's installing the PAE kernel (I guess I should have installed the
>> 64 bit version).  The problem is, when the system() is called - for
>> instance, to copy an airport btg file from work to output, I get an error.
>>
>> Here's debug from copying of said airport:
>>
>> running cp ./work/AirportObj/w090n30/w085n33/KATL.btg.gz
>> ./output/w090n30/w085n33
>> system: : Cannot allocate memory
>> returned -1
>>
>> I'm not buying the out of memory error.  I've googled for this, but
>> haven't seen anything interesting.  Is anyone else running a PAE kernel on
>> a 64 bit machine?  Has anyone seen this issue?
>>
>> I don't want to lose another weekend reinstalling linux (again)
>>
>
> Hi Peter, what command/tool are you using to copy files.  This is external
> to flightgear itself, right?  I would think that the 32 bit linux system
> would run just fine on 64 bit hardware -- as long as you stay within the
> expectations/limitations of a 32 bit system.
>
> I did run into an out of memory error recently trying to fsck a huge
> volume with an immense number of files (my "backuppc" drive) on a 1Gb
> system.  Moving the drive over to a 2Gb system allowed the fsck to complete.
>
> Regards,
>
> Curt.
> --
> Curtis Olson:
> http://www.atiak.com - http://aem.umn.edu/~uav/
> http://www.flightgear.org - http://gallinazo.flightgear.org
>
>
>
> --
> RSA(R) Conference 2012
> Mar 27 - Feb 2
> Save $400 by Jan. 27
> Register now!
> http://p.sf.net/sfu/rsa-sfdev2dev2
> ___
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
>
--
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] new fedora

[Curtis Olson]

On Fri, Jan 13, 2012 at 11:20 PM, Peter Sadrozinski
wrote:

> Hello,
>
> I'm hitting an 'interesting' problem with the new fedora.  For some
> reason, it's installing the PAE kernel (I guess I should have installed the
> 64 bit version).  The problem is, when the system() is called - for
> instance, to copy an airport btg file from work to output, I get an error.
>
> Here's debug from copying of said airport:
>
> running cp ./work/AirportObj/w090n30/w085n33/KATL.btg.gz
> ./output/w090n30/w085n33
> system: : Cannot allocate memory
> returned -1
>
> I'm not buying the out of memory error.  I've googled for this, but
> haven't seen anything interesting.  Is anyone else running a PAE kernel on
> a 64 bit machine?  Has anyone seen this issue?
>
> I don't want to lose another weekend reinstalling linux (again)
>

Hi Peter, what command/tool are you using to copy files.  This is external
to flightgear itself, right?  I would think that the 32 bit linux system
would run just fine on 64 bit hardware -- as long as you stay within the
expectations/limitations of a 32 bit system.

I did run into an out of memory error recently trying to fsck a huge volume
with an immense number of files (my "backuppc" drive) on a 1Gb system.
 Moving the drive over to a 2Gb system allowed the fsck to complete.

Regards,

Curt.
-- 
Curtis Olson:
http://www.atiak.com - http://aem.umn.edu/~uav/
http://www.flightgear.org - http://gallinazo.flightgear.org
--
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Flightgear-devel Digest, Vol 69, Issue 8

[Curtis Olson]

This shouldn't need to devolve into an argument, nor do we need to carry
over petty bickering from the forum.  Let us put all that aside and just
focus on the facts.  We must honor the GPL.  That is central to the entire
existence of FlightGear.

If there is non-gpl compatible copyrighted content included in various
aircraft, we simply have to suck up our ego and fix the problems.  Let's
not try to deflect the attention elsewhere.  I'm sure if we dig we can find
other issues to distract ourselves with, but we must address the issues in
front of us that we do know about.

For me, this is what it boils down to:

Every one makes mistakes; that is part of life.  We need to allow for that
in our dealings with each other and not come down too hard on each other.
 I think what is important is how we deal with those mistakes; that is the
more important characteristic.

I see a couple options here now that potential issues have been discovered
and brought to the public attention.

1. We could discuss (reasonably!) if these are indeed GPL/Copyright
violations or not -- and this would need to be on a case-by-case basis I
suppose.

2. If it is clear to everyone that there are indeed real issues here, then
we need to focus on those and fix them -- not argue about other things.

In terms of fixing the problems I would propose giving the original author
a reasonable time frame to address the issue.  Like I said, we all make
honest mistakes and we should be given a reasonable opportunity to address
them.

If there is a good faith intention to fix the problems, but we run out of
time before the v2.6.0 release, we could simply leave those identified
aircraft out of the release/distribution until the problems can be fully
resolved.

I thing we should assume the best of intentions and proceed in good faith
here.  Emmanuel (and others if they would choose to contribute) should be
given some reasonable time address these specific issues, or defend the
usage of the material in question.

At the end of all this we have to put aside all the arguments and
distractions and focus on making sure any problems with the GPL are cleaned
up before the next release so we will be able to include these aircraft.

Best regards,

Curt.


On Sat, Jan 14, 2012 at 9:15 AM, Pierre Mueller wrote:

> Dear  Emmanuel BARANGER,
>
> >First point, when you want to criticize and criticize only, it is best
> >to write correctly. My name is Emmanuel BARANGER.
>
> O.k. I'm sorry for that mistake. And I'm surprised to see that your
> surname is captilized. I didn't know that it is possible in France, so I
> wasn't aware of it.
>
> >6, or 8 airplanes on 203. It enough that you send free files for
> >replacement. Always wait for others to do is not the answer!
>
> >The interest of free, it is precisely that, normally, instead of be
> >scandalized, just to denigrate people, anyone can modify the data and
> >correct errors. If you are not able to do, so do not come drool on other.
>
> Sorry again, but I thought YOU are are the author and the maintainer. At
> least you created the mentioned aircraft, so I held YOU for being
> responsible for the mentioned aircraft.
>
> >I explained to you (on forum) that GIT was a place of development. The
> >files referred to are of course just for the present development. It
> >seems that you have cares of understanding and your favorite hobby is
> >the critical. This is not constructive.
>
> First: I'm a User. I have understanding of licences due to many reasons
> and some little understanding how OSS works, but not in creating an
> aircraft .
>
> So do I have to be a developer to critize?
> Aren't users allowed to critize and make aware of bugs, errors, mistakes
> done with and without intention?
> And how can users like me find out how to make remove things like the
> mentioned images, sounds etc.?
> Shoulden't be it enough to say: please  Dear Mr. BARANGER- Please remove
> the mentioned files, as you violating copyrights with?
>
> Second: with pushing your things into GIT and on your homepage you made
> them publicly available. All licences do not care about things being in
> developement- if you take protected things without permission and
> redistribute them, you are infringing the copyrights.
>
> And as I understood the developement process of FlightGear, all things in
> FGdata (=GIT?) are freezed and and packaged without further modifications,
> and again made publicly available.
>
> So there is a not so small chance that FGFS-Project can be made
> responsible for violating copyrights by redistributing copyrighted images
> and sound snapshots used in the aircraft available on the
> FGFS-Official-Downloadpage. And as I don't see any Disclaimer on the
> Download page or anywhere else, that FGFS-Project is not responsible for
> the content they provide,  it could be a nice invitation for some lawyers
> who wants to earn more money.
>
>
> >I am really tired of all these people who, instead of acting, prefer
> >disparage, 

Re: [Flightgear-devel] Flightgear-devel Digest, Vol 69, Issue 8

[Pierre Mueller]

Dear  Emmanuel BARANGER,

>First point, when you want to criticize and criticize only, it is best 
>to write correctly. My name is Emmanuel BARANGER.

O.k. I'm sorry for that mistake. And I'm surprised to see that your surname is 
captilized. I didn't know that it is possible in France, so I wasn't aware of 
it. 

>6, or 8 airplanes on 203. It enough that you send free files for 
>replacement. Always wait for others to do is not the answer!

>The interest of free, it is precisely that, normally, instead of be 
>scandalized, just to denigrate people, anyone can modify the data and 
>correct errors. If you are not able to do, so do not come drool on other.

Sorry again, but I thought YOU are are the author and the maintainer. At least 
you created the mentioned aircraft, so I held YOU for being responsible for the 
mentioned aircraft. 

>I explained to you (on forum) that GIT was a place of development. The 
>files referred to are of course just for the present development. It 
>seems that you have cares of understanding and your favorite hobby is 
>the critical. This is not constructive.

First: I'm a User. I have understanding of licences due to many reasons and 
some little understanding how OSS works, but not in creating an aircraft .

So do I have to be a developer to critize? 
Aren't users allowed to critize and make aware of bugs, errors, mistakes done 
with and without intention?
And how can users like me find out how to make remove things like the mentioned 
images, sounds etc.? 
Shoulden't be it enough to say: please  Dear Mr. BARANGER- Please remove the 
mentioned files, as you violating copyrights with?

Second: with pushing your things into GIT and on your homepage you made them 
publicly available. All licences do not care about things being in 
developement- if you take protected things without permission and redistribute 
them, you are infringing the copyrights. 

And as I understood the developement process of FlightGear, all things in 
FGdata (=GIT?) are freezed and and packaged without further modifications, and 
again made publicly available. 

So there is a not so small chance that FGFS-Project can be made responsible for 
violating copyrights by redistributing copyrighted images and sound snapshots 
used in the aircraft available on the FGFS-Official-Downloadpage. And as I 
don't see any Disclaimer on the Download page or anywhere else, that 
FGFS-Project is not responsible for the content they provide,  it could be a 
nice invitation for some lawyers who wants to earn more money. 


>I am really tired of all these people who, instead of acting, prefer 
>disparage, criticize, drooling on the authors etc. . It's really 
>pathetic.


No, the way critism handled here is pathetic.

As I said, there was no offense meant, but it seems to me you feel yourself 
personaly attacked. Sorry, that's not what I wanted, but making you aware of 
having done mistakes with using the copyrighted things.

With my Aircraft review on the forum I also gave you tips for improving your 
aircraft- a pity that you can't use it. 

Maybe someone others here on the mailing-list can explain the developement 
process of FGFS written in the FGFS-wiki to me again, so I can sure that I said 
above about the developement process is correct.

Kind Regards
Pierre Mueller
Switzerland




--
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel--
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Flightgear-devel Digest, Vol 69, Issue 8

[BARANGER Emmanuel]

Le 14/01/2012 12:42, flightgear-devel-requ...@lists.sourceforge.net a 
écrit :
> --
>
> Message: 12
> Date: Thu, 12 Jan 2012 17:09:13 + (GMT)
> From: Pierre Mueller
> Subject: Re: [Flightgear-devel] Reminder for the release process for
>   version 2.6.0
> To: FlightGear developers discussions
>   
> Message-ID:
>   <1326388153.90244.yahoomail...@web29801.mail.ird.yahoo.com>*All ? Not 
> GNU GPL compatibles things ? ?checked out??
Dear Pierre Mueller
>
> And especially for Helijah aka Emanuel Barranger:
First point, when you want to criticize and criticize only, it is best 
to write correctly. My name is Emmanuel BARANGER.

> Even if this is only a small number of the very high number of aircraft- the 
> use of the mentioned things violates the licences of each thing and is not 
> compatible with GNU GPL.
6, or 8 airplanes on 203. It enough that you send free files for 
replacement. Always wait for others to do is not the answer!

The interest of free, it is precisely that, normally, instead of be 
scandalized, just to denigrate people, anyone can modify the data and 
correct errors. If you are not able to do, so do not come drool on other.
> But I'm dissapointed as I always hoped there will be a flight simulator out 
> there who provides legal Add-Ons!
> You will find a lot "not-so-legal" things for MSFS and I saw some dubios 
> things for X-Plane. I hoped that FGFS as being OpenSource is better.
I explained to you (on forum) that GIT was a place of development. The 
files referred to are of course just for the present development. It 
seems that you have cares of understanding and your favorite hobby is 
the critical. This is not constructive.

I am really tired of all these people who, instead of acting, prefer 
disparage, criticize, drooling on the authors etc. . It's really 
pathetic.

Regards. Emmanuel

-- 
BARANGER Emmanuel

http://helijah.free.fr


--
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] FlightGear writes "autosave.xml" into ${FG_ROOT}

[James Turner]

On 14 Jan 2012, at 11:42, James Turner wrote:

>> While trying to find out about a different issue ('fgfs' not starting
>> at all) I noticed, that it still writes an "autosave.xml" into
>> ${FG_ROOT} despite the fact that I've explicitly set
>> --prop:/sim/startup/save-on-exit=false
>> Now I'd like to learn wether someone is deliberately trying piss users
>> off or it this is just a bug  ;-)

Just tested this and it seems to work for me (setting exactly that argument - 
there's also explicit options: --disable-save-on-exit and --enable-save-on-exit)

Where abouts did you specify the option? In a config file or on the command 
line? I made some changes to config file handling back in the autumn, but I've 
tested setting custom properties via those and it works in the general case.

What value do you see for the property in the inspector?

James


--
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] [Flightgear-commitlogs] TerraGear / Custom

[Gijs de Rooy]

> Martin wrote:
> I'd like to point out that I'm now having what I think should be
> topologically clean CLC2000v15 and VMap0 edition 5.0 datasets.  I'll
> load these into the Landcover-DB as replacements for the current VMap0
> and CLC layers.

That's excellent news indeed! Would you write a short update in the Newsletter?
If not, would you mind if I copy&edited some of your mail? This is something 
that
deserves some more attention and respect ;-)

Cheers,
Gijs
  --
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] [Flightgear-commitlogs] TerraGear / Custom

[James Turner]

On 13 Jan 2012, at 17:46, Martin Spott wrote:

> Finally 3.) As soon as the various tools are working in a predictable
> manner, I'm planning to revive the central idea, the driving motivation
> behind all the effort, which is to build an infrastructure for
> re-compiling the respective terrain tiles on a regular, maybe daily
> schedule after the land cover has been updated in a certain region.
> 
> Having a stable and reliable procedure to clean the vector data is one
> of the vital requirements for such an adventure, therefore I'm quite
> excited today 

Of course, this will be fantastic. Please let us know what help you need to 
make it happen, and thanks for all your long, hidden efforts on this.

James


--
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] FlightGear writes "autosave.xml" into ${FG_ROOT}

[James Turner]

On 13 Jan 2012, at 16:18, Martin Spott wrote:

> While trying to find out about a different issue ('fgfs' not starting
> at all) I noticed, that it still writes an "autosave.xml" into
> ${FG_ROOT} despite the fact that I've explicitly set
> --prop:/sim/startup/save-on-exit=false
> Now I'd like to learn wether someone is deliberately trying piss users
> off or it this is just a bug  ;-)
> 
> Is there really no way just to run FG without having _no_ garbage
> written out to any files ?

It's a bug, will take a look now.

James


--
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

[Flightgear-devel] Re : [Flightgear-commitlogs] TerraGear / Custom

[Olivier]

Martin Spott wrote:


> Finally 3.) As soon as the various tools are working in a predictable
> manner, I'm planning to revive the central idea, the driving motivation
> behind all the effort, which is to build an infrastructure for
> re-compiling the respective terrain tiles on a regular, maybe daily
> schedule after the land cover has been updated in a certain region.
>
> Having a stable and reliable procedure to clean the vector data is one
> of the vital requirements for such an adventure, therefore I'm quite
> excited today 

Martin,

This is really great news! A big thankyou  to you and everyone involved.
2012 is the year for FG scenery! Good luck for the latest steps to the
scenery generation.

Olivier
--
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel