[Flightgear-devel] Weekly CVS Changelog Summary: FlightGear data
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-04-06_10:46:03 (abory) /var/cvs/FlightGear-0.9/data/Aircraft/f-14b/Nasal/gear.nas - Alexis: fixed a couple of nasal bugs.. my fault. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-04-06_10:46:04 (abory) /var/cvs/FlightGear-0.9/data/Aircraft/f-14b/Nasal/hud.nas - Alexis: fixed a couple of nasal bugs.. my fault. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-04-06_11:00:03 (abory) /var/cvs/FlightGear-0.9/data/Aircraft/f-14b/Models/Cockpit/asi.ac - Alexis: minor cosmetic fixes. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-04-06_11:25:22 (abory) /var/cvs/FlightGear-0.9/data/Aircraft/f-14b/Models/Cockpit/asi.ac - Alexis: Cosmetic fix. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-04-06_16:06:06 (abory) /var/cvs/FlightGear-0.9/data/Aircraft/f-14b/Nasal/hud.nas - Alexis: Use simple setprop() and getprop() instead of props.globals.getNode() until we figure out why it doesn't work on only some configs. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-04-08_07:57:19 (helijah) /var/cvs/FlightGear-0.9/data/Aircraft/Starship/Models/Attic/color.rgb /var/cvs/FlightGear-0.9/data/Aircraft/Starship/Models/colors.png /var/cvs/FlightGear-0.9/data/Aircraft/Starship/Models/Attic/glass.rgb /var/cvs/FlightGear-0.9/data/Aircraft/Starship/Models/Attic/leath05.rgb /var/cvs/FlightGear-0.9/data/Aircraft/Starship/Models/prop.png /var/cvs/FlightGear-0.9/data/Aircraft/Starship/Models/Attic/prop.rgb /var/cvs/FlightGear-0.9/data/Aircraft/Starship/Models/starship.ac - new textures PNG, new pilot =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-04-08_07:57:21 (helijah) /var/cvs/FlightGear-0.9/data/Aircraft/Starship/Models/starship.xml /var/cvs/FlightGear-0.9/data/Aircraft/Starship/Models/Attic/wheels.rgb /var/cvs/FlightGear-0.9/data/Aircraft/Starship/Models/Panel/Attic/background.rgb /var/cvs/FlightGear-0.9/data/Aircraft/Starship/Models/Panel/colors.png /var/cvs/FlightGear-0.9/data/Aircraft/Starship/Models/Panel/Attic/leath05.rgb /var/cvs/FlightGear-0.9/data/Aircraft/Starship/Models/Panel/panel.ac /var/cvs/FlightGear-0.9/data/Aircraft/Starship/Models/Panel/panel.xml - new textures PNG, new pilot =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-04-08_07:57:22 (helijah) /var/cvs/FlightGear-0.9/data/Aircraft/Starship/Models/Panel/Instruments/alt/boeing747-400-alt-jw.ac /var/cvs/FlightGear-0.9/data/Aircraft/Starship/Models/Panel/Instruments/alt/boeing747-400-alt-jw.png /var/cvs/FlightGear-0.9/data/Aircraft/Starship/Models/Panel/Instruments/alt/Attic/boeing747-400-alt-jw.rgb /var/cvs/FlightGear-0.9/data/Aircraft/Starship/Models/Panel/Instruments/alt/boeing747-400-bezel-jw.png /var/cvs/FlightGear-0.9/data/Aircraft/Starship/Models/Panel/Instruments/alt/Attic/boeing747-400-bezel-jw.rgb /var/cvs/FlightGear-0.9/data/Aircraft/Starship/Models/Panel/Instruments/alt/digits.png /var/cvs/FlightGear-0.9/data/Aircraft/Starship/Models/Panel/Instruments/alt/Attic/digits.rgb /var/cvs/FlightGear-0.9/data/Aircraft/Starship/Models/Panel/Instruments/asi/boeing747-400-asi-jw.ac /var/cvs/FlightGear-0.9/data/Aircraft/Starship/Models/Panel/Instruments/asi/boeing747-400-asi-jw.png /var/cvs/FlightGear-0.9/data/Aircraft/Starship/Models/Panel/Instruments/asi/Attic/boeing747-400-asi-jw.rgb /var/cvs/FlightGear-0.9/data/Aircraft/Starship/Models/Panel/Instruments/asi/boeing747-400-bezel-jw.png - new textures PNG, new pilot =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-04-08_07:57:23 (helijah) /var/cvs/FlightGear-0.9/data/Aircraft/Starship/Models/Panel/Instruments/asi/Attic/boeing747-400-bezel-jw.rgb /var/cvs/FlightGear-0.9/data/Aircraft/Starship/Models/Panel/Instruments/enav/boeing747-400-efis-common-jw-01.png /var/cvs/FlightGear-0.9/data/Aircraft/Starship/Models/Panel/Instruments/enav/Attic/boeing747-400-efis-common-jw-01.rgb /var/cvs/FlightGear-0.9/data/Aircraft/Starship/Models/Panel/Instruments/enav/boeing747-400-enav-jw-01.png /var/cvs/FlightGear-0.9/data/Aircraft/Starship/Models/Panel/Instruments/enav/Attic/boeing747-400-enav-jw-01.rgb /var/cvs/FlightGear-0.9/data/Aircraft/Starship/Models/Panel/Instruments/enav/boeing747-400-enav-jw-02.png /var/cvs/FlightGear-0.9/data/Aircraft/Starship/Models/Panel/Instruments/enav/Attic/boeing747-400-enav-jw-02.rgb /var/cvs/FlightGear-0.9/data/Aircraft/Starship/Models/Panel/Instruments/enav/boeing747-400-enav-jw.ac /var/cvs/FlightGear-0.9/data/Aircraft/Starship/Models/Panel/Instruments/enav/digits.png /var/cvs/FlightGear-0.9/data/Aircraft/Starship/Models/Panel/Instruments/enav/Attic/digits.rgb /var/cvs/FlightGear-0.9/data/Aircraft/Starship/Models/Panel/Instruments/pfd/ati.png - new textures PNG, new pilot =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-04-08_07:57:24 (helijah)
[Flightgear-devel] Weekly CVS Changelog Summary: FlightGear source
2f585eeea02e2c79d7b1d8c4963bae2d - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Segfault on current HEAD?
On Sat, 2008-04-12 at 14:59 +0100, LeeE wrote: Does it segfault every time or is it inconsistent? I'm about a week Everytime. I'll try rolling back to an older OSG when I get a chance. -- James Sleeman [EMAIL PROTECTED] - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Segfault on current HEAD?
Hi! Everytime. I'll try rolling back to an older OSG when I get a chance. Are you sure you recompiled every single lib using up-to-date sources (CVS/SVN)? I encountered a segfault, as well, but I forgot to recompile simgear. Double check the compilation order, too! Regards, Tobias begin:vcard fn:Tobias Ramforth n:Ramforth;Tobias email;internet:[EMAIL PROTECTED] x-mozilla-html:FALSE version:2.1 end:vcard signature.asc Description: OpenPGP digital signature - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] AI Aircraft Models
* till busch -- Thursday 10 April 2008: Currently Aircraft/ is ~1200 MB on cvs. So yes. I think we can easily afford 100 or 200 MB for cheap ai models. I don't mind spending 200MB for something useful. But I think that 200MB for a mere duplication of existing files is a waste. I'd opt for inclusion of as many AI (lightweight) aircraft as possible. People who try FG, will see other models that they like, and will eventually download them. If it's only about a motivation to download the real aircraft, then a dialog on exit is just as effective. And it's questionable whether crappy/blurry AI aircraft are such a big motivation at all. Maybe just the opposite. And high-quality duplicated AI files are a no-go IMHO. Because you'd then come much closer to the 1200MB. The *.ac and texture files are the biggest parts of an aircraft after all, only instruments and sounds wouldn't be duplicated (and the usually smallish nasal and xml files). Could you propose a more detailed design that would allow all of that? I would volunteer to write the necessary code. A possible solution and compromise could be: - $FG_ROOT/AI/Aircraft/ contains stripped down (model details and texture sizes) of all relevant aircraft, no matter if the aircraft is installed. Non-relevant ones are Ogel and Colditz, for example). - there's a property/option that controls whether such rather low quality models are used or not. They are somewhat ugly, but may or may not be considered better than nothing. - as soon as the real aircraft is installed ($FG_ROOT/Aircraft/), this takes precedence over AI/Aircraft/. Proper LOD setup in $FG_ROOT/Aircraft/*/ makes sure that this comes at low cost in the MP case. An additional flag disable-on-mp/ or something added to an animation could be used to completely remove it in the MP case. (We might need a way to scale down textures, too?) I don't like the current setup much where MP-LOD is split off the real aircraft and resides in a separate dir. That's somewhat unclean. - aircraft could contain an indicator of their costs, so that one could set an option at startup to only display aircraft cheaper than some threshold. m. - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Segfault on current HEAD?
On Sunday, 13. April 2008, James Sleeman wrote: On Sat, 2008-04-12 at 14:59 +0100, LeeE wrote: Does it segfault every time or is it inconsistent? I'm about a week Everytime. I'll try rolling back to an older OSG when I get a chance. Just a note: I'm having the same problem since 2.3.7. A workaround is to just create a symlink from osgPlugins-2.3.8 to osgPlugins-2.3.6. Probably something in the build system changed, so one has to call an extra command (maybe make plugins_install or something like that?). Will investigate further when I'm back from enjoying the fine weather here :) Stefan - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Segfault on current HEAD?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stefan Seifert wrote: | On Sunday, 13. April 2008, James Sleeman wrote: | On Sat, 2008-04-12 at 14:59 +0100, LeeE wrote: | Does it segfault every time or is it inconsistent? I'm about a week | Everytime. I'll try rolling back to an older OSG when I get a chance. | | Just a note: I'm having the same problem since 2.3.7. A workaround is to just | create a symlink from osgPlugins-2.3.8 to osgPlugins-2.3.6. | Probably something in the build system changed, so one has to call an extra | command (maybe make plugins_install or something like that?). Will | investigate further when I'm back from enjoying the fine weather here :) | | Stefan I'm not seeing this with a very recent OSG (Friday). Given your workaround, I would suggest that there's an inconsistency between the version number in the code and that in the cmake build / install system; you should try running cmake or ccmake again and then rebuild OSG. Also, I always run ldconfig after installing a new build of OSG. Tim -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFIAny+eDhWHdXrDRURAslrAKCeaPrFWQWSk/q+mSUsnHMJIP6jpACgzAA6 uCjCOBcy3Hv+bkcEQKtOJNA= =86qT -END PGP SIGNATURE- - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Trees
My apologies to all the tree-huggers out there ;-) but how does one disable all the trees? Great for mountains and forests scenery tiles; however last month when I was up at Ames don't recall all that lumber around the runway and know that NASA will not care for all the trees around KDFW when they start the research phase of the project. Regards JW - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
