[Flightgear-devel] Weekly CVS Changelog Summary: FlightGear data
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-02-24_10:30:59 (mfranz) /var/cvs/FlightGear-0.9/data/Aircraft/bluebird/bluebird-base.xml Stuart ANDREASON: update =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-02-24_10:31:02 (mfranz) /var/cvs/FlightGear-0.9/data/Aircraft/bluebird/Models/bluebird-plib.xml /var/cvs/FlightGear-0.9/data/Aircraft/bluebird/Models/bluebird6.ac Stuart ANDREASON: update =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-02-24_10:31:04 (mfranz) /var/cvs/FlightGear-0.9/data/Aircraft/bluebird/Models/hotspot-collective.xml Stuart ANDREASON: update =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-02-24_20:17:46 (sydadams) /var/cvs/FlightGear-0.9/data/Aircraft/dhc6/Models/Instruments/ammeter.ac /var/cvs/FlightGear-0.9/data/Aircraft/dhc6/Models/Instruments/ammeter.xml system updates ... generators show a load ... =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-02-25_17:01:36 (tat) /var/cvs/FlightGear-0.9/data/Aircraft/A6M2/A6M2-base.xml /var/cvs/FlightGear-0.9/data/Aircraft/A6M2/A6M2-jsbsim-test-set.xml /var/cvs/FlightGear-0.9/data/Aircraft/A6M2/A6M2-jsbsim-test.xml Added: JSBSim experimental files for an old constant speed propeller (*-test*.xml) Modified: Reorganied -set.xml using A6M2-base.xml Modified: engine and prop config of JSBSim version for accurate power/thrust Modified: Some objects are added to the cockpit - a6m2.ac Modified: initial fuel pressure to 36 (psi) Fixed: FO-psi to show accurate fuel pressure Fixed: AMC was not properly working in jwarbirds.nas =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-02-25_17:01:37 (tat) /var/cvs/FlightGear-0.9/data/Aircraft/A6M2/Engines/CS-40B-test.xml /var/cvs/FlightGear-0.9/data/Aircraft/A6M2/Engines/Sakae-Type12-test.xml Added: JSBSim experimental files for an old constant speed propeller (*-test*.xml) Modified: Reorganied -set.xml using A6M2-base.xml Modified: engine and prop config of JSBSim version for accurate power/thrust Modified: Some objects are added to the cockpit - a6m2.ac Modified: initial fuel pressure to 36 (psi) Fixed: FO-psi to show accurate fuel pressure Fixed: AMC was not properly working in jwarbirds.nas =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-02-27_11:58:38 (mfranz) /var/cvs/FlightGear-0.9/data/Input/Joysticks/Saitek/Pro-Flight-Rudder-Pedals.xml Sven ALMGREN: Saitek Pro-Flight-Rudder-Pedals's name differs in windows from linux, and the axis for the rudder is 3, not 2... assumes Mac uses same channel as windows, but could be wrong... linux is set to channel 2, and windows and mac is set to 3 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-02-28_02:56:21 (vmmeazza) /var/cvs/FlightGear-0.9/data/Aircraft/seahawk/seahawk-2tanks-set.xml Add 2 tank variant =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-02-28_02:58:46 (vmmeazza) /var/cvs/FlightGear-0.9/data/Aircraft/seahawk/Models/seahawk-3d-model-2t.xml Add 2 tank variant =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-02-28_03:01:45 (vmmeazza) /var/cvs/FlightGear-0.9/data/AI/droptank_demo.xml Add 2 tank variant =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-02-28_03:11:23 (vmmeazza) /var/cvs/FlightGear-0.9/data/Aircraft/seahawk/Models/seahawk-submodels3.xml Add 2 tank variant =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-02-28_07:16:12 (abory) /var/cvs/FlightGear-0.9/data/Aircraft/f-14b/f-14b-set.xml /var/cvs/FlightGear-0.9/data/Aircraft/f-14b/f-14b-yasim.xml - Enrique: Improvement of the FDM. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-02-28_07:23:10 (abory) /var/cvs/FlightGear-0.9/data/Aircraft/f-14b/Models/common.rgb /var/cvs/FlightGear-0.9/data/Aircraft/f-14b/Models/f14.ac - Enrique: tests on textures. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-02-28_07:23:12 (abory) /var/cvs/FlightGear-0.9/data/Aircraft/f-14b/Models/side1.rgb /var/cvs/FlightGear-0.9/data/Aircraft/f-14b/Models/side2.rgb /var/cvs/FlightGear-0.9/data/Aircraft/f-14b/Models/topbottom1.rgb /var/cvs/FlightGear-0.9/data/Aircraft/f-14b/Models/topbottom2.rgb - Enrique: tests on textures. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-02-28_07:25:45 (abory) /var/cvs/FlightGear-0.9/data/Aircraft/f-14b/Nasal/SAS.nas /var/cvs/FlightGear-0.9/data/Aircraft/f-14b/Nasal/engines.nas /var/cvs/FlightGear-0.9/data/Aircraft/f-14b/Nasal/f-14b.nas - Enrique: Improvement of the FDM, SAS based on Nasal. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-02-28_07:27:58 (abory) /var/cvs/FlightGear-0.9/data/Aircraft/f-14b/Attic/f-14-AFCS.xml - Enrique: Renamed in f-14b-AFCS.xml =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-02-28_07:49:41 (abory) /var/cvs/FlightGear-0.9/data/Aircraft/f-14b/f-14b-AFCS.xml - Enrique: renamed f-14-AFCS.xml in
Re: [Flightgear-devel] wiki mess (was: Re: livery handling ( MP updates))
Hello, EG. I have just made a small edit to the front page which was to remove a fixed width of 500 pixels which messes up the page on a narrow screen or browser width. Ok, I didn't test it on a smaller screen. Thanks for editing! Melchior, which page would you call the page that need to be edited first. I agree though that the front page is too wordy for example duplicate links to Portal:User and Portal:Developer. What do you mean with that last sentence? I've already displaced almost all the links on the main page to the two portals. Is that okay? Cheers, Gijs _ De mooiste afbeeldingen van Angelina Jolie vind je met Live Search http://search.live.com/images/results.aspx?q=angelina%20jolieFORM=MIINTM- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] wiki mess (was: Re: livery handling ( MP updates)
On Sun, Mar 2, 2008 at 10:21 PM, Gijs de Rooy [EMAIL PROTECTED] wrote: Hello, EG. I have just made a small edit to the front page which was to remove a fixed width of 500 pixels which messes up the page on a narrow screen or browser width. Ok, I didn't test it on a smaller screen. Thanks for editing! Melchior, which page would you call the page that need to be edited first. I agree though that the front page is too wordy for example duplicate links to Portal:User and Portal:Developer. What do you mean with that last sentence? I've already displaced almost all the links on the main page to the two portals. Is that okay? The two portals are listed twice. once to the left of the heading saying Welcome to... The other instance is listed under Please choose a portal. My preference is to lose them from the top as its less to read before the main text of the page. George - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] wiki mess (was: Re: livery handling ( MP updates)
The two portals are listed twice. once to the left of the heading saying Welcome to... The other instance is listed under Please choose a portal. My preference is to lose them from the top as its less to read before the main text of the page. Yes, first i've put them in top, but it's not very prominent. So i've put them in the main text. But it's okay if you remove them. btw, Are there any more portals we could have? Maybey one for aircraft(makers), scenery etc.? _ Probeer Live Search: de zoekmachine van de makers van MSN! http://www.live.com/?searchOnly=true- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Request for Blender tutorials
On Saturday 01 March 2008 23:57, Jeff Koppe wrote: - Original Message - From: LeeE [EMAIL PROTECTED] To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] Request for Blender tutorials Date: Sat, 1 Mar 2008 18:35:24 + I guess that if you start learning 3D on Blender things make sense but if you've come from any other 3D package it seems impossible to get to grips with and very counter-intuitive. LeeE I'd have to agree with you on that. I'm not sure if they cover UV mapping yet but I found the http://blenderunderground.com/ tutorials pretty helpful. If you're not opposed to using a proprietary Windows solution I've always been fond of Ultimate Unwrap (http://www.unwrap3d.com/). I just never seem to find enough time to wrap my head around Blender. What? Someone's used my obj-ac Ruby script? I'm psyched! --jeff Thanks for the link - heh - found yet another reference to the BioRUST UV mapping tutorial:) I don't have a problem with proprietary s/w but I haven't got a windows m/c to run it on. Gradually making some progress with Blender though. LeeE - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] wiki mess (was: Re: livery handling ( MP updates))
* George Patterson -- Sunday 02 March 2008: I second Heiko's comments, if no one improves something, how does it supposed to get better? You miss the point. I'm not going to (1) write code, to (2) document it, *and* to (3) fix the wiki page that other people have turned into a mess. (2) isn't fun, but it needs to be done. But before I invest time in (3) I rather use that for more of (1). :-P m. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] wiki mess (was: Re: livery handling ( MP updates))
On Sun, Mar 2, 2008 at 11:31 PM, Melchior FRANZ [EMAIL PROTECTED] wrote: * George Patterson -- Sunday 02 March 2008: I second Heiko's comments, if no one improves something, how does it supposed to get better? You miss the point. I'm not going to (1) write code, to (2) document it, *and* to (3) fix the wiki page that other people have turned into a mess. (2) isn't fun, but it needs to be done. But before I invest time in (3) I rather use that for more of (1). :-P m. I'm happy to help maintain the docs in the wiki where I can. :-) Also Sometimes those that have not written the code can write better user documentation as they are not viewing the feature the back end the technology used. I guess I'll wait a few days until Gijs de Rooy (wiki user: gijs) completes his version and take it from there. Personally, the number of links on front page is not user friendly with some of the sections should be moved to sub pages. G. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Request for Blender tutorials
* LeeE -- Sunday 02 March 2008: Gradually making some progress with Blender though. BTW: I just wrote a simple script that packs manually UV mapped objects onto a texture square. I'll publish it as soon as it's ready (later today :-). Works like this: - map all objects individually, choosing the best unwrapping method for the object and the ideal mapping size - select all objects that you want to map on one texture (e.g. by selecting one, and choosing Select-Linked-Material for all fuselage objects) - call the script: this packs the maps of all selected objects on a square and scales them up as much as possible using the same factor - export to SVG (I need yet to rewrite the SVG exporter -- the included one isn't good enough :-) m. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] wiki mess (was: Re: liv ery handling ( MP updates ))
Am Sonntag, 2. März 2008 14:40 schrieb Gijs de Rooy: You could start with editing if you want. I'm done for now. May I say that after not visiting the wiki site for a while my first impression on the new look was: ***whow*** it looks much better than before! Thanks for the improvement! TOrsten - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] wiki mess
Torsten Dreyer schrieb: Am Sonntag, 2. März 2008 14:40 schrieb Gijs de Rooy: You could start with editing if you want. I'm done for now. May I say that after not visiting the wiki site for a while my first impression on the new look was: ***whow*** it looks much better than before! Thanks for the improvement! TOrsten Torsten's post made me also look at the new FG wiki and it really not only looks much better but is more user-friendly. This must have been a lot of hard work, as nobody likes to clean up the kitchen, therefore thank you very much for all who did it (first Gijs de Rooy, but also George Patterson, ?) Georg EDDW - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] wiki mess
* Georg Vollnhals -- Sunday 02 March 2008: Torsten's post made me also look at the new FG wiki and it really not only looks much better but is more user-friendly. Yes, indeed. Nice work. What's left to do is to remove such pages: http://wiki.flightgear.org/flightgear_wiki/index.php?title=FlightGear-Points_of_Interest http://wiki.flightgear.org/flightgear_wiki/index.php?title=Adding_features Those who know how to fill in the contents are certainly clever enough to create the page if necessary. Such skeletons are IMHO silly and frustrating. Needless clicks and page loading, only to see that there's *nothing*. Of course, it's a different matter if someone writes, let's say, a page about FDMs, fills in the JSBSim part, and adds only section headers for YASim, UIUC, etc. But headings *only* are bad. m. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] LH A320 near crash during crosswind and heavy gust
Hi all, there has been a heavy storm (to hurricane) situation here in Northern Europe during the last days. A Lufthansa A 320 touched! the runway with one winglet (damaged) in the final phase of the landing when not only executing a crosswind landing but getting into a heavy unexpected gust. The chief pilot of LH applauded the crew for their professional reaction. He said the regularly training of exactly such events paid off. The aircraft could land safely on another runway, some passengers felt really bad and came near to tears. Here is the video-link: http://www.liveleak.com/view?i=ddb_1204404185 Georg EDDW BTW: is there any possibility to load a special METAR situation into FlightGear? Is a METAR file of this time (EDDH, Saturday 01.Febr.2008, 14:00) available anywhere? - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] PNG files in CVS repository
Now that PNG files are inserted in the CVS repository, I would like to point out that these files should be inserted as Binary files. Some, that are already there, are considered as text files, with LF expanded to CRLF for Windows users, and are corrupted. One example is data/Aircraft/bo105/Models/Textures/empty.png I tried to change its binary status but : cvs admin -kb -- empty.png (in directory I:\Devel\fgfsbase\Aircraft\bo105\Models\Textures\) RCS file: /var/cvs/FlightGear-0.9/data/Aircraft/bo105/Models/Textures/empty.png,v cvs [admin aborted]: could not open lock file `/var/cvs/FlightGear-0.9/data/Aircraft/bo105/Models/Textures/,empty.png,': Permission denied or : cvs admin -kb -- oebh.png (in directory I:\Devel\fgfsbase\Aircraft\bo105\Models\Textures\Emblems) RCS file: /var/cvs/FlightGear-0.9/data/Aircraft/bo105/Models/Textures/Emblems/oebh.png,v cvs [admin aborted]: could not open lock file `/var/cvs/FlightGear-0.9/data/Aircraft/bo105/Models/Textures/Emblems/,oebh.png,': Permission denied So I would like owners to change the status themselves. On a more general note, it seems that every new directory in the CVS repository has permition problems that need to be fixed manually. I changed CVSROOT/cvswrappers to set binary attribute to future png additions. In the meantime, current files need to be fixed manually. -Fred -- Frédéric Bouvier http://my.fotolia.com/frfoto/ Photo gallery http://fgsd.sourceforge.net/FlightGear Scenery Designer - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] LH A320 near crash during crosswind and heavy gust
Hi! Georg Vollnhals wrote: A Lufthansa A 320 touched! the runway with one winglet (damaged) in the final phase of the landing when not only executing a crosswind landing but getting into a heavy unexpected gust. Looks like a horrible situation I would wish never to get into, neither as a pilot nor as a passenger. BTW: is there any possibility to load a special METAR situation into FlightGear? You can use the metar-tool (included in FlightGear) to determine the command line settings based on a METAR message. Is a METAR file of this time (EDDH, Saturday 01.Febr.2008, 14:00) available anywhere? According to http://adds.aviationweather.gov/metars/index.php these were the METARs for EDDH around that time: EDDH 011450Z 29027G40KT 8000 BKN035 07/01 Q0991 TEMPO 30035G55KT EDDH 011420Z 29029G43KT 8000 -SHRA BKN029 07/02 Q0990 TEMPO 30035G55KT EDDH 011350Z 29030G44KT 8000 BKN029 BKN120 07/02 Q0989 TEMPO 30035G55KT 4000 SHRA BKN008 EDDH 011320Z 29029G44KT 8000 -SHRA BKN023 07/03 Q0987 TEMPO 4000 SHRA BKN008 EDDH 011250Z 30030G49KT 8000 FEW015 BKN020 08/04 Q0986 TEMPO 4000 SHRA BKN008 EDDH 011220Z 29028G48KT 9000 -SHRA FEW011 BKN014 07/05 Q0984 TEMPO 29035G55KT 4000 SHRA BKN008 Temporary gusts up to 55 knots...nothing more to say about that... Cheers, Ralf - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] PNG files in CVS repository
* Frederic Bouvier -- Sunday 02 March 2008: So I would like owners to change the status themselves. Done for the bo105 files. On a more general note, it seems that every new directory in the CVS repository has permition problems that need to be fixed manually. Yes, that's annoying. A new dir gets the permissions of the creator, and nobody else can commit anything in them. m. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] [PREVIEW] Nellis AFB (KLSV)
hi, I just can't wait it to be finished (one or two more weeks), here is a preview of Nellis AFB (KLSV). http://croo.murgl.org/fgfs/scenery/KLSV-page/index.html Alexis - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [PREVIEW] Nellis AFB (KLSV)
On Sun, 2008-03-02 at 18:40 +0100, alexis bory wrote: hi, I just can't wait it to be finished (one or two more weeks), here is a preview of Nellis AFB (KLSV). http://croo.murgl.org/fgfs/scenery/KLSV-page/index.html Alexis Looks really good! And brings back some memories, on the little apron where the kc135s are parked I once stood between an F-4G and an F-4N, both running engines in full afterburner! Ron - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] PNG files in CVS repository
Melchior FRANZ a écrit : * Frederic Bouvier -- Sunday 02 March 2008: So I would like owners to change the status themselves. Done for the bo105 files. I managed to fix all other png files located under aircrafts There are still some thumbnail.jpg in some directories that need to be fixed too. -Fred -- Frédéric Bouvier http://my.fotolia.com/frfoto/ Photo gallery http://fgsd.sourceforge.net/FlightGear Scenery Designer - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] tree problems ...
--- SydSandy wrote: I know the differences between tree species , LeeE ,thats not the problem ... if I set a certain tree texture for a terrain type ... for example , I have 2 meter high shrub trees for the ShrubCover/ShrubGrassCover/ScrubCover. When I fly over the area , it is covered by mixed forest... I few south and there are shrub cover trees on a DeciduousNeedleCover material patch. The ground texture changes accordingly , just not the tree textures ... and yet I see tree sizes change correctly at the material boundaries I hadn't reaaly noticed this effect until I started flying around and checking terrain using geod.info so didn't expect it to jump out at anyone else Sorry for the delay in replying, I've been away ski-touring all week, so haven't been on email. Though I've still to look at the code in detail, I'm almost certain that this will be a bug in my tree shader code. I suspect that the same tree texture strip is being used for all the trees on a tile/quad. Could you give me a starting lon/lat and a flightplan that shows the problem? -Stuart __ Sent from Yahoo! Mail. A Smarter Inbox. http://uk.docs.yahoo.com/nowyoucan.html - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [PREVIEW] Nellis AFB (KLSV)
On Sun, 02 Mar 2008 18:40:43 +0100 alexis bory wrote: hi, I just can't wait it to be finished (one or two more weeks), here is a preview of Nellis AFB (KLSV). http://croo.murgl.org/fgfs/scenery/KLSV-page/index.html This is gorgeous stuff. Were you stationed there? Went there for an air show? If neither, where have you been getting the images/information to model the places you've worked on? Cheers, -c -- Chris Metzler [EMAIL PROTECTED] (remove snip-me. to email) As a child I understood how to give; I have forgotten this grace since I have become civilized. - Chief Luther Standing Bear signature.asc Description: PGP signature - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Request for Blender tutorials
* Melchior FRANZ -- Sunday 02 March 2008: BTW: I just wrote a simple script that packs manually UV mapped objects onto a texture square. That's committed now under ./utils/Modeller/uv_pack.py. Follow the instructions in the file, and please report problems. It turns an empty texture in something like this: http://members.aon.at/mfranz/uvmap.jpg [19.0 kB] You see a colored rectangle for every mapping. Unfortunately, it's ATM moment not possible to show all mappings -- you have to select them to get them displayed. There still a lot of free room, but I don't think that's bad. One always needs room to add new mappings later, anyway. :-) m. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] tree problems ...
On Sun, 2 Mar 2008 18:00:46 + (GMT) Stuart Buchanan [EMAIL PROTECTED] wrote: --- SydSandy wrote: I know the differences between tree species , LeeE ,thats not the problem ... if I set a certain tree texture for a terrain type ... for example , I have 2 meter high shrub trees for the ShrubCover/ShrubGrassCover/ScrubCover. When I fly over the area , it is covered by mixed forest... I few south and there are shrub cover trees on a DeciduousNeedleCover material patch. The ground texture changes accordingly , just not the tree textures ... and yet I see tree sizes change correctly at the material boundaries I hadn't reaaly noticed this effect until I started flying around and checking terrain using geod.info so didn't expect it to jump out at anyone else Sorry for the delay in replying, I've been away ski-touring all week, so haven't been on email. Though I've still to look at the code in detail, I'm almost certain that this will be a bug in my tree shader code. I suspect that the same tree texture strip is being used for all the trees on a tile/quad. Could you give me a starting lon/lat and a flightplan that shows the problem? -Stuart Hi Stuart, The most noticeable strange behaviour is south of KSFO , along the coast ... you can see changes in tree size and density at material borders , so that seems to work properly , but the selected tree texture seems wrong in places ... Cheers -- SydSandy [EMAIL PROTECTED] - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] electrical updates to kt70.xml break it
Ron Jensen wrote: On Sat, 2008-03-01 at 20:37 -0700, dave perry wrote: I just noticed that the recent electrical updates to the kt170.xml submitted by Ron Jenson make the kt70 bright white if the instrument lights are turned on in the pa24-250 and the pa28-161. This is because the material animation factor should be between 0 and 1 and this change makes it equal to the output voltage from the buss (usually either 14 or 28 volts in most light AC). factor-propsystems/electrical/outputs/instrument-lights/factor-prop This saturates the material red, green, blue values. snip Ron, is there a reason this needed to be changed for the kt70? Hi Dave, The change was to make the KT-70 only work when the electrical system was turned on. The old setting of /controls/lighting/panel-norm was wrong, and needed to be changed to something based on the electical system. In all the electrical systems I have done, bus_volts is always the voltage that results when a switch connects the item to a bus. That way I can model the impact of the loads when the bus is supplied only by the battery. That is, if the pilot sits on the ramp with all the lights on and the radios on, etc., then the battery will slowly discharge and the voltage on the bus will slowly drop. If I need to have a normalized value for a material animation, I normalize it in nasal and do a setprop for the normalized value. Before your change, that was setprop(/controls/lighting/panel-norm, bus_volts * 0.071428571 * (1.0 - factor)); where the term (1.0-factor) implements the dimmer. That was so I would not have to change the kt70.xml file. All the other panel objects illuminated by the instrument lights have their material factor controlled by setprop(/sim/model/material/instruments/factor, bus_volts * 0.071428571 * (1.0 - factor)); Notice that, either way, this means that the instrument lights will also slowly get dimmer as the loads discharges the battery. The number 0.071428571 is 1/14 and normalizes for the maximum voltage. The electrical systems I use normalize the property systems/electrical/outputs/instrument-lights. By normalizing the /system/electrical/output/... property, the battery discharge is no longer going to dim the instrument lights. I didn't realize you were using the KT70 or I would have verifed it worked on your planes, too. I don't like the property /sim/model/material/instruments/factor. I feel its in the wrong place, and isn't well named, and using both systems/electrical/outputs/instrument-lights and sim/model/material/instruments/factor is redundant. It is not redundant if you are trying to model a battery that can discharge which is the nature of real batteries. The fact that we need to normalize is an artifact of the material animation implementation, not a property of the electrical system. Using two properties here lets the battery, switches, load impact, and dimmers all be realistically taken into account. The artifact created by our implementation of material animation is then accommodated by the sim/model/material/instruments/factor. Normalizing /system/electrical/outputs/instrument-lights to a number between 0 and 1 means is is no longer an electrical output. It is in fact a model material factor. A grep thru CVS show there are only 5 aircraft using /sim/model/material/instruments/factor now. Most aircraft are using some variant of systems/electrical/outputs/instrument-lights. I'd like to use that as a normalized value to allow instruments to just work regardless of the system voltage modelled. What should be the standard for instrument lighting properties? Ron Ron, I am not sure what the standard should be. I just went through the Instruments-3d sub folders and (if I counted correctly) 24 of them use sim/model/material/instruments/factor while 10 use systems/electrical/outputs/instrument-lights to change the emission material properties. The remainder do not adjust the material properties. I gave my reasons for having a factor that represents the voltage separate from the normalized factor for the emission material property. I just looked at pa24-electrical.nas and I believe I can model the desired switch, dimmer, and battery discharge dimming using either approach. But I find it distasteful to assign a material factor between 0 and 1 to a property in /systems/electrical/output/... . What do the rest of the team think? Am I just being pedantic? - Dave - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Request for Blender tutorials
On Sunday 02 March 2008 13:21, Melchior FRANZ wrote: * LeeE -- Sunday 02 March 2008: Gradually making some progress with Blender though. BTW: I just wrote a simple script that packs manually UV mapped objects onto a texture square. I'll publish it as soon as it's ready (later today :-). Works like this: - map all objects individually, choosing the best unwrapping method for the object and the ideal mapping size - select all objects that you want to map on one texture (e.g. by selecting one, and choosing Select-Linked-Material for all fuselage objects) - call the script: this packs the maps of all selected objects on a square and scales them up as much as possible using the same factor - export to SVG (I need yet to rewrite the SVG exporter -- the included one isn't good enough :-) m. This just for entertainment:) I thought I'd mostly cracked it earlier today. Working on the YF-23 and using the upper fuselage/wing surface object I managed to produce a wire-frame type texture template from the unwrap that looked reasonable, with no overlaps etc, by saving the UV unwrap layout to a .tga. Then I coloured in some of the polys and added some reference lines to the .tga texture, saved it as .rgb and, back in Blender, applied it to the model. I then saved it as .ac and when I loaded it into AC3D to check that the texture had 'stuck' it looked fine:) It was only when I started work on the proper texture and came to mirror one side of the fuselage nacelle colouring to the other that I realised that not only was the unwrap rotated slightly but it was also very slightly banana shaped - the centerline was actually curved - lol:) I guessed that this was because there was no defined axis/edge/vertex starting datum/origin and the unwrap has to start somewhere, so I defined a seam down the centerline to set a starting datum/origin. This split the unwrap into two halves, which I expected, but both were still rotated a little bit and the left side was very slightly longer than the right side - doh! You've just got to laugh sometimes:) On a more serious note, does anyone know if any of the object formats supported by FG support multiple textures? For example, would any of them allow me to apply an overall base texture, using one projection, say top-view orthographic, and then apply smaller finite scope texture patches using different projections e.g. side-view ortho? This is more like the way I'm used to applying textures in 3D but the .ac format doesn't allow this. I had a look through the OSG wiki but couldn't find any basic object format specs/features. I haven't tried it yet, but can anyone tell me if it's possible to apply multiple textures in this way in Blender, and then 'bake' it all into a single uv unwrap texture? LeeE - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] ***SPAM*** Re: [PREVIEW] Nellis AFB (KLSV)
Chris Metzler wrote: On Sun, 02 Mar 2008 18:40:43 +0100 alexis bory wrote: hi, I just can't wait it to be finished (one or two more weeks), here is a preview of Nellis AFB (KLSV). http://croo.murgl.org/fgfs/scenery/KLSV-page/index.html This is gorgeous stuff. Were you stationed there? Went there for an air show? If neither, where have you been getting the images/information to model the places you've worked on? Hi Chris, ... And now the price for having the best pictures of Nellis is awarded to ... Microsoft ! Thank you Mister Bill ! http://maps.live.com/default.aspx?v=2cp=q183035dc7n3style=olvl=2scene=5065706#JnE9eXAubmVsbGlzK2FmYiU3ZXNzdC4wJTdlcGcuMSZiYj0zNi4yMzE3NTMxNTcxMTY0JTdlLTExNS4wNDc0NDI3Mzc3OTklN2UzNi4yMjkwNzY4OTMzMDM2JTdlLTExNS4wNDk5MDY0NTA5Nzk= Some other pictures are gathered here and there on the web. Well, I'd like (plan) to go there for an air show (or the rest of my life), but for now I'm still living in south of France. Alexis - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] electrical updates to kt70.xml break it
On Sun, 2008-03-02 at 14:01 -0700, dave perry wrote: Ron Jensen wrote: On Sat, 2008-03-01 at 20:37 -0700, dave perry wrote: snip In all the electrical systems I have done, bus_volts is always the voltage that results when a switch connects the item to a bus. That way I can model the impact of the loads when the bus is supplied only by the battery. That is, if the pilot sits on the ramp with all the lights on and the radios on, etc., then the battery will slowly discharge and the voltage on the bus will slowly drop. If I need to have a normalized value for a material animation, I normalize it in nasal and do a setprop for the normalized value. Before your change, that was setprop(/controls/lighting/panel-norm, bus_volts * 0.071428571 * (1.0 - factor)); where the term (1.0-factor) implements the dimmer. That was so I would not have to change the kt70.xml file. My point was factor should be /controls/lighting/panel-norm. That is, this property controls the intesity of the lighting. It is the knob. So we would have setprop(/systems/electrical/outputs/instrument-lights, bus_volts * 1/MAX_BUS_VOLT * getprop(/controls/lighting/panel-norm)); All the other panel objects illuminated by the instrument lights have their material factor controlled by setprop(/sim/model/material/instruments/factor, bus_volts * 0.071428571 * (1.0 - factor)); Notice that, either way, this means that the instrument lights will also slowly get dimmer as the loads discharges the battery. The number 0.071428571 is 1/14 and normalizes for the maximum voltage. The electrical systems I use normalize the property systems/electrical/outputs/instrument-lights. By normalizing the /system/electrical/output/... property, the battery discharge is no longer going to dim the instrument lights. That is not correct. In my formula above, and your instruments using /sim/model/instruments/factor, the properties are normalized. I didn't realize you were using the KT70 or I would have verifed it worked on your planes, too. I don't like the property /sim/model/material/instruments/factor. I feel its in the wrong place, and isn't well named, and using both systems/electrical/outputs/instrument-lights and sim/model/material/instruments/factor is redundant. It is not redundant if you are trying to model a battery that can discharge which is the nature of real batteries. The fact that we need to normalize is an artifact of the material animation implementation, not a property of the electrical system. Using two properties here lets the battery, switches, load impact, and dimmers all be realistically taken into account. The artifact created by our implementation of material animation is then accommodated by the sim/model/material/instruments/factor. Normalizing /system/electrical/outputs/instrument-lights to a number between 0 and 1 means is is no longer an electrical output. It is in fact a model material factor. A grep thru CVS show there are only 5 aircraft using /sim/model/material/instruments/factor now. Most aircraft are using some variant of systems/electrical/outputs/instrument-lights. I'd like to use that as a normalized value to allow instruments to just work regardless of the system voltage modelled. What should be the standard for instrument lighting properties? I am not sure what the standard should be. I just went through the Instruments-3d sub folders and (if I counted correctly) 24 of them use sim/model/material/instruments/factor while 10 use systems/electrical/outputs/instrument-lights to change the emission material properties. The remainder do not adjust the material properties. I gave my reasons for having a factor that represents the voltage separate from the normalized factor for the emission material property. I just looked at pa24-electrical.nas and I believe I can model the desired switch, dimmer, and battery discharge dimming using either approach. But I find it distasteful to assign a material factor between 0 and 1 to a property in /systems/electrical/output/... . What do the rest of the team think? Am I just being pedantic? - Dave Perhaps we could settle on /system/electrical/outputs/instrument-lights-norm? Ron - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] LH A320 near crash during crosswind and heavy gust
Hi, BTW: is there any possibility to load a special METAR situation into FlightGear? Is a METAR file of this time (EDDH, Saturday 01.Febr.2008, 14:00) available anywhere? I noticed it too, and followed a discussion at www.flightsimulation.ch about. I flew at this day too in FGFS but there was something important thing missing, which was in reality the cause of this incident: turbulences and gusts! In FGFS with real weather fetch there is a homogeneous wind. O.k., I can set the turbulences manually, but then I have no METAR-Datas. Regards HHS still in work: http://www.hoerbird.net/galerie.html But already done: http://www.hoerbird.net/reisen.html __ Ihre erste Baustelle? Wissenswertes für Bastler und Hobby Handwerker. www.yahoo.de/clever - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] electrical updates to kt70.xml break it
On Sun, 02 Mar 2008 15:04:45 -0700 Ron Jensen [EMAIL PROTECTED] wrote: On Sun, 2008-03-02 at 14:01 -0700, dave perry wrote: Ron Jensen wrote: On Sat, 2008-03-01 at 20:37 -0700, dave perry wrote: By normalizing the /system/electrical/output/... property, the battery discharge is no longer going to dim the instrument lights. I have no problem dimming the instrument-lights , based on percent of max voltage * dimmer factor ... I use : setprop(outPut~instrument-lights,((bus_volts * bus_norm) * INSTR_DIMMER) * srvc); works fine for me ... That is not correct. In my formula above, and your instruments using /sim/model/instruments/factor, the properties are normalized. What do the rest of the team think? Am I just being pedantic? - Dave Perhaps we could settle on /system/electrical/outputs/instrument-lights-norm? Ron I personally dont see why you need to know the exact voltage for light intensity ... but I'll go with instrument-lights-norm if it makes everyone happy.And it makes a lot more sense to make it a part of the electrical system than a separate /sim/model/property for every dimmer switch ... Cheers -- SydSandy [EMAIL PROTECTED] - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] wiki mess
On March 2, 2008 10:53:48 am Georg Vollnhals wrote: Torsten Dreyer schrieb: Am Sonntag, 2. März 2008 14:40 schrieb Gijs de Rooy: You could start with editing if you want. I'm done for now. May I say that after not visiting the wiki site for a while my first impression on the new look was: ***whow*** it looks much better than before! Thanks for the improvement! TOrsten It didn't look too bad before either until someone added a third column. Anyway, this new look is a great improvement indeed. Thank you! Ampere - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] LH A320 near crash during crosswind and heavy gust
Ralf Gerlich schrieb: Hi Ralf, first thank you for your reply and the hints .. and that you corrected the wrong date I gave. Of course it was MARCH, 1 and not February :-/ I did not know the metar tool until now and tried to find out more about how to use it. There is a little help displayed when you start it without any parameters and all the stuff like ./metar -c eddw or ./metar -c eddw -r eddw works fine. Nice tool! But despite searching the docs, the wiki and via Google I could not find any other documentation how to use it together with FlightGear. I want to start FlightGear with a given, older METAR string to have that special weather condition using this metar tool like your proposal. But as constructs like ./fgfs metar -c 'SampleMet.txt' manymore FG-Params failed I tried something more simple like ./fgfs metar -c eddw manymore FG-Params like the help sample $fgfs `metar -e 183 -c loww` but this all does not work. I tried a lot of thinkable variations, but no luck. So I have to ask: 1. Is the use of the metar tool really the only option to get an old METAR string into FlightGear? 2. How do I use it correctly as a Start-Parameter for FlightGear? Of course, there is the possibility to copy the FG-Parameter-Output of metar -c eddw and paste it into my special starter program. But this seems a little too complicated if one wants to set some SPECIAL Metar conditions from a METAR archive. Anyway, thankyou for your help to point to the metar tool and the link for getting some prior METARs. Georg EDDW - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] LH A320 near crash during crosswind and heavy gust
Heiko Schulz schrieb: I flew at this day too in FGFS but there was something important thing missing, which was in reality the cause of this incident: turbulences and gusts! In FGFS with real weather fetch there is a homogeneous wind. O.k., I can set the turbulences manually, but then I have no METAR-Datas. Regards HHS Hi Heiko, good point! This has to be checked. If turbulences really are not carried from METAR to FlightGear weather, then this is a real bug. Hopefully a developer reads your message and is interested in FG weather stuff :-) Georg EDDW - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] LH A320 near crash during crosswind and heavy gust
Melchior FRANZ schrieb: * Georg Vollnhals -- Monday 03 March 2008: $fgfs `metar -e 183 -c loww` Note that these are *backticks*, not single quotes (apostrophes). On bash shells you can also write it as $ fgfs $(metar -e 183 -c loww) 1. Is the use of the metar tool really the only option to get an old METAR string into FlightGear? There's no property or command line option for that AFAIK, but you can use metar for that, too. Just use it first to get the metar string: $ metar -v eddf # v ... verbose ... INPUT: 2008/03/02 22:50 EDDF 022250Z 24012KT -RA FEW020 BKN032 10/09 Q1010 NOSIG Then call metar and fgfs with that: $ fgfs `metar -e 183 -c EDDF 022250Z 24012KT -RA FEW020 BKN032 10/09 Q1010 NOSIG` metar doesn't only fetch metar data, but also parses what you feed it to. It's annoying that one has to specify the airport elevation for the cloud layers to be at the right altitudes, but I didn't want to query the apt.dat DB for metar. It was only meant to be a simple test app for simgear's METAR parser. m. Thank you Melchior, I'll try it with more knowledge :-) When searching for more documentation I read about your metar proxy ... long ago. I think this was the predecessor of the actual metar tool and the METAR capabilities of FG. Georg - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] LH A320 near crash during crosswind and heavy gust
Heiko Schulz schrieb: Here is a pic of the incident: http://www.airliners.net/uf/view.file?id=536882887filename=phpOltUWB.jpg Regards HHS Thank you. This is clear proof how much chance had a hand in this - beside pilot's skills. Georg - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] LH A320 near crash during crosswind and heavy gust
* Georg Vollnhals -- Monday 03 March 2008: When searching for more documentation I read about your metar proxy ... long ago. I think this was the predecessor of the actual metar tool and the METAR capabilities of FG. No. A perl script called metar was the predecessor. Then Erik demanded that I rewrite it in C++ for simgear (we had a metar parser before that, but it was imported from outside, very complex and hard(er) to understand). I wrote the metar proxy later, after someone asked for a built-in feature to replay old metar data. I found that this was a bad idea, and that the already implemented features could handle that already, if a fake NOAA server (the proxy) would just return old data. (I think the metar proxy has only one user, and it's not me. :-) m. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] LH A320 near crash during crosswind and heavy gust
* Georg Vollnhals -- Monday 03 March 2008: $fgfs `metar -e 183 -c loww` Note that these are *backticks*, not single quotes (apostrophes). On bash shells you can also write it as $ fgfs $(metar -e 183 -c loww) 1. Is the use of the metar tool really the only option to get an old METAR string into FlightGear? There's no property or command line option for that AFAIK, but you can use metar for that, too. Just use it first to get the metar string: $ metar -v eddf # v ... verbose ... INPUT: 2008/03/02 22:50 EDDF 022250Z 24012KT -RA FEW020 BKN032 10/09 Q1010 NOSIG Then call metar and fgfs with that: $ fgfs `metar -e 183 -c EDDF 022250Z 24012KT -RA FEW020 BKN032 10/09 Q1010 NOSIG` metar doesn't only fetch metar data, but also parses what you feed it to. It's annoying that one has to specify the airport elevation for the cloud layers to be at the right altitudes, but I didn't want to query the apt.dat DB for metar. It was only meant to be a simple test app for simgear's METAR parser. m. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] wiki mess
Yes, indeed. Nice work. What's left to do is to remove such pages: http://wiki.flightgear.org/flightgear_wiki/index.php?title=FlightGear- Points_of_Interest http://wiki.flightgear.org/flightgear_wiki/index.php?title=Adding_featu res Those who know how to fill in the contents are certainly clever enough to create the page if necessary. Such skeletons are IMHO silly and frustrating. Needless clicks and page loading, only to see that there's *nothing*. Of course, it's a different matter if someone writes, let's say, a page about FDMs, fills in the JSBSim part, and adds only section headers for YASim, UIUC, etc. But headings *only* are bad. m. I wish I had time to help out by adding stuff, but can't right now. However, anyone can feel free to take what they want from the JSBSim web sit and add the appropriate level of documentation on the FlightGear wiki. You can go to any of these places for material: www.jsbsim.org http://jsbsim.sourceforge.net/wiki/ http://jsbsim.wiki.sourceforge.net/ I got tired of placing little bits and pieces of documentation here and there, so I am writing a larger more complete document and will post that on the JSBSim web site when that is done. Jon - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] LH A320 near crash during crosswind and heavy gust
Melchior FRANZ schrieb: ... Then call metar and fgfs with that: $ fgfs `metar -e 183 -c EDDF 022250Z 24012KT -RA FEW020 BKN032 10/09 Q1010 NOSIG` ... Hi Melchior, just for all those reading along I want to approve that your above hint works for me. Starting from the bin directory I tested with your modified line ./fgfs `./metar -e 6 -c EDDW 022250Z 06055KT 0500 +RA FEW020 BKN032 10/09 Q1010 NOSIG` --fg-scenery= ... and a lot more I got the values in FlightGear. Thank you Georg - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] LH A320 near crash during crosswind and heavy gust
Georg Vollnhals schrieb: Heiko Schulz schrieb: I flew at this day too in FGFS but there was something important thing missing, which was in reality the cause of this incident: turbulences and gusts! In FGFS with real weather fetch there is a homogeneous wind. O.k., I can set the turbulences manually, but then I have no METAR-Datas. Regards HHS Hi Heiko, good point! This has to be checked. If turbulences really are not carried from METAR to FlightGear weather, then this is a real bug. Hopefully a developer reads your message and is interested in FG weather stuff :-) Georg EDDW Hello Heiko and all readers, I am back again, having to add something. When I looked at the METAR format I discovered that turbulences are not described, only gusts (like 80/30G20 = wind from 80 deg, 30 knots windspeed, gusts 20 knots). So I am not sure how it is handled within FlightGear. We have that turbulence slider in the weather menu and this value is not affected by the METAR data (as you checked) - but how are gusts handled within FlightGear? Maybe someone with more knowledge than me can acknowledge that tubulence and gusts are two different meteorological phenomenons and should treated different in the sim??? Regards Georg - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] LH A320 near crash during crosswind and heavy gust
Hi, --- Georg Vollnhals [EMAIL PROTECTED] schrieb: Hello Heiko and all readers, I am back again, having to add something. When I looked at the METAR format I discovered that turbulences are not described, only gusts (like 80/30G20 = wind from 80 deg, 30 knots windspeed, gusts 20 knots). So I am not sure how it is handled within FlightGear. We have that turbulence slider in the weather menu and this value is not affected by the METAR data (as you checked) - but how are gusts handled within FlightGear? Maybe someone with more knowledge than me can acknowledge that tubulence and gusts are two different meteorological phenomenons and should treated different in the sim??? Regards Georg Translation: Turbulence = Turbulenz gust = Böe In the case of the LH A320 it was a sudden gust, but it is difficult to say, because the turbulences of the buildings around can cause a gust too. But in FGFS we don't have a gust - it would be nice, such like other weather phenomens affecting aircrafts... Why we don't use the Google summer camp? Would be a chance... still in work: http://www.hoerbird.net/galerie.html But already done: http://www.hoerbird.net/reisen.html Heute schon einen Blick in die Zukunft von E-Mails wagen? Versuchen Sie´s mit dem neuen Yahoo! Mail. www.yahoo.de/mail - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] electrical updates to kt70.xml break it
On Sun, 2008-03-02 at 20:43 -0700, dave perry wrote: snip Perhaps we could settle on /system/electrical/outputs/instrument-lights-norm? Ron This works for me in kt70.xml. I will simply replace /controls/lighting/panel-norm (the original property in kt70.xml) with /system/electrical/outputs/instrument-lights-norm in the pa24-electrical.nas and pa28-electrical.nas. The changed kt70.xml uses this as a material emission factor not an electrical output. I will still have /system/electrical/outputs/instrument-lights as the actual voltage. This will allow for further model tweaks to account for wire IR drop or what ever. Sorry if this appears to be a nit and thanks for the positive constructive tone of this exchange! - Dave Thank you Dave, Now we just need some one to commit then new kt70 changes... The pa24 and pa28 are really nice aircraft, by the way. Ron - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] I am going to terminate mpserver04 - new mpserver?
Hi all, On Fri, Feb 29, 2008 at 03:20:20PM +0100, Csaba Hal?sz wrote: On Fri, Feb 29, 2008 at 3:13 PM, tpalinkas [EMAIL PROTECTED] wrote: We at Allied-Visions GmbH are pondering running an mpserver on one of our servers (with 100 mbit access). We have a few questions regarding to mpservers: - is it useful for the community to have one more mpserver? If you can also run a map server that would be very nice, IMHO. Can anyone tell me how much resources are needed? mpserver: traffic usage (approx)? Perhaps someone has a MRTG/RRD picture??? map server: how much storage is needed and how much traffic would be created (approx.)? Perhaps I have a wonderful solution for this but I need some numbers. Also I need some arguments why this one should be run (perhaps with scientific background (big projects with scientific background)). Regards, Holger -- # ## ## Holger Wirtz Phone : (+49 30) 884299-40 ## ## ## ### ## DFN-Verein Fax : (+49 30) 884299-70 ## ## ## Stresemannstr. 78E-Mail: [EMAIL PROTECTED] ## ## ## ## ### 10963 Berlin # ## ## ## GERMANY WWW : http://www.dfn.de GPG-Fingerprint: ABFA 1F51 DD8D 503C 85DC 0C51 E961 79E2 6685 9BCF - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
