Re: [Flightgear-devel] Duplicate files in base package
On Fri, 2010-02-26 at 21:13 +, Alan Teeder wrote: > I still support the idea common shared directories idea for such things as > instruments > > Alan This is a nice, happy thought. But in the real world it hasn't worked out so well. Since we model such a huge variety of aircraft, and different FDMs and systems provide different outputs, our common instrument folders would need to be huge to cover all the different kinds of instruments, plus variations and modifications to fit each individual aircraft's structure. It makes more sense to me to house each instrument with its aircraft. Also, each instrument is commonly comprised of three separate files, the texture (png), the model (ac) and the animations (xml). Needing a change in any one of these really necessitates all three being in the same place. So even if the texture and the model are the same, using a different animation file means the .png and .ac are duplicates, its true, but this also ensures the model and or texture don't change in ways that are incompatible with the animation file. -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] build on Windows; dependencies?
On Fri, 2010-02-26 at 16:39 -0600, stan.mar...@l-3com.com wrote: > Update on my own post, regarding the "missing" files... > > All the files which moved (apparently) from ATC to ATCDCL were > corrected. > > A few others were found in other locations in the source tree. > > I am left with references to the following files which do not occur in > the source tree: > > src/Scenery/newcache.cxx > src/GUI/puList.cxx > src/GUI/trackball.c > src/GUI/sgVec3Slider.cxx > src/Scenery/tileentry.cxx > src/Main/FGManipulator.cxx > > I have not found these files or anything which resembled these names. I > am unsure if these are needed for FlightGearLib or not. I am excluding > these from the build until I see indications that they are in fact > needed. Advice is welcome. > > Stan src/Scenery/newcache.cxx and src/Scenery/tileentry.cxx were deleted Wed May 14 22:10:08 2008 UTC http://cvs.flightgear.org/viewvc/source/src/Scenery/?hideattic=0 src/GUI/puList.cxx was removed Tue Mar 11 15:58:58 2008 UTC src/GUI/trackball.c deleted Wed Jul 9 12:37:54 2008 UTC src/GUI/sgVec3Slider.cxx removed Sun Apr 27 17:56:05 2008 UTC http://cvs.flightgear.org/viewvc/source/src/GUI/?hideattic=0 src/Main/FGManipulator.cxx was removed Tue Nov 18 22:45:57 2008 UTC http://cvs.flightgear.org/viewvc/source/src/Main/?hideattic=0 So assuming your source code checkout is later than 18 Nov 2008 you should be good. I don't recall the exact date of 1.9.0 but the version number was bumped Fri Dec 19 20:40:29 2008 UTC so you should be good in ignoring these files. Ron -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] build on Windows; dependencies?
Update on my own post, regarding the "missing" files... All the files which moved (apparently) from ATC to ATCDCL were corrected. A few others were found in other locations in the source tree. I am left with references to the following files which do not occur in the source tree: src/Scenery/newcache.cxx src/GUI/puList.cxx src/GUI/trackball.c src/GUI/sgVec3Slider.cxx src/Scenery/tileentry.cxx src/Main/FGManipulator.cxx I have not found these files or anything which resembled these names. I am unsure if these are needed for FlightGearLib or not. I am excluding these from the build until I see indications that they are in fact needed. Advice is welcome. Stan -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] build on Windows; dependencies?
On Fri, Feb 26, 2010 at 2:01 PM, Christian Menge wrote: > Hi Guys, > > Few months back we spent a couple days trying to compile FG on Windows using > the FG Wiki and did not have any luck. This is a very frustrating point for > people who only work with windows and would like to contribute but don't > have a clear document or path on how to make this work. > > Geoff, I appreciate your efforts in creating your own custom build process > but we could not get your files to work. > > I'm sure there are many developers running Windows that can provide > effective contribution to this project but can't because of the difficult > build process. > > Can someone explain why this has not been addressed? > > Thanks! > > Christian > > FreedomWorks Inc. > The external dependencies add to the difficulty somewhat. It's pretty straight-forward to build FG on Linux since, for most distros, the external dependencies are just a "yum install [packagename]" (or other package manager) away. For Windows, you may have to hunt down and compile many of these dependencies yourself. Where the resulting files are to be placed may require some time deciphering the MSVC project files and repeated attempts to get a successful FG compile. I suspect another cause for difficulty is that most of the FG developers with CVS commit privileges are using Linux and the few Windows FG developers each keep their own build environment updated incrementally without changes going into CVS promptly. Several times I have found that the MSVC project files in CVS do not reflect the current file/directory structure of the source code. Checking today, I see that FlightGear.vcproj was updated 5 days ago. Maybe it's good to go. Maybe I've just had unlucky timing in the past. This evening, I'll try to follow the wiki instructions (http://wiki.flightgear.org/index.php/Building_FlightGear_-_Windows) again and apply any corrections I can. I noticed a few important updates to that page over the last few months and would like to thank everyone who has helped to improve it. I'm not an FG developer but I love this flight simulator and would like to help get interested Windows developers on board when I have the time (which I don't ;). -Reagan -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Duplicate files in base package
-- From: "Gene Buckle" Sent: Friday, February 26, 2010 8:29 PM To: "FlightGear developers discussions" Subject: Re: [Flightgear-devel] Duplicate files in base package > On Fri, 26 Feb 2010, Alan Teeder wrote: > >>> Maybe it's time to use what's already there? >>> >> One problem which springs to mind is that there must be many same name >> files >> (e.g. HSI.xml and its related HSI.ac) which are specific to one aircraft >> and >> are in fact entirely different. >> >> These will need to be renamed per aircraft (e.g SpitfireMKX.HSI) or per >> instrument manufacturer (e.g. FD108HSI). >> > It's my understanding that the duplicate checker operates on checksums not > filenames. > > Apologies. The upper-lower case duplicate name problem was in my stupid head. I still support the idea common shared directories idea for such things as instruments Alan -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Duplicate files in base package
On Fri, 26 Feb 2010, Alan Teeder wrote: >> Maybe it's time to use what's already there? >> > One problem which springs to mind is that there must be many same name files > (e.g. HSI.xml and its related HSI.ac) which are specific to one aircraft and > are in fact entirely different. > > These will need to be renamed per aircraft (e.g SpitfireMKX.HSI) or per > instrument manufacturer (e.g. FD108HSI). > It's my understanding that the duplicate checker operates on checksums not filenames. g. -- Proud owner of F-15C 80-0007 http://www.f15sim.com - The only one of its kind. http://www.simpits.org/geneb - The Me-109F/X Project ScarletDME - The red hot Data Management Environment A Multi-Value database for the masses, not the classes. http://www.scarletdme.org - Get it _today_! -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] build on Windows; dependencies?
Hi Guys, Few months back we spent a couple days trying to compile FG on Windows using the FG Wiki and did not have any luck. This is a very frustrating point for people who only work with windows and would like to contribute but don't have a clear document or path on how to make this work. Geoff, I appreciate your efforts in creating your own custom build process but we could not get your files to work. I'm sure there are many developers running Windows that can provide effective contribution to this project but can't because of the difficult build process. Can someone explain why this has not been addressed? Thanks! Christian FreedomWorks Inc. US: 609-858-2290 Canada: 905-228-0285 Fax: 347-296-3666 Email: christ...@freedomworks.ca www.FreedomWorks.ca -Original Message- From: stan.mar...@l-3com.com [mailto:stan.mar...@l-3com.com] Sent: Friday, February 26, 2010 2:29 PM To: FlightGear developers discussions Subject: Re: [Flightgear-devel] build on Windows; dependencies? Csaba and Geoff, Thanks for your replies. I should have specified that I am trying to build FlightGear 1.9.1, downloaded 2/3/2010 from flightgear.org at which time it was the most current release (I see 2.0.0 is now out). I initially started to build just SimGear, same version, downloaded from www.simgear.org on the same day, using the similar solution file found under simgear/projects/VC8. I am using the VS8 solution files found in the projects subdirectory (projects/VC8) to build both FlightGear and SimGear. Pthreads is needed in SimGear sgthread.hxx. Per Geoff's post, they are required for SGThread. As you say, if SGThread is no longer required, it could be deleted and the dependency on pthread thereby removed. Meanwhile I downloaded POSIX Threads for Win32 from http://sourceware.org/pthreads-win32/ which got me over that problem. The Boost library was procured and having the headers solved my build issues. I'll still gently suggest that maybe Boost should be avoided if the use is minimal, which it currently is. If there is consensus in the community that it should be used, then it probably should be used extensively. Might as well! I am having another problem with 1.9.1, however. The project for FlightGearLib includes a number of files which appear to have moved in the download source tree. All were supposedly under the src/ATC path. They seem to have moved to src/ATCDCL directory instead. Here are the offenders: AIEntity.cxx AIGAVFRTraffic.cxx AILocalTraffic.cxx AIMgr.cxx AIPlane.cxx approach.cxx ATC.cxx ATCDialog.cxx ATCmgr.cxx ATCProjection.cxx ATCutils.cxx ATCvoice.cxx atis.cxx commlist.cxx ground.cxx tower.cxx transmission.cxx transmissionlist.cxx A few other files are turning up missing as well: src/FDM/Balloon.cxx src/fdm/balloon/BalloonSim.cpp src/FDM/MagicCarpet.cxx src/Scenery/newcache.cxx src/GUI/puList.cxx src/GUI/sgVec3Slider.cxx src/Scenery/tileentry.cxx src/Airports/trafficcontrol.cxx src/Main/FGManipulator.cxx trafficcontrol.cxx appears to be the lone occupant of src/ATC. I haven't found the others yet. Stan -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Duplicate files in base package
-- From: "Stefan Seifert" Sent: Friday, February 26, 2010 5:26 PM To: "FlightGear developers discussions" Subject: Re: [Flightgear-devel] Duplicate files in base package > This repeatedly strikes me as problems that Linux packages managers have > solved completely, elegantly and simply a long time ago. They support > dependencies, so commonly used parts only have to be installed once. They > support versioning, making upgrades simple and safe by for example not > allowing binaries to be installed alongside incompatible data. With > systems > like the openSUSE build service, users can even create their own > repositories > and link to others. Those systems even support mirrors to spread > downloads. > > Maybe it's time to use what's already there? > One problem which springs to mind is that there must be many same name files (e.g. HSI.xml and its related HSI.ac) which are specific to one aircraft and are in fact entirely different. These will need to be renamed per aircraft (e.g SpitfireMKX.HSI) or per instrument manufacturer (e.g. FD108HSI). However if a common library could be set up a great saving would be made, not only in unused duplicates, but in the ability of designers to find already completed instruments. -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] build on Windows; dependencies?
Csaba and Geoff, Thanks for your replies. I should have specified that I am trying to build FlightGear 1.9.1, downloaded 2/3/2010 from flightgear.org at which time it was the most current release (I see 2.0.0 is now out). I initially started to build just SimGear, same version, downloaded from www.simgear.org on the same day, using the similar solution file found under simgear/projects/VC8. I am using the VS8 solution files found in the projects subdirectory (projects/VC8) to build both FlightGear and SimGear. Pthreads is needed in SimGear sgthread.hxx. Per Geoff's post, they are required for SGThread. As you say, if SGThread is no longer required, it could be deleted and the dependency on pthread thereby removed. Meanwhile I downloaded POSIX Threads for Win32 from http://sourceware.org/pthreads-win32/ which got me over that problem. The Boost library was procured and having the headers solved my build issues. I'll still gently suggest that maybe Boost should be avoided if the use is minimal, which it currently is. If there is consensus in the community that it should be used, then it probably should be used extensively. Might as well! I am having another problem with 1.9.1, however. The project for FlightGearLib includes a number of files which appear to have moved in the download source tree. All were supposedly under the src/ATC path. They seem to have moved to src/ATCDCL directory instead. Here are the offenders: AIEntity.cxx AIGAVFRTraffic.cxx AILocalTraffic.cxx AIMgr.cxx AIPlane.cxx approach.cxx ATC.cxx ATCDialog.cxx ATCmgr.cxx ATCProjection.cxx ATCutils.cxx ATCvoice.cxx atis.cxx commlist.cxx ground.cxx tower.cxx transmission.cxx transmissionlist.cxx A few other files are turning up missing as well: src/FDM/Balloon.cxx src/fdm/balloon/BalloonSim.cpp src/FDM/MagicCarpet.cxx src/Scenery/newcache.cxx src/GUI/puList.cxx src/GUI/sgVec3Slider.cxx src/Scenery/tileentry.cxx src/Airports/trafficcontrol.cxx src/Main/FGManipulator.cxx trafficcontrol.cxx appears to be the lone occupant of src/ATC. I haven't found the others yet. Stan -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] flightgear-bugs and the dev list
On 26 Feb 2010, at 15:40, Curtis Olson wrote: > Are you talking about forwarding your bug tracker emails to the > flightgear-devel list? I would be against that. This is effectively signing > up a bunch of people to a new mailing list they didn't ask for and is > typically considered to be somewhere along the continuum between "bad form" > and "spam". > > We can certainly mention the existence of the other mailing list and folks > can be free to subscribe to it if they like I'd prefer a flightgear-bugs list, it's easy to subscribe to lists (and 'opt-in'), slightly (thought not much) harder to filter out auto-generated emails from in a mail client, and for people reading the archives online, it would be pure noise to send such things to the main -devel list. James -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Duplicate files in base package
On Friday 26 February 2010 17:16:38 Detlef Faber wrote: > I guess most duplicate files are instruments which are not in the > generic folder. > Of course it would be desireable to have them all in one place and > reference to there, but that would cause severe problems with the > aircraft downloads, because every aircraft on the download page would > need a second package for instruments which are not in the Base > package. > Including all these Instruments in the Base Package would greatly > increase the download size. This repeatedly strikes me as problems that Linux packages managers have solved completely, elegantly and simply a long time ago. They support dependencies, so commonly used parts only have to be installed once. They support versioning, making upgrades simple and safe by for example not allowing binaries to be installed alongside incompatible data. With systems like the openSUSE build service, users can even create their own repositories and link to others. Those systems even support mirrors to spread downloads. Maybe it's time to use what's already there? Stefan -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Multiplayer weirdness...
Hello all -- While flying Dave Culp's T2C using the windows 2.0.0 release candidate on a Vista system, taking off and landing at KNUQ and flying north towards KSFO before looping back, I observed the following console output. Also, the Pilots List disappeared at one point and returned about 30 seconds later. Here's the output: = Property systems/hook/tailhook-cmd-norm is already defined. Property systems/NWS/engaged is already defined. Property systems/crash-detect/crashed is already defined. Property systems/hook/tailhook-cmd-norm is already defined. Property systems/hook/tailhook-length-ft is already defined. Property systems/hook/tailhook-pos-min-deg is already defined. Property systems/hook/tailhook-pos-max-deg is already defined. Property systems/hook/tailhook-offset-x-in is already defined. Property systems/hook/tailhook-offset-y-in is already defined. Property systems/hook/tailhook-offset-z-in is already defined. Property systems/hook/tailhook-pos-deg is already defined. Property systems/NWS/engaged is already defined. Property aero/alpha_buffet/hertz is already defined. Property aero/alpha_buffet/sine_wave is already defined. Property systems/armament/release is already defined. Property systems/crash-detect/crashed is already defined. Property systems/beacon/frequency is already defined. loading scenario 'nimitz_demo' creating 3D noise texture... DONE FGMultiplayMgr::MP_ProcessData: No such file or directory FGMultiplayMgr::MP_ProcessData: No such file or directory FGMultiplayMgr::MP_ProcessData: No such file or directory MP model not installed: ←[31;1mAircraft/Fouga/Models/Zephyr-CM175.xml←[m Program's vertex attrib binding 10, usrAttr1 Program's vertex attrib binding 11, usrAttr2 FGMultiplayMgr::MP_ProcessData: No such file or directory PNG lib warning : Incomplete compressed datastream in iCCP chunk PNG lib warning : Profile size field missing from iCCP chunk FGMultiplayMgr::MP_ProcessData: No such file or directory FGMultiplayMgr::MP_ProcessData: No such file or directory FGMultiplayMgr::MP_ProcessData: No such file or directory floating point error in math.sin(): at C:/Program Files/FlightGear/data/Nasal/geo.nas, line 186 ←[33;40;1m#0←[m ←[31m0.6549864186760226←[m ←[33;40;1m#1←[m ←[31m-2.131011491008508←[m ←[33;40;1m#2←[m ←[31m0e-00←[m ←[33;40;1m#3←[m ←[31m0e-00←[m ←[33;40;1m#4←[m ←[31m0e-00←[m ←[33;40;1m#5←[m ←[31m'--'←[m Nasal runtime error: nil used in numeric context at C:/Program Files/FlightGear/data/Nasal/multiplayer.nas, line 285 called from: C:/Program Files/FlightGear/data/Nasal/multiplayer.nas, line 261 called from: C:/Program Files/FlightGear/data/Nasal/multiplayer.nas, line 297 called from: C:/Program Files/FlightGear/data/Nasal/multiplayer.nas, line 187 called from: C:/Program Files/FlightGear/data/Nasal/globals.nas, line 100 FGMultiplayMgr::MP_ProcessData: Domain error FGMultiplayMgr::MP_ProcessData: Domain error floating point error in math.sin(): at C:/Program Files/FlightGear/data/Nasal/geo.nas, line 186 ←[33;40;1m#0←[m ←[31m0.6549447477376435←[m ←[33;40;1m#1←[m ←[31m-2.130982380921875←[m ←[33;40;1m#2←[m ←[31m0e-00←[m ←[33;40;1m#3←[m ←[31m0e-00←[m ←[33;40;1m#4←[m ←[31m0e-00←[m ←[33;40;1m#5←[m ←[31m'--'←[m Nasal runtime error: nil used in numeric context at C:/Program Files/FlightGear/data/Nasal/multiplayer.nas, line 285 called from: C:/Program Files/FlightGear/data/Nasal/multiplayer.nas, line 261 called from: C:/Program Files/FlightGear/data/Nasal/multiplayer.nas, line 297 called from: C:/Program Files/FlightGear/data/Nasal/multiplayer.nas, line 187 called from: C:/Program Files/FlightGear/data/Nasal/globals.nas, line 100 FGMultiplayMgr::MP_ProcessData: Domain error FGMultiplayMgr::MP_ProcessData: Domain error FGMultiplayMgr::MP_ProcessData: Domain error FGMultiplayMgr::MP_ProcessData: Domain error FGMultiplayMgr::MP_ProcessData: Domain error FGMultiplayMgr::MP_ProcessData: Domain error FGMultiplayMgr::MP_ProcessData: Domain error FGMultiplayMgr::MP_ProcessData: Domain error FGMultiplayMgr::MP_ProcessData: Domain error FGMultiplayMgr::MP_ProcessData: Domain error FGMultiplayMgr::MP_ProcessData: Domain error FGMultiplayMgr::MP_ProcessData: Domain error FGMultiplayMgr::MP_ProcessData: Domain error FGMultiplayMgr::MP_ProcessData: Domain error FGMultiplayMgr::MP_ProcessData: Domain error FGMultiplayMgr::MP_ProcessData: Domain error FGMultiplayMgr::MP_ProcessData: Domain error FGMultiplayMgr::MP_ProcessData: No such file or directory floating point error in math.sin(): at C:/Program Files/FlightGear/data/Nasal/geo.nas, line 186 ←[33;40;1m#0←[m ←[31m0.6546278854822363←[m ←[33;40;1m#1←[m ←[31m-2.130717563934199←[m ←[33;40;1m#2←[m ←[31m0e-00←[m ←[33;40;1m#3←[m ←[31m0e-00←[m ←[33;40;1m#4←[m ←[31m0e-00←[m ←[33;40;1m#5←[m ←[31m'--'←[m Nasal runtime error: nil used in numeric contex
Re: [Flightgear-devel] Duplicate files in base package
Am Donnerstag, den 25.02.2010, 22:23 +0100 schrieb Roy Vegard Ovesen: > FSlint reports that the base package, or the data directory, contains quite a > lot of duplicate files. The file that is wasting the most bytes is > glass_shader.png (some instances named glass.png) with 43 974 656 bytes, or > around 45MB. This file is duplicated 89 times. The second biggest waster is > shader.png (here too some instances are named glass.png) with 31 457 280 > bytes > and 641 instances. > > Running fdupes in the data directory reports that duplicate files occupy > about > 420 megabytes of the 2.7 Gig. Thats roughly 15% (if my math is correct). > > Many of the duplicate files seem to be textures. This begs the question: > would > it be better to have a directory $FG_ROOT/Aircraft/Textures where one would > put textures that are shared by several aircraft? There already is a > $FG_ROOT/Textures directory, but this seems to contain only non-aircraft > textures. > > Comments? > I guess most duplicate files are instruments which are not in the generic folder. Of course it would be desireable to have them all in one place and reference to there, but that would cause severe problems with the aircraft downloads, because every aircraft on the download page would need a second package for instruments which are not in the Base package. Including all these Instruments in the Base Package would greatly increase the download size. Another thing are textures used in aircraft models. Most 3D Programs prefer to have texture files in the same directory as the model file. A change of texture file paths is possible but requires some post processing of the .ac file, which will be instantly dumped when the file is exported from the 3D Program. This workflow is rather annoying. Additionally the same problem with redistribution, who is going to sort out which files belong to which aircraft and creates download packages? Greetings -- Detlef Faber http://www.sol2500.net/flightgear -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] flightgear-bugs and the dev list
On Fri, Feb 26, 2010 at 9:28 AM, Pete Morgan wrote: > Its quite easy to forward all "New Issueses" and "Comments" to the > mailing list. > > Shall I switch it on? > > If it doesn't work, then it can just as easily be disabled, by any of > the administrators (under Administer >> Issue Tracking) > Are you talking about forwarding your bug tracker emails to the flightgear-devel list? I would be against that. This is effectively signing up a bunch of people to a new mailing list they didn't ask for and is typically considered to be somewhere along the continuum between "bad form" and "spam". We can certainly mention the existence of the other mailing list and folks can be free to subscribe to it if they like. Best regards, Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/ -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] flightgear-bugs and the dev list
Its quite easy to forward all "New Issueses" and "Comments" to the mailing list. Shall I switch it on? If it doesn't work, then it can just as easily be disabled, by any of the administrators (under Administer >> Issue Tracking) pete -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] build on Windows; dependencies?
On Thu, 2010-02-25 at 18:07 -0600, stan.mar...@l-3com.com wrote: > Newbie questions ... Hi Stan, Good to have you join us... a. alut - http://connect.creativelabs.com/openal/Downloads/Forms/AllItems.aspx I use the OpenAL SDK, but still compile alut separately. b. pthreads - http://sources.redhat.com/pthreads-win32/ Although FG uses OSG OpenThreads, normally in WIN32, SG is compiled as one big static library, thus this is required for SGThreads... c. boost - http://www.boost.org/users/download/#repository Note _ONLY_ the headers are required. You do not need to compile the libraries, at this time! d. osg - http://www.openscenegraph.org/projects/osg Note that to build all the required osg plugins for FG you also need at least :- libpng - http://sourceforge.net/projects/libpng/files/ which of course is always paired with zlib :- zlib - http://www.zlib.net/ which is required for SG/FG anyway... These need to be compiled BEFORE cmake OSG - check 'Show Advanced...' I do try to maintain a complete prerequisite page :- http://geoffair.net/fg/prereq.htm but it can get out-of-date easily. And have my own 'special' WIN32 MSVC native build system, TSS ;=))- http://geoffair.net/fg/fgfs-047.htm but Fred and others do well maintaining the msvc in FG source 'projects', using some '3rdParty' precompiled libraries that might suit you better. The first compile is a bit of a struggle in WIN32, but hang in there - IT IS WORTH IT ;=)) HTH, and good luck... Regards, Geoff. -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Proposed new set of splash screens
syd adams schrieb: > Just out of curiosity , what's the white bar above the bottom "Flightgear " > ? > It is decoration and should express some more dynamics. But meantime I am working on some new examples for the lettering (it is not a logo I think). It will be better to show the entire screen i.e. with default resolution 800 x 600. Reading in the thread - I am a bit afraid of choosing the wrong screen picture ;-) Is there any possibility to get the whole screen for the texture? The camera settings give 504 x 504 pixels also in default resolution on my screen. And in my version the image is smoothed in all resoultions and I doubt that this is not necessary at least in the default resolution? Or does it depend on camera setting? Is there any possibility to change to whole screen (or to screen ratio) for the texture instead of using the square texture size? With some other camera settings in osg (i.e. orthocamera)? Thanks - Yves -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Fixing the B787; Was: Proposed new set of splash screens
Pete Morgan wrote: > http://code.google.com/p/flightgear-bugs/issues/detail?id=27 Ah, I see, the link belongs to the above text, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Fixing the B787; Was: Proposed new set of splash screens
Pete Morgan wrote: > ... as is the case with the B787, its "dead" atmo with a fatal bug; > there is a fix [...] Where ? Description of the bug and the fix ? Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
