RE: [Flightgear-devel] Big Nasal Changes
For what this is worth: For work, I build flightgear with some custom modsusing 2003 .NET It builds with pretty much zero code changes. I dohave to munge around with the project files and add a bunch of include paths, lib paths, lib refs,etc. to get a clean build. However, the interesting part of 2003 .NET is the debugger. I have nothing but problems with it. It is just plain not as stable as the VC6 debugger. Constant crashes with large applications like FlightGear. I've been told that this is a install specific thing and that our messed up workstation config is the cause (our network IS/mgmt people are quite inept.) Other people tell me "no, it just sucks like that for any install." So I'm not sure where the truth lies. Probably somewhere in the middle. Many people in our company that are forced to do windows development refuse to upgrade to 2003 .NET even though the development environment is nicer than VC6. Hope this helps you at least somewhat. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Terry ReinertSent: Tuesday, April 19, 2005 8:25 AMTo: FlightGear developers discussionsSubject: Re: [Flightgear-devel] Big Nasal Changes I am still using VC++ 6.0 from 98 myself. I have been thinking of upgrading to either 2003 or 2005 but hesitant to do so until I find out whether I can still code the same way as I do now in those environments. I did some reading on the MS website last night and it seemed to imply that I do not need to program in .NET or the other fancy stuff they implimented but being Microsoft I am leary to believe them. So, anyone out there with VC++ 2003 that could shed some light on this? Will the programs I use now still compile without any modifications under the 2003 / 2005 IDE? Frederic Bouvier wrote: Selon Andy Ross: Frederic Bouvier wrote: I found where it is not C : you don't always declare local variables at the beginning of functions but you have the C++ habit to declare them as you need them. ... which is a well-established feature of the (now 6-year-old!) C99 standard. It's not a "C++" thing. And GCC stopped warning about this (in C mode, under -Wall) several years ago. You need to engage -ansi and disable --std=c99 to see stuff like this. I am not here to endorse Microsoft choices, but I see little point to use C syntax when C++ is available and is the language of choice for the overall FlightGear project. However, the link below should clarify Microsoft point of view : http://www.dotnet247.com/247reference/msgs/56/280444.aspx Not speaking about the fact that a lot of people are still using the v6 version that was released in 1998. Thanks for committing the patch. -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] FlightGear BitTorrents
Good idea! Now what would be really neat is if we could get some seeders started with the entire world scenery distribution. Things that size (i.e. HUGE!) is where bit torrent can really shine. I would volunteer, but I don't have the entire set ... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Arthur Wiebe Sent: Tuesday, March 15, 2005 2:24 PM To: FlightGear developers discussions; FlightGear user discussions Subject: [Flightgear-devel] FlightGear BitTorrents Hey everyone, FlightGear (source and base), and SimGear source are now available for download via BitTorrent, thanks to http://www.open-bits.org See: http://www.open-bits.org/browse.php?cat=3 http://www.open-bits.org/details.php?id=902 (SimGear Source) http://www.open-bits.org/details.php?id=901 (fgfs-base) http://www.open-bits.org/details.php?id=900 (FlightGear source) For those who don't know what BitTorrent is, see http://www.bittorrent.com/introduction.html And you can download the client from http://www.bittorrent.com Currently we need seeders. So even though I'm very sure most if not all of you already have the above releases, you can still seed for those who don't :) Curtis, Maybe you might want to link to the torrents on the download page? I have no idea what kind of load you have on your servers but this may sure help to reduce it. Thanks, and enjoy! (And happy seeding) -- Arthur/ ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Frame rates and Win32 builds
Title: Frame rates and Win32 builds Hullo the list! I've got a quick question with regards to win32 builds of flight gear, specifically builds with Visual Studio 2003 .NET. For the project I'm working right now, I need to be able to mod flight gear, which of course means I need to do my own builds. No big deal. Of course building on windows compared to building on linux is quite painful (alas I have not choice ...), but I built the latest release on VC.NET without too much drama. The problem, however is the frame rate. When I build the latest greatest with VC in the Release configuration I end up with frame rates of around 26 just sitting on 28R at KSFO in the F-23. When I use the prebuilt 0.9.6 Win32 release I get frame rates in the low 70s for the same spot. S something is very very different between these two builds. The size is very similar (both in the 3mb range). I would not be surprised seeing SOME frame rate delta between versions, but over 50% tells me I've likely done something wrong. My question is: does anyone know exactly what options were used to build the official win32 version? Was it built on .NET or on the older (but more stable!) VC6? GNU/Cygwin? What rates are the other VC.NET people seeing? I would really like to be able to build my own binary with a framerate near that of the official released version. Any and all input appreciated, dv ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
