Re: [Flightgear-devel] Flight Gear on Windows
On Sat, Dec 12, 2009 at 1:20 AM, Melchior FRANZ mfr...@aon.at wrote: * jean pellotier -- Friday 11 December 2009: got something like that too on linux, but guess what? with an ati card I'm better off on Linux (with an nvidia card). I can at least decide whether I want clouds *or* material animations broken: http://members.aon.at/mfranz/material-shaders.jpg [54.9 kB] I believe my recent checkin to simgear and data has fixed the materials animation + shaders problem. Tim -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Flight Gear on Windows
On the other hand probably most newcomers to Flightgear CVS are using Windows. The present setup has rather a steep learning curve to achieve first build and may cause many to think that Flightgear is broke and not worth the effort. I am using the 3rd party from ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/MSVC/ to which I have added the latest OpenAL and alut from the Creative site . Boost (headers only) is also required. The DLLs should be in the PATH environment. The VC90 setup already has the library and include file search paths set correctly. At the moment Simgear needs sample_group.cxx/hxx added to the project and NOMINMAX set. Flightgear needs 4 pairs of .cxx, .hxx files ( Sample_queue, FGGyro, FGMagnetometer, AIGroundVehice) to be added to the project and NOMINMAX set. Simgear.h is not generated automatically, so I make my own. OSGText.lib need to be added to the fgviewer project. My build tree is simple with Data, Source, Simgear, 3rd Party Boost.1.39.0 and Install directories all at the same level. This fits in with the Flightgear project that is in the CVS. I may have missed something out, but hopefully most of the changes are above. Finally the data needs to be updated via CVS as the latest gui and other files are needed. Unfortunately the documented build procedures in the FlightGear Wiki http://wiki.flightgear.org/index.php/Building_Flightgear_-_Windows and on Geoff Lane´s excellent FlightGear Build Centre http://www.geoffmclane.com/fg/ do not use this simple structure and require extensive downloading (after setting up CVS, SVN and Git) and then building of the prerequisites as well as the prerequisites of the prerequisites. They may even waste a day building Boost, when only the headers are needed. Alan P.s. I note that the following are not in my build, but do not cause any link errors. Simgear/scene/model :- animation, BoundingVolumeBuildVisitor, CheckSceneryVisitor,shadanim and shadowvisitor. -- From: Olaf Flebbe f...@oflebbe.de Sent: Tuesday, December 15, 2009 9:59 PM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] Flight Gear on Windows I was asked to remove them! Who asked, and why? I did not read this on the list, or maybe missed it, otherwise I would have offered an 'opinion' then ;=)) I was one of the guys who asked him. If I remember correctly I had it CC'ed on the list. The DSP Files where unchanged for years and didn't work out of the box for years. The am2dsp scripts had to be updated but no one seemed to care for years. I agree that it is rather futile to get vcproj files up-to-date. IMHO converting autoconf isn't optimal, too. Olaf -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Flight Gear on Windows
Correction;: I do have shadanim and CheckScenary visitor in my build. (Red face again) -- From: Alan Teeder ajtee...@v-twin.org.uk Sent: Wednesday, December 16, 2009 11:37 AM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] Flight Gear on Windows On the other hand probably most newcomers to Flightgear CVS are using Windows. The present setup has rather a steep learning curve to achieve first build and may cause many to think that Flightgear is broke and not worth the effort. I am using the 3rd party from ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/MSVC/ to which I have added the latest OpenAL and alut from the Creative site . Boost (headers only) is also required. The DLLs should be in the PATH environment. The VC90 setup already has the library and include file search paths set correctly. At the moment Simgear needs sample_group.cxx/hxx added to the project and NOMINMAX set. Flightgear needs 4 pairs of .cxx, .hxx files ( Sample_queue, FGGyro, FGMagnetometer, AIGroundVehice) to be added to the project and NOMINMAX set. Simgear.h is not generated automatically, so I make my own. OSGText.lib need to be added to the fgviewer project. My build tree is simple with Data, Source, Simgear, 3rd Party Boost.1.39.0 and Install directories all at the same level. This fits in with the Flightgear project that is in the CVS. I may have missed something out, but hopefully most of the changes are above. Finally the data needs to be updated via CVS as the latest gui and other files are needed. Unfortunately the documented build procedures in the FlightGear Wiki http://wiki.flightgear.org/index.php/Building_Flightgear_-_Windows and on Geoff Lane´s excellent FlightGear Build Centre http://www.geoffmclane.com/fg/ do not use this simple structure and require extensive downloading (after setting up CVS, SVN and Git) and then building of the prerequisites as well as the prerequisites of the prerequisites. They may even waste a day building Boost, when only the headers are needed. Alan P.s. I note that the following are not in my build, but do not cause any link errors. Simgear/scene/model :- animation, BoundingVolumeBuildVisitor, CheckSceneryVisitor,shadanim and shadowvisitor. -- From: Olaf Flebbe f...@oflebbe.de Sent: Tuesday, December 15, 2009 9:59 PM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] Flight Gear on Windows I was asked to remove them! Who asked, and why? I did not read this on the list, or maybe missed it, otherwise I would have offered an 'opinion' then ;=)) I was one of the guys who asked him. If I remember correctly I had it CC'ed on the list. The DSP Files where unchanged for years and didn't work out of the box for years. The am2dsp scripts had to be updated but no one seemed to care for years. I agree that it is rather futile to get vcproj files up-to-date. IMHO converting autoconf isn't optimal, too. Olaf -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Flight Gear on Windows
Alan wrote -- From: Alan Teeder ajtee...@v-twin.org.uk Sent: Wednesday, December 16, 2009 11:37 AM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] Flight Gear on Windows On the other hand probably most newcomers to Flightgear CVS are using Windows. The present setup has rather a steep learning curve to achieve first build and may cause many to think that Flightgear is broke and not worth the effort. I am using the 3rd party from ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/MSVC/ to which I have added the latest OpenAL and alut from the Creative site . Boost (headers only) is also required. The DLLs should be in the PATH environment. The VC90 setup already has the library and include file search paths set correctly. At the moment Simgear needs sample_group.cxx/hxx added to the project and NOMINMAX set. Flightgear needs 4 pairs of .cxx, .hxx files ( Sample_queue, FGGyro, FGMagnetometer, AIGroundVehice) to be added to the project and NOMINMAX set. Simgear.h is not generated automatically, so I make my own. OSGText.lib need to be added to the fgviewer project. My build tree is simple with Data, Source, Simgear, 3rd Party Boost.1.39.0 and Install directories all at the same level. This fits in with the Flightgear project that is in the CVS. I may have missed something out, but hopefully most of the changes are above. Finally the data needs to be updated via CVS as the latest gui and other files are needed. Unfortunately the documented build procedures in the FlightGear Wiki http://wiki.flightgear.org/index.php/Building_Flightgear_-_Windows and on Geoff Lane´s excellent FlightGear Build Centre http://www.geoffmclane.com/fg/ do not use this simple structure and require extensive downloading (after setting up CVS, SVN and Git) and then building of the prerequisites as well as the prerequisites of the prerequisites. They may even waste a day building Boost, when only the headers are needed. Alan P.s. I note that the following are not in my build, but do not cause any link errors. Simgear/scene/model :- animation, BoundingVolumeBuildVisitor, CheckSceneryVisitor,shadanim and shadowvisitor. You're a bit behind the power curve there: you also need AIEscort.cxx AIEscort.hxx to be up-to-date with cvs. I have plib-svn in my build, but I'm not sure if this is still needed. I use freealut-1.0.1 and OpenAL 1.1 Core SDK, which seem to give good results. While the reset and exit crashes have been cured, I still get unexplained and seemingly random crashes from time to time. Vivian -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Flight Gear on Windows
On Tue, 2009-12-15 at 13:42 +0100, Erik Hofman wrote: Geoff McLane wrote: About 5 weeks ago you removed the FlightGear.dsp and FlightGear.dsw Hmm, I get mixed request from different Windows developers. I was asked to remove them! Honestly I thought the project files are stored in their own directory (e.g. projetcs/MSVC9.0) these days. Hi Eric, I was asked to remove them! Who asked, and why? I did not read this on the list, or maybe missed it, otherwise I would have offered an 'opinion' then ;=)) the project files are stored in their own directory Yes, we do have projects/VC90 and VC7.1, and we did have VC80 as well, for both SG and FG! But these are only as up-to-date as the developer who put them there, and maintains them. Thus they are ONLY maintained if and when that developer does it, Fred. But his last update was now some time ago, although I note Tim has recently added some patches from Vivian... docs-mini/README.MSVC - last update by you 2005 This only really points to Fred's ftp directory at - ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/MSVC/ where the last build file zip is dated June 2005! docs-mini/README.MSVC8 - last update 2006 This refers to MSVC8, which has been removed! and points to a wiki - http://wiki.flightgear.org/flightgear_wiki/index.php?title=Building_Flightgear which, under the 'Building FlightGear - Windows', does provide quite a detailed build description, and as an external link at the bottom, points to my 'build' center! I assume this dependence on 'other' developers is why Curt? or who ever, wrote the am2dsp.pl script. Fred even made a small update to it a few years back to change to /MD... Now am2dsp.pl could be modified to write build files into say 'projects/MSVC' if desired, to get these files out of the root area... And am2dsp.pl provides a way you, and/or other cvs maintainers can ensure there are _ALWAYS_ up-do-date MSVC build files, regardless of the disposition of other developers. And I see NO REASON to provide multiple build version files. One MSVC6 set would be enough, since they can be used by ALL later versions. As stated, it is hard to have a really 'generic' way in MSVC, thus each native WIN developer has his/her own way of doing things. Very few of the 3rd party dependent libraries are available for something like the simple 'apt-get', so they have to get into building all of these themselves. Hence my detailed build center, that always gets into _ALL_ the other dependent sources, and how to build them... I would do the mods to am2dsp.pl to move the files to say :- projects/MSVC if that is desired/required, and could add some lines to README.MSVC and MSVC8 to talk about these 'generic', 'simple' am2dsp.pl generated build files if they are put back in either place... And, yes, let us hear from other native windows developers... What are other suggestions here? Regards, Geoff. -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Flight Gear on Windows
I was asked to remove them! Who asked, and why? I did not read this on the list, or maybe missed it, otherwise I would have offered an 'opinion' then ;=)) I was one of the guys who asked him. If I remember correctly I had it CC'ed on the list. The DSP Files where unchanged for years and didn't work out of the box for years. The am2dsp scripts had to be updated but no one seemed to care for years. I agree that it is rather futile to get vcproj files up-to-date. IMHO converting autoconf isn't optimal, too. Olaf -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Flight Gear on Windows
Alan Teeder wrote: I am no longer seeing the first two bugs which seem to have been sorted out this week, but do have a similar problem with sound. See my thread with Eric. Is this something I need to look after or is it a matter of finding the proper compile options? Erik -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Flight Gear on Windows
Erik wrote Alan Teeder wrote: I am no longer seeing the first two bugs which seem to have been sorted out this week, but do have a similar problem with sound. See my thread with Eric. Is this something I need to look after or is it a matter of finding the proper compile options? Erik No, nothing more needs doing atm in relation to the crash on reset, and the crash on exit bugs. Both were coding errors that Linux appears to swallow, while Windows did not using MSVC9. Sound seems OK here, but has not been subject to thorough testing. Vivian -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Flight Gear on Windows
It is strange that I am the only one reporting this fault, but it is still there. On both my Vista laptop and the XP box it fails if run from Visual C++ 2008 with Debug - Start Debugging. On the Vista laptop it also fails if I run the release build from fgrun , but only if sound is enabled. This case is OK on the XP box. The only compilation flag that I have added to the CVS VC90 configuration is NOMINMAX. VC90 build is very out of date and quite few new files and libraries have to be added. As of today version.h is not found. I have hand built one from version.h.in, with the line #define SIMGEAR_VERSION 1.99.4. Alan -- From: Erik Hofman e...@ehofman.com Sent: Monday, December 14, 2009 9:09 AM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] Flight Gear on Windows Alan Teeder wrote: I am no longer seeing the first two bugs which seem to have been sorted out this week, but do have a similar problem with sound. See my thread with Eric. Is this something I need to look after or is it a matter of finding the proper compile options? Erik -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Flight Gear on Windows
On Fri, 11 Dec 2009 23:37:44 +0100, jean wrote in message 4b22c9b8.6050...@wanadoo.fr: Vivian Meazza a écrit : Geoff, I agree with all you have said, but would add the following: The reset bug has been sorted. The crash-on-exit bug has probably been sorted, but I haven’t had time to test it yet. I don’t see the red/orange effect you report. got something like that too on linux, but guess what? with an ati card it's related to shaders, as once i remove the shader effects, scenary is ok. depending on sun and orientation, scenery get sudenly darker, or green, or blue affecting differently far and close field. some screens: http://janodesbois.free.fr/fg_screens/decembre09/fgfs-screen-005.png http://janodesbois.free.fr/fg_screens/decembre09/fgfs-screen-006.png http://janodesbois.free.fr/fg_screens/decembre09/fgfs-screen-024.png and an other (ati?) bug: if i have a look on the airport from obove vertically, then texture become a mess, and all is fine once shaders removed: http://janodesbois.free.fr/fg_screens/decembre09/fgfs-screen-027.png ps: and to answer to the question why have you taken an ati card? that was the only way to flight with shaders on an agp card, and so my PC can last some years more :) . using fglrx, on a debian sid with an ati radeonhd4650. ..try X.org's radeon and X.org/Novell's radeonHD too, and show us so we can compare them. -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Flight Gear on Windows
Alan Teeder wrote: VC90 build is very out of date and quite few new files and libraries have to be added. Honestly try to stay away from the build files, mainly because I have no way to test them. I might completely break building for MSVC and note even know it (typo's are made easily). If anyone has proper build files I would be happy to commit them. As of today version.h is not found. I have hand built one from version.h.in, with the line #define SIMGEAR_VERSION 1.99.4. That should be fixed again, sorry for the fuzz. Erik -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Flight Gear on Windows
On Thu, 2009-12-10 at 11:29 -0500, Joshua C. Stonestreet wrote: RE: Building SG/FG in native MS Windows using MSVC You do not specifically state which MSVC build files you started with, but assume you used those in the respective SG/FG cvs or tar.gz sources? Nearly ALWAYS the MSVC build files are OUT-OF-DATE! This is a FAST changing project, and it is nearly IMPOSSIBLE to keep MSVC build files fully up-to-date! But that said, it is usually a simple matter to start with the current build files, and (a) delete files that no longer exist in the respective source, and (b) when you come to the link, if new files have been added to either SG or FG they will show up as unresolved externals, and you just search for where the particular functions is defined in the source, and ADD those new files to the respective projects. And while you do not particularly need to re-create exactly the same folder structure, not doing so will always mean making more adjustments in the MSVC IDE Property Pages - Configuration Properties - C/C++ - General - Additional Include Directories, and Linker - General - Additional Library Directories, and/or Linker - Input - Additional Dependencies. I have dedicated a section of my site to building flightgear, but it too will always be out-of-date, sometimes just hours after putting it there ;=)), and I now use a 'complete' - that is _ALL_ dependent sources - approach _NOT_ suited to all ;=(), especially since it depends on re-creating the EXACT folder structure for SOURCE and then copies everything to a WORK folder, using the SETUPFG.BAT file... but it works well for me ;=)) See :- http://geoffair.net/fg , specifically http://geoffair.net/fg/fgfs-047.htm , but many other pages with hopefully helpful hints... I too have NOT done an update for a while, due to some new systems (sound, shaders, etc) being modified/added recently, such that I have not yet been able to build a fully stable WIN32 version using MSVC9. Two important things hold me back at the moment, and they are :- (i) a red/orange (and sometimes dark) pall, overlay, over the scene in certain, very repeatable, circumstances, see - http://www.av8n.com/fly/fgfs/htm/bug-list.htm#bug-orange-pall , and http://geoffair.net/tmp/fg/ , and (ii) using the reset causes a crash! The only other MSVC build file set I know about is here :- ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/ - and the sub-directory - ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/MSVC/ Maybe others could remind us of other MS WIN native, MSVC build help locations... and I read here and there some have good success with CygWin... But 'old' MSVC build files in native windows is a way of life in fast changing projects ;=)) Hope this helps. Geoff. -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Flight Gear on Windows
Geoff, I agree with all you have said, but would add the following: The reset bug has been sorted. The crash-on-exit bug has probably been sorted, but I haven't had time to test it yet. I don't see the red/orange effect you report. There is a binary here - a few days old, and using osg rev. 10753 - ftp://ftp.abbeytheatre2.org.uk/fgfs/executable/ It might be helpful if you could test it to see if it solves any of your bugs. Vivian -Original Message- From: Geoff McLane [mailto:ubu...@geoffair.info] Sent: 11 December 2009 12:37 To: FlightGear developers discussions Cc: joshua.c.stonestr...@ivv.nasa.gov Subject: Re: [Flightgear-devel] Flight Gear on Windows On Thu, 2009-12-10 at 11:29 -0500, Joshua C. Stonestreet wrote: RE: Building SG/FG in native MS Windows using MSVC You do not specifically state which MSVC build files you started with, but assume you used those in the respective SG/FG cvs or tar.gz sources? Nearly ALWAYS the MSVC build files are OUT-OF-DATE! This is a FAST changing project, and it is nearly IMPOSSIBLE to keep MSVC build files fully up-to-date! But that said, it is usually a simple matter to start with the current build files, and (a) delete files that no longer exist in the respective source, and (b) when you come to the link, if new files have been added to either SG or FG they will show up as unresolved externals, and you just search for where the particular functions is defined in the source, and ADD those new files to the respective projects. And while you do not particularly need to re-create exactly the same folder structure, not doing so will always mean making more adjustments in the MSVC IDE Property Pages - Configuration Properties - C/C++ - General - Additional Include Directories, and Linker - General - Additional Library Directories, and/or Linker - Input - Additional Dependencies. I have dedicated a section of my site to building flightgear, but it too will always be out-of-date, sometimes just hours after putting it there ;=)), and I now use a 'complete' - that is _ALL_ dependent sources - approach _NOT_ suited to all ;=(), especially since it depends on re-creating the EXACT folder structure for SOURCE and then copies everything to a WORK folder, using the SETUPFG.BAT file... but it works well for me ;=)) See :- http://geoffair.net/fg , specifically http://geoffair.net/fg/fgfs-047.htm , but many other pages with hopefully helpful hints... I too have NOT done an update for a while, due to some new systems (sound, shaders, etc) being modified/added recently, such that I have not yet been able to build a fully stable WIN32 version using MSVC9. Two important things hold me back at the moment, and they are :- (i) a red/orange (and sometimes dark) pall, overlay, over the scene in certain, very repeatable, circumstances, see - http://www.av8n.com/fly/fgfs/htm/bug-list.htm#bug-orange-pall , and http://geoffair.net/tmp/fg/ , and (ii) using the reset causes a crash! The only other MSVC build file set I know about is here :- ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/ - and the sub-directory - ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/MSVC/ Maybe others could remind us of other MS WIN native, MSVC build help locations... and I read here and there some have good success with CygWin... But 'old' MSVC build files in native windows is a way of life in fast changing projects ;=)) Hope this helps. Geoff. -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Flight Gear on Windows
I am no longer seeing the first two bugs which seem to have been sorted out this week, but do have a similar problem with sound. See my thread with Eric. From: Vivian Meazza Sent: Friday, December 11, 2009 9:13 PM To: 'FlightGear developers discussions' Subject: Re: [Flightgear-devel] Flight Gear on Windows Geoff, I agree with all you have said, but would add the following: The reset bug has been sorted. The crash-on-exit bug has probably been sorted, but I haven't had time to test it yet. I don't see the red/orange effect you report. There is a binary here - a few days old, and using osg rev. 10753 - ftp://ftp.abbeytheatre2.org.uk/fgfs/executable/ It might be helpful if you could test it to see if it solves any of your bugs. Vivian -Original Message- From: Geoff McLane [mailto:ubu...@geoffair.info] Sent: 11 December 2009 12:37 To: FlightGear developers discussions Cc: joshua.c.stonestr...@ivv.nasa.gov Subject: Re: [Flightgear-devel] Flight Gear on Windows On Thu, 2009-12-10 at 11:29 -0500, Joshua C. Stonestreet wrote: RE: Building SG/FG in native MS Windows using MSVC You do not specifically state which MSVC build files you started with, but assume you used those in the respective SG/FG cvs or tar.gz sources? Nearly ALWAYS the MSVC build files are OUT-OF-DATE! This is a FAST changing project, and it is nearly IMPOSSIBLE to keep MSVC build files fully up-to-date! But that said, it is usually a simple matter to start with the current build files, and (a) delete files that no longer exist in the respective source, and (b) when you come to the link, if new files have been added to either SG or FG they will show up as unresolved externals, and you just search for where the particular functions is defined in the source, and ADD those new files to the respective projects. And while you do not particularly need to re-create exactly the same folder structure, not doing so will always mean making more adjustments in the MSVC IDE Property Pages - Configuration Properties - C/C++ - General - Additional Include Directories, and Linker - General - Additional Library Directories, and/or Linker - Input - Additional Dependencies. I have dedicated a section of my site to building flightgear, but it too will always be out-of-date, sometimes just hours after putting it there ;=)), and I now use a 'complete' - that is _ALL_ dependent sources - approach _NOT_ suited to all ;=(), especially since it depends on re-creating the EXACT folder structure for SOURCE and then copies everything to a WORK folder, using the SETUPFG.BAT file... but it works well for me ;=)) See :- http://geoffair.net/fg , specifically http://geoffair.net/fg/fgfs-047.htm , but many other pages with hopefully helpful hints... I too have NOT done an update for a while, due to some new systems (sound, shaders, etc) being modified/added recently, such that I have not yet been able to build a fully stable WIN32 version using MSVC9. Two important things hold me back at the moment, and they are :- (i) a red/orange (and sometimes dark) pall, overlay, over the scene in certain, very repeatable, circumstances, see - http://www.av8n.com/fly/fgfs/htm/bug-list.htm#bug-orange-pall , and http://geoffair.net/tmp/fg/ , and (ii) using the reset causes a crash! The only other MSVC build file set I know about is here :- ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/ - and the sub-directory - ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/MSVC/ Maybe others could remind us of other MS WIN native, MSVC build help locations... and I read here and there some have good success with CygWin... But 'old' MSVC build files in native windows is a way of life in fast changing projects ;=)) Hope this helps. Geoff. -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Flight Gear on Windows
Vivian Meazza a écrit : Geoff, I agree with all you have said, but would add the following: The reset bug has been sorted. The crash-on-exit bug has probably been sorted, but I haven’t had time to test it yet. I don’t see the red/orange effect you report. got something like that too on linux, but guess what? with an ati card it's related to shaders, as once i remove the shader effects, scenary is ok. depending on sun and orientation, scenery get sudenly darker, or green, or blue affecting differently far and close field. some screens: http://janodesbois.free.fr/fg_screens/decembre09/fgfs-screen-005.png http://janodesbois.free.fr/fg_screens/decembre09/fgfs-screen-006.png http://janodesbois.free.fr/fg_screens/decembre09/fgfs-screen-024.png and an other (ati?) bug: if i have a look on the airport from obove vertically, then texture become a mess, and all is fine once shaders removed: http://janodesbois.free.fr/fg_screens/decembre09/fgfs-screen-027.png ps: and to answer to the question why have you taken an ati card? that was the only way to flight with shaders on an agp card, and so my PC can last some years more :) . using fglrx, on a debian sid with an ati radeonhd4650. jano -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Flight Gear on Windows
* jean pellotier -- Friday 11 December 2009: got something like that too on linux, but guess what? with an ati card I'm better off on Linux (with an nvidia card). I can at least decide whether I want clouds *or* material animations broken: http://members.aon.at/mfranz/material-shaders.jpg [54.9 kB] m. -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
