[Flightgear-devel] Menu update for Time Settings
Hi All, To be consistent with the new Time Settings dialog, the menu item should be "Time Settings" instead of "Time of Day". Path included below. Could someone please apply? Thanks -Stuart Index: menubar.xml === RCS file: /var/cvs/FlightGear-0.9/data/gui/menubar.xml,v retrieving revision 1.68 diff -u -r1.68 menubar.xml --- menubar.xml 4 Dec 2007 10:51:45 - 1.68 +++ menubar.xml 5 Dec 2007 07:53:27 - @@ -305,7 +305,7 @@ - Time of Day + Time Settings dialog-show timeofday ___ Yahoo! Answers - Got a question? Someone out there knows the answer. Try it now. http://uk.answers.yahoo.com/ - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [Fwd: Re: [Flightgear-users] Seneca II - couple of user comments]
> > For the upcoming release, should we select a scaling factor for the > adverse-aileron yaw in the c172p and SenecaII that result in the > performance more similar to the pa28-161 and pa24-250 respectively? For the SenecaII: Yes. I will work on that issue - hopefully today. Torsten - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
--- Stuart Buchanan wrote: > Finally, for those of us who have been developing exclusively on OSG for > windows, > it would be very useful to have a set of binaries available so we can test our > aircraft on plib before the data tarball is created, and the 175 aircraft are > uploaded to the website. And, indeed a very kind person has done so: ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32 Thanks! -Stuart ___ Yahoo! Answers - Got a question? Someone out there knows the answer. Try it now. http://uk.answers.yahoo.com/ - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] landing gear control
Ok I have another one Can we add a /controls/gear/gear-lever-lock to prevent accidental raising gear while on the ground , on aircraft that have this feature ? The key bindings can be over ridden , but there's also joystick configurations to consider , so the best place to add this would be the controls.nas routine itself... It could simply be added as a bool in the set file of any aircraft that needs it ... Cheers -- Syd&Sandy <[EMAIL PROTECTED]> - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] control trim reset
On Tue, 4 Dec 2007 22:56:04 -0600 "Curtis Olson" <[EMAIL PROTECTED]> wrote: > On Dec 4, 2007 10:26 PM, Syd&Sandy <[EMAIL PROTECTED]> wrote: > > > Hi all , > > I've added the elevator, aileron and rudder trim to the control-centering > > function - keypad ( 5 ). > > Should this be added before the release ? Or is there a particular reason > > that the trims aren't reset ? > > It,ll just take a minute to commit if everyone agrees ... > > > Most of the time reseting trims is not desirable. Pressing the 5 key is > sort of almost, but maybe not quite like letting go of the controls, or > maybe moving the controls to their neutral/zero pressure state. > > Regards, > > Curt. > -- > Curtis Olson: http://baron.flightgear.org/~curt/ > Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d > OK. I've always thought it was meant to just recenter everything , if joystick wasn't centered at startup , ... and Ive developed the habit of hitting the 5 key before releasing the brakes , just in case :) . The autopilot can really mess this up , so I suppose I could just disable that while WoW ... Cheers -- Syd&Sandy <[EMAIL PROTECTED]> - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] control trim reset
On Dec 4, 2007 10:26 PM, Syd&Sandy <[EMAIL PROTECTED]> wrote: > Hi all , > I've added the elevator, aileron and rudder trim to the control-centering > function - keypad ( 5 ). > Should this be added before the release ? Or is there a particular reason > that the trims aren't reset ? > It,ll just take a minute to commit if everyone agrees ... Most of the time reseting trims is not desirable. Pressing the 5 key is sort of almost, but maybe not quite like letting go of the controls, or maybe moving the controls to their neutral/zero pressure state. Regards, Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/ Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] control trim reset
Hi all , I've added the elevator, aileron and rudder trim to the control-centering function - keypad ( 5 ). Should this be added before the release ? Or is there a particular reason that the trims aren't reset ? It,ll just take a minute to commit if everyone agrees ... Cheers -- Syd&Sandy <[EMAIL PROTECTED]> - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
On Tue, 4 Dec 2007 18:59:11 -0600 Robert Black <[EMAIL PROTECTED]> wrote: > > > Hi, > > The Bravo's Primus 1000 system is a bit of a mess right now ... I'd feel > > better if it wasn't included with the release . Thanks > > How about the B1900 ? Any issues. It is know as having one of the best > panels. It would fill the commercial twin prop slot. > yes I dont have any immediate plans for that one :). As far as Carrier capable aircraft , I think the A-6E is another really well done candidate... -- Syd&Sandy <[EMAIL PROTECTED]> - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
I'd like to see the 737 stay. Also, I believe recent enhancements and fixes in JSBSim may have fixed the F-16, but I'm not sure. Jon - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
I agree with the pa24-250 or other complex single, whether it replaces pa24 (which I also like but I agree c172p should stay in) or another. On Dec 4, 2007 3:15 PM, Stuart Buchanan <[EMAIL PROTECTED]> wrote: > > --- Durk Talsma wrote: > > Another question: we always have a limited number of aircraft that are > > in the > > distribution, with the rest being available as separate downloads. We > > like to > > keep the number of aircraft constant, and representative of the many > > types of > > aircraft supported by FlightGear. Is there any pressing reason to swap > > one > > aircraft for another one? IIRC, there have been some suggestions of > > replacing > > the 737 by the 787. FWIW, we currently have the following selection of > > aircraft (Taken from Makefile.am): > > > > > data/Aircraft/UIUC \ > > Ditch this - I don't think we have any UIUC aircraft in common use (though > the Wright Flyer might be) > > > data/Aircraft/c172 \ > > data/Aircraft/c172p \ > > c172p should be included as it is mentioned extensively in the docs and > has basic tutorials. > > > data/Aircraft/c310 \ > > data/Aircraft/c310u3a \ > > Much as I like the c310 - it's now very primitive compared with recent > aircraft. Replace with the Seneca II. > > > > > data/Aircraft/j3cub \ > > Include as a nice easy taildragger. > > > data/Aircraft/Hunter \ > > data/Aircraft/p51d \ > > > data/Aircraft/pa28-161 \ > > I'd suggest replacing this with a complex single, say the pa24-250. Then > we have a nice progression from training to complex twin. > > > data/Aircraft/Rascal \ > > Does anyone actually use this? > > > data/Aircraft/T38 \ > > I'm sure that there are better jets, but I'm not familiar with them in > enough detail to suggest a replacement. > > > data/Aircraft/ufo \ > > data/Aircraft/wrightFlyer1903 \ > > As Melchior says - ditch as no-one uses it. > > I'd also suggest that we include a carrier-capable jet as well - seahawk? > > -Stuart > > > ___ > Support the World Aids Awareness campaign this month with Yahoo! For Good > http://uk.promotions.yahoo.com/forgood/ > > > - > SF.Net email is sponsored by: The Future of Linux Business White Paper > from Novell. From the desktop to the data center, Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > -- Hans Fugal Fugal Computing - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
> Hi, > The Bravo's Primus 1000 system is a bit of a mess right now ... I'd feel > better if it wasn't included with the release . Thanks How about the B1900 ? Any issues. It is know as having one of the best panels. It would fill the commercial twin prop slot. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
On mar 4 décembre 2007, Melchior FRANZ wrote:
> * Durk Talsma -- Tuesday 04 December 2007:
> > data/Aircraft/737-300 \
>
> Yes, I'd swap that with the 787. A flat panel that disappears
> when you look left/right is hard to bear. (Though I miss a VOR
> display on the 787. Need to search for that ...)
>
> > data/Aircraft/A-10 \
>
> Good choice. Very detailed, very good quality.
>
> > data/Aircraft/bf109 \
>
> Hmm ... it's well done and all, but I think it's "too realistic",
> read: too hard to take off/land due to the very narrow gear. The
> A6M2 would IMHO be a better choice (or the fw190, but I think that's
> not finished yet).
>
> > data/Aircraft/bo105 \
>
> Good choice, of course. Approved by a real bo105 pilot ("very
> impressed"). :-)
>
> > data/Aircraft/c172 \
> > data/Aircraft/c172p \
>
> use pa24 instead? But I see the pa28 further down, so ...
>
> > data/Aircraft/c310 \
> > data/Aircraft/c310u3a \
>
> use Seneca instead?
>
> > data/Aircraft/f16 \
>
> Totally broken! Don't ship this! The FCS winds up after a few
> minutes and kills you. Very frustrating. After starting fgfs,
> let is parked for a few minutes, then try to fly it. Good luck!
> (Though the HUD is nice. :-)
>
> > data/Aircraft/wrightFlyer1903 \
>
> Waste of disk space. Everyone tries it once or twice, and never
> again, because it's just *boring*.
>
> m.
>
>
I getting surprised,
What about the concorde isn't it one of the most representative ?
--
Gérard
http://pagesperso-orange.fr/GRTux/
<< Less i work, better i go >>
-
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
On Tue, 4 Dec 2007 21:57:00 +0100 Durk Talsma <[EMAIL PROTECTED]> wrote: > On Thursday 22 November 2007 07:36, Durk Talsma wrote: > > This is a quick note to everybody: I'm planning to build an "official" > > FlightGear pre-release tonight. I did a full dress rehearsal last sunday > > and that all seemed to work well, but I still needed Curt's okay for a few > > remaining issues. In the mean time, if there are any *urgent* patches > > remaining please try to get them into CVS ASAP. > > > > FWIW, FlightGear/PLIB is probably in a releasable state as it is, but given > > the time since the last release, there may be riding a lot of expectancy on > > this release, so I'd like to be a little more careful and to at least one > > more pre-release -and should any problems arise- a second one. > > > > To follow up on this: It seems like the initial testing round went pretty > well, with mostly minor problems being reported, and many of them being fixed > already. I'm hoping to roll up the tar files for the release itself this > weekend. I'm not sure whether we'll be able to transfer those to the main > webserver instantly, as there were some problems recently. If not, I hope > that John Wojnaroski can again provide some server space. In the mean time, > I guess we need to make a final decision on the version number... > > Another question: we always have a limited number of aircraft that are in the > distribution, with the rest being available as separate downloads. We like to > keep the number of aircraft constant, and representative of the many types of > aircraft supported by FlightGear. Is there any pressing reason to swap one > aircraft for another one? IIRC, there have been some suggestions of replacing > the 737 by the 787. FWIW, we currently have the following selection of > aircraft (Taken from Makefile.am): > > data/Aircraft/Generic \ > data/Aircraft/Instruments \ > data/Aircraft/Instruments-3d \ > data/Aircraft/UIUC \ > data/Aircraft/737-300 \ > data/Aircraft/A-10 \ > data/Aircraft/bf109 \ > data/Aircraft/bo105 \ > data/Aircraft/c172 \ > data/Aircraft/c172p \ > data/Aircraft/c310 \ > data/Aircraft/c310u3a \ > data/Aircraft/Citation-Bravo \ > data/Aircraft/f16 \ > data/Aircraft/j3cub \ > data/Aircraft/Hunter \ > data/Aircraft/p51d \ > data/Aircraft/pa28-161 \ > data/Aircraft/Rascal \ > data/Aircraft/T38 \ > data/Aircraft/ufo \ > data/Aircraft/wrightFlyer1903 \ > > > Cheers, > Durk > > - > SF.Net email is sponsored by: The Future of Linux Business White Paper > from Novell. From the desktop to the data center, Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel Hi, The Bravo's Primus 1000 system is a bit of a mess right now ... I'd feel better if it wasn't included with the release . Thanks -- Syd&Sandy <[EMAIL PROTECTED]> - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] [PATCH] wxradar bug fix and added feature
Hi!
First patch fixes a bug caused by the uninitialized _range_nm member.
If it happens to contain nan, this will never get overwritten.
Second patch adds support for filtering what should be displayed.
Comments welcome.
--
Csaba/Jester
Index: src/Instrumentation/wxradar.cxx
===
RCS file: /var/cvs/FlightGear-0.9/source/src/Instrumentation/wxradar.cxx,v
retrieving revision 1.20
diff -u -r1.20 wxradar.cxx
--- src/Instrumentation/wxradar.cxx 4 Oct 2007 20:40:29 - 1.20
+++ src/Instrumentation/wxradar.cxx 4 Dec 2007 23:01:24 -
@@ -84,7 +84,8 @@
_sim_init_done ( false ),
_resultTexture( 0 ),
_wxEcho( 0 ),
-_odg( 0 )
+_odg( 0 ),
+_range_nm( 40.0 )
{
const char *tacan_source = node->getStringValue("tacan-source",
"/instrumentation/tacan");
Index: src/Instrumentation/wxradar.cxx
===
RCS file: /var/cvs/FlightGear-0.9/source/src/Instrumentation/wxradar.cxx,v
retrieving revision 1.20
diff -u -r1.20 wxradar.cxx
--- src/Instrumentation/wxradar.cxx 4 Oct 2007 20:40:29 - 1.20
+++ src/Instrumentation/wxradar.cxx 4 Dec 2007 23:01:24 -
@@ -172,6 +172,9 @@
_radar_rotate_node = n->getNode("rotate", true);
_radar_font_node= _Instrument->getNode("font", true);
_radar_font_node->addChangeListener(this);
+_radar_mask_node= n->getNode("mask", true);
+if (!_radar_mask_node->hasValue())
+_radar_mask_node->setIntValue((1 << FGAIBase::MAX_OBJECTS) - 1);
updateFont();
@@ -615,10 +618,14 @@
double selected_radius = 0;
double selected_bearing = 0;
int selected_id = fgGetInt("/instrumentation/radar/selected-id", -1);
+int type_mask = ~_radar_mask_node->getIntValue();
for (; it != end; ++it) {
FGAIBase *ac = *it;
+
int type = ac->getType();
+if ((1 << type) & type_mask) continue;
+
double lat = ac->_getLatitude();
double lon = ac->_getLongitude();
double alt = ac->_getAltitude();
Index: src/Instrumentation/wxradar.hxx
===
RCS file: /var/cvs/FlightGear-0.9/source/src/Instrumentation/wxradar.hxx,v
retrieving revision 1.15
diff -u -r1.15 wxradar.hxx
--- src/Instrumentation/wxradar.hxx 9 Sep 2007 23:22:14 - 1.15
+++ src/Instrumentation/wxradar.hxx 4 Dec 2007 23:01:24 -
@@ -106,6 +106,7 @@
SGPropertyNode_ptr _radar_hdg_marker_node;
SGPropertyNode_ptr _radar_rotate_node;
SGPropertyNode_ptr _radar_font_node;
+SGPropertyNode_ptr _radar_mask_node;
SGPropertyNode_ptr _ai_enabled_node;
-
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] rain view
On Tue, 04 Dec 2007 19:43:38 +0100, Markus wrote in message <[EMAIL PROTECTED]>: > Csaba Halász wrote: > > On Dec 4, 2007 12:38 PM, Markus Zojer <[EMAIL PROTECTED]> wrote: > > > >> I have created some sample rain/snow usable with flightgear osg, > >> > > > > May I request a screenshot please? Thanks. > > > > > Sure :-) > > http://homepage.univie.ac.at/markus.zojer/fgfs/rain.png ..errr, we're gonna take off uphill? ;o) > http://homepage.univie.ac.at/markus.zojer/fgfs/snow.png ..snow looks more like your rain.png, only whiter and coming "right at your face" "from slightly above your destination." ..driving at night exaggerate this because your head lamps will light up the falling snow and mask the road. Landing in snow storms at night, we probably want this effect anyway. ..David M, have you flown in snowy weather yet? -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
Hi, Durk Talsma schrieb am 04.12.2007 21:57: > FWIW, we currently have the following selection of > aircraft (Taken from Makefile.am): > > data/Aircraft/Generic \ > data/Aircraft/Instruments \ > data/Aircraft/Instruments-3d \ > data/Aircraft/UIUC \ > data/Aircraft/737-300 \ > data/Aircraft/A-10 \ > data/Aircraft/bf109 \ > data/Aircraft/bo105 \ > data/Aircraft/c172 \ > data/Aircraft/c172p \ > data/Aircraft/c310 \ > data/Aircraft/c310u3a \ > data/Aircraft/Citation-Bravo \ > data/Aircraft/f16 \ > data/Aircraft/j3cub \ > data/Aircraft/Hunter \ > data/Aircraft/p51d \ > data/Aircraft/pa28-161 \ > data/Aircraft/Rascal \ > data/Aircraft/T38 \ > data/Aircraft/ufo \ > data/Aircraft/wrightFlyer1903 \ > > > Cheers, > Durk > I would like to see a glider with aero-towing-capability (bocian) in the release. Although the J3 has towing capability I would like to see the beaver in the release, too, because due to its higher mass it is much easier with tho aircraft. (I am not voting against the J3, it is a nice taildragger with minimal disk-usage.) Maik - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] patch to use OpenSceneGraph database pager
Tim Moore > > Sent: 04 December 2007 23:01 > To: FlightGear developers discussions > Subject: [Flightgear-devel] patch to use OpenSceneGraph database pager > > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hello, > http://www.bricoworks.com/moore/0001-OSG-pager-megapatch.patch > is a patch against current flightgear that uses the OSG > database pager to load scenery tiles instead of the old tile > loader. The main advantage of the database pager is that it > schedules texture loading and display list compilation in a > way that doesn't hammer the frame rate. Currently we don't do > anything at all about compiling OpenGL resources, so you can > get terrible stutter the first time you look at parts of a > scene. With this patch, that's gone. Also, old tiles are > deleted in the database pager thread, eliminating another > potential cause of stutter. > > This will be checked into CVS soon, but I've been hesitating > for three reasons: > > * It breaks the GLUT version; > > * Some bugs turned up with multiplayer play. I think I've > fixed these, but some more testing would be good; > > * Without patches to OSG that have been submitted to > osg-submissions, startup time is noticeably longer. > > Nevertheless, the patch is quite usable with OSG 2.2. Give it > a try if you're feeling adventurous. > I've been running with this patch for a while now with OSG 2.2. The load time isn't too excessive. It provides enhanced smoothness, but the stutters around KSFO are still apparent here. Overall, the advantages outweigh the small disadvantge of increased laoding time. I certianly won't be reverting the patch, and look forward to it being in cvs, and osg taking the changes aboard. Vivian - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
Stuart wrote: > > Sent: 04 December 2007 22:16 > To: FlightGear developers discussions > Subject: Re: [Flightgear-devel] FlightGear prerelease > > > > --- Durk Talsma wrote: > > Another question: we always have a limited number of > aircraft that are > > in the distribution, with the rest being available as separate > > downloads. We like to > > keep the number of aircraft constant, and representative of the many > > types of > > aircraft supported by FlightGear. Is there any pressing > reason to swap > > one > > aircraft for another one? IIRC, there have been some suggestions of > > replacing > > the 737 by the 787. FWIW, we currently have the following > selection of > > aircraft (Taken from Makefile.am): > > > > > data/Aircraft/UIUC \ > > Ditch this - I don't think we have any UIUC aircraft in > common use (though the Wright Flyer might be) > > > data/Aircraft/c172 \ > > data/Aircraft/c172p \ > > c172p should be included as it is mentioned extensively in > the docs and has basic tutorials. > > > data/Aircraft/c310 \ > > data/Aircraft/c310u3a \ > > Much as I like the c310 - it's now very primitive compared > with recent aircraft. Replace with the Seneca II. > > > > > data/Aircraft/j3cub \ > > Include as a nice easy taildragger. > > > data/Aircraft/Hunter \ > > data/Aircraft/p51d \ > > > data/Aircraft/pa28-161 \ > > I'd suggest replacing this with a complex single, say the > pa24-250. Then we have a nice progression from training to > complex twin. > > > data/Aircraft/Rascal \ > > Does anyone actually use this? > > > data/Aircraft/T38 \ > > I'm sure that there are better jets, but I'm not familiar > with them in enough detail to suggest a replacement. > > > data/Aircraft/ufo \ > > data/Aircraft/wrightFlyer1903 \ > > As Melchior says - ditch as no-one uses it. > > I'd also suggest that we include a carrier-capable jet as > well - seahawk? > The Seahawk is the most complete carrier-capable ac that we have, so if we want to include that capability that the one to have. On the Other hand the Hunter is probably the easiest ac to fly that we have in the inventory. I'd like to see the Lightning included - it is very complete, it has a nice tutorial, and demonstrates the aar capability. Vivian - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] real UFO
Melchior FRANZ wrote: >> Perhaps the improvements I made, regarding VTOL or vertical hovering, could >> be integrated into your ufo? >> > It's not really "my" UFO, although I kind-of maintain it ATM. You should > be aware that the UFO is primarily a means to explore the scenery, to take > screenshots, for scenery object placement etc. An UFO cockpit and fancy > "realistic" flight behavior might not be compatible with this purpose. > We'd have to take a look at this first. In the end it might be desirable > to have two *-set.xml files: one boring development version, and one "real" > UFO. > Hi, With my model sufficiently far into development, I'd finally like to ask; What are the requirements for an acceptable "real UFO"? Link to bluebird: http://www.geocities.com/sandreas41/flightgear_aircraft.html Stewart - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] patch to use OpenSceneGraph database pager
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, http://www.bricoworks.com/moore/0001-OSG-pager-megapatch.patch is a patch against current flightgear that uses the OSG database pager to load scenery tiles instead of the old tile loader. The main advantage of the database pager is that it schedules texture loading and display list compilation in a way that doesn't hammer the frame rate. Currently we don't do anything at all about compiling OpenGL resources, so you can get terrible stutter the first time you look at parts of a scene. With this patch, that's gone. Also, old tiles are deleted in the database pager thread, eliminating another potential cause of stutter. This will be checked into CVS soon, but I've been hesitating for three reasons: * It breaks the GLUT version; * Some bugs turned up with multiplayer play. I think I've fixed these, but some more testing would be good; * Without patches to OSG that have been submitted to osg-submissions, startup time is noticeably longer. Nevertheless, the patch is quite usable with OSG 2.2. Give it a try if you're feeling adventurous. Tim -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHVdw3eDhWHdXrDRURAgvLAKDSjQRESPTwSLXItzJW3Cd2vxcUJACcC3wu jdm4lHdup+D4sjmOLlH3XWM= =Nrzz -END PGP SIGNATURE- - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Custom protocol issues
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Well my need is this: I got an advanced joystick (X52 Pro) that got some "programmable" features. For example: * Setting colors of LEDs on buttons (red, yellow or green for most). (19 LEDs in total!) * Setting text on the display on the throttle. (3 rows x 16 chars) * Setting brightness of the backlit display and of the LEDs. * Setting the built in date and time (including 2 alternative "offset timezones" from main time, I would use UTC as main time, and local where you fly as the second time) I wrote a daemon that uses libusb to do this and parse the commands as udp packages, now I need nasal to send the commands as needed. For example: * If gear is down, show green on that button, yellow if it gear is moving up/down and red if it is up. * Same for flaps and speedbrakes and other buttons. * Show stuff like current speed, heading and such on the display. The data shown on the display would be change depending on what mode the joystick is in (a 3-state mode selector on the top of joystick), what button below the MFD you clicked, and so on. Doing this with the current custom protocol support turned out as a bad idea that either caused stutter or didn't provide enough properties. Sending from nasal would be the SANE way to solve this for me. Regards, Arvid Norlander K. Hoercher wrote: > On Sat, 01 Dec 2007 20:46:33 +0100 > AnMaster <[EMAIL PROTECTED]> wrote: >> I'm working on a custom protocol (generic protocol via xml file) for talking >> with a daemon, however I do have some issues: >> >> * How do I make fg send some properties less often than others? >> * How do I make fg only send a property when it changes? >> * How can I send custom strings to the daemon from nasal? >> >> I use udp for the protocol and I really need these features. > > > Hi, > > just to throw out a few more thoughts on that. I stumbled upon roughly > the same set of needs a couple of months ago. I was hacking on some > external fmc sort of thing, which needed to get the basic flight > parameters (such as position, orientation, speeds, eventually engine > settings, you get the picture). The generic protocol lended itself > quite readily to such task. > > Problems arose when I wanted to send the needed information for a > tcas/radar-like display, which would need (preferrably configurable) > the pertinent data for all mp/ai aircraft (or perhaps even carriers or > other objects). I did a even more hackish workaround using nasal, > writing to a local file, but clearly missed a feature to do some basic > networking with nasal too. > > For preliminary inspection on how to possibly improve the protocol/io > stuff I also looked at the opengc protocol. There I found some changes > needed to get it into working order, and how easy it would be with some > small changes to not rely on that hard-coded module. > > Around that time I got distracted by the internal ATC/radar stuff (and > real life too). But up to that time I thought a rewrite of the Protocol > code along the following lines desireable: > > - generic enough to substitute the "easier" ones (opengc, nmea, > lfsglass, atlas, perhaps others too..) with fitting xmlconfigs > > - a possibility in the defining xml to specify a "class" of nodes from > the property tree to be trasmitted > (e.g. /ai/models/aircraft*/callsign). Perhaps even recursive? > > - make the actual sending conditional/changeable at runtime (sounds > like getting to nasal style of doing things) > > - eventually incorporating some changes suggested here a couple of > weeks ago regarding binary input > > While I think the needed changes are to massive to do before the > release, I might give it a try afterwards and would like to solicit > some opinions or comments as to avoid marching off into a completely > unwanted direction. (and I'm constantly fearing the ever creative nasal > gurus coming up with a "Oh sure, look here, we've done a couple of > functions, it can now also do this and control your refrigerator as a > bonus" *g*) > > regards > K. Hoercher -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHVdkMWmK6ng/aMNkRCsMkAKCjGhCrtWgAdglU/iuXyJqip9Nq0gCfdvZm 31+Uc7dqDvlfTIUGiUhNhf4= =2qrW -END PGP SIGNATURE- - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
On Tuesday 04 December 2007 23:27, Melchior FRANZ wrote: > $ du -sh bo105 V22-Osprey A-10 787 an2 > 3.2Mbo105 (actually smaller; I have some devel files there) > 8.8MV22-Osprey > 20M A-10 > 20M 787 > 47M an2<-- whoops > Oh, yes that's a bit on the heavy side... D. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Stuart Buchanan wrote: > --- Durk Talsma wrote: >> Another question: we always have a limited number of aircraft that are >> in the >> distribution, with the rest being available as separate downloads. We >> like to >> keep the number of aircraft constant, and representative of the many >> types of >> aircraft supported by FlightGear. Is there any pressing reason to swap >> one >> aircraft for another one? IIRC, there have been some suggestions of >> replacing >> the 737 by the 787. FWIW, we currently have the following selection of >> aircraft (Taken from Makefile.am): >> > >> data/Aircraft/UIUC \ > > Ditch this - I don't think we have any UIUC aircraft in common use (though > the Wright Flyer might be) Well one of the splash screens picture an UIUC aircraft iirc. >> data/Aircraft/j3cub \ > > Include as a nice easy taildragger. I agree > >> data/Aircraft/Rascal \ > > Does anyone actually use this? Good question. > >> data/Aircraft/T38 \ > > I'm sure that there are better jets, but I'm not familiar with them in > enough detail to suggest a replacement. I would suggest Lightning. It is very detailed aircraft and nice looking. It is also (in my opinion) easier to fly than T38, both with mouse and with joystick. > As Melchior says - ditch as no-one uses it. > > I'd also suggest that we include a carrier-capable jet as well - seahawk? I agree. Regards, Arvid Norlander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHVdUSWmK6ng/aMNkRCrX6AJ0fNTFPSrDvBV4qMPG3veoIp1L2vQCfaHHg FKA0l3OgYeAfwJnQId8KmSU= =41sy -END PGP SIGNATURE- - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
--- Durk Talsma wrote: > To follow up on this: It seems like the initial testing round went pretty > well, with mostly minor problems being reported, and many of them being fixed > already. I'm hoping to roll up the tar files for the release itself this > weekend. Is this just the final tarballs for the binary, or are you rolling up the data tarballs as well? I'd _really_ like to include a fix for the MP repeated chat, as it is unusable in it's current state and I have some enhancements as well, so a timescale for the data code-freeze would be good. I also need to coordinate with Martin Spott generating The Manual for inclusion in the release. To generate The Manual, I need a version number. To get a version number we need a decison! I think all the opinions are in, so I think Curt now needs to collate them and tell us what the result is. Of course, the opinions have been so varied that he can pretty much decide what he wants and convince us that the majority agree with him :) Finally, for those of us who have been developing exclusively on OSG for windows, it would be very useful to have a set of binaries available so we can test our aircraft on plib before the data tarball is created, and the 175 aircraft are uploaded to the website. -Stuart __ Sent from Yahoo! - the World's favourite mail http://uk.mail.yahoo.com - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
* Durk Talsma -- Tuesday 04 December 2007: > What about swapping this with the "Legendary Russian AN2"? > I discovered that aircraft at FSWeekend, and got instantly > hooked. It seems fairly complete to me and it would be a nice > aircraft for the "historical" aircraft section. Yes, but ... $ du -sh bo105 V22-Osprey A-10 787 an2 3.2Mbo105 (actually smaller; I have some devel files there) 8.8MV22-Osprey 20M A-10 20M 787 47M an2<-- whoops m. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
On Tuesday 04 December 2007 22:46, Melchior FRANZ wrote: > > > data/Aircraft/wrightFlyer1903 \ > > Waste of disk space. Everyone tries it once or twice, and never > again, because it's just *boring*. > In general I agree with your suggestions. What about swapping this with the "Legendary Russian AN2"? I discovered that aircraft at FSWeekend, and got instantly hooked. It seems fairly complete to me and it would be a nice aircraft for the "historical" aircraft section. Cheers, Durk - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Alouette III
Hello, To follow the previous topic about some helicopters which are in my "private" hangar , Alouette III, Lynx, and Puma, Alouette III is now available on cvs, That model will need: a "good" FDM, the Maik know how will be very useful :) a cockpit witht instruments and animations , i must do it. probably others missing details The next one will be the Lynx, according to my available free time, it should be available by the end of the next week. Regards -- Gérard http://pagesperso-orange.fr/GRTux/ << Less i work, better i go >> - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Custom protocol issues
On Sat, 01 Dec 2007 20:46:33 +0100 AnMaster <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > I'm working on a custom protocol (generic protocol via xml file) for talking > with a daemon, however I do have some issues: > > * How do I make fg send some properties less often than others? > * How do I make fg only send a property when it changes? > * How can I send custom strings to the daemon from nasal? > > I use udp for the protocol and I really need these features. Hi, just to throw out a few more thoughts on that. I stumbled upon roughly the same set of needs a couple of months ago. I was hacking on some external fmc sort of thing, which needed to get the basic flight parameters (such as position, orientation, speeds, eventually engine settings, you get the picture). The generic protocol lended itself quite readily to such task. Problems arose when I wanted to send the needed information for a tcas/radar-like display, which would need (preferrably configurable) the pertinent data for all mp/ai aircraft (or perhaps even carriers or other objects). I did a even more hackish workaround using nasal, writing to a local file, but clearly missed a feature to do some basic networking with nasal too. For preliminary inspection on how to possibly improve the protocol/io stuff I also looked at the opengc protocol. There I found some changes needed to get it into working order, and how easy it would be with some small changes to not rely on that hard-coded module. Around that time I got distracted by the internal ATC/radar stuff (and real life too). But up to that time I thought a rewrite of the Protocol code along the following lines desireable: - generic enough to substitute the "easier" ones (opengc, nmea, lfsglass, atlas, perhaps others too..) with fitting xmlconfigs - a possibility in the defining xml to specify a "class" of nodes from the property tree to be trasmitted (e.g. /ai/models/aircraft*/callsign). Perhaps even recursive? - make the actual sending conditional/changeable at runtime (sounds like getting to nasal style of doing things) - eventually incorporating some changes suggested here a couple of weeks ago regarding binary input While I think the needed changes are to massive to do before the release, I might give it a try afterwards and would like to solicit some opinions or comments as to avoid marching off into a completely unwanted direction. (and I'm constantly fearing the ever creative nasal gurus coming up with a "Oh sure, look here, we've done a couple of functions, it can now also do this and control your refrigerator as a bonus" *g*) regards K. Hoercher - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
* dave perry -- Tuesday 04 December 2007: > 2. Removes the redundant "sense" from FGPropellers.cpp. > Jon, you indicated #2 should be done. how hard is porting #1 from > JSBSim cvs? That's already committed. > 2. de Havilland Beaver - Floats (shows the on-water progress this > release and a great bush AC) Oh, yes, indeed, I support that. m. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
--- Durk Talsma wrote: > Another question: we always have a limited number of aircraft that are > in the > distribution, with the rest being available as separate downloads. We > like to > keep the number of aircraft constant, and representative of the many > types of > aircraft supported by FlightGear. Is there any pressing reason to swap > one > aircraft for another one? IIRC, there have been some suggestions of > replacing > the 737 by the 787. FWIW, we currently have the following selection of > aircraft (Taken from Makefile.am): > > data/Aircraft/UIUC \ Ditch this - I don't think we have any UIUC aircraft in common use (though the Wright Flyer might be) > data/Aircraft/c172 \ > data/Aircraft/c172p \ c172p should be included as it is mentioned extensively in the docs and has basic tutorials. > data/Aircraft/c310 \ > data/Aircraft/c310u3a \ Much as I like the c310 - it's now very primitive compared with recent aircraft. Replace with the Seneca II. > data/Aircraft/j3cub \ Include as a nice easy taildragger. > data/Aircraft/Hunter \ > data/Aircraft/p51d \ > data/Aircraft/pa28-161 \ I'd suggest replacing this with a complex single, say the pa24-250. Then we have a nice progression from training to complex twin. > data/Aircraft/Rascal \ Does anyone actually use this? > data/Aircraft/T38 \ I'm sure that there are better jets, but I'm not familiar with them in enough detail to suggest a replacement. > data/Aircraft/ufo \ > data/Aircraft/wrightFlyer1903 \ As Melchior says - ditch as no-one uses it. I'd also suggest that we include a carrier-capable jet as well - seahawk? -Stuart ___ Support the World Aids Awareness campaign this month with Yahoo! For Good http://uk.promotions.yahoo.com/forgood/ - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
Durk Talsma wrote: > On Thursday 22 November 2007 07:36, Durk Talsma wrote: > >> This is a quick note to everybody: I'm planning to build an "official" >> FlightGear pre-release tonight. I did a full dress rehearsal last sunday >> and that all seemed to work well, but I still needed Curt's okay for a few >> remaining issues. In the mean time, if there are any *urgent* patches >> remaining please try to get them into CVS ASAP. >> >> >> I hope Jon Berndt will submit patches to the fgfs JSBSim code that 1. Turns off JSBSim modeling of turbulence that plays havoc with the default c172p, and 2. Removes the redundant "sense" from FGPropellers.cpp. Jon, you indicated #2 should be done. how hard is porting #1 from JSBSim cvs? > > > Another question: we always have a limited number of aircraft that are in the > distribution, with the rest being available as separate downloads. We like to > keep the number of aircraft constant, and representative of the many types of > aircraft supported by FlightGear. Is there any pressing reason to swap one > aircraft for another one? IIRC, there have been some suggestions of replacing > the 737 by the 787. FWIW, we currently have the following selection of > aircraft (Taken from Makefile.am): > > data/Aircraft/Generic \ > data/Aircraft/Instruments \ > data/Aircraft/Instruments-3d \ > data/Aircraft/UIUC \ > data/Aircraft/737-300 \ > data/Aircraft/A-10 \ > data/Aircraft/bf109 \ > data/Aircraft/bo105 \ > data/Aircraft/c172 \ > data/Aircraft/c172p \ > IMHO we should not include the two c310 and replace them with 1. SenecaII (great twin with lots of documentation) 2. de Havilland Beaver - Floats (shows the on-water progress this release and a great bush AC) This exchange leaves a modern light twin and adds the on-water and bush categories to fgfs. > data/Aircraft/c310 \ > data/Aircraft/c310u3a \ > data/Aircraft/Citation-Bravo \ > data/Aircraft/f16 \ > data/Aircraft/j3cub \ > data/Aircraft/Hunter \ > data/Aircraft/p51d \ > data/Aircraft/pa28-161 \ > data/Aircraft/Rascal \ > data/Aircraft/T38 \ > data/Aircraft/ufo \ > data/Aircraft/wrightFlyer1903 \ > > > Cheers, > Durk > > -Dave Perry - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
* Melchior FRANZ -- Tuesday 04 December 2007: > > data/Aircraft/c172 \ > > data/Aircraft/c172p \ > > use pa24 instead? I take that back. It has tutorials, and is often used as an example in the manual, with screenshots, etc. A second helicopter would be nice, but most have severe rendering problems, as they were done for fg/osg and not adapted for fg/plib. The V22-Osprey would probably be a good idea (instead of the Wright Flyer). It works with fg/plib, has a very nice folding animation and sounds, and is a very known and remarkable aircraft. There's no carrier capable aircraft (other than the bo105 and the j3cub ;-), so we might want to swap the hunter for the seahawk. m. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
--- Durk Talsma <[EMAIL PROTECTED]> schrieb: > On Thursday 22 November 2007 07:36, Durk Talsma > wrote: > > This is a quick note to everybody: I'm planning to > build an "official" > > FlightGear pre-release tonight. I did a full dress > rehearsal last sunday > > and that all seemed to work well, but I still > needed Curt's okay for a few > > remaining issues. In the mean time, if there are > any *urgent* patches > > remaining please try to get them into CVS ASAP. > > > > FWIW, FlightGear/PLIB is probably in a releasable > state as it is, but given > > the time since the last release, there may be > riding a lot of expectancy on > > this release, so I'd like to be a little more > careful and to at least one > > more pre-release -and should any problems arise- a > second one. > > > > To follow up on this: It seems like the initial > testing round went pretty > well, with mostly minor problems being reported, and > many of them being fixed > already. I'm hoping to roll up the tar files for the > release itself this > weekend. I'm not sure whether we'll be able to > transfer those to the main > webserver instantly, as there were some problems > recently. If not, I hope > that John Wojnaroski can again provide some server > space. In the mean time, > I guess we need to make a final decision on the > version number... > > Another question: we always have a limited number of > aircraft that are in the > distribution, with the rest being available as > separate downloads. We like to > keep the number of aircraft constant, and > representative of the many types of > aircraft supported by FlightGear. Is there any > pressing reason to swap one > aircraft for another one? IIRC, there have been some > suggestions of replacing > the 737 by the 787. FWIW, we currently have the > following selection of > aircraft (Taken from Makefile.am): > > data/Aircraft/Generic \ > data/Aircraft/Instruments \ > data/Aircraft/Instruments-3d \ > data/Aircraft/UIUC \ > data/Aircraft/737-300 \ > data/Aircraft/A-10 \ > data/Aircraft/bf109 \ > data/Aircraft/bo105 \ > data/Aircraft/c172 \ > data/Aircraft/c172p \ > data/Aircraft/c310 \ > data/Aircraft/c310u3a \ > data/Aircraft/Citation-Bravo \ > data/Aircraft/f16 \ > data/Aircraft/j3cub \ > data/Aircraft/Hunter \ > data/Aircraft/p51d \ > data/Aircraft/pa28-161 \ > data/Aircraft/Rascal \ > data/Aircraft/T38 \ > data/Aircraft/ufo \ > data/Aircraft/wrightFlyer1903 \ > > > Cheers, > Durk > Hi, sounds great! There is still one suggest by me for the win32-version: adding the sim-frame-throttle-thingy (that one for preventing too high fps) in preference.xml or other easy way. I see some problems with people with very good (up-todate) computers. That's something I miss on the win32 version! Regards HHS Heute schon einen Blick in die Zukunft von E-Mails wagen? www.yahoo.de/mail - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I would suggest including the lightning instead of f16, lightning is really good
quality and both are fighters.
Regards,
Arvid Norlander
Melchior FRANZ wrote:
> * Durk Talsma -- Tuesday 04 December 2007:
>
>> data/Aircraft/737-300 \
>
> Yes, I'd swap that with the 787. A flat panel that disappears
> when you look left/right is hard to bear. (Though I miss a VOR
> display on the 787. Need to search for that ...)
>
>
>
>> data/Aircraft/A-10 \
>
> Good choice. Very detailed, very good quality.
>
>
>
>> data/Aircraft/bf109 \
>
> Hmm ... it's well done and all, but I think it's "too realistic",
> read: too hard to take off/land due to the very narrow gear. The
> A6M2 would IMHO be a better choice (or the fw190, but I think that's
> not finished yet).
>
>
>
>> data/Aircraft/bo105 \
>
> Good choice, of course. Approved by a real bo105 pilot ("very
> impressed"). :-)
>
>
>
>> data/Aircraft/c172 \
>> data/Aircraft/c172p \
>
> use pa24 instead? But I see the pa28 further down, so ...
>
>
>
>> data/Aircraft/c310 \
>> data/Aircraft/c310u3a \
>
> use Seneca instead?
>
>
>
>> data/Aircraft/f16 \
>
> Totally broken! Don't ship this! The FCS winds up after a few
> minutes and kills you. Very frustrating. After starting fgfs,
> let is parked for a few minutes, then try to fly it. Good luck!
> (Though the HUD is nice. :-)
>
>
>
>> data/Aircraft/wrightFlyer1903 \
>
> Waste of disk space. Everyone tries it once or twice, and never
> again, because it's just *boring*.
>
> m.
>
> -
> SF.Net email is sponsored by: The Future of Linux Business White Paper
> from Novell. From the desktop to the data center, Linux is going
> mainstream. Let it simplify your IT future.
> http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
> ___
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
iD8DBQFHVcu3WmK6ng/aMNkRCli0AKCHnb5sopm8HyMAIBFKwZiGcC1mDACgsatD
gthI7NqIvTwpS3741SGKr6A=
=jad0
-END PGP SIGNATURE-
-
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
* Durk Talsma -- Tuesday 04 December 2007:
> data/Aircraft/737-300 \
Yes, I'd swap that with the 787. A flat panel that disappears
when you look left/right is hard to bear. (Though I miss a VOR
display on the 787. Need to search for that ...)
> data/Aircraft/A-10 \
Good choice. Very detailed, very good quality.
> data/Aircraft/bf109 \
Hmm ... it's well done and all, but I think it's "too realistic",
read: too hard to take off/land due to the very narrow gear. The
A6M2 would IMHO be a better choice (or the fw190, but I think that's
not finished yet).
> data/Aircraft/bo105 \
Good choice, of course. Approved by a real bo105 pilot ("very
impressed"). :-)
> data/Aircraft/c172 \
> data/Aircraft/c172p \
use pa24 instead? But I see the pa28 further down, so ...
> data/Aircraft/c310 \
> data/Aircraft/c310u3a \
use Seneca instead?
> data/Aircraft/f16 \
Totally broken! Don't ship this! The FCS winds up after a few
minutes and kills you. Very frustrating. After starting fgfs,
let is parked for a few minutes, then try to fly it. Good luck!
(Though the HUD is nice. :-)
> data/Aircraft/wrightFlyer1903 \
Waste of disk space. Everyone tries it once or twice, and never
again, because it's just *boring*.
m.
-
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Feature request: UDP from nasal
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 As I mentioned before on this list ([Flightgear-devel] Custom protocol issues), I requested support for UDP from nasal, however I got no response at all, so now I raise the issue again, basically I need to send messages to a daemon from nasal, custom protocols does not fit this: * I need to send at changing rate, from 50 or so / second to just one / 10 seconds. * The protocol is message based, I send instructions, I don't dump data. * I tried using custom protocols but when I sent enough properties to be able to send all needed commands as fast as needed I got horrible stutter. * Sending less I can't always send all I need. So I request support for sending UDP data from nasal code. This would be under controlled circumstances to prevent security issues: For example a command line switch saying what target port and ip nasal could use. Regards, Arvid Norlander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHVcFHWmK6ng/aMNkRCmWjAJ9P7xySo7+D6OyXFYpMu2OaPb9K0ACfYRqU f1KDmhpmu9Rasbvmy7XgytA= =pvym -END PGP SIGNATURE- - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
On Thursday 22 November 2007 07:36, Durk Talsma wrote: > This is a quick note to everybody: I'm planning to build an "official" > FlightGear pre-release tonight. I did a full dress rehearsal last sunday > and that all seemed to work well, but I still needed Curt's okay for a few > remaining issues. In the mean time, if there are any *urgent* patches > remaining please try to get them into CVS ASAP. > > FWIW, FlightGear/PLIB is probably in a releasable state as it is, but given > the time since the last release, there may be riding a lot of expectancy on > this release, so I'd like to be a little more careful and to at least one > more pre-release -and should any problems arise- a second one. > To follow up on this: It seems like the initial testing round went pretty well, with mostly minor problems being reported, and many of them being fixed already. I'm hoping to roll up the tar files for the release itself this weekend. I'm not sure whether we'll be able to transfer those to the main webserver instantly, as there were some problems recently. If not, I hope that John Wojnaroski can again provide some server space. In the mean time, I guess we need to make a final decision on the version number... Another question: we always have a limited number of aircraft that are in the distribution, with the rest being available as separate downloads. We like to keep the number of aircraft constant, and representative of the many types of aircraft supported by FlightGear. Is there any pressing reason to swap one aircraft for another one? IIRC, there have been some suggestions of replacing the 737 by the 787. FWIW, we currently have the following selection of aircraft (Taken from Makefile.am): data/Aircraft/Generic \ data/Aircraft/Instruments \ data/Aircraft/Instruments-3d \ data/Aircraft/UIUC \ data/Aircraft/737-300 \ data/Aircraft/A-10 \ data/Aircraft/bf109 \ data/Aircraft/bo105 \ data/Aircraft/c172 \ data/Aircraft/c172p \ data/Aircraft/c310 \ data/Aircraft/c310u3a \ data/Aircraft/Citation-Bravo \ data/Aircraft/f16 \ data/Aircraft/j3cub \ data/Aircraft/Hunter \ data/Aircraft/p51d \ data/Aircraft/pa28-161 \ data/Aircraft/Rascal \ data/Aircraft/T38 \ data/Aircraft/ufo \ data/Aircraft/wrightFlyer1903 \ Cheers, Durk - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] rain view
On Tue, 04 Dec 2007 12:38:57 +0100 Markus Zojer <[EMAIL PROTECTED]> wrote: > Hallo all! > > I have created some sample rain/snow usable with flightgear osg, > viewable only from cockpit view. > Currently it is linked with the B-1B, but I would like to bind it to > view 0, in order to be usable with any aircraft. > Here I ran into some problem: Models are added at model.ac datum while I > wanted to add them at virtual aircraft datum, at view 0 (like the hud) > actually. As the datums differ, I could not use the view 0 offset, which > was the only distance reference I could find in the property tree. > Now my question: How can that be done and/or is there a similar nasal > code to the geo.put_model that adds models to an existing one. > > For the curious(howto included): > http://homepage.univie.ac.at/markus.zojer/fgfs/Models.tar.gz > > Thanks, > Markus > > - > SF.Net email is sponsored by: The Future of Linux Business White Paper > from Novell. From the desktop to the data center, Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel Hi the screen shots look promising IMHO i think rain should be centered around the eyepoint position and speed But thats just my opinion since I dont lnow how to implement it myself :) Cheers -- Syd&Sandy <[EMAIL PROTECTED]> - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Braking chute from joystick?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 How does one activate braking chute from a joystick config, each aircraft with braking chute seems to do it differently, I looked at Lightning and vulcanb2. Is there a generic way? If not then I request it. Regards, Arvid Norlander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHVbTLWmK6ng/aMNkRCnhIAJsH1t9CvkzrXJLA/IFF/j47/4qcugCgvLAa SpfBUhH0/cOk00zdCt3+c1M= =CE0t -END PGP SIGNATURE- - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] rotation sense error remains in JSBSim FGPropeller.cpp
On Behalf Of dave perry > Sent: Tuesday, December 04, 2007 1:13 PM > > While looking into the AP oscillation about the ILS near the > runway for the SenecaII, I noticed that the sense is still > accounted for twice (see > Re: [Flightgear-devel] Bug in JSBSim FGPropeller.cpp, > 08/07/2007) in FGPropeller.cpp. > > Jon, shouldn't this be fixed before the next release of FlightGear. > > -Dave Perry Dave, That is correct. This was fixed in JSBSim CVS some time ago. It would probably be a good thing for this one to get into FlightGear right away. I'm not sure how extensively the JSBSim CVS version and the FlightGear version of FGPropeller differ right now, but I suspect that's the only difference. If someone with CVS access would take care of that it would be appreciated. Jon - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] dual head problem
Hi, OK, I've just starting working with OSG and multiple cameras so may not have all the details. OSG only requires a single instance of FG to use multiple cameras. You'll need to set up your xorg.conf file to run your graphics boards under a single X server and there are some lines you'll need in the preferences.xml file to configure the cameras, FOVs, and displays. If you understand what I've just said and have done this, then that pretty much exhausts my current understanding of OSG and multiple cameras. If OTOH, you're not clear on how to do this, I can provide a copy of the files that others have been kind enough to provide and I've edited for my setup. I'm not at my machine with those files, but will send them later today via private mail, if you like. These files set up X windows and configure FG-OSG to produce three views (left, center, right). You'll need pretty hefty graphics cards to get a decent frame rate. John jean pellotier wrote: >hi, I think i did (I'm using a script to compile). >I've got the following line in my configure.log: >#define ENABLE_OSGVIEWER 1 > > > >John Wojnaroski a écrit : > > >>Hi, >> >>did you run configure with " --enable-osgviewer" ? >> >>JW >> >>jean pellotier wrote: >> >> >> >> >>>Hi all >>>I tryed to run flightgear cvs-OSG using two displays, running two X >>>instances (different resolution) and when I start flightgear in a >>>terminal on the second display, it always start on the fist one. >>>The 0.9.10 version worked fine for this. >>>is this a bug or there's something to do before compiling? >>> >>>debian SID, amd2800+, geforce 6200 >>> >>>jano. >>> >>> >>> >>> >>> >>> >>> >>> >> >> >> - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Patch for absolute property path in bf109
Am Dienstag, den 04.12.2007, 15:22 +0100 schrieb AnMaster: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Attached is a patch that fixes some absolute property paths in bf109, as > mentioned before on the mailing list this breaks over mp. > Did you get display errors in MP? The bf19 display should be handled by the AI model in AI/Aircraft/bf109/Models/ You can notice the difference by the Fuselage nunber. The AI Model has none, the regular model is white 13. If you get the regular model (this should not happen), I would like to find out what went wrong. Greetings Detlef > Regards, > > Arvid Norlander > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.7 (GNU/Linux) > > iD8DBQFHVWKYWmK6ng/aMNkRCvsOAKCj1FQp7XH8db2a0Jsql3AoQy3MGwCePFsX > 56CDUF9jSVswIxD6w4NWHA4= > =cvHd > -END PGP SIGNATURE- > einfaches Textdokument-Anlage (bf109-property-path.patch) > ? bf109-property-path.patch > Index: Models/Bf-109g.xml > === [...] - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] [Fwd: Re: [Flightgear-users] Seneca II - couple of user comments]
dave perry wrote: > Laurence Vanek wrote: > >> I believe, however, that something else is going on with the A/P during >> ILS approach. I do not get the behavior you report on approach. The A/P >> begins to make large over corrections about one mile out, to the point >> where I need to disable the A/P & make the approach manually using the >> HSI. Not good if in poor IMC conditions with no visual refs. until at DH >> (~200 ft). >> >> > I get this behavior with any non zero turbulence even with the 0.3 > scaling. If I open the Weather menu and the Weather Conditions sub menu > and make sure all the turbulence tabs are slid all the way to the left > and then click on apply, the SenecaII settles down and follows the ILS > down to the runway. You cannot just use the fgrun advanced options > weather tab to zero the turbulence as it does not really zero the > turbulence. Make sure the property > /environment/turbulence/magnitude-norm is '0' (double). With fgrun > advanced weather turbulence set to zero, this property will still be > 0.00067 ... which is enough to cause the oscillations on my system. > > One more interesting result. Since I beleive that the AP is chasing even very small turbulence and the aileron inputs are causing the adverse yaw out of phase with the turbulence, I tried using "auto-coordination" with 0.05 turbulence value. The AP flew the SenecaII right down the LOC/GS. There was continuous control movements and the ball was biased off to one side (see the note on the double sense - I had not yet recompiled with the 2nd sense removed). The point here is that with the rudder outputs from the auto-coordination to correct the adverse yaw, the out of phase yaw oscillations were gone. Conclusions: 1. We know that Jon is going to rework the JSBSim turbulence which should help a lot. 2. Even after that, the adverse-aileron yaw needs to be toned down a lot in JSBSim models to achieve more realistic response in low power cruse such as one has when flying an instrument approach. For the upcoming release, can we modify the JSBSim in fgfs to turn off turbulence modeling? For the upcoming release, should we select a scaling factor for the adverse-aileron yaw in the c172p and SenecaII that result in the performance more similar to the pa28-161 and pa24-250 respectively? -Dave Perry - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] rotation sense error remains in JSBSim FGPropeller.cpp
While looking into the AP oscillation about the ILS near the runway for the SenecaII, I noticed that the sense is still accounted for twice (see Re: [Flightgear-devel] Bug in JSBSim FGPropeller.cpp, 08/07/2007) in FGPropeller.cpp. Jon, shouldn't this be fixed before the next release of FlightGear. -Dave Perry - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] dual head problem
hi, I think i did (I'm using a script to compile). I've got the following line in my configure.log: #define ENABLE_OSGVIEWER 1 John Wojnaroski a écrit : > Hi, > > did you run configure with " --enable-osgviewer" ? > > JW > > jean pellotier wrote: > > >> Hi all >> I tryed to run flightgear cvs-OSG using two displays, running two X >> instances (different resolution) and when I start flightgear in a >> terminal on the second display, it always start on the fist one. >> The 0.9.10 version worked fine for this. >> is this a bug or there's something to do before compiling? >> >> debian SID, amd2800+, geforce 6200 >> >> jano. >> >> >> >> >> >> > > > > - > SF.Net email is sponsored by: The Future of Linux Business White Paper > from Novell. From the desktop to the data center, Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > > > - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] rain view
Csaba Halász wrote: > On Dec 4, 2007 12:38 PM, Markus Zojer <[EMAIL PROTECTED]> wrote: > >> I have created some sample rain/snow usable with flightgear osg, >> > > May I request a screenshot please? Thanks. > > Sure :-) http://homepage.univie.ac.at/markus.zojer/fgfs/rain.png http://homepage.univie.ac.at/markus.zojer/fgfs/snow.png g, markus - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Property path patch for the 787
On Dec 4, 2007 9:34 AM, JOSHUA WILSON <> wrote: > Thank you very much for your assistance. You are right about the > property paths. However, if you look in CVS, you will find that 787/787- > 8-set.xml has been replaced by 787/787-8ANA-set.xml, 787/787-8CO-set.xml, > and 787/787-8FC-set.xml. These files do not make reference to > 787/Models/787.xml, but they point to files that replaced it. In those > files, the issue in question has already been resolved. If someone would > remove 787/Models/787.xml from CVS, I would greatly appreciate it. > Done ... Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/ Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] rain view
On Dec 4, 2007 12:38 PM, Markus Zojer <[EMAIL PROTECTED]> wrote: > > I have created some sample rain/snow usable with flightgear osg, May I request a screenshot please? Thanks. -- Csaba - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] rain view
"Rain and snow should work in all views in my opinion." Thats true. But right now I am working on cockpit view, the others will follow or maybe the build in precipitation effect can be used here. g, markus AnMaster wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Do you mean that rain and snow would not work in external view, or co-pilot > view > and so on? Rain and snow should work in all views in my opinion. > > Markus Zojer wrote: > >> Hallo all! >> >> I have created some sample rain/snow usable with flightgear osg, >> viewable only from cockpit view. >> Currently it is linked with the B-1B, but I would like to bind it to >> view 0, in order to be usable with any aircraft. >> Here I ran into some problem: Models are added at model.ac datum while I >> wanted to add them at virtual aircraft datum, at view 0 (like the hud) >> actually. As the datums differ, I could not use the view 0 offset, which >> was the only distance reference I could find in the property tree. >> Now my question: How can that be done and/or is there a similar nasal >> code to the geo.put_model that adds models to an existing one. >> >> For the curious(howto included): >> http://homepage.univie.ac.at/markus.zojer/fgfs/Models.tar.gz >> >> Thanks, >> Markus >> > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.7 (GNU/Linux) > > iD8DBQFHVT3yWmK6ng/aMNkRCropAJ0S1M8hY3/4kRgGM+iGENSlVV7q4gCfWVtt > PiWNZ2AD3yJjUST0toHz6ZI= > =ryKo > -END PGP SIGNATURE- > > - > SF.Net email is sponsored by: The Future of Linux Business White Paper > >from Novell. From the desktop to the data center, Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > > - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Property path patch for the 787
Arvid Norlander wrote: >-BEGIN PGP SIGNED MESSAGE- >Hash: SHA512 > >Attached is a patch to fix some absolute property paths in 787. See earlier >mails to the mailing list for why they are a bad idea. > >Regards, > >Arvid Norlander >-BEGIN PGP SIGNATURE- >Version: GnuPG v1.4.7 (GNU/Linux) > >iD8DBQFHVW1dWmK6ng/aMNkRCrfkAJ9BSOAoH5js66p8ygducNaDqBbdwACdFAnp >Tz2VGWRopZUbngc0gyrvCqw= >=QZyF >-END PGP SIGNATURE- Thank you very much for your assistance. You are right about the property paths. However, if you look in CVS, you will find that 787/787-8-set.xml has been replaced by 787/787-8ANA-set.xml, 787/787-8CO-set.xml, and 787/787-8FC-set.xml. These files do not make reference to 787/Models/787.xml, but they point to files that replaced it. In those files, the issue in question has already been resolved. If someone would remove 787/Models/787.xml from CVS, I would greatly appreciate it. Josh- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Property path patch for ec135.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 As requested by Heiko Schulz here is a patch for the ec135. Regards, Arvid Norlander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHVW5dWmK6ng/aMNkRCvxCAJ4uYD30O0C1yOzYJVn5lsv9swNQfQCgtKkA TuJ5mzHHeB9oCAMScF0yURw= =/SGh -END PGP SIGNATURE- Index: Models/ec135.xml === RCS file: /var/cvs/FlightGear-0.9/data/Aircraft/ec135/Models/ec135.xml,v retrieving revision 1.2 diff -u -p -r1.2 ec135.xml --- Models/ec135.xml3 Jun 2007 14:51:19 - 1.2 +++ Models/ec135.xml4 Dec 2007 15:01:16 - @@ -133,7 +133,7 @@ blurred2 blurred3 blurred4 - /rotors/main/rpm + rotors/main/rpm -0.74 -1.003 @@ -167,7 +167,7 @@ blade4b blade4c blade4d - /rotors/main/rpm + rotors/main/rpm -1.0 -1.003 @@ -203,7 +203,7 @@ mainrotors - /rotors/main/rpm + rotors/main/rpm 175 @@ -847,7 +847,7 @@ rotate blurred1 - /rotors/main/cone-deg + rotors/main/cone-deg 1.5 @@ -863,7 +863,7 @@ rotate blurred2 - /rotors/main/cone-deg + rotors/main/cone-deg 1.5 -0.425 @@ -878,7 +878,7 @@ rotate blurred3 - /rotors/main/cone-deg + rotors/main/cone-deg 1.5 0.320 @@ -893,7 +893,7 @@ rotate blurred4 - /rotors/main/cone-deg + rotors/main/cone-deg 1.5 -1.674 @@ -992,7 +992,7 @@ rotor_disc_T - /rotors/tail/rpm + rotors/tail/rpm 200 @@ -1003,7 +1003,7 @@ tailrotors - /rotors/tail/rpm + rotors/tail/rpm 201 @@ -1023,7 +1023,7 @@ frontdoor_re.i frontdoorglas_re - /sim/model/door-positions/pilotDoor/position-norm + sim/model/door-positions/pilotDoor/position-norm 60 @@ -1042,7 +1042,7 @@ frontdoor_li.i frontdoorglas_li - /sim/model/door-positions/copilotDoor/position-norm + sim/model/door-positions/copilotDoor/position-norm -60 @@ -1059,7 +1059,7 @@ rotate reardoor_re reardoor_re.i - /sim/model/door-positions/rearDoors/position-norm + sim/model/door-positions/rearDoors/position-norm 100 @@ -1077,7 +1077,7 @@ reardoor_li reardoor_li.i rearglas_li - /sim/model/door-positions/rearDoors/position-norm + sim/model/door-positions/rearDoors/position-norm -100 @@ -1098,7 +1098,7 @@ backdoor_re.i backdoorglas_re - /sim/model/door-positions/ribackDoor/position-norm + sim/model/door-positions/ribackDoor/position-norm 0 @@ -1128,7 +1128,7 @@ backdoor_re.i backdoorglas_re - /sim/model/door-positions/ribackDoor/position-norm + sim/model/door-positions/ribackDoor/position-norm 0 @@ -1158,7 +1158,7 @@ backdoor_li.i backdoorglas_li - /sim/model/door-positions/lebackDoor/position-norm + sim/model/door-positions/lebackDoor/position-norm 0 @@ -1188,7 +1188,7 @@ backdoor_li.i backdoorglas_li - /sim/model/door-positions/lebackDoor/position-norm + sim/model/door-
[Flightgear-devel] Property path patch for the 787
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Attached is a patch to fix some absolute property paths in 787. See earlier mails to the mailing list for why they are a bad idea. Regards, Arvid Norlander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHVW1dWmK6ng/aMNkRCrfkAJ9BSOAoH5js66p8ygducNaDqBbdwACdFAnp Tz2VGWRopZUbngc0gyrvCqw= =QZyF -END PGP SIGNATURE- 787-property-path.patch.bz2 Description: Binary data - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Property path patches for B-2 and F-86
Hi, can you update the ec135 too? I know, you have changed it on your local system, but I haven't the time now to fix it myself. It seems to me, that there are coming some changes to my life in the coming weeks, so I wil have not much time so I can't do it on my own. It would be very nice! Thanks a lot! Regards HHs --- AnMaster <[EMAIL PROTECTED]> schrieb: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Here are property path fixes for B-2 and F-86. As > described before, absolute > paths break over multiplayer. > > Regards, > > Arvid Norlander > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.7 (GNU/Linux) > > iD8DBQFHVWY1WmK6ng/aMNkRChghAKCe2p1IOQW3rsunATPKPldLk01ogACfa8t5 > Q/Xtc8sK/P0ymPhlOtUyi74= > =kaAz > -END PGP SIGNATURE- > > Index: Models/F-86f.xml > === > RCS file: > /var/cvs/FlightGear-0.9/data/Aircraft/F-86/Models/F-86f.xml,v > retrieving revision 1.1 > diff -u -p -r1.1 F-86f.xml > --- Models/F-86f.xml 29 Jul 2007 19:26:49 - 1.1 > +++ Models/F-86f.xml 4 Dec 2007 14:34:03 - > @@ -460,7 +460,7 @@ > >rotate >flap.L > - > /surface-positions/flap-pos-norm > + > surface-positions/flap-pos-norm >-50 > > 5.676 > @@ -480,7 +480,7 @@ > >rotate >flap.R > - > /surface-positions/flap-pos-norm > + > surface-positions/flap-pos-norm >50 > > 5.676 > > Index: Models/la_light.xml > === > RCS file: > /var/cvs/FlightGear-0.9/data/Aircraft/B-2/Models/la_light.xml,v > retrieving revision 1.2 > diff -u -p -r1.2 la_light.xml > --- Models/la_light.xml 26 Feb 2007 20:33:16 - > 1.2 > +++ Models/la_light.xml 4 Dec 2007 14:26:14 - > @@ -39,7 +39,7 @@ > > > > - > /gear/gear[0]/position-norm > + gear/gear[0]/position-norm > 1 > > > > - > SF.Net email is sponsored by: The Future of Linux > Business White Paper > from Novell. From the desktop to the data center, > Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4> ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > __ Ihr erstes Fernweh? Wo gibt es den schönsten Strand? www.yahoo.de/clever - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Property path patches for B-2 and F-86
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Here are property path fixes for B-2 and F-86. As described before, absolute paths break over multiplayer. Regards, Arvid Norlander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHVWY1WmK6ng/aMNkRChghAKCe2p1IOQW3rsunATPKPldLk01ogACfa8t5 Q/Xtc8sK/P0ymPhlOtUyi74= =kaAz -END PGP SIGNATURE- Index: Models/F-86f.xml === RCS file: /var/cvs/FlightGear-0.9/data/Aircraft/F-86/Models/F-86f.xml,v retrieving revision 1.1 diff -u -p -r1.1 F-86f.xml --- Models/F-86f.xml29 Jul 2007 19:26:49 - 1.1 +++ Models/F-86f.xml4 Dec 2007 14:34:03 - @@ -460,7 +460,7 @@ rotate flap.L - /surface-positions/flap-pos-norm + surface-positions/flap-pos-norm -50 5.676 @@ -480,7 +480,7 @@ rotate flap.R - /surface-positions/flap-pos-norm + surface-positions/flap-pos-norm 50 5.676 Index: Models/la_light.xml === RCS file: /var/cvs/FlightGear-0.9/data/Aircraft/B-2/Models/la_light.xml,v retrieving revision 1.2 diff -u -p -r1.2 la_light.xml --- Models/la_light.xml 26 Feb 2007 20:33:16 - 1.2 +++ Models/la_light.xml 4 Dec 2007 14:26:14 - @@ -39,7 +39,7 @@ - /gear/gear[0]/position-norm + gear/gear[0]/position-norm 1 - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Patch for absolute property path in bf109
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Attached is a patch that fixes some absolute property paths in bf109, as mentioned before on the mailing list this breaks over mp. Regards, Arvid Norlander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHVWKYWmK6ng/aMNkRCvsOAKCj1FQp7XH8db2a0Jsql3AoQy3MGwCePFsX 56CDUF9jSVswIxD6w4NWHA4= =cvHd -END PGP SIGNATURE- ? bf109-property-path.patch Index: Models/Bf-109g.xml === RCS file: /var/cvs/FlightGear-0.9/data/Aircraft/bf109/Models/Bf-109g.xml,v retrieving revision 1.2 diff -u -p -r1.2 Bf-109g.xml --- Models/Bf-109g.xml 28 Nov 2007 08:35:01 - 1.2 +++ Models/Bf-109g.xml 4 Dec 2007 14:20:37 - @@ -408,7 +408,7 @@ rotate Stick - /controls/flight/elevator + controls/flight/elevator -10 3.14 @@ -425,7 +425,7 @@ rotate Stick - /controls/flight/aileron + controls/flight/aileron -10 3.14 @@ -445,7 +445,7 @@ Propeller1 -/engines/engine[0]/rpm +engines/engine[0]/rpm 1000 @@ -456,7 +456,7 @@ Propturn -/engines/engine[0]/rpm +engines/engine[0]/rpm 1000 @@ -465,7 +465,7 @@ spin Propturn -/engines/engine[0]/rpm +engines/engine[0]/rpm -0.01 3.40 @@ -483,7 +483,7 @@ spin Propeller1 Prop - /engines/engine[0]/rpm + engines/engine[0]/rpm -0.479 3.40 @@ -500,7 +500,7 @@ rotate leftgear - /gear/gear[0]/position-norm + gear/gear[0]/position-norm 0.0 @@ -526,7 +526,7 @@ rotate leftwheelstop - /gear/gear[0]/position-norm + gear/gear[0]/position-norm 0.0 @@ -552,7 +552,7 @@ rotate rightgear - /gear/gear[1]/position-norm + gear/gear[1]/position-norm 0.0 @@ -582,7 +582,7 @@ rotate rightwheelstop - /gear/gear[1]/position-norm + gear/gear[1]/position-norm 0.0 @@ -642,7 +642,7 @@ rightwheel -/gear/gear[1]/compression-norm +gear/gear[1]/compression-norm 0.0 @@ -653,7 +653,7 @@ leftwheel -/gear/gear[0]/compression-norm +gear/gear[0]/compression-norm 0.0 @@ -666,7 +666,7 @@ rotate rightcoolflap - /surface-positions/flap-pos-norm + surface-positions/flap-pos-norm 57.0 @@ -685,7 +685,7 @@ rotate leftcoolflap - /surface-positions/flap-pos-norm + surface-positions/flap-pos-norm 57.0 @@ -704,7 +704,7 @@ rotate leftflap - /controls/engines/engine[0]/cowl-flaps-norm + controls/engines/engine[0]/cowl-flaps-norm -20.0 @@ -725,7 +725,7 @@ rotate rightflap - /controls/engines/engine[0]/cowl-flaps-norm + controls/engines/engine[0]/cowl-flaps-norm 20.0 @@ -766,7 +766,7 @@ rotate leftoutflap - /surface-positions/flap-pos-norm + surface-positions/flap-pos-norm 47.0 @@ -785,7 +785,7 @@ rotate rightaileron - /controls/flight/aileron + controls/flight/aileron -15.0 @@ -806,7 +806,7 @@ rotate LeftAileron - /controls/flight/aileron + controls/flight/aileron 15.0 @@ -826,7 +826,7 @@ rotate Rudder - /surface-positions/rudder-pos-norm + surface-positions/rudder-pos-norm 30.0 @@ -845,7 +845,7 @@ rotate LeftElevator - /surface-positions/elevator-pos-norm + surface-positions/elevator-pos-norm -1.0 @@ -892,7 +892,7 @@ translate leftwheel - /gear/gear[0]/compression-norm + gear/gear[0]/compression-norm 0.0 @@ -917,7 +917,7 @@ translate rightwheel - /gear/gear[1]/compression-norm + gear/gear[1]/compression-norm 0.0 @@ -942,7 +942,7 @@ spin leftwheel - /velocities/uBody-fps + velocities/uBody-fps -1.5 2.0325 @@ -959,7 +959,7 @@ spin rightwheel - /velocities/uBody-fps + velocities/uBody-fps -1.5 2.0325 @@ -978,7 +978,7 @@ rightwheelstop -/gear/gear[1]/compression-norm +gear/gear[1]/compression-norm 0.0 @@ -989,7 +989,7 @@ leftwheelstop -/gear/gear[0]/compression-norm +gear/gear[0]/compression-norm 0.0 @@ -998,7 +998,7 @@ translate leftslat - /surface-positions/slat-pos-norm + surface-positions/slat-pos-norm 0.0 @@ -1019,7 +1019,7 @@ translate rightslat - /surface-positions/slat-pos-norm + surface-positions/slat-pos-norm 0.0 Index: Models/bf109g-model.xml === RCS file: /var/cvs/FlightGear-0.9/data/Aircraft/bf109/Models/bf109g-model.xml,v retrieving revision 1.4 diff -u -p -r1.4 bf109g-model.xml --- Models/bf109g-model.xml 5 Jul 2007 07:36:48 - 1.4 +++ Models/bf109g-model.xml 4 Dec 2007 14:20:37 - @@ -409,7 +409,7 @@ rotate Stick rhand - /controls/flight/elevator + controls/flight/elevator -10 3.
[Flightgear-devel] Patch for absolute property paths in bleriot-XI
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 bleriot-XI contains some absolute property paths and as described before on this mailing list, that breaks over multiplayer. Attached is a patch that fixes it. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHVV2AWmK6ng/aMNkRCoV2AKC3Lnuhfsl42i2oCI0e0BhL8ED0BACfUgCL v9/Lw+b34JybNpoksY/aAD0= =h2J3 -END PGP SIGNATURE- ? bleriot-XI-property-path.patch Index: Models/bleriot-XI.xml === RCS file: /var/cvs/FlightGear-0.9/data/Aircraft/bleriot-XI/Models/bleriot-XI.xml,v retrieving revision 1.1 diff -u -p -r1.1 bleriot-XI.xml --- Models/bleriot-XI.xml 3 Oct 2007 17:32:47 - 1.1 +++ Models/bleriot-XI.xml 4 Dec 2007 13:58:45 - @@ -57,7 +57,7 @@ helice propdisc propblur -/engines/engine[0]/rpm +engines/engine[0]/rpm 1 -2.063 @@ -75,7 +75,7 @@ rotate volant -/controls/flight/elevator +controls/flight/elevator 10 -0.319 @@ -92,7 +92,7 @@ rotate volant -/controls/flight/aileron +controls/flight/aileron 10 -0.319 @@ -111,7 +111,7 @@ rotate profondeur profondeur2 - /controls/flight/elevator + controls/flight/elevator 11 4.523 @@ -130,7 +130,7 @@ rotate gouverne gouverne2 - /controls/flight/rudder + controls/flight/rudder 20 5.123 @@ -149,7 +149,7 @@ rotate suspensionAG roueG - /gear/gear[0]/compression-norm + gear/gear[0]/compression-norm 0.0 @@ -175,7 +175,7 @@ rotate suspensionbarre - /gear/gear[0]/compression-norm + gear/gear[0]/compression-norm 0.0 @@ -204,7 +204,7 @@ suspensionBG ressortG1 ressortG2 - /gear/gear[0]/compression-norm + gear/gear[0]/compression-norm 0.0 @@ -225,7 +225,7 @@ rotate suspensionBG - /gear/gear[0]/compression-norm + gear/gear[0]/compression-norm 0.0 @@ -252,7 +252,7 @@ rotate suspensionAD roueD - /gear/gear[1]/compression-norm + gear/gear[1]/compression-norm 0.0 @@ -278,7 +278,7 @@ rotate suspensionbarre - /gear/gear[1]/compression-norm + gear/gear[1]/compression-norm 0.0 @@ -307,7 +307,7 @@ suspensionBD ressortD1 ressortD2 - /gear/gear[1]/compression-norm + gear/gear[1]/compression-norm 0.0 @@ -328,7 +328,7 @@ rotate suspensionBD - /gear/gear[1]/compression-norm + gear/gear[1]/compression-norm 0.0 @@ -355,7 +355,7 @@ rotate suspensionQA roueA - /gear/gear[2]/compression-norm + gear/gear[2]/compression-norm 0.0 @@ -381,7 +381,7 @@ translate suspensionQB - /gear/gear[2]/compression-norm + gear/gear[2]/compression-norm 0.0 @@ -402,7 +402,7 @@ rotate suspensionQB - /gear/gear[2]/compression-norm + gear/gear[2]/compression-norm 0.0 - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Nasal var issue patch for data/Nasal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I made a patch that add some missing "var" to the data/Nasal/*.nas files. It
also changes props.wrap to use named arguments and remove a duplicate of
math.asin in lead_target.nas, making it use the math.asin one instead. (As far
as I could find, nothing outside the file itself used it, if I'm wrong about
that: sorry).
I also changed everything in data/Nasal to use math.abs instead of globals.abs,
however a lot remains that uses globals.abs in aircrafts and other places (see
my earlier mail to the list)
As I'm rather new to nasal could someone please have a look at my patch to see
that it is ok?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
iD8DBQFHVVwpWmK6ng/aMNkRCjG+AJ9hz44kQTNM/jvDAvJHUXOnVbm5JACgoPc2
ne0/AveKS2TyZSWfXXBvBFQ=
=YVgH
-END PGP SIGNATURE-
? nasal-var.diff
Index: aircraft.nas
===
RCS file: /var/cvs/FlightGear-0.9/data/Nasal/aircraft.nas,v
retrieving revision 1.45
diff -u -p -r1.45 aircraft.nas
--- aircraft.nas6 Nov 2007 21:22:06 - 1.45
+++ aircraft.nas4 Dec 2007 13:50:01 -
@@ -135,7 +135,7 @@ var door = {
# door.move(double)-> move to arbitrary position
move: func {
- time = abs(me.getpos() - arg[0]) * me.swingtime;
+ time = math.abs(me.getpos() - arg[0]) * me.swingtime;
interpolate(me.positionN, arg[0], time);
me.target = !me.target;
},
Index: atc-chatter.nas
===
RCS file: /var/cvs/FlightGear-0.9/data/Nasal/atc-chatter.nas,v
retrieving revision 1.8
diff -u -p -r1.8 atc-chatter.nas
--- atc-chatter.nas 15 May 2007 14:40:58 - 1.8
+++ atc-chatter.nas 4 Dec 2007 13:50:01 -
@@ -11,16 +11,16 @@
# Global shared variables
#
-fg_root = "";
-chatter = "UK";
-chatter_dir = "";
-
-chatter_min_interval = 20.0;
-chatter_max_interval = 40.0;
-
-chatter_index = 0;
-chatter_size = 0;
-chatter_list = 0;
+var fg_root = "";
+var chatter = "UK";
+var chatter_dir = "";
+
+var chatter_min_interval = 20.0;
+var chatter_max_interval = 40.0;
+
+var chatter_index = 0;
+var chatter_size = 0;
+var chatter_list = 0;
#
@@ -28,7 +28,7 @@ chatter_list = 0;
# up and running
#
-CHATTER_INIT = func {
+var CHATTER_INIT = func {
# default values
fg_root = getprop("/sim/fg-root");
chatter_dir = sprintf("%s/ATC/Chatter/%s", fg_root, chatter);
@@ -46,7 +46,7 @@ settimer(CHATTER_INIT, 0);
# main update function to be called each frame
#
-chatter_update = func {
+var chatter_update = func {
if ( chatter_index >= chatter_size ) {
chatter_index = 0;
}
@@ -76,7 +76,7 @@ chatter_update = func {
# Use tha nasal timer to update every 10 seconds
#
-nextChatter = func {
+var nextChatter = func {
# schedule next message in next min-max interval seconds so we have a bit
# of a random pacing
next_interval = chatter_min_interval
Index: dynamic_view.nas
===
RCS file: /var/cvs/FlightGear-0.9/data/Nasal/dynamic_view.nas,v
retrieving revision 1.37
diff -u -p -r1.37 dynamic_view.nas
--- dynamic_view.nas3 Nov 2007 14:08:40 - 1.37
+++ dynamic_view.nas4 Dec 2007 13:50:01 -
@@ -43,7 +43,7 @@ var cos = func(a) { math.cos(a * math.pi
var sigmoid = func(x) { 1 / (1 + math.exp(-x)) }
var nsigmoid = func(x) { 2 / (1 + math.exp(-x)) - 1 }
var pow = func(v, w) { v < 0 ? nil : v == 0 ? 0 : math.exp(math.ln(v) * w) }
-var npow = func(v, w) { v == 0 ? 0 : math.exp(math.ln(abs(v)) * w) * (v < 0 ?
-1 : 1) }
+var npow = func(v, w) { v == 0 ? 0 : math.exp(math.ln(math.abs(v)) * w) * (v <
0 ? -1 : 1) }
var clamp = func(v, min, max) { v < min ? min : v > max ? max : v }
var normatan = func(x) { math.atan2(x, 1) * 2 / math.pi }
Index: geo.nas
===
RCS file: /var/cvs/FlightGear-0.9/data/Nasal/geo.nas,v
retrieving revision 1.14
diff -u -p -r1.14 geo.nas
--- geo.nas 7 Oct 2007 15:12:06 - 1.14
+++ geo.nas 4 Dec 2007 13:50:01 -
@@ -276,7 +276,7 @@ var tile_index = func(lat, lon) {
var format = func(lat, lon) {
- sprintf("%s%03d%s%02d", lon < 0 ? "w" : "e", abs(lon), lat < 0 ? "s" :
"n", abs(lat));
+ sprintf("%s%03d%s%02d", lon < 0 ? "w" : "e", math.abs(lon), lat < 0 ?
"s" : "n", math.abs(lat));
}
Index: globals.nas
===
RCS file
Re: [Flightgear-devel] rain view
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Do you mean that rain and snow would not work in external view, or co-pilot view and so on? Rain and snow should work in all views in my opinion. Markus Zojer wrote: > Hallo all! > > I have created some sample rain/snow usable with flightgear osg, > viewable only from cockpit view. > Currently it is linked with the B-1B, but I would like to bind it to > view 0, in order to be usable with any aircraft. > Here I ran into some problem: Models are added at model.ac datum while I > wanted to add them at virtual aircraft datum, at view 0 (like the hud) > actually. As the datums differ, I could not use the view 0 offset, which > was the only distance reference I could find in the property tree. > Now my question: How can that be done and/or is there a similar nasal > code to the geo.put_model that adds models to an existing one. > > For the curious(howto included): > http://homepage.univie.ac.at/markus.zojer/fgfs/Models.tar.gz > > Thanks, > Markus -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHVT3yWmK6ng/aMNkRCropAJ0S1M8hY3/4kRgGM+iGENSlVV7q4gCfWVtt PiWNZ2AD3yJjUST0toHz6ZI= =ryKo -END PGP SIGNATURE- - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] rain view
Hallo all! I have created some sample rain/snow usable with flightgear osg, viewable only from cockpit view. Currently it is linked with the B-1B, but I would like to bind it to view 0, in order to be usable with any aircraft. Here I ran into some problem: Models are added at model.ac datum while I wanted to add them at virtual aircraft datum, at view 0 (like the hud) actually. As the datums differ, I could not use the view 0 offset, which was the only distance reference I could find in the property tree. Now my question: How can that be done and/or is there a similar nasal code to the geo.put_model that adds models to an existing one. For the curious(howto included): http://homepage.univie.ac.at/markus.zojer/fgfs/Models.tar.gz Thanks, Markus - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Duplicate nasal functions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The abs function exists in both globals.nas and math.nas, in my opinion one should be removed once all references are changed to use the other. I suggest the abs function from globals.nas to be removed and the one in math.nas to be kept. I'm willing to make patches against other files using these functions. And comments/suggestions? Regards, Arvid Norlander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHVR9zWmK6ng/aMNkRCsgxAJ9xIuY/ukejueJwCDyBgjyeCGQ+IgCgippY /8kFYFLVy+WCilzz1Ts2kNA= =b2eg -END PGP SIGNATURE- - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
