Re: [Flightgear-devel] New FlightGear Multiplayer Server
Hi Lloyd, I have updated mpserver01 and http://mpmap01.flightgear.org/mpstatus/ Thank you for providing me with feedback for BSD. I've updated the sources and pushed them to gitorious so the source should compile out of the boy now. Regards, Oliver Am 06.07.2013 08:33, schrieb Lloyd A. Stevens: I had a bit of trouble getting fgms to build on FreeBSD 9.0. The source I used was from git://gitorious.org/fgms/fgms-0-x.git ERRORS for: fgms-0-x/src/libcli/libcli.cxx /usr/include/malloc.h:3:2: error: #error malloc.h has been replaced by stdlib.h Changes made to fgms-0-x/src/libcli/libcli.cxx #if !defined(__FreeBSD__) # include malloc.h #endif ERRORS for: fgms-0-x/src/server/fg_util.cxx /usr/ports/local/fgms-0-x/src/server/fg_util.cxx:107: error: integer constant is too large for 'long' type /usr/ports/local/fgms-0-x/src/server/fg_util.cxx:109: error: integer constant is too large for 'long' type /usr/ports/local/fgms-0-x/src/server/fg_util.cxx:113: error: integer constant is too large for 'long' type /usr/ports/local/fgms-0-x/src/server/fg_util.cxx:115: error: integer constant is too large for 'long' type Changes made to fgms-0-x/src/server/fg_util.cxx (added decimal points for the listed lines): if (bytes 1125899906842624.) ret_val = (bytes / 1125899906842624.); else if (bytes 1099511627776.) ret_val = (bytes / 1099511627776.); *The server is now running.* The server is located in Los Angeles, California, USA on a multi-homed 100 Mb sustained connection. This is my backup development server and is rarely used. http://ns3.galacticnet.com/stats/ Uptime is greater than 99% (up for 461 days). Intel(R) Pentium(R) 4 CPU 2.66GHz Logfile: 05.07.2013 18:16:38 # This is newmpserver 05.07.2013 18:16:38 # FlightGear Multiplayer Server v0.11.0 started 05.07.2013 18:16:38 # using protocol version v1.1 (LazyRelay enabled) 05.07.2013 18:16:38 # listening to port 5000 05.07.2013 18:16:38 # telnet port 5001 05.07.2013 18:16:38 # admin port 5002 05.07.2013 18:16:38 # using logfile /var/log/fgms.log 05.07.2013 18:16:38 # listening on 64. 05.07.2013 18:16:38 # tracking is disabled. 05.07.2013 18:16:38 # I have 1 relays 05.07.2013 18:16:38 # relay mpserver14.flightgear.org:5000 05.07.2013 18:16:38 # I have 0 crossfeeds 05.07.2013 18:16:38 # I have 2 blacklisted IPs 05.07.2013 18:16:38 # Files: exit=[/tmp/fgms_exit] stat=[/tmp/fgms_stat] 05.07.2013 18:16:38 # My PID is 34144 05.07.2013 18:16:38 Main server started! 05.07.2013 18:53:15 New LOCAL Client: N1035G 108.228.5.67:61421 (Aircraft/danube/Models/danube-osg.xml) current clients: 1 max: 1 The IP is 64.69.45.88. If you want to add this server to http://mpmap01.flightgear.org/mpstatus/ please provide me with correct values for my fgms.conf: server.name = newmpserver server.tracked = false server.tracking_server = 62.112.194.20 server.tracking_port = 8000 server.is_hub = false server.out_of_reach = 1 #relay.host = mpserver01.flightgear.org #relay.port = 5000 relay.host = mpserver14.flightgear.org relay.port = 5000 # crossfeed.host = foo.example.com # crossfeed.port = 5002 blacklist = 123.123.123.123 ~Lloyd Stevens lists.sourceforge.net@boxisp. net (was this the correct place to post this?) (I still can’t get fgms-1-x to compile) -- This message has been scanned for viruses and dangerous content by *MailScanner* http://www.mailscanner.info/, and is believed to be clean. -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-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 Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Tupolev 154 goes GPL
This is terrific news. Big thanks for the hard work, and especially for going for GPL in the end! This will easily be one of the showcase planes of FG. * Thorsten -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Tupolev 154 goes GPL
On Mon, 8 Jul 2013 13:48:22 +0700, Yurik wrote in message 201307081348.22614.yu...@kbrare.ru: Hello All Flightgear developers! It has been almost 5 years since Tu-154B first appeared in FlightGear. Now, after years of development and bug-fixing, release 3.0 is available - and it is GPL compliant and Rembrandt ready! Unfortunately, many FlightGear pilots do not even know this airplane exists. ..one way to make it known, is make a wee bit of noise around its hydrogen sibling: http://en.wikipedia.org/wiki/Tupolev_Tu-155 ;o) We have now been allowed by Project Tupolev to distribute Tu-154B under GNU/GPL. In addition, the model has undergone major overhaul regarding the Rembrandt project. It now provides a full specter of real lighting, for both exterior model and the cockpit. ..and the interior too? Way different for the 155 and 156. On the FDM side, the hydrogen and proposed methane fuels are liquid at these cryogenic pressures and temperatures, and the 155 carried common hydrocarbon jet fuel as back-up. -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...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. -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] reminder: entering feature freeze now
Hi Guys, A 30 second thought on this: On Tue, Jun 25, 2013 at 10:58 PM, Curtis Olson wrote: Once we clear past the 2.10, 2.12, etc. series, I'd like to go back to keeping things single digits in the major and minor version numbers and when we run out of a single digits bump up the major number (so 3.8.x - 4.0.x). Number are numbers, but this one confused a lot more people than I expected it would or should so maybe it's good to be sensitive to that after we clear the 2.x series of versions. That sounds OK to me, as it would imply a full release every 2.5 years, give a clear flag ahead of time when we're nearing a major release, and save having these discussions in the future. For reference, with the current plan there will be 4 years between 2.0.0 (Feb 2010) was and 3.0.0 (Feb 2014). -Stuart -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] some models updates available
Hi Ahmad, On Thu, Jul 4, 2013 at 2:28 AM, grtuxhangar team wrote: Hello, Crusader: After check out , we have found some other mistake, landing gear and catapult related. =The landing gear did not behave correctly on water ( it should not take any water solid ). =The catapult force was too weak. the F-8E-Crusader/Systems/landing-gear.xml and F-8E-Crusader/Systems/catapult_free.xml are updated git clone g...@gitorious.org:eekpo/f-8e-crusader Catalina: Same error than Crusader landing gear against water ( only the sea was right ) It want also an update PBY-Catalina/Systems/landing-gear.xml git clone g...@gitorious.org:eekpo/pby-catalina.git Sorry for that huge noise. Thanks for letting me know about the updates, and sorry for the late response. I should be able to look at these later this week. -Stuart -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Lots of Progress on Download_and_compile.sh
The next branch on the team clone has the changes to download and compile.sh listed below. There are just a couple of things left to do, plus extensive testing. I gave up on trying to do small incremental changes to the script. There would be too many variations to test if what I wanted to accomplish were done in small steps. its all available here: https://www.gitorious.org/+fg-download-and-compile/fg/fg-download-and-compile-fgmeta/blobs/next/download_and_compile.sh Initial testing is complete Variant builds work well and flightgear/fgcom/fgrun all start and run as expected. I've used it with -G 3.1.9 and it built. It remains to be proven that it actually built using OSG-3.1.9 or 3.0.1 as usual.. Try your favorite combinations of parameters and let me know how things work for you. Remember this is an alpha version. Not yet approved for general use. Suggestions: put download_and_compile.sh in a new directory, away from your current build create a subdirectory and run ../download_and_compile.sh from there. -Pat Recently added options: -G OSG version number -B Version # for Flightgear and Simgear, should correctly resolve version for openrti -R sets a revision for Flightgear and Simgear -D 1 Directory management option (reduces disk space, clutter, and network usage -N x -DSG_SVN_CLIENT=$OPTARG -g may actually work -w verbose makefile -x sets -x -v sets -v Here's what I have been working on. The next branch has most of this working. 0. Change the title of the window in which the build is run Indicate what variant is being worked on and which component is currently being built. 1. Timestamped log files with or without -x, -v or -xv 2. Build any of next, master, 2.10.0, 2.8.0 2a. Build with any git tag. 2b. If building only one part, such as flightgear, simgear or openrti, you can specify a commit #. 3. Build the old way and get the same simple directory structure Variant builds are done as usual in separate directories which contain the entire flightgear component trees including fgdata. 4. a rebuild script is left in the build directory. Executing it will rerun Download_and_compile.sh with the same options. The script documents what was built and the final status of the most recent build. 5. Support for personal and team clones on gitorious. 6. Build a new way and get a directory structure: Variant builds are still done in separate directories, but contain only the variant's build and install directories A parent directory, above the variant build directories contains fgsrc: sources for flightgear, openrti, simgear, fgrun, fgcom, fgcomgui etc othersrc: sources for OSG (mulitple versions supported), sources for plib (version 1.8.5 supported) containers for different versions of fgdata: fgdata_2.12.0, fgdata_2.11.0, fgdata_2.10.0, fgdata_2.8.0 etc. This new directory structure supports: 1. No more multiple downloads of fgdata for each separate build. You download only one, and if you need more than one version, it is created locally with copy and git commands. All variant builds use a copy of fgdata from a parent directory 2. No more multiple download and builds of plib and osg. You download and build plib-1.8.5 and osg-3.0.1 once. 3. A single copy of flightgear, simgear and openrti sources that can be used to build whatever versions are needed 4. Support for additional versions of osg such as 3.1.9 -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
