Hello Fred
Yes the latest data version (30.03.2010) crashes FG.
With the data from 28 th and 29 th FGFS runs nice. With the version from 29
th I can see the landmass effect with the price of a huge drop of frame rate
(45 fps down to 20 fps).
With the version from 30 th the screen goes black as
I am not sure I understand the situation. Do you mean the last version of the
shader crash fgfs ?
If it's the case, what is your hardware setup ?
> what means no cube map?
I was replying to a side question earlier in this thread about a patch Vivian
mentioned to make the new Lightning F1 wor
Oliver,
The patch has been available since Sunday. There is no delay it always
takes this long.
Vivian
-Original Message-
From: Oliver Thurau [mailto:oli.thu...@googlemail.com]
Sent: 30 March 2010 21:29
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel
Hello Fred
After trying the settings i figured the landmass shader causes the crash.
After reading the post of the topping I was trying to check out 29 th and 27
and figured I was always getting the same files. It seems my version of
tortoise cvs when set to German has issues with the Date. It use
But already done: http://www.hoerbird.net/reisen.html
>
> --- Oliver Thurau schrieb am Di, 30.3.2010:
>
> Von: Oliver Thurau
> Betreff: Re: [Flightgear-devel] CVS binary (fred) from 28.03.2010 - freeze
> without any log entry and freeze with a black screen
> An: "Flight
this may be the
cause of the freezing.
still in work: http://www.hoerbird.net/galerie.html
But already done: http://www.hoerbird.net/reisen.html
--- Oliver Thurau schrieb am Di, 30.3.2010:
Von: Oliver Thurau
Betreff: Re: [Flightgear-devel] CVS binary (fred) from 28.03.2010 - freeze
withou
Hello Fred
Thanks for the quick response and sorry for the unspecified error report...
figured today I send that mail instead of saving it.
for options & shaders:
- CVS data matches the binary data (28th)
- Shaders are all active (no urban shader),
- Options: automatic trees, ai-models, time-noon
as I wondered why he uses a win32, as you also have a win64
package available.
>
> still in work: http://www.hoerbird.net/galerie.html
> But already done: http://www.hoerbird.net/reisen.html
>
> --- Frederic Bouvier schrieb am Di, 30.3.2010:
>
> Von: Frederic Bouvi
Betreff: Re: [Flightgear-devel] CVS binary (fred) from 28.03.2010 - freeze
without any log entry and freeze with a black screen
An: "FlightGear developers discussions"
Datum: Dienstag, 30. März, 2010 10:09 Uhr
#yiv689103692 p {margin:0;}A lot of applications are still Win32, including
Vis
ng, as I
somewhere hear a similar problem (Not FGFS)
> still in work: http://www.hoerbird.net/galerie.html
> But already done: http://www.hoerbird.net/reisen.html
>
> --- Frederic Bouvier schrieb am Di, 30.3.2010:
>
> Von: Frederic Bouvier
> Betreff: Re: [Flightgear-
Bouvier
Betreff: Re: [Flightgear-devel] CVS binary (fred) from 28.03.2010 - freeze
without any log entry and freeze with a black screen
An: "FlightGear developers discussions"
Datum: Dienstag, 30. März, 2010 09:41 Uhr
#yiv1641570632 p {margin:0;}> are you really running a FGFS win
> are you really running a FGFS win32 on a win64?
> If so, that could be the problem.
Why ?
-Fred
--
Frédéric Bouvier
http://my.fotolia.com/frfoto/ Photo gallery - album photo
http://www.youtube.com/user/fgfred64 Videos
---
-devel] CVS binary (fred) from 28.03.2010 - freeze without
any log entry and freeze with a black screen
An: flightgear-devel@lists.sourceforge.net
Datum: Dienstag, 30. März, 2010 01:27 Uhr
What steps will reproduce the problem?
1.
loading FG with any plane at KSFO or Moffet
2. after plane
Are the new binary compiled with patch
ftp://ftp.abbeytheatre2.org.uk/fgfs/Shader/Reflect/cube-map.patch ?
--Buganini
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find
What about shaders and other rendering options ?
Are the data in sync with the program ?
Is there a rendering option where the problem doesn't arise ? (try to disable
shaders one by one)
- Fred
- "Oliver Thurau" a écrit :
>
What steps will reproduce the problem?
> 1. loading FG with a
What steps will reproduce the problem?
1. loading FG with any plane at KSFO or Moffet
2. after plane loading switch to outside view and look around
3. FG crashes after a couple of seconds without any log entry and freeze
with a black screen. cpu load 100%. terragear seems to still work.
What is t
* Vivian Meazza -- Friday 12 February 2010:
> It's an option - we're not racist here :-). We should look after everyone.
OK, let me put it that way: it's a bug. Not that I really care ...
m.
--
SOLARIS 10 is the OS for D
Melchior wrote
>
> * Vivian Meazza -- Friday 12 February 2010:
> >
> > Microsoft-PC-Joysticktreiber
>
> So we have a new default joystick on German MS Vista installations?
> Funny idea ...
>
> m.
It's an option - we're not racist here :-). We should look after everyone.
V.
* Vivian Meazza -- Friday 12 February 2010:
>
> Microsoft-PC-Joysticktreiber
So we have a new default joystick on German MS Vista installations?
Funny idea ...
m.
--
SOLARIS 10 is the OS for Data Centers - provide
On 19 Dec 2009, at 19:03, Vivian Meazza wrote:
> Hey guys, don't we test code/scripts nowadays before stuffing it into CVS?
Well the C++ code works - for this kind of thing I was lazy and hoped the
person who requested the feature will test it and let me know if they encounter
problems. I also
On 19 Dec 2009, at 18:55, Melchior FRANZ wrote:
> Still wrong. Since when do we use minus signs in variable names?
Ah, that's annoying. Can't map property names to Nasal, since '-' is a token in
Nasal.
Hmmm.
ilsFrequenceyMHz?
ils_frequency_mhz?
If there's a Nasal convention here please let
Melchior FRANZ wrote
>
> * James Turner -- Saturday 19 December 2009:
> > - HASHSET("ils-frequency-mhz", 3, naNum(rwy->ILS()->get_freq()
> / 100.0));
> > + HASHSET("ils-frequency-mhz", 17, naNum(rwy->ILS()->get_freq()
> / 100.0));
>
> Still wrong. Since when do we use minus sign
* James Turner -- Saturday 19 December 2009:
> Onwards and upwards (in CVS, now). Shortest code review I've ever had (so
> far!)
Well, since people have taken over who pretend to know better (and I don't mean
you), I can't be bothered to write verbose reports. :-P
m.
--
* James Turner -- Saturday 19 December 2009:
> - HASHSET("ils-frequency-mhz", 3, naNum(rwy->ILS()->get_freq() /
> 100.0));
> + HASHSET("ils-frequency-mhz", 17, naNum(rwy->ILS()->get_freq() /
> 100.0));
Still wrong. Since when do we use minus signs in variable names?
m.
--
On 19 Dec 2009, at 18:38, Melchior FRANZ wrote:
>> + HASHSET("ils-frequency-mhz", 3, naNum(rwy->ILS()->get_freq() /
>> 100.0));
>
> FAIL
Onwards and upwards (in CVS, now). Shortest code review I've ever had (so far!)
James
* James Turner -- Saturday 19 December 2009:
> + HASHSET("ils-frequency-mhz", 3, naNum(rwy->ILS()->get_freq() /
> 100.0));
FAIL
m.
--
This SF.Net email is sponsored by the Verizon Developer Community
Take advan
Can NOMINMAX be added to all the MSVC9 projects that need it at the same
time please?
-Original Message-
From: Vivian Meazza [mailto:vivian.mea...@lineone.net]
Sent: 19 September 2009 12:05
To: 'FlightGear developers discussions'
Subject: [Flightgear-devel] CVS HEAD - am
Hi,
This morning's FG CVS head fails to compile under MSVC9 (nothing new there
then!). Flightgear/source/src/ATCDCL/ATCVoice.cxx and ATIS.cxx are the
problems.
There's a fix here:
http://gitorious.org/~vivian/fg/vivians-clone
for those who want to attempt git.
It works, but unfortunately it u
Hi Curtis,
Can you fix the permissions on the flightgear/source/projects/VC90 subdirectory?
Also, I suspect that the permissions are wrong on data/Shaders and data/Effects.
Perhaps there's a way to configure CVS so that new directories are writable by
all?
Thanks,
Tim
---
Hi,
- "Rob Shearman, Jr." a écrit :
> Speaking of CVS builds -- Fred, I see there's a new one on the FTP
> site for 7/26, but I'm getting http error "550: Not a directory" when
> I attempt to open it. Anyone else having this problem?
My connection timed out yesterday evening with a half upload
Me:
"This morning at around 0200UTC another user and I were to meet at KNZY (San
Diego North Island Naval Air Station) to do a little for-fun dogfight
practice. Both of us were on mpserver02. He was using one of Dave
Culp's F4s and I was in the CVS A6E. However, although I could see his
plane, h
* Mathias Froehlich -- Sunday 07 June 2009:
> Modified Files:
> NasalSys.cxx
> Log Message:
> No need to zero the _props variable.
> This reference is released by the SGSharedPtr destructor anyway.
>
> Modified Files:
> src/Scripting/NasalSys.cxx
> -_props = 0;
Yes, but it's r
Hi All,
This is a 'fix' to sgscreen library,
for those with a glX extension implementation
that still reports version 1.2...
Wow, I got there!!! Boy I love coding when
you persist, and try, and try some more,
and you discover what makes it work ;=))
even when you do not fully 'understand'
all tha
On mardi 05 mai 2009, Gijs de Rooy wrote:
> Hi Torsten and others,
>
> > > I assumed that the function should also be accessible via other
> > > means than just the dialog (e.g. keyboard bindings). If not,
> > > then I absolutely agree with your change. That's the cleanest way.
> >
> > I'll leave t
> The best solution is probably to make the magnitude be set per plane.
> Large/heavy
>
> planes need more powerfull trucks than small ones, as we know. Even nicer
> would be
>
> to have a slide for speed instead of power. But that's way to complicated
> for me to
>
> make, even easy things are a c
P pauses the simulation, but if you mean "P" as in uppercase P(ie. Shift
+P), then it's okay.
> Hi Torsten and others,
>
> > > I assumed that the function should also be accessible via other
> > > means than just the dialog (e.g. keyboard bindings). If not,
> > > then I absolutely agree with your
Hi Torsten and others,
> > I assumed that the function should also be accessible via other
> > means than just the dialog (e.g. keyboard bindings). If not,
> > then I absolutely agree with your change. That's the cleanest way.
> I'll leave this to the original author (Gijs) if he wants to extend
* Torsten Dreyer -- Tuesday 05 May 2009:
> [...] the truck (door) keeps moving until it reached its final
> position. Probably because the underlying interpolate() function keeps
> running until its finished.
Yes. But you can immediately stop the movement on with the
aircraft.door.stop() method
> I assumed that the function should also be accessible via other
> means than just the dialog (e.g. keyboard bindings). If not,
> then I absolutely agree with your change. That's the cleanest way.
I'll leave this to the original author (Gijs) if he wants to extend the
functionality that way. If s
* Torsten Dreyer -- Tuesday 05 May 2009:
> I moved the initialization of the aircraft.door object into the
> pushback.xml when the dialog is opened.
I assumed that the function should also be accessible via other
means than just the dialog (e.g. keyboard bindings). If not,
then I absolutely agree
> Let's help Gijs to make it work for the 747-400 and then we will see
> what is needed or not so we use this feature the bestway.
>
> Again, now that it is commited, everyone can bring its ideas. That's
> exactly what you are doing Heiko :-) So thanks.
Thanks Gijs and Alexis for bringing pushback
* Melchior FRANZ -- Monday 04 May 2009:
> - it uses variable names:
Which would be fine, of course. I meant: *bad* variable names ;-)
m.
--
Register Now & Save for Velocity, the Web Performance & Operations
Conference
* Alexis Bory - xiii -- Monday 04 May 2009:
> But I do not have the piece which is necessary for testing.
I didn't test it either. It's just obviously wrong (and ugly :-).
Wrong, because ...
- it uses aircraft.door before that is guaranteed to exist
- because it doesn't use "var" where it should
Hi guys,
I've sent this code to Alexis, so he could commit it to CVS, without knowing
that
files within the $FG_ROOT/Nasal directory are automaticly loaded with every
aircraft. On my machine the file gave no errors at all. Therefore it's hard for
me
to find what I did wrong supposendly.
Lu
Right, we don't get too bent out of shape if problems and bugs are
discovered in newly committed code, as long as the person responsible is
aggressively pursuing the issues and fixing them as quickly as possible.
(No one is perfect on the first try every time.)
But that said, we really like to kee
Heiko Schulz wrote:
>
>
> May I ask something here? Why there is something comitted, which
> isn't tested yet?
But commiting to the CVS is the faster way to get usefull feed back and
gather differents opinions on a proposal.
> A generic pushback sounds nice, but so much as I
> understood, the
May I ask something here?
Why there is something comitted, which isn't tested yet? A generic pushback
sounds nice, but so much as I understood, the feature is only for JSBSim and
all the JSBsim aircafts who wants to use this feature, needs an update. At
least there should be one aircraft exam
Melchior FRANZ wrote:
> * Alexis Bory -- Monday 04 May 2009:
> > Added Files: pushback.nas
>
> This is not only verbose and ugly code, it will cause error messages
> and not work on some machines. Just saying ...
>
> m. :-}
Hi Melchior,
I did not had such a strong feeling when receiving Gijs
* Alexis Bory -- Monday 04 May 2009:
> Added Files:
> pushback.nas
This is not only verbose and ugly code, it will cause error
messages and not work on some machines. Just saying ...
m. :-}
--
Register Now & Sav
* Frederic Bouvier -- Thursday 19 March 2009:
> Support old compilers
- if(argc < 2 or argc > 3)
+ if(argc < 2 || argc > 3)
Argh ... sorry! That's a contamination from Nasal. I don't get why
g++ doesn't turn this nonsense off by default. Won't happen again.
m.
--
* Melchior Franz -- Sunday 15 March 2009:
> Modified Files:
> xmlauto.cxx
> Log Message:
>
> Merge branch 'master' of ../.fg.osg
Sorry, should have been:
Roy V. OVESEN: Actually initialize Ti and Td to the values in the
config file.
I used to fix such mishaps by changing the log mess
On dimanche 15 février 2009, Nicolas Quijano wrote:
> Gerard, you're not getting it : if I want wildfire to spread when I crash a
> Crusader, you shouldn't have a say in it, period.
> Let me try to explain it from the user's perspective : a user of both the
> dev's creation, the simulation, and in
Gerard, you're not getting it : if I want wildfire to spread when I crash a
Crusader, you shouldn't have a say in it, period.
Let me try to explain it from the user's perspective : a user of both the
dev's creation, the simulation, and in this case, your a/c.
I'm the one piloting the Crusader, and
gerard robin wrote:
> I was STUPID since, i thought that the modelers were free to create
> the Aircraft in order to answer to these old criteria ( best FDM, eye
> candy). I noticed now that we are dependent of some constraints, we
> must accept anything coming from the mind of DEVELOPPER who
On dimanche 15 février 2009, Arnt Karlsen wrote:
> On Sat, 14 Feb 2009 23:36:30 + (GMT), Stuart wrote in message
>
>
> ..then you have exotic compromises like crashing on ice, dead stick
> landings in methane clouds downwind of broken pipelines, ripe full
> hydrazine tanks as you ditch in free
* Sébastien MARQUE -- Sunday 15 February 2009:
> I'm quite "surprised" not to see someone purpose an other solution which
> is only to override wildfire.ignite() function in a single aircraft, as
> we are used to do for brakes, or starting engines.
That's because this is *still* wrong. This is a
Hi all,
I understand the both point of view about wildfire and "gaming" issues.
but I think that changing wildfire-on-crash property is not a good
solution because it is registered, but it is also a problem if an
aircraft designer wants to create his own crash animation.
I'm quite "surprised"
On dimanche 15 février 2009, Detlef Faber wrote:
> Am Sonntag, den 15.02.2009, 09:45 +0100 schrieb Detlef Faber:
> > Am Samstag, den 14.02.2009, 23:15 +0100 schrieb gerard robin:
> > > On samedi 14 février 2009, Melchior FRANZ wrote:
> > > > * Gerard Robin -- Saturday 14 February 2009:
> > > > > Lo
On Sat, 14 Feb 2009 23:36:30 + (GMT), Stuart wrote in message
<628624.58015...@web26003.mail.ukl.yahoo.com>:
>
> gerard robin wrote:
> > On dimanche 15 février 2009, Ron Jensen wrote:
> > > Respectfully I must disagree with you here. This is a system
> > > feature and should not be adjuste
Am Sonntag, den 15.02.2009, 09:45 +0100 schrieb Detlef Faber:
> Am Samstag, den 14.02.2009, 23:15 +0100 schrieb gerard robin:
> > On samedi 14 février 2009, Melchior FRANZ wrote:
> > > * Gerard Robin -- Saturday 14 February 2009:
> > > > Log Message:
> > > > withdraw the "game coat"
> > > >
> > > >
Am Samstag, den 14.02.2009, 23:15 +0100 schrieb gerard robin:
> On samedi 14 février 2009, Melchior FRANZ wrote:
> > * Gerard Robin -- Saturday 14 February 2009:
> > > Log Message:
> > > withdraw the "game coat"
> > >
> > > +
> > > +
> > > + false
> > > +
On dimanche 15 février 2009, Laurent wrote:
> IMHO, in that case this is a bug about when wildfire should be
> started. If the plane is actually missing a landing on water, it
> should be detected by the main program as it, not as a land crash. A
> catalina crashing on land should create fire. Deac
gerard robin wrote:
> On dimanche 15 février 2009, Ron Jensen wrote:
> > Respectfully I must disagree with you here. This is a system feature
> > and should not be adjusted in random aircraft -set files. It is
> > properly set in preferences.xml and autosave.xml, not each aircraft -set
> > file
On dimanche 15 février 2009, gerard robin wrote:
> On dimanche 15 février 2009, Ron Jensen wrote:
> > On Sat, 2009-02-14 at 23:56 +0100, gerard robin wrote:
> > > On samedi 14 février 2009, gerard robin wrote:
> > > > On samedi 14 février 2009, Melchior FRANZ wrote:
> > > > > * Gerard Robin -- Satu
On Sun, 15 Feb 2009, gerard robin wrote:
> That is part of a model.
>
> Can you imagine a Catalina gently crashing on water ( when landing) gerring
> Wildfire ?
If you haven't noticed: Water does not burn.
But yes, one would like to have the possibility the insert an aircraft
specific function
Melchior FRANZ wrote:
> * Curtis Olson -- Saturday 14 February 2009:
> > No I think Melchior is justified (as occasionally can be the case) :-)
>
> :-P
>
> > We could simply default wild fires to off in the preferences.xml file and
> > that is perhaps the thing to do.
>
> Exactly, and as I've
IMHO, in that case this is a bug about when wildfire should be
started. If the plane is actually missing a landing on water, it
should be detected by the main program as it, not as a land crash. A
catalina crashing on land should create fire. Deactivate wildfire for
the whole environment is not the
On dimanche 15 février 2009, Ron Jensen wrote:
> On Sat, 2009-02-14 at 23:56 +0100, gerard robin wrote:
> > On samedi 14 février 2009, gerard robin wrote:
> > > On samedi 14 février 2009, Melchior FRANZ wrote:
> > > > * Gerard Robin -- Saturday 14 February 2009:
> > > > > Log Message:
> > > > > wit
On Sat, 2009-02-14 at 23:56 +0100, gerard robin wrote:
> On samedi 14 février 2009, gerard robin wrote:
> > On samedi 14 février 2009, Melchior FRANZ wrote:
> > > * Gerard Robin -- Saturday 14 February 2009:
> > > > Log Message:
> > > > withdraw the "game coat"
> > > >
> > > > +
> > > > +
On samedi 14 février 2009, Melchior FRANZ wrote:
> * Gerard Robin -- Saturday 14 February 2009:
> > Log Message:
> > withdraw the "game coat"
> >
> > +
> > +
> > + false
> > +
> > +
>
> AIRCRAFT MUST *NOT* CHANGE SYSTEM SETTING!
>
> This s
On samedi 14 février 2009, gerard robin wrote:
> On samedi 14 février 2009, Melchior FRANZ wrote:
> > * Gerard Robin -- Saturday 14 February 2009:
> > > Log Message:
> > > withdraw the "game coat"
> > >
> > > +
> > > +
> > > + false
> > > +
> > > +
On samedi 14 février 2009, Melchior FRANZ wrote:
> * Gerard Robin -- Saturday 14 February 2009:
> > Log Message:
> > withdraw the "game coat"
> >
> > +
> > +
> > + false
> > +
> > +
>
> AIRCRAFT MUST *NOT* CHANGE SYSTEM SETTING!
>
> This s
Curt,
Curtis Olson wrote:
> Wild fires are a newly added feature to CVS, the table is wide open for
> discussion if anyone cares to discuss the issue. Let's not bring our pet
> peaves into the discussion, that only obfuscates the real issues.
What you are trivializing by calling it our pet peev
* Curtis Olson -- Saturday 14 February 2009:
> No I think Melchior is justified (as occasionally can be the case) :-)
:-P
> We could simply default wild fires to off in the preferences.xml file and
> that is perhaps the thing to do.
Exactly, and as I've said before:
| Melchior FRANZ -- Saturd
On Sat, Feb 14, 2009 at 2:16 PM, Martin Spott wrote:
> Curtis Olson wrote:
>
> > No I agree, we shouldn't be mixing policy and capability up like this.
>
> Well, as long as the Flightgear development crowd fails at establishing
> procedures that, for example, allow to negotiate on 'moderate' syst
On Sat, Feb 14, 2009 at 2:12 PM, Martin Spott wrote:
> Melchior FRANZ wrote:
> > * Gerard Robin -- Saturday 14 February 2009:
> >> Log Message:
> >> withdraw the "game coat"
> >
> >> +
> >> +
> >> + false
> >> +
> >> +
> >
> >
> > AIRCRAF
Curtis Olson wrote:
> No I agree, we shouldn't be mixing policy and capability up like this.
Well, as long as the Flightgear development crowd fails at establishing
procedures that, for example, allow to negotiate on 'moderate' system
settings (or whatever is at stake), you can't expect people to
Melchior FRANZ wrote:
> * Gerard Robin -- Saturday 14 February 2009:
>> Log Message:
>> withdraw the "game coat"
>
>> +
>> +
>> + false
>> +
>> +
>
>
> AIRCRAFT MUST *NOT* CHANGE SYSTEM SETTING!
>
> This setting disqualifies the F8 for
No I agree, we shouldn't be mixing policy and capability up like this.
These things should be set at an application level according to individual
user preference, it always turns into a big mess when an aircraft author
tries to change global settings from within an aircraft. It also leads to
suppo
* Gerard Robin -- Saturday 14 February 2009:
> Log Message:
> withdraw the "game coat"
> +
> +
> + false
> +
> +
AIRCRAFT MUST *NOT* CHANGE SYSTEM SETTING!
This setting disqualifies the F8 for inclusion in a release.
Oh, well. Why do I
Martin Spott wrote:
> Tim Moore wrote:
>> Martin Spott wrote:
>>> Erik Hofman wrote:
Update of /var/cvs/FlightGear-0.9/data/Aircraft/Boeing314
In directory baron.flightgear.org:/tmp/cvs-serv11895
Modified Files:
Boeing314A.xml
Log Message:
Add the license
Maybe I'm being naive here , but wouldn't be easier to jusr remove the word
"Boeing" from the files ?
--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-s
On Wed, 21 Jan 2009 14:06:42 +0100, gerard wrote in message
<200901211406.42997.ghma...@gmail.com>:
> On mercredi 21 janvier 2009, Melchior FRANZ wrote:
> > * Erik Hofman -- Wednesday 21 January 2009:
> > [...]
> >
> > > Modified Files:
> > > Boeing314A.xml
> > > Log Message:
> > > Add the lice
Tim Moore wrote:
> Martin Spott wrote:
> > Erik Hofman wrote:
> >> Update of /var/cvs/FlightGear-0.9/data/Aircraft/Boeing314
> >> In directory baron.flightgear.org:/tmp/cvs-serv11895
> >>
> >> Modified Files:
> >> Boeing314A.xml
> >> Log Message:
> >> Add the license statement
> >>
> >> +
Martin Spott wrote:
> Erik Hofman wrote:
>> Update of /var/cvs/FlightGear-0.9/data/Aircraft/Boeing314
>> In directory baron.flightgear.org:/tmp/cvs-serv11895
>>
>> Modified Files:
>> Boeing314A.xml
>> Log Message:
>> Add the license statement
>>
>> + This simulation model is not
On mercredi 21 janvier 2009, Martin Spott wrote:
> Erik Hofman wrote:
> > Update of /var/cvs/FlightGear-0.9/data/Aircraft/Boeing314
> > In directory baron.flightgear.org:/tmp/cvs-serv11895
> >
> > Modified Files:
> > Boeing314A.xml
> > Log Message:
> > Add the license statement
> >
> > +
Erik Hofman wrote:
> Update of /var/cvs/FlightGear-0.9/data/Aircraft/Boeing314
> In directory baron.flightgear.org:/tmp/cvs-serv11895
>
> Modified Files:
> Boeing314A.xml
> Log Message:
> Add the license statement
>
> + This simulation model is not endorsed by the manufacturer.
http://www.gnu.org/licenses/gpl-faq.html#DoesTheGPLAllowMoney
"Does the GPL allow me to sell copies of the program for money?
Yes, the GPL allows everyone to do this. The right to sell copies
is part of the definition of free software. Except in one special
situation, there is no limit on what pr
On Wednesday, 21. January 2009, Martin Spott wrote:
> b) The GPL states that "You may charge a fee for the physical act of
> transferring a copy, [...]", but "You may not copy, modify, sublicense,
> or distribute the Program except as expressly provided under this
> License".
>
> Now, how would yo
* gerard robin -- Wednesday 21 January 2009:
> I was told by a layer, since we are writing that the model is copyrighted
> protected under Licence GPLV2 , we may write anything we want as addons
> regarding the protection, these addons won't be taken in account , and one
> may ignore it.
That
Melchior FRANZ wrote:
> * Erik Hofman -- Wednesday 21 January 2009:
> > +
> > + GPL (General Public License)
> > + http://www.gnu.org/licenses/gpl.html
> > +
> > +
> > + [...]This model
> > + is not to be sold.
> > +
>
Melchior FRANZ wrote:
> * Erik Hofman -- Wednesday 21 January 2009:
> [...]
>> Modified Files:
>> Boeing314A.xml
>> Log Message:
>> Add the license statement
>
>> +
>> + GPL (General Public License)
>> + http://www.gnu.org/licenses/gpl.html
>> +
>> +
On mercredi 21 janvier 2009, Melchior FRANZ wrote:
> * Erik Hofman -- Wednesday 21 January 2009:
> [...]
>
> > Modified Files:
> > Boeing314A.xml
> > Log Message:
> > Add the license statement
> >
> > +
> > + GPL (General Public License)
> > + http://www.gnu.org/lic
* Erik Hofman -- Wednesday 21 January 2009:
[...]
> Modified Files:
> Boeing314A.xml
> Log Message:
> Add the license statement
> +
> + GPL (General Public License)
> + http://www.gnu.org/licenses/gpl.html
> +
> +
> + [...]This mode
On Thu, 2009-01-08 at 18:39 +, Geoff Air wrote:
>
> Could someone with simgear CVS access please fix the coremag.cxx file.
> Each time I checkout (or update) this file has this in its head :-
>
> <<< coremag.cxx
> // $Id: coremag.cxx,v 1.5 2006-10-28 22:12:48 curt Exp $
> ===
> // $
On Thu, 8 Jan 2009, Geoff Air wrote:
> Could someone with simgear CVS access please fix the coremag.cxx
> file.Each time I checkout (or update) this file has this in its head :-
>
> <<< coremag.cxx// $Id: coremag.cxx,v 1.5 2006-10-28 22:12:48 curt
Exp $===// $Id: coremag.cxx,v 1.6 2008/0
Could someone with simgear CVS access please fix the coremag.cxx file.Each time
I checkout (or update) this file has this in its head :-
<<< coremag.cxx// $Id: coremag.cxx,v 1.5 2006-10-28 22:12:48 curt Exp
$===// $Id: coremag.cxx,v 1.6 2008/07/25 18:35:42 ehofman Exp $>>> 1.6
* Melchior Franz -- Sunday 21 December 2008:
> Modified Files:
> SGMaterialAnimation.cxx
> Log Message:
>
> Merge branch 'master' of ../.sg.osg
Whoops, sorry. I thought this problem with my git<=>cvs gateway
wouldn't happen any more. The correct log text is the following
(and it's also fix
Modified Files:
view.nas aircraft.nas geo.nas globals.nas
Log Message:
make constants D2R, R2D, M2FT, FT2M global
Is there anything modified within geo.nas ?
Is there any consequence when using it ?
Thanks
--
Gérard
http://pagesperso-orange.fr/GRTux/
J'ai décidé d'être heureux parce
On 23 Oct 2008, at 16:14, Alasdair Campbell wrote:
> Thanks to Csaba for helping out with the C++. This works a treat. I
> attach the complete patch for fixing the MK_VIII problems. Could some
> check and commit please?
Looks good to me, someone please apply.
James
---
1 - 100 of 282 matches
Mail list logo
