[Flightgear-devel] directional sound...
Hi guys, Just a note to say fantastic job on the directional/doppler sounds ! I'm never going to get any flying done now , I just keep buzzing the tower :) Cheers. -- syd sandy [EMAIL PROTECTED] - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Bug found
Hello all, a found a litlle bug in CVS (osg branch) in AIMode/AIBase.hxx there is #include plib/ssh.h of course it's not compiling but with plib/ssg.h it's working :-) regards, Didier. -- Didier Fabert [EMAIL PROTECTED] KFreeFlight project : A FlightGear GUI-Frontend designed for KDE users http://kfreeflight.sourceforge.net - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Bug found
* Didier Fabert -- Saturday 23 June 2007: a found a litlle bug in CVS (osg branch) in AIMode/AIBase.hxx there is #include plib/ssh.h This is not in CVS. Your copy is (once again) messed up. $ cd src/AIModel/ $ cvs up -AC AIBase.hxx $ cvs status AIBase.hxx === File: AIBase.hxxStatus: Up-to-date Working revision:1.64 Repository revision: 1.64 /var/cvs/FlightGear-0.9/FlightGear/src/AIModel/AIBase.hxx,v Commit Identifier: 7KbYjFyNCGDn20ls Sticky Tag: (none) Sticky Date: (none) Sticky Options: (none) $ grep plib AIBase.hxx $ m. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Experimental screen streamer patch
Hi, I've come up with a screen streamer for FG. The idea is to stream the screen directly to any video encoder or player, to make FG video-making easier. At the moment it streams via (a very basic) http. You run FG like: $ fgfs --screenstreamer=localhost,2 Then you can do things like (using ffmpeg and ffplay as examples): - watch FG screen directly: ffplay -f rawvideo -pix_fmt rgb24 -s 800x600 http://localhost:2/ ffplay -f mjpeg http://localhost:2/?format=mpjpeg; - encode FG screen into video on the fly: ffmpeg -r 20 -f rawvideo -pix_fmt rgb24 -s 800x600 -i http://localhost:2/?fps=20; -vcodec mpeg4 -an output.avi It also has very basic query string support, so you can tune things with a different URL like: http://localhost:2/?fps=20scale=2 which asks for stream fps 20 and scaled the frame down by a half. At the moment it can stream out raw rgb data or multipart jpeg. Raw rgb data is there mainly for local video encoding and it uses less cpu. While the multipart jpeg can be played directly in a video player or inside a webpage directly (which works with firefox and the likes). For more details please read the descriptions on top of the src/Network/screenstreamer.cxx file. The patch is at http://pigeond.net/~pigeon/fg.ss.patch Apply in FG source dir with patch -p1. It works with both plib and osg FG. Tested only on Linux for now. Comments and feedbacks are much welcomed. I'm particularly interested in how much the streaming degrades FG's performance. The first thing to watch out for is FG's window size. 800x600 seems to be a good choice to start with. And obviously the higher the streaming fps the slower it gets FG to. Also mpjpeg does jpeg compressions which will slow down FG's fps as well. Thanks. Pigeon. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [ANN] OSG - Improved Weather Radar
syd sandy wrote: Hi again, I checked the source code , recent update , and delete rt is already commented out , so I recompiled and tried my Aerostar 700, which I recently added a weather radar to , and no more error message when I exit FG , so that must have done the trick ... Cheers Hi Syd - when can I try it out :-) - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [ANN] OSG - Improved Weather Radar
Vivian, Vivian Meazza wrote: I will attend to thus once the patches are approved/agreed in principle. [...] filename=fg_wx_radar_osg.diff.tgz In Instrumentation/wxradar.hxx at line 26 this patch introduces a dependency on plib/ssg.h. I think this is neither required nor desired, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [ANN] OSG - Improved Weather Radar
Martin Sent: 23 June 2007 14:08 To: flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] [ANN] OSG - Improved Weather Radar Vivian, Vivian Meazza wrote: I will attend to thus once the patches are approved/agreed in principle. [...] filename=fg_wx_radar_osg.diff.tgz In Instrumentation/wxradar.hxx at line 26 this patch introduces a dependency on plib/ssg.h. I think this is neither required nor desired, If it's not required, then it's certainly not desirable. I'm sure that can be removed. Thanks Vivian - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] no doppler sound with actual build (osg branch), experimental patch included
Hi,
at the osg branch, the directional sound and doppler effects should work
since two days.
It seems that (at least) on windows there is a bug within OpenAL
calculating the Doppler effect.
Either there is no Doppler Effect (like I have) or it is totally wrong
(as aerotro has with the same executable than I have). Eventually it
affects the performance of flightgear.
The enclosed patch switches of the Doppler calculation of OpenAL and
adds a own Doppler calculation.
The patch is not designed for cvs (now). I first need the feedback, if
all windows builds or even other OS are affected.
With this patch Doppler effect should be ok at every OS. I hope, that
the performance issue is solved with that, too (or is independent from
the sound former sound patch).
Now that the Doppler effect works here I got aware of some bugs:
- the effect is wrong, if the aircraft changes its orientation (pitch
and heading)
- the sound is switched off for one frame if the fly-by view jumps to a
new eyepoint (and often some 3d models are loaded at this time this
frame can be noticeable long)
- the same happens, if you change the view
- if you move (rotate) the eye-point in an external view you hear
Doppler effects
I will try to make a patch for this within the next days.
Maik
Index: sound/sample_openal.cxx
===
RCS file: /var/cvs/SimGear-0.3/source/simgear/sound/sample_openal.cxx,v
retrieving revision 1.27
diff -u -p -r1.27 sample_openal.cxx
--- sound/sample_openal.cxx 21 Jun 2007 21:46:21 - 1.27
+++ sound/sample_openal.cxx 24 Jun 2007 00:06:53 -
@@ -75,6 +75,10 @@ SGSoundSample::SGSoundSample() :
reference_dist(500.0),
max_dist(3000.),
loop(AL_FALSE),
+#ifndef USE_OPEN_AL_DOPPLER
+doppler_pitch_factor(1),
+doppler_volume_factor(1),
+#endif
playing(false)
{
}
@@ -273,7 +277,7 @@ SGSoundSample::set_pitch( double p ) {
if ( p 2.0 ) { p = 2.0; }
pitch = p;
if (playing) {
-alSourcef( source, AL_PITCH, pitch );
+alSourcef( source, AL_PITCH, pitch * doppler_pitch_factor );
print_openal_error(set_pitch);
}
}
@@ -282,7 +286,7 @@ void
SGSoundSample::set_volume( double v ) {
volume = v;
if (playing) {
-alSourcef( source, AL_GAIN, volume );
+alSourcef( source, AL_GAIN, volume * doppler_volume_factor );
print_openal_error(set_volume);
}
}
@@ -354,9 +358,35 @@ SGSoundSample::set_source_vel( ALfloat *
source_vel[0] = vel[0];
source_vel[1] = vel[1];
source_vel[2] = vel[2];
+#ifdef USE_OPEN_AL_DOPPLER
if (playing) {
alSourcefv( source, AL_VELOCITY, source_vel );
}
+#else
+double doppler, msv, mfp;
+sgVec3 final_pos;
+sgAddVec3( final_pos, source_pos, offset_pos );
+msv = sgLengthVec3(source_vel);
+mfp = sgLengthVec3(final_pos);
+if (mfp 1e-6)
+doppler = (msv 339) ? (340 -
+sgScalarProductVec3( source_vel, final_pos ) / mfp) / (340 - msv)
+: 0;
+else
+doppler = 1;
+if (doppler 0.1) {
+doppler_pitch_factor = doppler;
+doppler_volume_factor = 1;
+}
+else {
+doppler_pitch_factor = 0.1;
+doppler_volume_factor = (doppler 0) ? doppler * 10 : 0;
+}
+if (playing) {
+alSourcef( source, AL_GAIN, volume * doppler_volume_factor );
+alSourcef( source, AL_PITCH, pitch * doppler_pitch_factor );
+}
+#endif
}
void
Index: sound/sample_openal.hxx
===
RCS file: /var/cvs/SimGear-0.3/source/simgear/sound/sample_openal.hxx,v
retrieving revision 1.17
diff -u -p -r1.17 sample_openal.hxx
--- sound/sample_openal.hxx 8 Mar 2006 18:16:09 - 1.17
+++ sound/sample_openal.hxx 24 Jun 2007 00:06:54 -
@@ -90,6 +90,10 @@ private:
double pitch;
double volume;
+#ifndef USE_OPEN_AL_DOPPLER
+double doppler_pitch_factor;
+double doppler_volume_factor;
+#endif
double reference_dist;
double max_dist;
ALboolean loop;
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] AWOS
On 06/22/2007 04:14 PM, Hans Fugal wrote:
This is a drop-in replacement for $FG_ROOT/ATC/default.atis
The file is at http://hans.fugal.net/tmp/default.atis
1) That is a big improvement. Thanks.
2) This is important, for the following reasons among others:
I fly a lot of general aviation at small airports without ATIS, and
where there is no controlled airport for miles around. There are two
frustrations I experience with flightgear in these situations:
1. The ATC/Frequencies box always says there's nothing within 40 nm.
But in many cases there *is* an airport with ATIS close enough to
receive ATIS (but not within 40 nm). Maybe this radius could be
expanded, at least when nothing else was found? My local area happens
to be a pathological case: KLRU is 40.7nm from KELP.
2. A lot of these airports, and almost always one within range no
matter how remote you get (in the US anyway), have ASOS or AWOS
(basically, almost everywhere you have a METAR you have either ATIS or
ASOS/AWOS). They're essentially the same as ATIS, at least in all the
ways that matter. FlightGear's database has these frequencies, but you
hear nothing when tuning to them.
The first point is a minor inconvenience, since a good pilot should be
gathering things like radio frequencies *before* flying. :-) The
second point makes it hard to get in-sim weather information (without
cheating by looking at the weather scenario METAR) out west.
Agreed.
On 01/03/2007 05:19 PM, Curtis Olson wrote:
I'm coming at this from the perspective of an instrument flying
lesson.
And that is a perspective we fully want to support and promote .
I'm hoping someone who has the authority to commit stuff to CVS will
in fact support and promote this.
Listening to ATIS is an important part of real-world flying that
is currently quite badly broken in the CVS version of FGFS.
=
1) The following comments are tangential and must *not* be
construed as being even slightly non-supportive of what Hans
has been doing. Remember the maxim:
Do not let the perfect be the enemy of the good.
the more festival-friendly names for airports that existed in the
old default.atis.
Can you say a few words about what festival-friendly means?
I've seen some examples that consist merely of spelling out
abbreviations such as Intl--International and Rgnl--Regional.
If that's all there is to it, a simple rule-based approach might
be preferable to hacking the databases. That is, I would suggest
leaving apt.dat alone and implementing some remapping rules in the
nasal code that generates the ATIS/AWOS text.
doing the right thing would be to parse apt.dat directly
Agreed!
The current file
Airports/apt_loader.cxx
contains the code:
else if ( line_id = 50 line_id = 56 ) {
// frequency entries (ignore)
so it would not be hard to improve on this. Half a day's work
at most.
On IRC it was suggested that hacking apt.dat would be ill-timed as we
are waiting for the 850 apt.dat format database to be released.
I don't see how any timing issues could stand in the way of doing
the right thing in apt_loader.cxx. The 8.50 format is documented
to be identical to the 8.10 format with respect to ATC frequencies
... so implementing a proper apt.dat parser commutes with transitioning
to the new format.
Also it commutes with whatever festival-friendly remapping needs
to be done.
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] C++ code beautifier / Coding
On 06/14/2007 01:18 AM, Reagan Thomas wrote: In a collaborative project, spaces *will* get mixed in whether any one person likes it or not. The two, together, cause ugliness. So why not fully embrace the wonderful and (almost) free 0x20? As quoted above, any *modern* source editor will be happy to auto-indent to your columnar preference using tabs or spaces... No doubt, in the FG source, there is quite an ugly mixture of spaces and tabs. That's the fact of the matter. In theory, it doesn't have to be that way, and I've seen plenty of collaborative projects where the issue of tabs never came up. IMHO that's because there is an important distinction: -- a /collaborative/ project, versus -- a multi-programmer project. any *modern* source editor will be happy to auto-indent to your columnar preference using tabs or spaces... Heretofore the true nature of the problem has not been fully discussed. As analyzed at e.g. http://www.jwz.org/doc/tabs-vs-spaces.html there are at least three separate issues involved. The issues are somewhat related, but they are certainly not the same thing. There are #1: display-appearance-intention issues, #2: file-encoding issues, and #3: keyboard issues. It hardly makes sense to expect the programmer to set the tab-stops correctly if he doesn't even know what is the nature of the problem he's trying to solve. On 06/13/2007 11:32 PM, Jon S. Berndt wrote: I won't use tabs, and remove them wherever I see them. Given the exiting mess, adopting a policy of no tabs in files seems like a step in the right direction, namely a way of dealing with point #2, i.e. the file-encoding issues. Getting rid of tabs in files is easier said than done. You have to know what was /intended/. Some programmers intend the tab-stops to be every 4 places, while some intend them to be every 8 places (and other options are possible). And in the case where one programmer has edited part of the file and another programmer has edited another part, it is possible to have a situation where each guy's part looks OK /to him/ but no mutually-consistent interpretation of the tabs is possible. Somebody with even a modest understanding of code should be able to do the job. For each region of the file, set tab-width to 4 and then set it to 8, and choose whichever looks better. Then untabify the region. *) This would be labor-intensive, but worth it in the long run. *) Doing it imperfectly would be better than not doing it at all. *) It doesn't need to be done all at once. *) Once the job is done, simple scripts will suffice to make sure the files /remain/ tab-free. It must be emphasized that even though point #1 (i.e. author's intention) governs point #2 (i.e. how untabification is to be done), the converse is absolutely not true. Even without tab characters in the file, the author can still make decisions as to how the code should look, and still has fully effective ways of implementing those decisions. Also let me recommend that untabification be done /separately/ from any edits that affect the function of the code. If you want to edit a file, and it needs to be untabified, do it in two steps, and submit two deltas. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ 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-06-17_16:01:43 (mfranz) /var/cvs/SimGear-0.3/source/simgear/scene/model/animation.cxx sooner than planned: fix scale animation offsets (1 - 0) =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-06-19_13:10:36 (mfranz) /var/cvs/SimGear-0.3/source/simgear/props/props.cxx beautify TRACE message =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-06-19_13:22:38 (mfranz) /var/cvs/SimGear-0.3/source/simgear/props/props.cxx d'oh ... beautify the TRACE message that we actually see! :-} =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-06-23_11:48:04 (mfranz) /var/cvs/SimGear-0.3/source/simgear/sound/xmlsound.cxx don't only complain that the volume is larger than 1.0, but say how much it actually is =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-06-23_16:55:18 (mfranz) /var/cvs/SimGear-0.3/source/simgear/environment/visual_enviro.cxx /var/cvs/SimGear-0.3/source/simgear/environment/visual_enviro.hxx Vivian MEAZZA: add aircraft signature support to weather radar 2f585eeea02e2c79d7b1d8c4963bae2d - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Weekly CVS Changelog Summary: FlightGear source
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-06-17_03:14:05 (mfranz)
/var/cvs/FlightGear-0.9/source/src/Main/fg_init.cxx
256 Bytes ought to be enough for anybody ... hmm, better 512.
Why /sim/fg-current at all? Because we have a file selector dialog
(still unfinished), and one might like to start it from the current
directory, to find saved flights/screenshots/whatever.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-06-19_05:10:03 (mfranz)
/var/cvs/FlightGear-0.9/source/src/Main/fg_commands.cxx
loadxml, savexml: don't pop up a GUI error message on error, but use a
simple SG_LOG instead. The user didn't call the fgcommand, so why should
s/he be bothered with that? And the actually caller of the command gets a
return value and can pop up a dialog if it thinks it's necessary.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-06-19_05:18:17 (mfranz)
/var/cvs/FlightGear-0.9/source/src/Main/main.cxx
fix bug that prevented /sim/sceneryloaded from ever becoming true if
/sim/screneryloaded-override was true. At least one subsystem (od_gauge)
waits for /sim/sceneryloaded to bypass CPU intensive code until the scenery
is up. This broke e.g. the RTT-radar when using /sim/screneryloaded-override
--prop:sim/sceneryloaded-override=true has the effect that fgfs
doesn't show the splash screen until the scenery is loaded, but shows
the OTW view (scenery/aircraft) at the earliest possible moment. This is
useful for developers who often need to run fgfs only to check some minor
detail, while not caring about stuttering caused by scenery loading.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-06-19_05:56:52 (mfranz)
/var/cvs/FlightGear-0.9/source/src/Main/fg_commands.cxx
... but use the exception text, of course. :-)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-06-22_13:12:06 (mfranz)
/var/cvs/FlightGear-0.9/source/src/ATC/ATCDialog.cxx
increase range of searched and displayed frequencies 40 - 50 nm
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-06-23_01:41:21 (mfranz)
/var/cvs/FlightGear-0.9/source/src/FDM/YASim/Rotorpart.cpp
Maik JUSTUS: ease the rotor of the hornet if not rotating
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-06-23_10:25:43 (mfranz)
/var/cvs/FlightGear-0.9/source/src/Scripting/NasalSys.cxx
add geodinfo(lat, lon) function that returns an array [elev, matdata]
or nil if no terrain intersection could be made (tile not loaded yet).
matdata is a hash with information about the surface material, or nil
if no material is assigned (shouldn't really happen, but one never knows).
Example:
var ac = geo.aircraft_position();
var data = geoddata(ac.lat(), ac.lon());
debug.dump(data);
# which outputs
[ 294.5862574369132, { light_coverage : 0, bumpiness : 0, load_resistance :
1e+30,
solid : 1, names : [ pc_taxiway, dirt_rwytaxiway ], friction_factor : 1,
rolling_friction : 0.02 } ]
With this information it can be determined how far an object would sink in,
if the coordinate is on a runway, etc.
foreach (var n; data[1].names)
if (string.match(n, p[ac]_*))
im_on_a_runway();
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-06-23_16:58:45 (mfranz)
/var/cvs/FlightGear-0.9/source/src/Instrumentation/od_gauge.cxx
comment out RenderTexture class destruction. This leads to crashes on
nvidia cards, and seems to be redundant. (Isn't done in the cloud code
and not even in Mark HARRIS' RenderTexture demonstration. Also, the
GL resources are supposed to be freed at the end of the GL application,
anyway.)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-06-23_17:02:41 (mfranz)
/var/cvs/FlightGear-0.9/source/src/AIModel/AIShip.cxx
/var/cvs/FlightGear-0.9/source/src/Instrumentation/wxradar.cxx
/var/cvs/FlightGear-0.9/source/src/Instrumentation/wxradar.hxx
Vivian MEAZZA: new improved c++ radar implementation
mf: I asked Vivian not to do any cleanup in existing code, so that his
changes would be easier to see. But the next patch will have to fix
some messy parts.
2f585eeea02e2c79d7b1d8c4963bae2d
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] C++ code beautifier / Coding
John Denker wrote: Given the exiting mess, adopting a policy of no tabs in files seems like a step in the right direction, namely a way of dealing with point #2, i.e. the file-encoding issues. I need to clarify that I do that in code that I am the main editor for. Fortunately, other developers for JSBSim have adopted the same approach. Unfortunately, I've used some tools that quietly insert tabs. They still sneak in. I also tend to use two spaces, because we have some fairly deep indentation at times. Also let me recommend that untabification be done /separately/ from any edits that affect the function of the code. If you want to edit a file, and it needs to be untabified, do it in two steps, and submit two deltas. An excellent idea. It's sometimes convenient to separate (when possible) edits based on intention, and that goes for more than just cosmetic edits. Jon - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ 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-06-17_17:09:31 (mfranz) /var/cvs/FlightGear-0.9/data/Aircraft/A-10/Models/pedals.rgb Alexis BORY: - improve pedals - fix scale animation =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-06-17_17:46:11 (mfranz) /var/cvs/FlightGear-0.9/data/Aircraft/vulcanb2/Models/vulcanb2.xml scale animation: set formerly implict offset of 1 now explicitly =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-06-18_05:23:34 (mfranz) /var/cvs/FlightGear-0.9/data/Aircraft/bocian/Nasal/winch.nas adapt for geo.nas changes (swapping lon lat) =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-06-18_06:41:56 (vmmeazza) /var/cvs/FlightGear-0.9/data/Aircraft/Spitfire/Models/puff-impact.ac /var/cvs/FlightGear-0.9/data/Aircraft/Spitfire/Models/puff-new.ac /var/cvs/FlightGear-0.9/data/Aircraft/Spitfire/Models/recoil.nas /var/cvs/FlightGear-0.9/data/Aircraft/Spitfire/Models/seafire-subsubmodels.xml /var/cvs/FlightGear-0.9/data/Aircraft/Spitfire/Models/smoke-impact.xml Add recoil, impacts, more scale animation fixes =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-06-18_11:39:46 (martin) /var/cvs/FlightGear-0.9/data/Protocol/Attic/fg_sqawk.xml /var/cvs/FlightGear-0.9/data/Protocol/fgcom.xml Holger Wirtz: Prepare for new FlightGear voice communication agent. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-06-18_12:35:25 (mfranz) /var/cvs/FlightGear-0.9/data/Aircraft/bocian/Nasal/winch.nas AJ MacLEOD: update to winch code =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-06-18_15:02:54 (mfranz) /var/cvs/FlightGear-0.9/data/Aircraft/A-6E/Models/divs-instr.rgb /var/cvs/FlightGear-0.9/data/Aircraft/A-6E/Models/ldg-controls.ac Alexis BORY: update (includes scale animation fix) =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-06-18_15:02:55 (mfranz) /var/cvs/FlightGear-0.9/data/Aircraft/A-6E/Models/ldg-controls.rgb /var/cvs/FlightGear-0.9/data/Aircraft/A-6E/Models/p-console-center-fwd.xml Alexis BORY: update (includes scale animation fix) =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-06-19_14:04:51 (curt) /var/cvs/FlightGear-0.9/data/Aircraft/Noratlas/Engines/Rotol-AERO.xml Gerard Robin: Here is an updated Noratlas: The full package here: http://perso.orange.fr/GRTux/Noratlas.tar.gz The diff file package here: http://perso.orange.fr/GRTux/Noratlas-2007-06-19.diff.tar.gz =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-06-19_14:18:23 (curt) /var/cvs/FlightGear-0.9/data/Aircraft/SR71-BlackBird/splash3-BB.rgb /var/cvs/FlightGear-0.9/data/Aircraft/SR71-BlackBird/Instruments/ALT-8-bb.xml /var/cvs/FlightGear-0.9/data/Aircraft/SR71-BlackBird/Instruments/Bezel-ttpt-bb.xml /var/cvs/FlightGear-0.9/data/Aircraft/SR71-BlackBird/Instruments/Bipolaire-f8e.xml /var/cvs/FlightGear-0.9/data/Aircraft/SR71-BlackBird/Instruments/Cde-Switch-bb.xml /var/cvs/FlightGear-0.9/data/Aircraft/SR71-BlackBird/Instruments/FUPMP-bb.xml Gerard Robin: Here is an update of SR71-BlackBird. The full Package is here: http://perso.orange.fr/GRTux/SR71-BlackBird.tar.gz And the diff package is here: http://perso.orange.fr/GRTux/SR71-BlackBird-2007-06-19.diff.tar.gz Some new snapshots: http://perso.orange.fr/GRTux/BlackBird-pic11.jpg http://perso.orange.fr/GRTux/BlackBird-pic13.jpg http://perso.orange.fr/GRTux/BlackBird-pic14.jpg =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-06-19_14:18:24 (curt) /var/cvs/FlightGear-0.9/data/Aircraft/SR71-BlackBird/Instruments/PRBCDE-bb.xml /var/cvs/FlightGear-0.9/data/Aircraft/SR71-BlackBird/Instruments/Temoin-2Base.xml /var/cvs/FlightGear-0.9/data/Aircraft/SR71-BlackBird/Instruments/Temoin-BasePt.xml /var/cvs/FlightGear-0.9/data/Aircraft/SR71-BlackBird/Instruments/Temoin-FuelLowEng.xml /var/cvs/FlightGear-0.9/data/Aircraft/SR71-BlackBird/Instruments/Temoin-PrbPump.xml /var/cvs/FlightGear-0.9/data/Aircraft/SR71-BlackBird/Instruments/Temoin-PrbSpdbk.xml /var/cvs/FlightGear-0.9/data/Aircraft/SR71-BlackBird/Instruments/Temoin-Refuel.xml /var/cvs/FlightGear-0.9/data/Aircraft/SR71-BlackBird/Instruments/Temoin-train.xml /var/cvs/FlightGear-0.9/data/Aircraft/SR71-BlackBird/Instruments/Models/Temoin-2Base.ac /var/cvs/FlightGear-0.9/data/Aircraft/SR71-BlackBird/Instruments/Models/Temoin-BasePt.ac /var/cvs/FlightGear-0.9/data/Aircraft/SR71-BlackBird/Instruments/Models/Temoin-FuelLowEng.ac /var/cvs/FlightGear-0.9/data/Aircraft/SR71-BlackBird/Instruments/Models/Temoin-Gears.ac /var/cvs/FlightGear-0.9/data/Aircraft/SR71-BlackBird/Instruments/Models/Temoin-PrbSpdbk.ac /var/cvs/FlightGear-0.9/data/Aircraft/SR71-BlackBird/Instruments/Models/Temoin-Refuel.ac /var/cvs/FlightGear-0.9/data/Aircraft/SR71-BlackBird/Instruments/Models/bezel-ttpt-bb.ac /var/cvs/FlightGear-0.9/data/Aircraft/SR71-BlackBird/Instruments/Models/bipolaire-f8e.ac
