[Flightgear-devel] Base package repository move pending
Heads up! The bpr server is changing IP's in the next couple of days. The repository itself may be migrated to flightgear.org, but expect a few hours of outage between now and sunday. TTL John ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] J3 Cub -- sitting in the backseat
David Megginson [EMAIL PROTECTED] said: How do you like flying from the back in fgfs? I might raise the viewpoint a bit to make it easier to see over the nose, but it's definitely a different kind of experience. It's fun. The cub is really a blast anyway, and it flys fine from back there. Having the door off does help. Back seat view really shows off the fine modeling as well. Actually, I tried doing this a while back without realizing that was the proper solo config. Haven't tried landing that way yet but I'm sure if you nose down for a sec to see that the runway is really down there, it shouldn't be a problem. The eye position you have looks about right...might even move back a bit further (this said by someone who has never flown a cub or anything solo). BTW if you select j3cub-yasim, instead of j3cub-3d-yasim, you fly from the front seat. Not sure if that was intended. Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Current CVS still not compile
Make a copy of the file, then edit it for your joystick and put it somewhere FlightGear can find it. Then something like this to your $HOME/.fgfsrc file: Ok, the attached file is my work. I simply copy and paste the area of the throttle and rename all throttle to rudder. but it doesn't work? :-? I also add the entry to the $HOME/.fgfsrc file. Roland ?xml version=1.0? !-- Default 4-axis joystick bindings. Assume that we have a conventional, four-axis, three/four-button joystick, and that the first button is the trigger. -- PropertyList axis n=0 descAileron/desc binding commandproperty-scale/command property/controls/aileron/property squared type=booltrue/squared /binding /axis axis n=1 descElevator/desc binding commandproperty-scale/command property/controls/elevator/property factor type=double-1.0/factor squared type=booltrue/squared /binding /axis axis n=2 descThrottle/desc binding commandproperty-scale/command property/controls/throttle[0]/property offset type=double-1.0/offset factor type=double-0.5/factor /binding binding commandproperty-scale/command property/controls/throttle[1]/property offset type=double-1.0/offset factor type=double-0.5/factor /binding /axis axis n=3 descRudder/desc binding commandproperty-scale/command property/controls/rudder[0]/property offset type=double-1.0/offset factor type=double-0.5/factor /binding binding commandproperty-scale/command property/controls/rudder[1]/property offset type=double-1.0/offset factor type=double-0.5/factor /binding /axis button n=0 descBrakes/desc binding commandproperty-assign/command property/controls/brakes[0]/property value type=double1.0/value /binding binding commandproperty-assign/command property/controls/brakes[1]/property value type=double1.0/value /binding binding commandproperty-assign/command property/controls/brakes[2]/property value type=double1.0/value /binding mod-up binding commandproperty-assign/command property/controls/brakes[0]/property value type=double0.0/value /binding binding commandproperty-assign/command property/controls/brakes[1]/property value type=double0.0/value /binding binding commandproperty-assign/command property/controls/brakes[2]/property value type=double0.0/value /binding /mod-up /button button n=1 descElevator trim up/desc repeatable type=booltrue/repeatable binding commandproperty-adjust/command property/controls/elevator-trim/property step type=double0.001/step /binding /button button n=2 descElevator trim down/desc repeatable type=booltrue/repeatable binding commandproperty-adjust/command property/controls/elevator-trim/property step type=double-0.001/step /binding /button /PropertyList !-- end of joystick.xml --
[Flightgear-devel] CIGI Host Emulator
Hi , I have read your messages http://seneca.me.umn.edu/pipermail/flightgear-devel/2001-November/001129.html can you help me? :) I try use CIGI Host Emulator from http://cigi.sourceforge.net but it's do not work for me. on XP/w2k this tool have crash :( You used it? -- Best regards, Anatoly mailto:[EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] real-time video possibility
What I am really thinking is much simpler(I think) than what Curt has in his mind. My idea is to use FlightGear to control a real time remote control airplane(a real one, not simulate) As I understand so far, the flightgear FDM is that part that controls the airplane's dynamic, so we can create a FDM that is specifically designed to control a RC plane. the inputed data from like the keyboards joystick or mouse will be sent thru the FDM to a radio that is linked on the computer. The radio will transmit the signal on like VHF or HF band. After, the Radio signal will be recieved by the RC plane. and then the RC plane's GPS information will be transmitted thru the radio onboard the RC plane and reach the computer's radio. the radio will send the information to flightgear's FDM and past them to the FG's main loop. So now, instead of playing a remote controlled airplane with just the joystick. We can now control our RC plane with flightgear which hopefully with be more fun. And also, if the designer of the RC plane decided to install a video camera on the RC plane, I think there can be ways to feed the real life video in the flightgear while keeping the panel to be a simulated on the computer. But in case there is like bad visibility, flying at night or the video signal that can only be transmit on VHF band is out of range, we can switch back to FlightGear's simulated enviroment instead of looking at the real life video. Is that what you have in mind, Brandon? ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] real-time video possibility
On Thu, 30 Jan 2003 18:52:35 -0500, socf [EMAIL PROTECTED] wrote in message 004201c2c8ba$aa3dbc00$2bb1fea9@socfstation: What I am really thinking is much simpler(I think) than what Curt has in his mind. My idea is to use FlightGear to control a real time remote control airplane(a real one, not simulate) As I understand so far, the flightgear FDM is that part that controls the airplane's dynamic, so we can create a FDM that is specifically designed to control a RC plane. the inputed data from like the keyboards joystick or mouse will be sent thru the FDM to a radio that is linked on the ...thru the autopilot etc fdm's in both the ground station computer and the airborne... computer. The radio will transmit the signal on like VHF or HF band. ..have laptops and 802.11b cards and planes, only need a wee camera to fly a web server etc for live New Year fireworks footage. ;-) Cell phones suck at 9.6kbps, but this too will work in a pinch. After, the Radio signal will be recieved by the RC plane. and then the RC plane's GPS information will be transmitted thru the radio onboard the RC plane and reach the computer's radio. the radio will send the information to flightgear's FDM and past them to the FG's main loop. So now, instead of playing a remote controlled airplane with just the joystick. We can now control our RC plane with flightgear which hopefully with be more fun. And also, if the designer of the RC plane decided to install a video camera on the RC plane, I think there can be ways to feed the real life video in the flightgear while keeping the panel to be a simulated on the computer. But in case there is like bad visibility, flying at night or the video signal that can only be transmit on VHF band is out of range, we can switch back to ..I have a use for this: emergency link nodes and inspection drones for my 802.11 isp and business client. He too, is a modeller. ;-) ..and there are the local radio stations broadcasting rush hour traffic advice, and we could fly to Iraq for live footage of what Saddam doesn't want inspected or bombed, and its possible to drop a wee chute phone to interview people on the ground, and to help them out of harms way... ..neat investor opportunities. Hi? ;-) FlightGear's simulated enviroment instead of looking at the real life video. Is that what you have in mind, Brandon? -- ..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
[Flightgear-devel] T-38 flight model for JSBSim
Here's a Northrop T-38A flight model for the JSBSim FDM. It flies nicely. Takeoff with flaps at first detent. Rotate to 10 degrees pitch at about 140 knots. Raise gear when airborne. Raise flaps at 200 knots. Trim stab down to maintain 10 degree climb and accelerate to 300 knots. Climb at 300 knots. For landing put gear and flaps out at 200 knots. Full flaps at 170 knots. Fly final at 160 knots. Touchdown at 150 knots. Try aerobraking without getting airborne again. http://home.attbi.com/~davidculp2/t38/t38-set.xml http://home.attbi.com/~davidculp2/t38/t38.xml http://home.attbi.com/~davidculp2/t38/J85-GE-5.xml http://home.attbi.com/~davidculp2/t38/J85_nozzle.xml Dave Culp ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] T-38 flight model for JSBSim
Here's a Northrop T-38A flight model for the JSBSim FDM. It flies nicely. Takeoff with flaps at first detent. Rotate to 10 degrees pitch at about 140 knots. Raise gear when airborne. Raise flaps at 200 knots. Trim stab down to maintain 10 degree climb and accelerate to 300 knots. Climb at 300 knots. Dang! You're fast at this. That one was on my list. Glad you got this together. I may not be able to get them into JSBSim CVS right away but they'll surely end up there within a day or two. Where did you get the data? Nicolai's book has T-38 data. Is that where you got it? Jon smime.p7s Description: application/pkcs7-signature
[Flightgear-devel] Mac OS X: at a loss
Hello everyone, If you've not worked with FlightGear under Mac OS X, delete now. OK, both of you that are left reading this, thanks. I'll make a long story short: every attempt I have made to compile FlightGear, whether 0.9.1 or from CVS, fails in the final link in the same way: ld is unable to resolve the symbols gen_leaf and ssgVtxTable::ssgVtxTable. I have attempted the compile in every permutation I can imagine, which is not a few. More importantly, I have attempted the compile on a fresh install of OS, etc. with as little as possible installed. Same error. I can only conclude that I am introducing the problem somewhere in the same way each time. I am installing: - Mac OS X 10.2.0 (minus all extra languages and applications) - Mac OS X Update Combo 10.2.3 (at this point I change my shell to bash) - Dec 2002 Dev Tools CD (plus BSD SDK) - StuffIt STD 7.01 OS X Install - Fink 0.5.0a (at this point I add the Fink init.sh to my .bashrc, and source it) - cvs-1.11.2.tar.gz (to support fink, installed via fink) - dlcompat-20021117.tar.gz (to support fink, installed via fink) - X4211src.tar.bz2 (via fink) (everything below is installed in a work directory in my $HOME) - plib-1.6.0.tar.gz - metakit-2.4.3-33.tar.gz - SimGear (via CVS) - FlightGear (via CVS) Here is the final link in the compile and resulting messages: g++ -DPKGLIBDIR=\/Users/david/FlightGear/FlightGear-20030103/lib/FlightGear\ -g -O1 -finline-limit=6 -finline-functions -faltivec -D_REENTRANT -L/sw/lib -L/usr/X11R6/lib -L/Users/david/FlightGear/FlightGear-20030103/lib -o fgfs main.o fg_commands.o fg_init.o fg_io.o fg_props.o fgfs.o globals.o logger.o options.o splash.o util.o viewer.o viewmgr.o location.o ../../src/Aircraft/libAircraft.a ../../src/ATC/libATC.a ../../src/Autopilot/libAutopilot.a ../../src/Cockpit/libCockpit.a ../../src/Cockpit/built_in/libBuilt_in.a ../../src/Controls/libControls.a ../../src/FDM/libFlight.a ../../src/FDM/Balloon/libBalloon.a ../../src/FDM/ExternalNet/libExternalNet.a ../../src/FDM/JSBSim/libJSBSim.a ../../src/FDM/YASim/libYASim.a ../../src/FDM/JSBSim/filtersjb/libfiltersjb.a ../../src/FDM/LaRCsim/libLaRCsim.a ../../src/FDM/UIUCModel/libUIUCModel.a ../../src/GUI/libGUI.a ../../src/Input/libInput.a ../../src/Instrumentation/libInstrumentation.a ../../src/Model/libModel.a ../../src/Navaids/libNavaids.a ../../src/Scenery/libScenery.a ../../src/Sound/libSound.a ../../src/Airports/libAirports.a ../../src/Network/libNetwork.a ../../src/NetworkOLK/libNetworkOLK.a ../../src/Objects/libObjects.a ../../src/Systems/libSystems.a ../../src/Time/libTime.a ../../src/Environment/libEnvironment.a -lsgroute -lsgsky -lsgephem -lsgtiming -lsgio -lsgscreen -lsgmath -lsgbucket -lsgdebug -lsgmagvar -lsgmisc -lsgxml -lsgserial -lsgthreads -lplibpu -lplibfnt -lplibjs -lplibnet -lplibssg -lplibsg -lplibul -lmk4 -lz -lpthread -lm -framework GLUT -framework OpenGL -framework Carbon -lobjc -lplibsl -lplibsm -lm ld: warning table of contents of library: ../../src/FDM/JSBSim/libJSBSim.a not sorted slower link editing will result (use the ranlib(1) -s option) ld: Undefined symbols: ssgVtxTable::ssgVtxTable[in-charge](unsigned, ssgVertexArray*, ssgNormalArray*, ssgTexCoordArray*, ssgColourArray*) gen_leaf(std::basic_stringchar, std::char_traitschar, std::allocatorchar const, unsigned long, std::basic_stringchar, std::char_traitschar, std::allocatorchar const, std::vectorPoint3D, std::allocatorPoint3D const, std::vectorPoint3D, std::allocatorPoint3D const, std::vectorPoint3D, std::allocatorPoint3D const, std::vectorint, std::allocatorint const, std::vectorint, std::allocatorint const, std::vectorint, std::allocatorint const, bool, ssgVertexArray*) make[2]: *** [fgfs] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all-recursive] Error 1 Any thoughts would be greatly appreciated. Regards, David K. Drum [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
