Re: [Flightgear-devel] FlightGear prerelease
* Tiago Gusmão -- Friday 23 November 2007: gerard robin wrote: if we ask for Menu/Sound Configuration/Mute Sound and behind we make pause (key p) we get again the sound Wrote a quick patch for #2, seems to work fine here, doesn't preserve mute through a reset though. That's OK. It's not supposed to. It's my first patch so make sure i'm not introducing new bugs and stuff. Thanks, committed. (I only changed fgGetNode()-getBoolValue() to fgGetBool()). And I fabricated another broken cvslogs message, sorry. But *now* it should really be fixed, and the message is fixed in cvs, of course. I've also turned on a lot of debug messages, so that I can better see what's going wrong, if there's still a problem. (I couldn't yet reproduce that on my local test repository.) m. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Nasal var
I just wanted to reaffirm that Melchior's message about use of var in
nasal code is a very important one ... important enough to top post and
re-quote the whole thing below :-) and encourage everyone to read it again!
If anyone out there is doing aircraft design or involved in doing any nasal
scripting at all, they really need to read through this message and
understand it. If it's not clear to you, print it out and read it later
with a fresh head. (It's well written, but technical, so you need to read
it with patience and care.) If something is still not clear, please ask
questions!
On Nov 23, 2007 7:15 AM, Melchior FRANZ [EMAIL PROTECTED] wrote:
Most people seem to think that var in Nasal is a kind of
redundant decoration, and really just noise. It isn't.
In fact, I consider Nasal code *not* using it broken.
var makes a variable guaranteed to be local. And note that
functions assigned to variables are no exception! If you write
code without using var on variables, then you risk (often
hard to debug) breakage at a later time. Consider this code
in one of your scripts:
output = func(v) {# missing var
state = getprop(/sim/foo/state);# missing var
do_something(state, v);
}
where neither output nor state have been declared to
be a local variable using var in this file. Everything will
work fine. For a while. Until someone creates a file
$FG_ROOT/Nasal/state.nas or $FG_ROOT/Nasal/output.nas.
Then your output and state will no longer create
a safe variable, but they'll overwrite the global namespaces
that these files meant to create. You can try this with these
examples:
props = func {# missing var
print(I'm props. And I just wiped the whole props namespace.);
}
Or with this:
foo = func { # missing var
props = :-P ; # missing var
}
...
foo();
After this code was run, all props methods will stop working,
as the props namespace containing all the important stuff was
replaced by cheesy, thought to be local stuff.
Note, again, that variables set to hold a function object are
no exception. They should use the var keyword as well:
var foo = func {}
But there's another reason why var should be used consequently,
even if a variable is safe enough from later side effects, because
it's called bo105_livery or something. The var keyword makes
reading code for others (and for the author after some time) easier,
as it makes clear: this variable starts its life *HERE*. No need
to search around to see whether assigning a value to it means
something to other code outside or not. Also, with an editor
offering proper syntax highlighting reading such code is actually
easier, despite the noise.
But why then does some code still not use var, even code written
by Andy? Because the keyword didn't exist from the beginning. It was
added after I had run into weird error messages when starting with
the bo105. It took me a while to find out that a variable state
had nasty and unexpected side effects on the $FG_ROOT/Nasal/state.nas
script. And now you know why this script is now known as ac_state.nas.
m.
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
--
Curtis Olson: http://baron.flightgear.org/~curt/
Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
On Nov 22, 2007 5:04 PM, Tatsuhiro Nishioka [EMAIL PROTECTED] wrote: Durk, Thanks for building the official pre2 source packages. I tried your pre2 sources on my MacBook Pro and I successfully built it with no problem. so there's no urgent patches for Mac OS X port. What about the square sun problem? I'm still seeing that in CVS fgfs-plib from a month ago. I'm also still seeing the stubborn weather problem - where no matter what I set weather scenario to, changing wind or clouds does not stick. These bugs may have been fixed in the meantime. I'm downloading the prerelease to build and see for sure. -- Hans Fugal Fugal Computing - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
OS X Leopard (10.5) on a Macbook, gcc 4.0.1, a patched plib 1.8.4.
Simgear 0.3.11-pre2 needs the following patch in order to build:
Index: SimGear-0.3.11-pre2/simgear/screen/RenderTexture.cpp
===
--- SimGear-0.3.11-pre2.orig/simgear/screen/RenderTexture.cpp 2007-11-17
00:35:45.0 -0700
+++ SimGear-0.3.11-pre2/simgear/screen/RenderTexture.cpp2007-11-24
10:26:50.0 -0700
@@ -514,7 +514,7 @@
}
if (error =
- CGLChoosePixelFormat(pixFormatAttribs[0], pixFormat,
iNumFormats))
+ CGLChoosePixelFormat(pixFormatAttribs[0], pixFormat,
(GLint*)iNumFormats))
{
fprintf(stderr,
RenderTexture Error: CGLChoosePixelFormat() failed.\n);
@@ -556,7 +556,7 @@
}
long screen;
- if (error = CGLGetVirtualScreen(CGLGetCurrentContext(), screen))
+ if (error = CGLGetVirtualScreen(CGLGetCurrentContext(),
(GLint*)screen))
{
_cglCheckError(error);
return false;
Please apply.
--
Hans Fugal
Fugal Computing
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] set file naming
Hello all, While I'm in the process of updating nasal and other files , is there a naming style we should stick to in the set files for cold and idle startup modes ? I have a b1900d-set and a b1900d-quickstart-set , which is too long , IMHO. Im looking for something consistent , that we can all agree on ... Cheers -- SydSandy [EMAIL PROTECTED] - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] set file naming
* SydSandy -- Saturday 24 November 2007: is there a naming style we should stick to in the set files for cold and idle startup modes ? I have a b1900d-set and a b1900d-quickstart-set , which is too long I'm opposed to separate *-set.xml files for that at all, just like I'm against separate *-set.xml files for each livery. This just makes any aircraft list like $ fgfs --show-aircraft, or the selection in fgrun, or bash shell completion a pain to use. We have already more than enough set files if we have just one per aircraft. IMHO, we should have a standardized property or a command line option for that, and additionally a menu entry to select it. m. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] set file naming
On sam 24 novembre 2007, SydSandy wrote: Hello all, While I'm in the process of updating nasal and other files , is there a naming style we should stick to in the set files for cold and idle startup modes ? I have a b1900d-set and a b1900d-quickstart-set , which is too long , IMHO. Im looking for something consistent , that we can all agree on ... Cheers Didn't you give the answer yourself ? :) b1990d-set.xml= cold start b1900d-idle-set.xml = idle start or b1900d-cold-set.xml = cold start b1900d-set.xml = idle start or b1900d-cold-set.xml = cold start b1900d-idle-set.xml = idle start Regards -- Gérard http://pagesperso-orange.fr/GRTux/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] set file naming
On Saturday 24 November 2007 19:09:03 Melchior FRANZ wrote: IMHO, we should have a standardized property or a command line option for that, and additionally a menu entry to select it. As just mentioned on IRC, I fully agree - it's got to the stage now where fgfs --show-aircraft is pretty much useless without piping it through a grep command. That's great, because it means we have an astonishing array of aircraft, but unnecessary -set files are to be avoided at all costs. I also dislike having to type --aircraft=ThisType-YASim etc when in fact there is no other version anyway, but that's another taste matter :-) I would happily create a (frequently requested) magic start function for the Lightning if a suitable standardised menu entry existed for it. Cheers, AJ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] set file naming
On Sat, 24 Nov 2007 20:12:58 +0100 gerard robin [EMAIL PROTECTED] wrote: On sam 24 novembre 2007, SydSandy wrote: Hello all, While I'm in the process of updating nasal and other files , is there a naming style we should stick to in the set files for cold and idle startup modes ? I have a b1900d-set and a b1900d-quickstart-set , which is too long , IMHO. Im looking for something consistent , that we can all agree on ... Cheers Didn't you give the answer yourself ? :) b1990d-set.xml= cold start b1900d-idle-set.xml = idle start or b1900d-cold-set.xml = cold start b1900d-set.xml = idle start or b1900d-cold-set.xml = cold start b1900d-idle-set.xml = idle start Regards -- Gérard http://pagesperso-orange.fr/GRTux/ Well yes , but I wanted to get a solution acceptable to everyone , so I dont have change everything again a few months down the road. But it's beginning to appear that a single set file (cold start), with a menu option to cheat , might be the way to go . Maybe a startup option that will flick on the switches , etc , while you wait ? Cheers -- SydSandy [EMAIL PROTECTED] - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] set file naming
* Melchior FRANZ -- Saturday 24 November 2007: [...] or bash shell completion [...] If you don't know that one: http://members.aon.at/mfranz/flightgear/fgfs.bash [5.6 kB] Just run it once from a bash shell (and again every time after you added a new aircraft), and source it from ~/.bashrc with [ -e $FG_HOME/fgfs.bash ] source /path/to/fgfs.bash completion This allows to use TAB completion to complete fgfs options, aircraft, carrier names, season names, time-of-day options, etc. $ fgfs --aircTAB=haTAB --disTABreTAB completes to $ fgfs --aircraft=harrier --disable-real-weather-fetch m. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] startup menu option
Ok ,continuing with this line of thought , will anyone object if I insert Aircraft back into the main menu ? (for aircraft specific options ). -- SydSandy [EMAIL PROTECTED] - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] startup menu option
* SydSandy -- Saturday 24 November 2007: Ok ,continuing with this line of thought , will anyone object if I insert Aircraft back into the main menu ? (for aircraft specific options ). Let's first discuss what that should be. I wouldn't be happy to release 0.9.11 with an Aircraft menu with a single entry, which is supported by a single aircraft, which isn't even shipped with the release. m. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] startup menu option
On Sat, 24 Nov 2007 20:55:59 +0100 Melchior FRANZ [EMAIL PROTECTED] wrote: * SydSandy -- Saturday 24 November 2007: Ok ,continuing with this line of thought , will anyone object if I insert Aircraft back into the main menu ? (for aircraft specific options ). Let's first discuss what that should be. I wouldn't be happy to release 0.9.11 with an Aircraft menu with a single entry, which is supported by a single aircraft, which isn't even shipped with the release. m. OK so in your opinion ,what would be better , a popup when FG starts , for aircraft that have the option for a cold start ? -- SydSandy [EMAIL PROTECTED] - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] startup menu option
Just to make this clear: I'm not against an Aircraft menu,
if it isn't empty and/or non-functional in 99.% of the
fgfs runs. But exactly that will happen if we rush it in now.
I suggest to wait with that until after the release, which,
as everyone knows, will happen around Xmas (we just don't
know yet, in which year. :-)
* SydSandy -- Saturday 24 November 2007:
OK so in your opinion ,what would be better , a popup when
FG starts , for aircraft that have the option for a cold start ?
Obligatory clicking on startup dialogs is a pain, and I don't
think we want that. I'd say we make an option like
--startup-mode={parked,idle}(or something)
This could default to idle, and everyone who doesn't like to
get his hornet dropped on the biggest runway, with a 747 in
the neck, can set it to parked in his/her ~/.fgfsrc.
And, additionally, one could change the startup option in the
menu. But for that it would IMHO be better to put it into a
custom menu entry for now, like some aircraft do already. And
after the release do it right and make as many aircraft as
possible respect it.
m.
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] startup menu option
* Melchior FRANZ -- Saturday 24 November 2007:
Obligatory clicking on startup dialogs is a pain, and I don't
think we want that. I'd say we make an option like
--startup-mode={parked,idle}(or something)
BTW: there are a lot of optional startup locations defined in
apt.dat:
$ zgrep ^15 fgfs/Base/Airports/apt.dat.gz|wc -l
5873
The problem is, that they have an ugly format:
15 lat lon hdg name
where name seems to be totally free and without rules.
Some examples are Custom Startup Location, Startup,
Anchor, Ramp, Gate A 1, East Mil cargo Ramp 65,
249.660 (huh?), Plataforma 1 (oh, plataforma ...),
etc.
There should be a type number before the name. Sigh.
m.
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] startup menu option
SydSandy a écrit : On Sat, 24 Nov 2007 20:55:59 +0100 Melchior FRANZ [EMAIL PROTECTED] wrote: * SydSandy -- Saturday 24 November 2007: Ok ,continuing with this line of thought , will anyone object if I insert Aircraft back into the main menu ? (for aircraft specific options ). Let's first discuss what that should be. I wouldn't be happy to release 0.9.11 with an Aircraft menu with a single entry, which is supported by a single aircraft, which isn't even shipped with the release. m. OK so in your opinion ,what would be better , a popup when FG starts , for aircraft that have the option for a cold start ? I would think for the short term: - Default to cold start. - Short explanation, in the HelpAircraft help menu, telling how to quick-start the aircraft in one key stroke (ie Ctrl-s or any free composed key at this time). This key would trigger the following script. - A nasal script wich sets all the needed props as fast as possible so the aircraft has his engines on, all doors closed, and panel light on if needed. Don't touch others controls like flaps, or mixture or anything wich could be set as desired. Alexis - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] startup menu option
On Sat, 24 Nov 2007 21:21:23 +0100
Melchior FRANZ [EMAIL PROTECTED] wrote:
Just to make this clear: I'm not against an Aircraft menu,
if it isn't empty and/or non-functional in 99.% of the
fgfs runs. But exactly that will happen if we rush it in now.
I suggest to wait with that until after the release, which,
as everyone knows, will happen around Xmas (we just don't
know yet, in which year. :-)
* SydSandy -- Saturday 24 November 2007:
OK so in your opinion ,what would be better , a popup when
FG starts , for aircraft that have the option for a cold start ?
Obligatory clicking on startup dialogs is a pain, and I don't
think we want that. I'd say we make an option like
--startup-mode={parked,idle}(or something)
This could default to idle, and everyone who doesn't like to
get his hornet dropped on the biggest runway, with a 747 in
the neck, can set it to parked in his/her ~/.fgfsrc.
And, additionally, one could change the startup option in the
menu. But for that it would IMHO be better to put it into a
custom menu entry for now, like some aircraft do already. And
after the release do it right and make as many aircraft as
possible respect it.
m.
OK the startup option sound like a good idea ... Im just in the process of
trying to clean up and remove all those set files .FGRUN works here for viewing
aircraft , just not selecting airports . I know the reason , just dont want to
recompile :) .But anyway , going through the aircraft list show 3-4 identical
aircraft . Those would be mine :). AJ point me to 2 aircraft that use an
aircraft created options menu so I will do that for the time being ...
But I also like the idea of a special menu entry to hold aircaft options ... in
the future
Cheers
--
SydSandy [EMAIL PROTECTED]
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
I verified that these two do still exist. Allow me to elaborate, though they have been reported before. On OSX, for some unknown reason the sun is displayed as a square (or diamond, if you like) instead of as a circle. Unknown to me, anyway; I think the MacFlightGear folks have a patch. Here's a screenshot: http://hans.fugal.net/tmp/fg/square-sun.png The weather bug is in two pieces, actually. First, when you go into the Weather Scenario dialog, None is always selected, regardless of what weather is actually being used. If one is using real weather fetch as I am, it should say METAR. When real weather fetch is enabled, no matter what Weather Scenario (thunderstorm, none, fair) or what conditions or clouds I set manually, it instantly reverts to real weather. I think these two bugs should be fixed before release. I think the square sun is an easy fix (hopefully the MacFlightGear people can chime in here). If fixing the weather bug isn't feasible, then we should at least disable those dialogs when real weather fetch is enabled. On Nov 24, 2007 10:19 AM, Hans Fugal [EMAIL PROTECTED] wrote: On Nov 22, 2007 5:04 PM, Tatsuhiro Nishioka [EMAIL PROTECTED] wrote: Durk, Thanks for building the official pre2 source packages. I tried your pre2 sources on my MacBook Pro and I successfully built it with no problem. so there's no urgent patches for Mac OS X port. What about the square sun problem? I'm still seeing that in CVS fgfs-plib from a month ago. I'm also still seeing the stubborn weather problem - where no matter what I set weather scenario to, changing wind or clouds does not stick. These bugs may have been fixed in the meantime. I'm downloading the prerelease to build and see for sure. -- Hans Fugal Fugal Computing -- Hans Fugal Fugal Computing - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] startup menu option
Hi All, I like the way the cvs c150 starts. It has a pop up menu, Hot or Cold start. The apt.dat file supports named start up locations associated with an airport. As an example the latest apt.dat file has one location defined for KSFO named CAL RAMP AREA. FlightGear could make use of start up locations from the in the apt.dat file. Best Regards, Paul B. SydSandy [EMAIL PROTECTED] wrote: On Sat, 24 Nov 2007 20:55:59 +0100 Melchior FRANZ wrote: * SydSandy -- Saturday 24 November 2007: Ok ,continuing with this line of thought , will anyone object if I insert Aircraft back into the main menu ? (for aircraft specific options ). Let's first discuss what that should be. I wouldn't be happy to release 0.9.11 with an Aircraft menu with a single entry, which is supported by a single aircraft, which isn't even shipped with the release. m. OK so in your opinion ,what would be better , a popup when FG starts , for aircraft that have the option for a cold start ? -- SydSandy - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel - Never miss a thing. Make Yahoo your homepage.- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] EMERGENCY
Hi all , Ive had a little emergency here , Ive accidentally wiped-out the ch47 after attempting to remove some extra files today ... I tried checking out yesterdays version , but no luck... Could someone send me a copy of the ch47 folder before updating , so I can attempt to restore it ? Thanks a bunch ... Time to try something other than Cervisia... Cheers -- SydSandy [EMAIL PROTECTED] - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] EMERGENCY
On Sat, 24 Nov 2007 15:44:09 -0800 SydSandy [EMAIL PROTECTED] wrote: Hi all , Ive had a little emergency here , Ive accidentally wiped-out the ch47 after attempting to remove some extra files today ... I tried checking out yesterdays version , but no luck... Could someone send me a copy of the ch47 folder before updating , so I can attempt to restore it ? Thanks a bunch ... Time to try something other than Cervisia... Cheers -- SydSandy [EMAIL PROTECTED] Whew I got it back -- SydSandy [EMAIL PROTECTED] - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Weekly CVS Changelog Summary: SimGear
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-11-18_08:22:08 (durk) /var/cvs/SimGear-0.3/source/README.OpenAL /var/cvs/SimGear-0.3/source/README.plib Minor documentation update. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-11-18_17:30:34 (timoore) /var/cvs/SimGear-0.3/source/simgear/scene/tgdb/SGTexturedTriangleBin.hxx Some scene graph optimizations When loading terrain, use DrawElementsUShort where possible. Don't chunk unconnected triangles in the terrain into seperate Geometry sets; make the sets as big as possible. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-11-22_12:15:54 (durk) /var/cvs/SimGear-0.3/source/Makefile.am /var/cvs/SimGear-0.3/source/SimGear.dsp /var/cvs/SimGear-0.3/source/configure.ac A few prerelease related changes: - new version number - modified path for make dist post processing - new autogenerated dsp file 2f585eeea02e2c79d7b1d8c4963bae2d - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Weekly CVS Changelog Summary: FlightGear data
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-11-18_06:20:17 (mfranz)
/var/cvs/FlightGear-0.9/data/Nasal/prop-key-handler.nas
/var/cvs/FlightGear-0.9/data/gui/dialogs/devel-extensions.xml
- add Debug-Development Extensions dialog with two checkboxes to
- allow turning on/off extra widgets for developers (HUD dialog: colors,
rendering dialog: visualization of shadow edges), and to turn on/off new
- property key handler ('/'-key)
Both features are off by default, and their state is saved to autosave.xml.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-11-18_06:46:40 (dfaber)
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/spit9-yasim.xml
Supermarine Spitfire MK IX, initial release.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-11-18_06:46:41 (dfaber)
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/spit9.nas
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/spitfireIX-set.xml
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/ASI.rgb
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/DI.rgb
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/altimeter.ac
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/altimeter.rgb
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/altimeter.xml
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/ammeter.ac
Supermarine Spitfire MK IX, initial release.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-11-18_06:46:42 (dfaber)
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/ammeter.rgb
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/ammeter.xml
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/asi.ac
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/asi.xml
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/asi480kts.rgb
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/attitude.ac
Supermarine Spitfire MK IX, initial release.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-11-18_06:46:43 (dfaber)
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/attitude.rgb
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/attitude.xml
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/attitude_background.rgb
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/brake_supply.rgb
Supermarine Spitfire MK IX, initial release.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-11-18_06:46:44 (dfaber)
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/compass.ac
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/compass.xml
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/early_turn_and_slip.rgb
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/fuel-pressure.ac
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/fuel-pressure.xml
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/fuel.ac
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/fuel.rgb
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/fuel.xml
Supermarine Spitfire MK IX, initial release.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-11-18_06:46:45 (dfaber)
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/fuel_pressure_body.rgb
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/mag_switch.rgb
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/magcompass.rgb
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/magneto.ac
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/oil-pressure.ac
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/oil-pressure.xml
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/oil-temp.ac
Supermarine Spitfire MK IX, initial release.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-11-18_06:46:46 (dfaber)
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/oil-temp.xml
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/oil_pressure.rgb
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/oil_temp.rgb
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/oil_temp_black.rgb
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/rad-temp.ac
Supermarine Spitfire MK IX, initial release.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-11-18_06:46:47 (dfaber)
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/rad-temp.xml
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/rad_temp_black.rgb
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/rpm-5k.rgb
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/rpm.ac
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/rpm.xml
/var/cvs/FlightGear-0.9/data/Aircraft/spitfireIX/Instruments/slot_screw_med_flat.rgb
[Flightgear-devel] Weekly CVS Changelog Summary: FlightGear source
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-11-18_02:07:31 (durk) /var/cvs/FlightGear-0.9/source/src/Traffic/TrafficMgr.cxx Backport from CVS HEAD. Make traffic directory scanning work. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-11-18_02:53:43 (durk) /var/cvs/FlightGear-0.9/source/src/Traffic/TrafficMgr.cxx Remove remaining debugging statements which were apparently not saved by the MSVC editor. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-11-18_08:23:16 (durk) /var/cvs/FlightGear-0.9/source/README.OpenAL /var/cvs/FlightGear-0.9/source/README.plib Minor documentation update. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-11-22_13:21:23 (durk) /var/cvs/FlightGear-0.9/source/FlightGear.dsp Prerelease related changes: - New version number - Make sure fgadmin related Makefiles are generated - New dsp file - More selective inclusion of AI aircraft =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-11-22_13:21:24 (durk) /var/cvs/FlightGear-0.9/source/Makefile.am /var/cvs/FlightGear-0.9/source/configure.ac Prerelease related changes: - New version number - Make sure fgadmin related Makefiles are generated - New dsp file - More selective inclusion of AI aircraft =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-11-24_02:37:46 (mfranz) /var/cvs/FlightGear-0.9/source/src/Main/fg_props.cxx Tiago GUSMAO: keep sound muted after pause/unpause 2f585eeea02e2c79d7b1d8c4963bae2d - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
