RE: [Flightgear-devel] CVS and branch development
How does one create a branch? I know how to tag changed files locally: cvs tag -b JSB_New_XML FGAircraft.cpp FGAircraft.h Is that what you mean? This is for creating a branch. Then you have to tell that you are working on it by doing : cvs update -r JSB_New_XML FGAircraft.cpp FGAircraft.h check with : cvs status FGAircraft.cpp FGAircraft.h you should see JSB_New_XML as a sticky tag. -Fred I did that, and saw the sticky tag. I believe JSBSim CVS is now in a good state. I tagged my local copy of all the good files with PRIOR_TO_NEW_XML_FORMAT. Then, I copied into my local directories the new files that are being modified for the new XML capability, and tagged then with a branch tag (-b option) JSB_New_XML. Then, I did the cvs update as you specified. Now the question I have is how do I commit my local work so that it is on a branch in the CVS repository? If I simply do a cvs commit does that commit my local changed files (that have been tagged with a branch tag) into CVS on a branch - not on HEAD? Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] ATC Network Test
Boris Koenig wrote: Arnt Karlsen wrote: On Mon, 04 Oct 2004 11:17:07 -0700, John wrote in message [EMAIL PROTECTED]: A few details... Volunteers will get a package of software that contains the TNL libraries and a basic set of software to connect to the ATC net as a controller or pilot. Package will include ALL source code and make files for a Linux system. Sorry, I'm just not an MS type. However, it will build under Cygwin. ..GPL? Url? John isn't yet 'releasing' anything, rather he asks for people who would be willing to participate in some field tests. I'd be happy to help test it. -- Jon Stockill [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] ATC Network Test
On 4 Oct 2004, at 19:17, John Wojnaroski wrote: A few details... Volunteers will get a package of software that contains the TNL libraries and a basic set of software to connect to the ATC net as a controller or pilot. Package will include ALL source code and make files for a Linux system. Sorry, I'm just not an MS type. However, it will build under Cygwin. I'm happy to test, and probably even get the code building on OS-X, since it should be very close to working already. HH James ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] CVS and branch development
Jon Berndt wrote : How does one create a branch? I know how to tag changed files locally: cvs tag -b JSB_New_XML FGAircraft.cpp FGAircraft.h Is that what you mean? This is for creating a branch. Then you have to tell that you are working on it by doing : cvs update -r JSB_New_XML FGAircraft.cpp FGAircraft.h check with : cvs status FGAircraft.cpp FGAircraft.h you should see JSB_New_XML as a sticky tag. -Fred I did that, and saw the sticky tag. I believe JSBSim CVS is now in a good state. I tagged my local copy of all the good files with PRIOR_TO_NEW_XML_FORMAT. Then, I copied into my local directories the new files that are being modified for the new XML capability, and tagged then with a branch tag (-b option) JSB_New_XML. Then, I did the cvs update as you specified. Now the question I have is how do I commit my local work so that it is on a branch in the CVS repository? If I simply do a cvs commit does that commit my local changed files (that have been tagged with a branch tag) into CVS on a branch - not on HEAD? The commit will happened in the branch specified by the sticky tag you are seeing by doing cvs status. If you did cvs add in a directory, the file will get the last tag used to update or check out the directory. You are working on Windows, right ? So I advise you to use WinCVS instead of the bare command line tools. This way you'll see instantaneously what are the current sticky tags ( or date if you used the -D option ). You can download it at http://www.wincvs.org/ . It has dialog for all available option and is very easy to use, and doesn't prevent you to use the command line whenever you want. -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] ATC Network Test
James Turner wrote: On 4 Oct 2004, at 19:17, John Wojnaroski wrote: A few details... Volunteers will get a package of software that contains the TNL libraries and a basic set of software to connect to the ATC net as a controller or pilot. Package will include ALL source code and make files for a Linux system. Sorry, I'm just not an MS type. However, it will build under Cygwin. I'm happy to test, and probably even get the code building on OS-X, since it should be very close to working already. That would be really nice, actually I offered yesterday to make it compile under Win32 - but I didn't have MSVC in mind, but rather I was thinking of using MingW32 (Dev C++) - I am not sure how many people are actually using it here, so if there's anybody here who could assist making it compile natively under MS VC it would be appreciated. John told me yesterday he would be about to downstrip the package, so all volunteers who can help make it compile on a different platform should inform him, so that the makefiles/sources can be modified accordingly. -- Boris ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] CVS and branch development
Well, I've just about had it with cvs branches. I tagged some files in a branch, then moved to a test directory and checked out that branch, but only got the branch-tagged files. I needed all of the files, except I wanted the updated files on the specified branch. One thing that makes this difficult is that it seems as though cvs at sourceforge has a lag. What I check in is not what I can check until a few hours later. I am trying to develop the new XML capability in JSBSim. There are some new files that I have checked in that are new and do not need to be on a new branch. But, there are some that are currently used and I do not want to commit these to the HEAD branch until the whole set of changes is done. However, CVS using branches is giving me a big headache - it seems to work differently than I expect it to. I'm not sure what to do. Suggestions welcome. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] CVS and branch development
Jon Berndt wrote: Well, I've just about had it with cvs branches. I tagged some files in a branch, then moved to a test directory and checked out that branch, but only got the branch-tagged files. I needed all of the files, except I wanted the updated files on the specified branch. use the -f option for cvs update to get the head if the tag is not present. One thing that makes this difficult is that it seems as though cvs at sourceforge has a lag. What I check in is not what I can check until a few hours later. Use your developer account ( :ext2:... ) instead of the anonymous one ( :pserver: ) I am trying to develop the new XML capability in JSBSim. There are some new files that I have checked in that are new and do not need to be on a new branch. But, there are some that are currently used and I do not want to commit these to the HEAD branch until the whole set of changes is done. However, CVS using branches is giving me a big headache - it seems to work differently than I expect it to. I'm not sure what to do. Suggestions welcome. Branches are tought so I preferably assign them to directory instead of simple files. Unfortunately, jsbsim files are located in the cvs root folder, not in an src folder. It is easy to create a mess when managing simple files, and this is why I recommend using a visual tool such as WinCVS or its counterpart on Linux or anything else. If I where you, I would tag the whole tree so that I wouldn't have to remember what are files that need to be in the branch and those that are not. cvs do a good job when adding or removing solely in the branch. -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] CVS and branch development
I incorrectly wrote: If I where you, ... Oops, bad english: I meant 'If I was you, ...' -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] ATC Network Test
- Original Message - From: Jon Stockill [EMAIL PROTECTED] To: FlightGear developers discussions [EMAIL PROTECTED] Sent: Tuesday, October 05, 2004 3:37 AM Subject: Re: [Flightgear-devel] ATC Network Test I'd be happy to help test it. Okay, let's tentatively plan for this weekend, it should be a fairly quick test. A master node will be available from 0900GMT to 1200GMT on 9 OCT 2004 at 216.86.210.202:29002. To run the master node requires a static IP and a broadband (DSL or higher) connection. If anyone would like to run as a master node we'll need info as to the IP address and a time slot when the master will be active. ATM there is no capability to share/exchange data between master server nodes. Again, I want to emphasize, this is a very rudimentary test using the TNL libraries and protocols. One of the objectives is to just see if it will work over long-haul networks. Realize some prefer not to reveal their private email address, so it probably makes sense to just upload the files to the SF site Boris established. Best guess, is check the site Wednesday and that will allow a few days to build and play with it. You can run an internal test using 127.0.0.1:29002 on a single machine or on a LAN. Regards JohnW ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] ATC Network Test
DevC++ has some problems; last time I tried, you couldn't build FGFS on it because of the number of files in the final link; (it can't process the command line - too long). Giles Robertson -Original Message- From: Boris Koenig [mailto:[EMAIL PROTECTED] Sent: 05 October 2004 13:30 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] ATC Network Test James Turner wrote: On 4 Oct 2004, at 19:17, John Wojnaroski wrote: A few details... Volunteers will get a package of software that contains the TNL libraries and a basic set of software to connect to the ATC net as a controller or pilot. Package will include ALL source code and make files for a Linux system. Sorry, I'm just not an MS type. However, it will build under Cygwin. I'm happy to test, and probably even get the code building on OS-X, since it should be very close to working already. That would be really nice, actually I offered yesterday to make it compile under Win32 - but I didn't have MSVC in mind, but rather I was thinking of using MingW32 (Dev C++) - I am not sure how many people are actually using it here, so if there's anybody here who could assist making it compile natively under MS VC it would be appreciated. John told me yesterday he would be about to downstrip the package, so all volunteers who can help make it compile on a different platform should inform him, so that the makefiles/sources can be modified accordingly. -- Boris ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] ATC Network Test
A quick disclaimer ;-) I'm no make wizard. It's basically a clone. In particular you will have to manually install the TNL headers files. Either in /usr/include/tnl and usr/include/tnl/encrypt or location of your choice and modify the Makefile files accordingly. Regards John W. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] ATC Network Test
On Tue, 5 Oct 2004 08:44:22 -0700, John wrote in message [EMAIL PROTECTED]: - Original Message - From: Jon Stockill [EMAIL PROTECTED] To: FlightGear developers discussions [EMAIL PROTECTED] Sent: Tuesday, October 05, 2004 3:37 AM Subject: Re: [Flightgear-devel] ATC Network Test I'd be happy to help test it. Okay, let's tentatively plan for this weekend, it should be a fairly quick test. A master node will be available from 0900GMT to 1200GMT on 9 OCT 2004 at 216.86.210.202:29002. To run the master node requires a static IP and a broadband (DSL or ..before messing up sitewise throttling, I can set up a box with 200kbps out on its own ip, will that do? ..hardwarewise and stripped way down, what will the box need, except your new code and a _bare_ debian install? higher) connection. If anyone would like to run as a master node we'll need info as to the IP address and a time slot when the master will be active. ATM there is no capability to share/exchange data between master server nodes. Again, I want to emphasize, this is a very rudimentary test using the TNL libraries and protocols. One of the objectives is to just see if it will work over long-haul networks. Realize some prefer not to reveal their private email address, so it probably makes sense to just upload the files to the SF site Boris established. Best guess, is check the site Wednesday and that will allow a few days to build and play with it. You can run an internal test using 127.0.0.1:29002 on a single machine or on a LAN. -- ..med vennlig hilsen = with Kind Regards from Arnt... ;-) ...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. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] ATC Network Test
Giles Robertson wrote: DevC++ has some problems; last time I tried, you couldn't build FGFS on it because of the number of files in the final link; (it can't process the command line - too long). yes, I see - but that would probably not be a problem when linking only a -compared to FG - relatively small application ? :-) This command line restriction is probably a windows-problem, and not related to MinW ... maybe it's worth to check out what's possible using GCC as a cross-compiler for Win32. -- Boris ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] ATC Network Test
John Wojnaroski wrote: To run the master node requires a static IP and a broadband (DSL or higher) connection. If anyone would like to run as a master node we'll need info as to the IP address and a time slot when the master will be active. If it compiles on Solaris, I'd be able to provide a server for that with enough bandwidth for several clients, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] joystick interrupts?
I have a PII 450 MHz running Win 98 and using an Nvidia GeForce Ti4200 and 512 Mb of RAM with a 128/256 Graphics aperture. Using the latest NVidia control set I can set the monitor timing to GTF, and using a 72Hz refresh rate with the FG model running at 60Hz and the frame rate throttled (!) to 24Hz I am getting4- 6 fps on taxiing and 12-14 fps in the air (using the Yasim Hunter and the 3d panel). This is acceptable though not brilliant. However, more than the slightest course correction from my MS Sidewinder (v 2.0, USB) causes a serious drop in frame rate. The sim doesn't stop, becuase i suddenly find I am using eg 30deg more bank than i thought i put on. It seems like the screen freezes, but the plane carries on! I haven't tried landing anything yet! On the other hand if I change to an exterior view and circle the a/c the frame rate drops only slightly - 1-2 fps. So this doesn't seeme to be a basic frame rate problem? Having said that, from time to time the frame rate does drop and there is some disc activity - but not consistently with use of the joystick. So, to me this seems to be a joystick handling / USB? problem? I have rewritten joysticks.xml to point straight to the MS stick in ref0. I didn't getthis problemin Linux, though there I have both processors on my MB running, and possibly better USB drivers than W98, though I think I've downloaded the latest support. Any ideas? Tks, R ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] ATC Network Test
Martin Spott wrote: John Wojnaroski wrote: To run the master node requires a static IP and a broadband (DSL or higher) connection. If anyone would like to run as a master node we'll need info as to the IP address and a time slot when the master will be active. If it compiles on Solaris, I'd be able to provide a server for that with enough bandwidth for several clients, Martin. Boris is editing the make files at this time to clean up some of my goofs. Once their uploaded give it a go. I'll post some notes on setting up. Good luck John W. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Buildiing/running the ATC network test
Hi, For those who expressed an interest in participating in the network test this weekend: After downloading the two tiles from SF, untar them in /usr/local/src/ and that will create two directories as ATC-0.1 and TNL-1.4. Note: For now, you will have to install the TNL headers files by hand: the following script should work #!/bin/bash cd /usr/include mkdir tnl cd tnl mkdir encrypt mkdir master cd /usr/local/src/TNL-0.1/src/encrypt cp *.h /usr/include/tnl/encrypt/ cd ../master cp *.h /usr/include/tnl/master cd ../tnl cp *.h /usr/include/tnl/ ## end of script Build the TNL libraries first which should produce three static libraries (libtnl.a, libencrypt.a and libatcmaster.a) which will be installed in /usr/local/lib/ Next build the libraries, the configure.in file conatains a lot of cruft used for plib/SimGear. We might wind up using some of that but for now Boris is working on a simpler version. If plib and Simgear is on your system you can use the *big* version. Next go to the ATC directory /usr/local/src/ATC-0.1 and build and install. Again, depending on your system configurations you can try aclocal automake autoconf ./configure make make install This will produce three binary applications ( master, controller, node ) located in /usr/local/bin. To run as a master simply type master at the commad prompt after checking that there is a small master.cfg file located in the same directory as the binary. To run as a controller or pilot you can enter the following commad controller IP_ADDRESS_MASTER:PORT or pilot IP_ADDRESS_MASTER:PORT The address(s) fo the master nodes will be posted on the OpenATC site http://openatc.sourceforge.net/test/ Again, don't expect anything dramatic or earth-moving, but hope you can join use ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Buildiing/running the ATC network test
John Wojnaroski wrote: Build the TNL libraries first which should produce three static libraries (libtnl.a, libencrypt.a and libatcmaster.a) which will be installed in /usr/local/lib/ Built, although I had to build libencrypt.a by running make in its own directory rather than at the top level. Next build the libraries, the configure.in file conatains a lot of cruft used for plib/SimGear. We might wind up using some of that but for now Boris is working on a simpler version. If plib and Simgear is on your system you can use the *big* version. All there already - I just pointed configure to the correct paths. Next go to the ATC directory /usr/local/src/ATC-0.1 and build and install. Again, depending on your system configurations you can try aclocal automake autoconf ./configure I think I'm a victim of some of that cruft - configure is failing here with: configure: error: conditional ENABLE_XMESA_FX was never defined. Usually this means the macro was only invoked conditionally. -- Jon Stockill [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] CVS and branch development
If I where you, I would tag the whole tree so that I wouldn't have to remember what are files that need to be in the branch and those that are not. cvs do a good job when adding or removing solely in the branch. Sounds like a good idea. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Buildiing/running the ATC network test
- Original Message - From: Jon Stockill [EMAIL PROTECTED] To: FlightGear developers discussions [EMAIL PROTECTED] Sent: Tuesday, October 05, 2004 1:48 PM Subject: Re: [Flightgear-devel] Buildiing/running the ATC network test John Wojnaroski wrote: Build the TNL libraries first which should produce three static libraries (libtnl.a, libencrypt.a and libatcmaster.a) which will be installed in /usr/local/lib/ Built, although I had to build libencrypt.a by running make in its own directory rather than at the top level. Yes, my fault. Just grabbed what was already there... should have mention that in the build notes I'll add that to the build notes and/or redo the makefile to work with configure.in. Thanks. Next build the libraries, the configure.in file conatains a lot of cruft used for plib/SimGear. We might wind up using some of that but for now Boris is working on a simpler version. If plib and Simgear is on your system you can use the *big* version. All there already - I just pointed configure to the correct paths. Next go to the ATC directory /usr/local/src/ATC-0.1 and build and install. Again, depending on your system configurations you can try aclocal automake autoconf ./configure I think I'm a victim of some of that cruft - configure is failing here with: configure: error: conditional ENABLE_XMESA_FX was never defined. Usually this means the macro was only invoked conditionally. Yes, more and likely. ATM there is no need for any sort of opengl library or graphics capability or plib/Simgear. Odds are some of those libraries will be used but you can comment all that stuff out for now. Plus there may be some macros or other things that happen between aclocal_to_make that I (quite honestly) don't fully understand. So things work on my system and may fail on others. When and if this becomes a living, breathing project all those items need to be dealt with and cleaned up Regards John W. P.S. Hope to have an update or two before the field test. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] hi res screen shots
I just committed a set of changes to move the hi res screen capture feature back towards a useable state. The hires screenshot snapper now uses the same render code as the normal res screen shot snapper which uses the same render code as the main program. That should reduce code maintenance work and code rot in the future. There are currently 2 issues that remain. The first (which I'm scratching my head over) is this. Shots taken from inside a 3d cockpit don't show any external scenery. However, shots taken from outside (chase/tower) seem to work perfectly. If you select hi-res screen shot from the menu, that means the menu is active, and it is drawn on every tile (so if you are doing a 3x3 scheme, you would get 9 instances on the menu.) This is probably easier to figure out than my first problem, but for now you can turn off the menu, then telnet in and run the screen dump command remotely to work around this problem. Regards, Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] ATC Bug #1
Okay, see a small problem on deleting nodes that drop off the net. Seems the linked list shows one controller left even after all nodes have dropped off. A pilot node requesting an arranged connection will wait a very, very long time rather than a no controllers available msg. Small change to the login command string, one may now specify controller name and type Syntax is : controller addess:port [name] [facility] as in controller IP_ADDRESS:PORT Oakland Approach or controller IP_ADDRESS:PORT Miami Tower Use single word tokens, spaces are token breaks. No entries defaults to first example Regards John W. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
