Re: [Flightgear-devel] Any alpha testers with a bit of extra time on their hands?
On Mon, 26 Sep 2011 13:04:02 -0500, Curtis wrote in message CAHtsj_fM87grwpzG-vYmANWnALfojsGhOA=dWGajb4gSj2=w...@mail.gmail.com: Updated to Beta02 -- with hopefully a bit better view management and some more small gain tweaks (probably nothing anyone will notice.) ..tried to set camera target to some place on-shore with the camera operator click-to-point-to-orbit, on climb-out this is over-ridden to Carrier, just like on the Alphas. Beta02 is a step in the wrong direction, the drone climbs to ~800ft before diving into the drink. ..on resets, launch is uncommanded, one engine dies, and the drone drives and dives in to that side off the bow. ..incompatible with FG-1.9.1, unless we fix it. I set the tower position to be the carrier deck target touch down spot, and then set the manually controlled tower view to point directly up the ideal approach path ... simulating a PLAT camera (if I got my terminology right.) Essentially if the landing aircraft is exactly on the right approach path it will be dead center of the video screen. Any deviation shows up very clearly. Curt. On Sun, Sep 25, 2011 at 10:04 AM, Arnt Karlsen a...@c2i.net wrote: On Sat, 24 Sep 2011 17:10:29 -0500, Curtis wrote in message CAHtsj_f6u5=_2hgcxdtxho1tvtiup+gex-bphtpciafjy0f...@mail.gmail.com: Hi Geoff (and Arnt, et. al.) I have another update to try. This one drives the roll angle by manipulating the ailerons directly, rather than trying to modify /controls/flight/SAS-roll. SAS-roll worked for me, and I was just following the example of the existing f-14b dg-heading controller. But driving /control/flight/aileron seems to work just as well for me. If there is some sort of order of execution problem with nasal or something conflicting with SAS-roll, perhaps this will work better? I'd be interested in hearing if it helps if anyone gets a chance to try it. ..roll is _much_ smoother, for Alpha05, copy your success on the elevators too. -- ..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. -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Any alpha testers with a bit of extra time on their hands?
On Tue, Sep 27, 2011 at 4:36 PM, Arnt Karlsen a...@c2i.net wrote: ..tried to set camera target to some place on-shore with the camera operator click-to-point-to-orbit, on climb-out this is over-ridden to Carrier, Hi Arnt, There is some logic going on there to try to automatically guess what an operator is most likely to want or a user will find most interesting to look at. I won't claim this handles every situation, but in the short term why not get airborne, climb out and then find the spot you want to look at? This is intended to be a demonstration of a few different uav concepts implemented in FlightGear. just like on the Alphas. Beta02 is a step in the wrong direction, the drone climbs to ~800ft before diving into the drink. A couple things: I haven't tested with the Nimitz -- sorry, can't vouch for what might or might not work there. I've only flown with the Vinson. It's basically a problem that I lack infinite time. Is this still on your tablet pc that gets 2-3 fps. Honestly, this demo will never work with frame rates that low, sorry. What version of FlightGear are you flying? I'm testing with v2.4 and git here, again I don't have infinite time to test on earlier versions. Again sorry about that. ..on resets, launch is uncommanded, one engine dies, The only time I've see the f-14b engine flame out has been due to lack of fuel? You might try calling the fuel truck over and topping you off if you have problems with your engine not running. and the drone drives and dives in to that side off the bow. ..incompatible with FG-1.9.1, unless we fix it. Yeah, sorry, there's a limit to the number of combinations of versions and scenarios I can test and try to support. This was developed for the v2.4 release so going forward you can ding me for not being backwards compatible with v2.4, but it's hard to ask for something developed today to be compatible with 2 1/2 year old release of our code. Anyway, I appreciate you trying it and sorry it didn't work out. I think if I try to put together another demo like this, perhaps it will be base on a heavier than air balloon ... Curt. -- Curtis Olson: http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://gallinazo.flightgear.org -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Any alpha testers with a bit of extra time on their hands?
On Tuesday 27 September 2011 15:53:26 Curtis Olson wrote: a heavier than air balloon ... Would that be a Led Zeppelin? :) Ron -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Any alpha testers with a bit of extra time on their hands?
On Tue, Sep 27, 2011 at 9:47 PM, Ron Jensen wrote: On Tuesday 27 September 2011 15:53:26 Curtis Olson wrote: a heavier than air balloon ... Would that be a Led Zeppelin? That's more clever than what I was thinking. :-) Open-humor. Curt. -- Curtis Olson: http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://gallinazo.flightgear.org -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Any alpha testers with a bit of extra time on their hands?
Hi Curt, Ok, version 04 zip nailed it exactly ;= Now it circles PERFECTLY... I can see in Atlas that each circle exactly overlays the last... I have not yet tried adding TURBULENCE and WINDS but will... Holding exactly 150@2000, the HUD bank-o-meter seldom gets beyond the 3rd marking - that is the first big mark... I added multiplayer, but have not run across any others out there yet... This verified what I have suspected for quite a while, that the mpmap calculation of the aircraft speed is wildly erratic, showing values from 87kts to over 200kts... but I understand this is only an estimate based on current and last position over time... It is a shame the carrier, attendant boat and helicopter do not appear on multiplayer ;=() so just circling blue water... And so far, each 'gohome' has been spot on ;=)) As smooth as a babies bum... I would say, from my perspective, this bumps the demo from Alpha, to Beta or BETTER ;=)) Regards, Geoff. PS: OT: Very neat 'obscurification' of the nasal, with seemingly random generated variable names on each version... fascinating ;=() Some facts - Now I have SMOOTH graphs :- http://geoffair.org/tmp/uas-03-graph.jpg Look at the accurate circling :- http://geoffair.org/tmp/uas-03-track.jpg And the data to load into Atlas :- http://geoffair.org/tmp/uas-atlas-03.txt Or to playback in fgfs (10MB) :- http://geoffair.org/tmp/uas-03.csv Even the script I use to run the demo - http://geoffair.org/tmp/run_f14b.sh Of course it has to be ADJUSTED to suit your environment, AND uses my run_fgfs.sh to run fgfs... g. On Sat, 2011-09-24 at 17:10 -0500, Curtis Olson wrote: Hi Geoff (and Arnt, et. al.) I have another update to try. This one drives the roll angle by manipulating the ailerons directly, rather than trying to modify /controls/flight/SAS-roll. SAS-roll worked for me, and I was just following the example of the existing f-14b dg-heading controller. But driving /control/flight/aileron seems to work just as well for me. If there is some sort of order of execution problem with nasal or something conflicting with SAS-roll, perhaps this will work better? I'd be interested in hearing if it helps if anyone gets a chance to try it. Download link for Alpha04 version and instructions here: http://www.flightgear.org/uas-demo/ Curt. On Sat, Sep 24, 2011 at 11:42 AM, Arnt Karlsen a...@c2i.net wrote: On Sat, 24 Sep 2011 12:54:05 +0200, Arnt wrote in message 20110924125405.072bc...@nb6.lan: On Fri, 23 Sep 2011 21:06:00 -0500, Curtis wrote in message CAHtsj_c=qrUGW4=F9PfEMoDGfgdC2yZVK77pp3gE3P=tbjr...@mail.gmail.com: Here's one for your guys. Do any nasal errors pop up on the console when things go bad? Are you able to manually fly the f-14b (non-uas version) around just fine? ..yup, even on the eeepc keyboard, one up tap elevator, full power, let it roll and wait out the rotation, 2 down taps on the elevator to keep the nose down to 15 to 30 degrees, gets it safely up at 1-2 fps. Once in maybe 20-50 flights I do see something go goofy with the f-14b stability augmentation's roll control. Maybe this same issue is popping up less rarely for some people? I haven't dug into how the SAS is implemented on the f-14b ... it's intricately woven I can tell ... maybe there's something lurking down in the guts of the f-14b SAS. ..or your settings. Curt. On Fri, Sep 23, 2011 at 8:35 PM, Arnt Karlsen a...@c2i.net wrote: On Fri, 23 Sep 2011 23:44:02 +0200, Citronnier wrote in message 4e7cfda2.7060...@gmail.com: Le 23/09/2011 23:12, Curtis Olson a écrit : Geoff and Arnt and anyone else who is interested. I just updated the zip file overlay with a few changes. Geoff: you may be getting tired of being a bunny, but I played around with the roll controller and limited max target roll angle to +/-35 degrees. I also dialed down the gains a bit on final approach which will hopefully slow down the wild swings. More adjustment may be necessary, but I'd be interested in hearing if any of this helps your situation. ..a wee bit, now takes off and makes it ~1000 feet up, then it rolls to the right and makes it ~200 feet into the drink, and repeats the stunt seated in the cockpit (rather than in
Re: [Flightgear-devel] Any alpha testers with a bit of extra time on their hands?
On Sat, 24 Sep 2011 17:10:29 -0500, Curtis wrote in message CAHtsj_f6u5=_2hgcxdtxho1tvtiup+gex-bphtpciafjy0f...@mail.gmail.com: Hi Geoff (and Arnt, et. al.) I have another update to try. This one drives the roll angle by manipulating the ailerons directly, rather than trying to modify /controls/flight/SAS-roll. SAS-roll worked for me, and I was just following the example of the existing f-14b dg-heading controller. But driving /control/flight/aileron seems to work just as well for me. If there is some sort of order of execution problem with nasal or something conflicting with SAS-roll, perhaps this will work better? I'd be interested in hearing if it helps if anyone gets a chance to try it. ..roll is _much_ smoother, for Alpha05, copy your success on the elevators too. ..on start-up, I overshoot the altitude by around 4000feet, so now I have time to try the Go home button. Wild enough ride, blackouts alternating with redouts, but it climbs out. ..on resets, I still land in the cockpit and are immediately launched into the drink, first run T/O were tracking left on the deck and rolling off it to the left, on my second run, both to the right, as if I had an one side flame-out on the get-go. Download link for Alpha04 version and instructions here: http://www.flightgear.org/uas-demo/ Curt. On Sat, Sep 24, 2011 at 11:42 AM, Arnt Karlsen a...@c2i.net wrote: On Sat, 24 Sep 2011 12:54:05 +0200, Arnt wrote in message 20110924125405.072bc...@nb6.lan: On Fri, 23 Sep 2011 21:06:00 -0500, Curtis wrote in message CAHtsj_c=qrUGW4=F9PfEMoDGfgdC2yZVK77pp3gE3P=tbjr...@mail.gmail.com: Here's one for your guys. Do any nasal errors pop up on the console when things go bad? Are you able to manually fly the f-14b (non-uas version) around just fine? ..yup, even on the eeepc keyboard, one up tap elevator, full power, let it roll and wait out the rotation, 2 down taps on the elevator to keep the nose down to 15 to 30 degrees, gets it safely up at 1-2 fps. Once in maybe 20-50 flights I do see something go goofy with the f-14b stability augmentation's roll control. Maybe this same issue is popping up less rarely for some people? I haven't dug into how the SAS is implemented on the f-14b ... it's intricately woven I can tell ... maybe there's something lurking down in the guts of the f-14b SAS. ..or your settings. Curt. On Fri, Sep 23, 2011 at 8:35 PM, Arnt Karlsen a...@c2i.net wrote: On Fri, 23 Sep 2011 23:44:02 +0200, Citronnier wrote in message 4e7cfda2.7060...@gmail.com: Le 23/09/2011 23:12, Curtis Olson a écrit : Geoff and Arnt and anyone else who is interested. I just updated the zip file overlay with a few changes. Geoff: you may be getting tired of being a bunny, but I played around with the roll controller and limited max target roll angle to +/-35 degrees. I also dialed down the gains a bit on final approach which will hopefully slow down the wild swings. More adjustment may be necessary, but I'd be interested in hearing if any of this helps your situation. ..a wee bit, now takes off and makes it ~1000 feet up, then it rolls to the right and makes it ~200 feet into the drink, and repeats the stunt seated in the cockpit (rather than in the camera), uncommanded on Reset button pushes. ..it's trying to orbit the carrier in the vertical plane? ..trying the operator click mode on targets like the merchantman near the Nimitz, works, until the demo is airborne, then it picks the Carrier target and tries a vertical orbit around it. ..refetching the merchantman with the operator mouse click mode, dives the demo into the drink between the 2 vessels. ..debug idea for Curtis: try the Nimitz too. I also set the default carrier speed to zero so if we get a few people out there playing around with this, we should be able to see each other via MP. That could be an additional fun element. I was just out there dodging XIII who trailed me around the pattern and let me live thankfully. :-) Here is the link with the zip file overlay download + installation and operation instructions: http://www.flightgear.org/uas-demo/ MP Call Sign: Shrike :-) Woot :-) so I missed the update, I just read this post after posting the previous one. And was wondering who was flying around there ! Model view ought to be interesting in case of one other tester just encounter problems. Greetings, Alexis Maybe see a few of you out there? Curt. On Fri, Sep 23, 2011 at 1:12 PM, Citronnier - Alexis Bory wrote: Le
Re: [Flightgear-devel] Any alpha testers with a bit of extra time on their hands?
Here's one for your guys. Do any nasal errors pop up on the console when things go bad? Are you able to manually fly the f-14b (non-uas version) around just fine? Once in maybe 20-50 flights I do see something go goofy with the f-14b stability augmentation's roll control. Maybe this same issue is popping up less rarely for some people? I haven't dug into how the SAS is implemented on the f-14b ... it's intricately woven I can tell ... maybe there's something lurking down in the guts of the f-14b SAS. Curt. On Fri, Sep 23, 2011 at 8:35 PM, Arnt Karlsen a...@c2i.net wrote: On Fri, 23 Sep 2011 23:44:02 +0200, Citronnier wrote in message 4e7cfda2.7060...@gmail.com: Le 23/09/2011 23:12, Curtis Olson a écrit : Geoff and Arnt and anyone else who is interested. I just updated the zip file overlay with a few changes. Geoff: you may be getting tired of being a bunny, but I played around with the roll controller and limited max target roll angle to +/-35 degrees. I also dialed down the gains a bit on final approach which will hopefully slow down the wild swings. More adjustment may be necessary, but I'd be interested in hearing if any of this helps your situation. ..a wee bit, now takes off and makes it ~1000 feet up, then it rolls to the right and makes it ~200 feet into the drink, and repeats the stunt seated in the cockpit (rather than in the camera), uncommanded on Reset button pushes. ..it's trying to orbit the carrier in the vertical plane? ..trying the operator click mode on targets like the merchantman near the Nimitz, works, until the demo is airborne, then it picks the Carrier target and tries a vertical orbit around it. ..refetching the merchantman with the operator mouse click mode, dives the demo into the drink between the 2 vessels. ..debug idea for Curtis: try the Nimitz too. I also set the default carrier speed to zero so if we get a few people out there playing around with this, we should be able to see each other via MP. That could be an additional fun element. I was just out there dodging XIII who trailed me around the pattern and let me live thankfully. :-) Here is the link with the zip file overlay download + installation and operation instructions: http://www.flightgear.org/uas-demo/ MP Call Sign: Shrike :-) Woot :-) so I missed the update, I just read this post after posting the previous one. And was wondering who was flying around there ! Model view ought to be interesting in case of one other tester just encounter problems. Greetings, Alexis Maybe see a few of you out there? Curt. On Fri, Sep 23, 2011 at 1:12 PM, Citronnier - Alexis Bory wrote: Le 23/09/2011 16:47, Curtis Olson a écrit : Hi Geoff, I'm starting to run low on ideas here. I assume you don't have any crazy/severe turbulence turned on or your plots would be all over the place. Are you running out of fuel and your engines dying? If you open the autopilot dialog (F11) you can see the target speed and if you have the hud turned on you can see the actual speed in any view. If you are circling with a target speed of 150 and your airspeed is less than than and you are decending, then definitely check your engine output. There is a fuel dialog box under the f-14b menu and you might double check that to see if you have any fuel in your tanks. For what it's worth, I'm rock solid in circling and the only time I have ever stalled out of the sky or really got out of kilter is when I've had severe turbulence turned on. Moderate turbulence at all levels is actually pretty interesting because despite getting thrown all over the sky, I still hit the carrier deck pretty spot on every time. Curt. Still no tests yet but just a though, In normal use (without the UAV script) I know that after TO (flaps down) you have to rise the flaps in before engaging the attitude autopilot mode. If you rise the flaps after engaging attitude autopilot mode, the a/c start to pitch up consistently. This has to be documented or fixed. I'll try to bring the maintainer to his workstation ASAP. Alexis On Fri, Sep 23, 2011 at 9:35 AM, Geoff McLane wrote: Hi Curt, Ok, removed my joystick, and entered a '5', but still crashed while just in 'circle' mode - no route entered ;=(( As usual Atlas provides a good 'view' as to what happened - added - ATLAS=--atlas=socket,out,IP,5500,udp to output to Atlas running in a 2nd machine... See - http://geoffair.org/tmp/uas-01.jpg for a
Re: [Flightgear-devel] Any alpha testers with a bit of extra time on their hands?
On Sat, 24 Sep 2011 12:54:05 +0200, Arnt wrote in message 20110924125405.072bc...@nb6.lan: On Fri, 23 Sep 2011 21:06:00 -0500, Curtis wrote in message CAHtsj_c=qrUGW4=F9PfEMoDGfgdC2yZVK77pp3gE3P=tbjr...@mail.gmail.com: Here's one for your guys. Do any nasal errors pop up on the console when things go bad? Are you able to manually fly the f-14b (non-uas version) around just fine? ..yup, even on the eeepc keyboard, one up tap elevator, full power, let it roll and wait out the rotation, 2 down taps on the elevator to keep the nose down to 15 to 30 degrees, gets it safely up at 1-2 fps. Once in maybe 20-50 flights I do see something go goofy with the f-14b stability augmentation's roll control. Maybe this same issue is popping up less rarely for some people? I haven't dug into how the SAS is implemented on the f-14b ... it's intricately woven I can tell ... maybe there's something lurking down in the guts of the f-14b SAS. ..or your settings. Curt. On Fri, Sep 23, 2011 at 8:35 PM, Arnt Karlsen a...@c2i.net wrote: On Fri, 23 Sep 2011 23:44:02 +0200, Citronnier wrote in message 4e7cfda2.7060...@gmail.com: Le 23/09/2011 23:12, Curtis Olson a écrit : Geoff and Arnt and anyone else who is interested. I just updated the zip file overlay with a few changes. Geoff: you may be getting tired of being a bunny, but I played around with the roll controller and limited max target roll angle to +/-35 degrees. I also dialed down the gains a bit on final approach which will hopefully slow down the wild swings. More adjustment may be necessary, but I'd be interested in hearing if any of this helps your situation. ..a wee bit, now takes off and makes it ~1000 feet up, then it rolls to the right and makes it ~200 feet into the drink, and repeats the stunt seated in the cockpit (rather than in the camera), uncommanded on Reset button pushes. ..it's trying to orbit the carrier in the vertical plane? ..trying the operator click mode on targets like the merchantman near the Nimitz, works, until the demo is airborne, then it picks the Carrier target and tries a vertical orbit around it. ..refetching the merchantman with the operator mouse click mode, dives the demo into the drink between the 2 vessels. ..debug idea for Curtis: try the Nimitz too. I also set the default carrier speed to zero so if we get a few people out there playing around with this, we should be able to see each other via MP. That could be an additional fun element. I was just out there dodging XIII who trailed me around the pattern and let me live thankfully. :-) Here is the link with the zip file overlay download + installation and operation instructions: http://www.flightgear.org/uas-demo/ MP Call Sign: Shrike :-) Woot :-) so I missed the update, I just read this post after posting the previous one. And was wondering who was flying around there ! Model view ought to be interesting in case of one other tester just encounter problems. Greetings, Alexis Maybe see a few of you out there? Curt. On Fri, Sep 23, 2011 at 1:12 PM, Citronnier - Alexis Bory wrote: Le 23/09/2011 16:47, Curtis Olson a écrit : Hi Geoff, I'm starting to run low on ideas here. I assume you don't have any crazy/severe turbulence turned on or your plots would be all over the place. Are you running out of fuel and your engines dying? If you open the autopilot dialog (F11) you can see the target speed and if you have the hud turned on you can see the actual speed in any view. If you are circling with a target speed of 150 and your airspeed is less than than and you are decending, then definitely check your engine output. There is a fuel dialog box under the f-14b menu and you might double check that to see if you have any fuel in your tanks. For what it's worth, I'm rock solid in circling and the only time I have ever stalled out of the sky or really got out of kilter is when I've had severe turbulence turned on. Moderate turbulence at all levels is actually pretty interesting because despite getting thrown all over the sky, I still hit the carrier deck pretty spot on every time. Curt. Still no tests yet but just a though, In normal use (without the UAV script) I know that after TO (flaps down) you have to rise the flaps in before engaging the attitude autopilot mode. If you rise the flaps after engaging attitude autopilot mode, the a/c start to pitch up
Re: [Flightgear-devel] Any alpha testers with a bit of extra time on their hands?
Not convenient we chose Vinson because the deck is indeed identical to Nimitz. Vivian -Original Message- From: Curtis Olson [mailto:curtol...@gmail.com] Sent: 22 September 2011 23:21 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] Any alpha testers with a bit of extra time on their hands? I went with the Vinson because it is spiffier. Everything should (theoretically) work the same and just as well from the Nimitz. I believe the deck geometries are identical in FlightGear (conveniently.) ;-) Curt. On Thu, Sep 22, 2011 at 5:02 PM, Arnt Karlsen a...@c2i.net wrote: On Thu, 22 Sep 2011 22:36:45 +0200, Citronnier wrote in message 4e7b9c5d.6080...@gmail.com: Le 22/09/2011 22:04, Arnt Karlsen a écrit : On Thu, 22 Sep 2011 14:00:49 -0500, Curtis wrote in message CAHtsj_crOGWDX43J5oKw7F6g12AWsRePoceNGW=a1b0txod...@mail.gmail.com: On Thu, Sep 22, 2011 at 1:25 PM, Geoff McLane wrote: You seem to be deliberately holding its speed down around 150 - I see air-brakes come up when greater than this, and throttle back - and although flaps (I think full flap?) are still applied, 150 must be quite 'low' for this sleek bird... Normal landing approach in the real aircraft I believe is about 120 kts? I fly 135 kt approaches in the simulator. It should be able to hold 150 kts with the flaps down pretty easily. ..the Navy guys fly approaches using AOA, not speeds, AFAIK. And a max 6000 lbs fuel in the tanks. FG's f-14b is quite tricky to fly with what is *supposed* to be the right AoA for approach. Side departure happen easily if your aren't smooth enough in your final turn. ..and it does not like to T/O and climb on idle power, all Launch!!! button action I see is wild pre-crash oscillations, the Reset button tosses me into the cockpit rather than in the camera. ..Curtis, any reason your demo needs the USS Vinson, rather than a renamed USS Nimitz copy? ..Alexis, any changes to the f-14b since FG-1.9.1? Curt, I didn't test yet, sorry, lake of time, but the last mods on properties in engines.nas and instrument.nas should be comited soon. Happy to see you all playing with the beast :-) Alexis -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Curtis Olson: http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://gallinazo.flightgear.org -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Any alpha testers with a bit of extra time on their hands?
Hi Curt, Ok, removed my joystick, and entered a '5', but still crashed while just in 'circle' mode - no route entered ;=(( As usual Atlas provides a good 'view' as to what happened - added - ATLAS=--atlas=socket,out,IP,5500,udp to output to Atlas running in a 2nd machine... See - http://geoffair.org/tmp/uas-01.jpg for a graph of the flight... The two blips in the graphs show the first stall, but it recovers and begins to climb back, and the 2nd the second stall, this time too low to recover, so into the drink ;=(( CRASH! This is a view of the 'crazy' flight track http://geoffair.org/tmp/uas-02.jpg Obviously the pig-tail loops are the 'stalls'... remember with NO joystick attached and starting with centered controls (NumPad 5)... And if you want to load this track into Atlas, or further study speeds, etc, then this is the Atlas track data :- http://geoffair.org/tmp/uas-01.txt Then on the NEXT flight I tried :- IO=--generic=file,out,10,uas-02.csv,playback Then I added a header line, to help analyze it in say an OpenOffice spreadsheet import - see - http://geoffair.org/tmp/uas-02.csv On this 2nd flight, this crash took longer, since it (randomly) turned left first, where as mentioned it holds more stable, but then eventually went into a right turn, stalled, recovered, stalled again, and CRASHED... And as you know well, downloading this file, and using say - $ ./fgfs --fg-root=/point/to/fgfs/data --timeofday=noon \ --aircraft=f-14b-uas --carrier=Vinson \ --generic=file,in,10,uas-02.csv,playback --fdm=external you too can enjoy this fateful flight ;=)) In 'chase' view, you can clearly see the right roll increase, the nose coming up, and the stall, recovery, then repeated, and BANG, into the water... I know it is difficult to work on, debug, fix something that obviously does not happen in your case... Maybe if you do not enter any route, or something... And this is all with SG/FG git of 2011-09-14... Any other ideas? Regards, Geoff. On Thu, 2011-09-22 at 14:00 -0500, Curtis Olson wrote: On Thu, Sep 22, 2011 at 1:25 PM, Geoff McLane wrote: Hi Curt, A pleasure, and FUN ;=)) Yes, I know a low frame rate can play havoc when you are trying to fine control an aircraft from its attitude feedback, and I should have mentioned my rate, but is always in the high 50-70 fps range in this Ubuntu machine... so should NOT be a factor... Ok, 50-70 should be perfect. I just did another few runs, and this time it crashed just while circling... it was in a right bank, which got too much and the nose came up, and it stalled... I am mostly in the 'chase' view... This is really strange. I have seen nothing like this except when I inadvertantly applied external control inputs through a strange combination of linux virtual desktops and flightgear capturing the hotkey to come back to the FlightGear virtual desktop. So two thoughts here. If you have a joystick connected, could you try unplugging it to see if that helps? Could you also press 5 on the numeric keypad to make sure all the flight control inputs are centered. Because of the way the F-14b FCS is wired together in combination with the yasim flight surfaces, you can still input elevator and aileron and trim and cause conflicts that you might not see in other simpler aircraft that use aileron and elevator directly. The first time this happened at 2000 feet, it caught itself - leveled a bit and bumped the throttles, and began climbing back... But a little later, 20-30 secs, it happened again, and this time was still too low to recover, and SPLASH... I had not previously let it fly in the 'circle' mode for too long, but now note if I leave it in circling mode, it will eventually end up in the water... seldom lasts more than 5 or 10 minutes... You seem to be deliberately holding its speed down around 150 - I see air-brakes come up when greater than this, and throttle back - and although flaps (I think full flap?) are still applied, 150 must be quite 'low' for this sleek bird... Normal landing approach in the real aircraft I believe is about 120 kts? I fly 135 kt approaches in the simulator. It should be able to hold 150 kts with the flaps down pretty easily. The point of slowing way down when circling is to keep the circle radius small enough so you can see what you are looking at. If you fly the circle at 600 kts, your radius will be 20 miles (just guessing) :-) and you won't be able to see anything. And I am not sure how many degrees each marking on the hud bottom bank indicator represents, and while it starts the banking in between the 1 and 2 of the 'big' marks, at the
Re: [Flightgear-devel] Any alpha testers with a bit of extra time on their hands?
Hi Geoff, I'm starting to run low on ideas here. I assume you don't have any crazy/severe turbulence turned on or your plots would be all over the place. Are you running out of fuel and your engines dying? If you open the autopilot dialog (F11) you can see the target speed and if you have the hud turned on you can see the actual speed in any view. If you are circling with a target speed of 150 and your airspeed is less than than and you are decending, then definitely check your engine output. There is a fuel dialog box under the f-14b menu and you might double check that to see if you have any fuel in your tanks. For what it's worth, I'm rock solid in circling and the only time I have ever stalled out of the sky or really got out of kilter is when I've had severe turbulence turned on. Moderate turbulence at all levels is actually pretty interesting because despite getting thrown all over the sky, I still hit the carrier deck pretty spot on every time. Curt. On Fri, Sep 23, 2011 at 9:35 AM, Geoff McLane wrote: Hi Curt, Ok, removed my joystick, and entered a '5', but still crashed while just in 'circle' mode - no route entered ;=(( As usual Atlas provides a good 'view' as to what happened - added - ATLAS=--atlas=socket,out,IP,5500,udp to output to Atlas running in a 2nd machine... See - http://geoffair.org/tmp/uas-01.jpg for a graph of the flight... The two blips in the graphs show the first stall, but it recovers and begins to climb back, and the 2nd the second stall, this time too low to recover, so into the drink ;=(( CRASH! This is a view of the 'crazy' flight track http://geoffair.org/tmp/uas-02.jpg Obviously the pig-tail loops are the 'stalls'... remember with NO joystick attached and starting with centered controls (NumPad 5)... And if you want to load this track into Atlas, or further study speeds, etc, then this is the Atlas track data :- http://geoffair.org/tmp/uas-01.txt Then on the NEXT flight I tried :- IO=--generic=file,out,10,uas-02.csv,playback Then I added a header line, to help analyze it in say an OpenOffice spreadsheet import - see - http://geoffair.org/tmp/uas-02.csv On this 2nd flight, this crash took longer, since it (randomly) turned left first, where as mentioned it holds more stable, but then eventually went into a right turn, stalled, recovered, stalled again, and CRASHED... And as you know well, downloading this file, and using say - $ ./fgfs --fg-root=/point/to/fgfs/data --timeofday=noon \ --aircraft=f-14b-uas --carrier=Vinson \ --generic=file,in,10,uas-02.csv,playback --fdm=external you too can enjoy this fateful flight ;=)) In 'chase' view, you can clearly see the right roll increase, the nose coming up, and the stall, recovery, then repeated, and BANG, into the water... I know it is difficult to work on, debug, fix something that obviously does not happen in your case... Maybe if you do not enter any route, or something... And this is all with SG/FG git of 2011-09-14... Any other ideas? Regards, Geoff. On Thu, 2011-09-22 at 14:00 -0500, Curtis Olson wrote: On Thu, Sep 22, 2011 at 1:25 PM, Geoff McLane wrote: Hi Curt, A pleasure, and FUN ;=)) Yes, I know a low frame rate can play havoc when you are trying to fine control an aircraft from its attitude feedback, and I should have mentioned my rate, but is always in the high 50-70 fps range in this Ubuntu machine... so should NOT be a factor... Ok, 50-70 should be perfect. I just did another few runs, and this time it crashed just while circling... it was in a right bank, which got too much and the nose came up, and it stalled... I am mostly in the 'chase' view... This is really strange. I have seen nothing like this except when I inadvertantly applied external control inputs through a strange combination of linux virtual desktops and flightgear capturing the hotkey to come back to the FlightGear virtual desktop. So two thoughts here. If you have a joystick connected, could you try unplugging it to see if that helps? Could you also press 5 on the numeric keypad to make sure all the flight control inputs are centered. Because of the way the F-14b FCS is wired together in combination with the yasim flight surfaces, you can still input elevator and aileron and trim and cause conflicts that you might not see in other simpler aircraft that use aileron and elevator directly. The first time this happened at 2000 feet, it caught itself - leveled a bit and bumped the throttles, and began climbing back... But a little later, 20-30 secs, it happened again, and this time was still too low to recover, and SPLASH... I had not previously let it fly in the 'circle' mode for too long, but now note if I leave it in circling
Re: [Flightgear-devel] Any alpha testers with a bit of extra time on their hands?
On Fri, 23 Sep 2011 09:47:35 -0500, Curtis wrote in message cahtsj_edpuscxjf3m8_fbzzx4+-m8ugdahhcx9nfk+43zwd...@mail.gmail.com: Hi Geoff, I'm starting to run low on ideas here. I assume you don't have any crazy/severe turbulence turned on or your plots would be all over the place. Are you running out of fuel and your engines dying? If you open the autopilot dialog (F11) you can see the target speed and if you have the hud turned on you can see the actual speed in any view. ..what's your autopilot, fuel load etc settings? The works, please, I suspect you have something set that we guinea pigs are missing. Is e.g. your script actually controlling both jet engines? If you are circling with a target speed of 150 and your airspeed is less than than and you are decending, then definitely check your engine output. There is a fuel dialog box under the f-14b menu and you might double check that to see if you have any fuel in your tanks. For what it's worth, I'm rock solid in circling and the only time I have ever stalled out of the sky or really got out of kilter is when I've had severe turbulence turned on. Moderate turbulence at all levels is actually pretty interesting because despite getting thrown all over the sky, I still hit the carrier deck pretty spot on every time. Curt. On Fri, Sep 23, 2011 at 9:35 AM, Geoff McLane wrote: Hi Curt, Ok, removed my joystick, and entered a '5', but still crashed while just in 'circle' mode - no route entered ;=(( As usual Atlas provides a good 'view' as to what happened - added - ATLAS=--atlas=socket,out,IP,5500,udp to output to Atlas running in a 2nd machine... See - http://geoffair.org/tmp/uas-01.jpg for a graph of the flight... The two blips in the graphs show the first stall, but it recovers and begins to climb back, and the 2nd the second stall, this time too low to recover, so into the drink ;=(( CRASH! This is a view of the 'crazy' flight track http://geoffair.org/tmp/uas-02.jpg Obviously the pig-tail loops are the 'stalls'... remember with NO joystick attached and starting with centered controls (NumPad 5)... And if you want to load this track into Atlas, or further study speeds, etc, then this is the Atlas track data :- http://geoffair.org/tmp/uas-01.txt Then on the NEXT flight I tried :- IO=--generic=file,out,10,uas-02.csv,playback Then I added a header line, to help analyze it in say an OpenOffice spreadsheet import - see - http://geoffair.org/tmp/uas-02.csv On this 2nd flight, this crash took longer, since it (randomly) turned left first, where as mentioned it holds more stable, but then eventually went into a right turn, stalled, recovered, stalled again, and CRASHED... And as you know well, downloading this file, and using say - $ ./fgfs --fg-root=/point/to/fgfs/data --timeofday=noon \ --aircraft=f-14b-uas --carrier=Vinson \ --generic=file,in,10,uas-02.csv,playback --fdm=external you too can enjoy this fateful flight ;=)) In 'chase' view, you can clearly see the right roll increase, the nose coming up, and the stall, recovery, then repeated, and BANG, into the water... I know it is difficult to work on, debug, fix something that obviously does not happen in your case... Maybe if you do not enter any route, or something... And this is all with SG/FG git of 2011-09-14... Any other ideas? Regards, Geoff. On Thu, 2011-09-22 at 14:00 -0500, Curtis Olson wrote: On Thu, Sep 22, 2011 at 1:25 PM, Geoff McLane wrote: Hi Curt, A pleasure, and FUN ;=)) Yes, I know a low frame rate can play havoc when you are trying to fine control an aircraft from its attitude feedback, and I should have mentioned my rate, but is always in the high 50-70 fps range in this Ubuntu machine... so should NOT be a factor... Ok, 50-70 should be perfect. I just did another few runs, and this time it crashed just while circling... it was in a right bank, which got too much and the nose came up, and it stalled... I am mostly in the 'chase' view... This is really strange. I have seen nothing like this except when I inadvertantly applied external control inputs through a strange combination of linux virtual desktops and flightgear capturing the hotkey to come back to the FlightGear virtual desktop. So two thoughts here. If you have a joystick connected, could you try unplugging it to see if that helps? Could you also press 5 on the numeric keypad to make sure all the flight control inputs are centered. Because of the way the F-14b FCS is wired together in combination with the yasim flight surfaces, you can still input elevator and aileron and trim and cause conflicts that you might not see in other simpler aircraft that
Re: [Flightgear-devel] Any alpha testers with a bit of extra time on their hands?
Hi Curt, Using real weather fetch... no particular turbulence... Have HUD on, and holding 150, steady... as indicated in auto-target (F11), and as shown by the speed (kts) graph... Not descending, in fact usually still climbing to target 2000, or holding steady at 2000... as the Altitude and Climb Rate graphs show... Got more than 1100 lbs of fuel... from f-14b menu item... in the stall see and hear the engines come up due to the rapid speed drop from too steep of AOA... As the playback shows, in a right bank, quite quickly the nose pitches up, putting it in a stall... If in the cockpit at the time, you hear what I think is a stall warning... Takes about 1200-1400 feet to recover... if it has that altitude at the time... and will have more than 170+ at recovery, due to engine increase... lots of fuel... And in more tries, using the 'gohome' before this stall problem happens, get a smooth landing only about 1 out of 5 or 10 ;=(( Into the back (little too low), into the superstructure (little too high), into the water after touching the deck at a 30-40 degree off runway line diagonal ;=(( Ok, I too am out of ideas... I guess the scenario only works for some ;=)) will leave it for now... this 'bunny' is dying... Maybe others will have better luck... and FUN... Regards, Geoff. On Fri, 2011-09-23 at 09:47 -0500, Curtis Olson wrote: Hi Geoff, I'm starting to run low on ideas here. I assume you don't have any crazy/severe turbulence turned on or your plots would be all over the place. Are you running out of fuel and your engines dying? If you open the autopilot dialog (F11) you can see the target speed and if you have the hud turned on you can see the actual speed in any view. If you are circling with a target speed of 150 and your airspeed is less than than and you are decending, then definitely check your engine output. There is a fuel dialog box under the f-14b menu and you might double check that to see if you have any fuel in your tanks. For what it's worth, I'm rock solid in circling and the only time I have ever stalled out of the sky or really got out of kilter is when I've had severe turbulence turned on. Moderate turbulence at all levels is actually pretty interesting because despite getting thrown all over the sky, I still hit the carrier deck pretty spot on every time. Curt. On Fri, Sep 23, 2011 at 9:35 AM, Geoff McLane wrote: Hi Curt, Ok, removed my joystick, and entered a '5', but still crashed while just in 'circle' mode - no route entered ;=(( As usual Atlas provides a good 'view' as to what happened - added - ATLAS=--atlas=socket,out,IP,5500,udp to output to Atlas running in a 2nd machine... See - http://geoffair.org/tmp/uas-01.jpg for a graph of the flight... The two blips in the graphs show the first stall, but it recovers and begins to climb back, and the 2nd the second stall, this time too low to recover, so into the drink ;=(( CRASH! This is a view of the 'crazy' flight track http://geoffair.org/tmp/uas-02.jpg Obviously the pig-tail loops are the 'stalls'... remember with NO joystick attached and starting with centered controls (NumPad 5)... And if you want to load this track into Atlas, or further study speeds, etc, then this is the Atlas track data :- http://geoffair.org/tmp/uas-01.txt Then on the NEXT flight I tried :- IO=--generic=file,out,10,uas-02.csv,playback Then I added a header line, to help analyze it in say an OpenOffice spreadsheet import - see - http://geoffair.org/tmp/uas-02.csv On this 2nd flight, this crash took longer, since it (randomly) turned left first, where as mentioned it holds more stable, but then eventually went into a right turn, stalled, recovered, stalled again, and CRASHED... And as you know well, downloading this file, and using say - $ ./fgfs --fg-root=/point/to/fgfs/data --timeofday=noon \ --aircraft=f-14b-uas --carrier=Vinson \ --generic=file,in,10,uas-02.csv,playback --fdm=external you too can enjoy this fateful flight ;=)) In 'chase' view, you can clearly see the right roll increase, the nose coming up, and the stall, recovery, then repeated, and BANG, into the water... I know it is difficult to work on, debug, fix something that obviously does not happen in your case... Maybe if you do not enter any route, or something... And this is all with SG/FG git of
Re: [Flightgear-devel] Any alpha testers with a bit of extra time on their hands?
Le 23/09/2011 16:47, Curtis Olson a écrit : Hi Geoff, I'm starting to run low on ideas here. I assume you don't have any crazy/severe turbulence turned on or your plots would be all over the place. Are you running out of fuel and your engines dying? If you open the autopilot dialog (F11) you can see the target speed and if you have the hud turned on you can see the actual speed in any view. If you are circling with a target speed of 150 and your airspeed is less than than and you are decending, then definitely check your engine output. There is a fuel dialog box under the f-14b menu and you might double check that to see if you have any fuel in your tanks. For what it's worth, I'm rock solid in circling and the only time I have ever stalled out of the sky or really got out of kilter is when I've had severe turbulence turned on. Moderate turbulence at all levels is actually pretty interesting because despite getting thrown all over the sky, I still hit the carrier deck pretty spot on every time. Curt. Still no tests yet but just a though, In normal use (without the UAV script) I know that after TO (flaps down) you have to rise the flaps in before engaging the attitude autopilot mode. If you rise the flaps after engaging attitude autopilot mode, the a/c start to pitch up consistently. This has to be documented or fixed. I'll try to bring the maintainer to his workstation ASAP. Alexis On Fri, Sep 23, 2011 at 9:35 AM, Geoff McLane wrote: Hi Curt, Ok, removed my joystick, and entered a '5', but still crashed while just in 'circle' mode - no route entered ;=(( As usual Atlas provides a good 'view' as to what happened - added - ATLAS=--atlas=socket,out,IP,5500,udp to output to Atlas running in a 2nd machine... See - http://geoffair.org/tmp/uas-01.jpg for a graph of the flight... The two blips in the graphs show the first stall, but it recovers and begins to climb back, and the 2nd the second stall, this time too low to recover, so into the drink ;=(( CRASH! This is a view of the 'crazy' flight track http://geoffair.org/tmp/uas-02.jpg Obviously the pig-tail loops are the 'stalls'... remember with NO joystick attached and starting with centered controls (NumPad 5)... And if you want to load this track into Atlas, or further study speeds, etc, then this is the Atlas track data :- http://geoffair.org/tmp/uas-01.txt Then on the NEXT flight I tried :- IO=--generic=file,out,10,uas-02.csv,playback Then I added a header line, to help analyze it in say an OpenOffice spreadsheet import - see - http://geoffair.org/tmp/uas-02.csv On this 2nd flight, this crash took longer, since it (randomly) turned left first, where as mentioned it holds more stable, but then eventually went into a right turn, stalled, recovered, stalled again, and CRASHED... And as you know well, downloading this file, and using say - $ ./fgfs --fg-root=/point/to/fgfs/data --timeofday=noon \ --aircraft=f-14b-uas --carrier=Vinson \ --generic=file,in,10,uas-02.csv,playback --fdm=external you too can enjoy this fateful flight ;=)) In 'chase' view, you can clearly see the right roll increase, the nose coming up, and the stall, recovery, then repeated, and BANG, into the water... I know it is difficult to work on, debug, fix something that obviously does not happen in your case... Maybe if you do not enter any route, or something... And this is all with SG/FG git of 2011-09-14... Any other ideas? Regards, Geoff. On Thu, 2011-09-22 at 14:00 -0500, Curtis Olson wrote: On Thu, Sep 22, 2011 at 1:25 PM, Geoff McLane wrote: Hi Curt, A pleasure, and FUN ;=)) Yes, I know a low frame rate can play havoc when you are trying to fine control an aircraft from its attitude feedback, and I should have mentioned my rate, but is always in the high 50-70 fps range in this Ubuntu machine... so should NOT be a factor... Ok, 50-70 should be perfect. I just did another few runs, and this time it crashed just while circling... it was in a right bank, which got too much and the nose came up, and it stalled... I am mostly in the 'chase' view... This is really strange. I have seen nothing like this except when I inadvertantly applied external control inputs through a strange combination of linux virtual desktops and flightgear capturing the hotkey to come back to the FlightGear virtual desktop. So two thoughts here. If you have a joystick connected, could you try unplugging it to see if that
Re: [Flightgear-devel] Any alpha testers with a bit of extra time on their hands?
Geoff and Arnt and anyone else who is interested. I just updated the zip file overlay with a few changes. Geoff: you may be getting tired of being a bunny, but I played around with the roll controller and limited max target roll angle to +/-35 degrees. I also dialed down the gains a bit on final approach which will hopefully slow down the wild swings. More adjustment may be necessary, but I'd be interested in hearing if any of this helps your situation. I also set the default carrier speed to zero so if we get a few people out there playing around with this, we should be able to see each other via MP. That could be an additional fun element. I was just out there dodging XIII who trailed me around the pattern and let me live thankfully. :-) Here is the link with the zip file overlay download + installation and operation instructions: http://www.flightgear.org/uas-demo/ MP Call Sign: Shrike :-) Maybe see a few of you out there? Curt. On Fri, Sep 23, 2011 at 1:12 PM, Citronnier - Alexis Bory wrote: Le 23/09/2011 16:47, Curtis Olson a écrit : Hi Geoff, I'm starting to run low on ideas here. I assume you don't have any crazy/severe turbulence turned on or your plots would be all over the place. Are you running out of fuel and your engines dying? If you open the autopilot dialog (F11) you can see the target speed and if you have the hud turned on you can see the actual speed in any view. If you are circling with a target speed of 150 and your airspeed is less than than and you are decending, then definitely check your engine output. There is a fuel dialog box under the f-14b menu and you might double check that to see if you have any fuel in your tanks. For what it's worth, I'm rock solid in circling and the only time I have ever stalled out of the sky or really got out of kilter is when I've had severe turbulence turned on. Moderate turbulence at all levels is actually pretty interesting because despite getting thrown all over the sky, I still hit the carrier deck pretty spot on every time. Curt. Still no tests yet but just a though, In normal use (without the UAV script) I know that after TO (flaps down) you have to rise the flaps in before engaging the attitude autopilot mode. If you rise the flaps after engaging attitude autopilot mode, the a/c start to pitch up consistently. This has to be documented or fixed. I'll try to bring the maintainer to his workstation ASAP. Alexis On Fri, Sep 23, 2011 at 9:35 AM, Geoff McLane wrote: Hi Curt, Ok, removed my joystick, and entered a '5', but still crashed while just in 'circle' mode - no route entered ;=(( As usual Atlas provides a good 'view' as to what happened - added - ATLAS=--atlas=socket,out,IP,5500,udp to output to Atlas running in a 2nd machine... See - http://geoffair.org/tmp/uas-01.jpg for a graph of the flight... The two blips in the graphs show the first stall, but it recovers and begins to climb back, and the 2nd the second stall, this time too low to recover, so into the drink ;=(( CRASH! This is a view of the 'crazy' flight track http://geoffair.org/tmp/uas-02.jpg Obviously the pig-tail loops are the 'stalls'... remember with NO joystick attached and starting with centered controls (NumPad 5)... And if you want to load this track into Atlas, or further study speeds, etc, then this is the Atlas track data :- http://geoffair.org/tmp/uas-01.txt Then on the NEXT flight I tried :- IO=--generic=file,out,10,uas-02.csv,playback Then I added a header line, to help analyze it in say an OpenOffice spreadsheet import - see - http://geoffair.org/tmp/uas-02.csv On this 2nd flight, this crash took longer, since it (randomly) turned left first, where as mentioned it holds more stable, but then eventually went into a right turn, stalled, recovered, stalled again, and CRASHED... And as you know well, downloading this file, and using say - $ ./fgfs --fg-root=/point/to/fgfs/data --timeofday=noon \ --aircraft=f-14b-uas --carrier=Vinson \ --generic=file,in,10,uas-02.csv,playback --fdm=external you too can enjoy this fateful flight ;=)) In 'chase' view, you can clearly see the right roll increase, the nose coming up, and the stall, recovery, then repeated, and BANG, into the water... I know it is difficult to work on, debug, fix something that obviously does not happen in your case... Maybe if you do not enter any route, or something... And this is all with SG/FG git of 2011-09-14... Any other ideas? Regards, Geoff. On Thu, 2011-09-22 at 14:00 -0500, Curtis Olson wrote: On Thu, Sep 22, 2011 at 1:25 PM, Geoff McLane wrote:
Re: [Flightgear-devel] Any alpha testers with a bit of extra time on their hands?
Le 22/09/2011 05:03, Curtis Olson a écrit : I have something here that I think is kind of fun. Yup, I confirm this is plenty fun :-) It worked like a charm here. However with local weather, cold front, rough day condition, the challenge is there. Due to heavy turbs the system entered huge pitch oscillations at one mile or so in approach, but recovered stability just in time, doing a step descent (at least from chase view). Then it missed the wires, but well I think the bolter function is not there yet :-) Whit acceptable weather every thing worked as expected for the two first attempts. Then, as I was continuing this mail, the thing started to try turning the hardest possible, +/- 75deg roll and 43 AoA, ending in the water. the last attempt was aborted due to dinner time but I noticed that the switch between climbout and circle induced also a serious oscillation phase, that is AP overacting during 10 or 20 secs. (fps around 20). Then after dinner a long serial of perfect runs. I've no idea yet about what could help solving those problems. Actually there are 2 birds flying mostly the same pattern 150KTS@2000FT above the Vinson !!! That's Shrike. Some ideas: - Key 'Enter' closes the control window, it shouldn't. - The engineering HUD would be more appropriate with aircraft reference instead of f-16 like with camera reference, at least to have an idea of the controls setting. - Why not simply add the camera view with a high view number so it take place in the original numbering scheme between RIO and Pilot's view, thus keeping the usual shortcuts available ? - This kind of well formed approach would be very nice: http://www.maison-capestang.com/fg/a6/A-6E-carrier-landing-pattern-ng.png - The Downwind to Final switch is a bit rough and the gear is downed at the same time, this has a weird visual effect. - Moving target detection on mouse click and lock. - A 3D control panel in the cockpit, looking a bit custom, with red tape and big labels, like those you can see on test beds... I wonder who could do that. - Readable Nasal ??? Conclusion: AWESOME !!! Thanks a lot for sharing this, Alexis I've been fiddling with this off and on since last fall and decided it was time to clean it up a bit and quit hording all the fun for myself. Basically I have taken the F-14b and created a high performance Navy drone out of it. It can auto-launch from a carrier, auto fly a route (if you've input one) and can do circle holds (compensating for wind.) I've added a simulated gyro stabilized camera that will point at anything you click on and then hold that view steady no matter what the airplane does (similar to what real uav's can do.) Finally, you can command it to return home and it will find the carrier, setup a reasonable approach and nail the landing perfectly every time (factoring in wind, carrier speed, etc.) I put together a quick web page that includes more of an explanation and description of what the demo does. I have a link to a zip file you need to download. This must be extracted over the top of the existing f-14b as per the installation instructions on the following web site: http://www.flightgear.org/uas-demo/ I'm hoping to get a few people that would like to try this and report back on a couple things: - were you able to get it to work? Were there any missing files or major blunders in the .zip file package? - are there places where my web page instructions stink, and can you help me write better or more accurate instructions, especially for the Mac - I already know my instructions for setting up the vinson demo aren't good, but it's been so long since I tried to do this on windows I forget all the fgrun details. Maybe there is an easier way now? - finally, what do you think? general impressions? things you thought were especially cool, or especially stupid? You probably can think of a dozen feature requests, and I have some things in the pipeline already. (For instance I have a refueling mode that is currently disabled, but almost is close to working. And I've done some preliminary work on adapting all of the auto-land logic for runway landings.) - if you happen to go look at the nasal code that does all the magic, please don't judge me (quoting Eskeletor from nacho libre) -- that was actually a fun sub-project (for a former computer scientist.) :-) - Oh, and eventually I'd like to add pictures to the instructions. If you happen to catch an especially cool looking view (weather, clouds, time of day, sun, sun glint, scene composition, etc.) then please feel free to send me a picture or two (or even a youtube movie) so I can make the instructions prettier and more exciting. :-) If I can get this demo all cleaned up and generally running pretty well, I have another UAS demo that is similar, but centered around the ATI Resolution-3 airframe (which is a 92 2.33m composite marinized
Re: [Flightgear-devel] Any alpha testers with a bit of extra time on their hands?
Le 23/09/2011 23:12, Curtis Olson a écrit : Geoff and Arnt and anyone else who is interested. I just updated the zip file overlay with a few changes. Geoff: you may be getting tired of being a bunny, but I played around with the roll controller and limited max target roll angle to +/-35 degrees. I also dialed down the gains a bit on final approach which will hopefully slow down the wild swings. More adjustment may be necessary, but I'd be interested in hearing if any of this helps your situation. I also set the default carrier speed to zero so if we get a few people out there playing around with this, we should be able to see each other via MP. That could be an additional fun element. I was just out there dodging XIII who trailed me around the pattern and let me live thankfully. :-) Here is the link with the zip file overlay download + installation and operation instructions: http://www.flightgear.org/uas-demo/ MP Call Sign: Shrike :-) Woot :-) so I missed the update, I just read this post after posting the previous one. And was wondering who was flying around there ! Model view ought to be interesting in case of one other tester just encounter problems. Greetings, Alexis Maybe see a few of you out there? Curt. On Fri, Sep 23, 2011 at 1:12 PM, Citronnier - Alexis Bory wrote: Le 23/09/2011 16:47, Curtis Olson a écrit : Hi Geoff, I'm starting to run low on ideas here. I assume you don't have any crazy/severe turbulence turned on or your plots would be all over the place. Are you running out of fuel and your engines dying? If you open the autopilot dialog (F11) you can see the target speed and if you have the hud turned on you can see the actual speed in any view. If you are circling with a target speed of 150 and your airspeed is less than than and you are decending, then definitely check your engine output. There is a fuel dialog box under the f-14b menu and you might double check that to see if you have any fuel in your tanks. For what it's worth, I'm rock solid in circling and the only time I have ever stalled out of the sky or really got out of kilter is when I've had severe turbulence turned on. Moderate turbulence at all levels is actually pretty interesting because despite getting thrown all over the sky, I still hit the carrier deck pretty spot on every time. Curt. Still no tests yet but just a though, In normal use (without the UAV script) I know that after TO (flaps down) you have to rise the flaps in before engaging the attitude autopilot mode. If you rise the flaps after engaging attitude autopilot mode, the a/c start to pitch up consistently. This has to be documented or fixed. I'll try to bring the maintainer to his workstation ASAP. Alexis On Fri, Sep 23, 2011 at 9:35 AM, Geoff McLane wrote: Hi Curt, Ok, removed my joystick, and entered a '5', but still crashed while just in 'circle' mode - no route entered ;=(( As usual Atlas provides a good 'view' as to what happened - added - ATLAS=--atlas=socket,out,IP,5500,udp to output to Atlas running in a 2nd machine... See - http://geoffair.org/tmp/uas-01.jpg for a graph of the flight... The two blips in the graphs show the first stall, but it recovers and begins to climb back, and the 2nd the second stall, this time too low to recover, so into the drink ;=(( CRASH! This is a view of the 'crazy' flight track http://geoffair.org/tmp/uas-02.jpg Obviously the pig-tail loops are the 'stalls'... remember with NO joystick attached and starting with centered controls (NumPad 5)... And if you want to load this track into Atlas, or further study speeds, etc, then this is the Atlas track data :- http://geoffair.org/tmp/uas-01.txt Then on the NEXT flight I tried :- IO=--generic=file,out,10,uas-02.csv,playback Then I added a header line, to help analyze it in say an OpenOffice spreadsheet import - see - http://geoffair.org/tmp/uas-02.csv On this 2nd flight, this crash took longer, since it (randomly) turned left first, where as mentioned it holds more stable, but then eventually went into a right turn, stalled, recovered, stalled again, and CRASHED... And as you know well, downloading this file, and using say - $ ./fgfs --fg-root=/point/to/fgfs/data --timeofday=noon \ --aircraft=f-14b-uas --carrier=Vinson \
Re: [Flightgear-devel] Any alpha testers with a bit of extra time on their hands?
On Fri, 23 Sep 2011 23:44:02 +0200, Citronnier wrote in message 4e7cfda2.7060...@gmail.com: Le 23/09/2011 23:12, Curtis Olson a écrit : Geoff and Arnt and anyone else who is interested. I just updated the zip file overlay with a few changes. Geoff: you may be getting tired of being a bunny, but I played around with the roll controller and limited max target roll angle to +/-35 degrees. I also dialed down the gains a bit on final approach which will hopefully slow down the wild swings. More adjustment may be necessary, but I'd be interested in hearing if any of this helps your situation. ..a wee bit, now takes off and makes it ~1000 feet up, then it rolls to the right and makes it ~200 feet into the drink, and repeats the stunt seated in the cockpit (rather than in the camera), uncommanded on Reset button pushes. ..it's trying to orbit the carrier in the vertical plane? ..trying the operator click mode on targets like the merchantman near the Nimitz, works, until the demo is airborne, then it picks the Carrier target and tries a vertical orbit around it. ..refetching the merchantman with the operator mouse click mode, dives the demo into the drink between the 2 vessels. ..debug idea for Curtis: try the Nimitz too. I also set the default carrier speed to zero so if we get a few people out there playing around with this, we should be able to see each other via MP. That could be an additional fun element. I was just out there dodging XIII who trailed me around the pattern and let me live thankfully. :-) Here is the link with the zip file overlay download + installation and operation instructions: http://www.flightgear.org/uas-demo/ MP Call Sign: Shrike :-) Woot :-) so I missed the update, I just read this post after posting the previous one. And was wondering who was flying around there ! Model view ought to be interesting in case of one other tester just encounter problems. Greetings, Alexis Maybe see a few of you out there? Curt. On Fri, Sep 23, 2011 at 1:12 PM, Citronnier - Alexis Bory wrote: Le 23/09/2011 16:47, Curtis Olson a écrit : Hi Geoff, I'm starting to run low on ideas here. I assume you don't have any crazy/severe turbulence turned on or your plots would be all over the place. Are you running out of fuel and your engines dying? If you open the autopilot dialog (F11) you can see the target speed and if you have the hud turned on you can see the actual speed in any view. If you are circling with a target speed of 150 and your airspeed is less than than and you are decending, then definitely check your engine output. There is a fuel dialog box under the f-14b menu and you might double check that to see if you have any fuel in your tanks. For what it's worth, I'm rock solid in circling and the only time I have ever stalled out of the sky or really got out of kilter is when I've had severe turbulence turned on. Moderate turbulence at all levels is actually pretty interesting because despite getting thrown all over the sky, I still hit the carrier deck pretty spot on every time. Curt. Still no tests yet but just a though, In normal use (without the UAV script) I know that after TO (flaps down) you have to rise the flaps in before engaging the attitude autopilot mode. If you rise the flaps after engaging attitude autopilot mode, the a/c start to pitch up consistently. This has to be documented or fixed. I'll try to bring the maintainer to his workstation ASAP. Alexis On Fri, Sep 23, 2011 at 9:35 AM, Geoff McLane wrote: Hi Curt, Ok, removed my joystick, and entered a '5', but still crashed while just in 'circle' mode - no route entered ;=(( As usual Atlas provides a good 'view' as to what happened - added - ATLAS=--atlas=socket,out,IP,5500,udp to output to Atlas running in a 2nd machine... See - http://geoffair.org/tmp/uas-01.jpg for a graph of the flight... The two blips in the graphs show the first stall, but it recovers and begins to climb back, and the 2nd the second stall, this time too low to recover, so into the drink ;=(( CRASH! This is a view of the 'crazy' flight track http://geoffair.org/tmp/uas-02.jpg Obviously the pig-tail loops are the 'stalls'... remember with NO joystick attached and starting with centered controls (NumPad 5)... And if you want to load this track into Atlas, or further study speeds, etc, then this is the Atlas track data :-
Re: [Flightgear-devel] Any alpha testers with a bit of extra time on their hands?
Hi Curt, Always a bunny to try NEW things, and eventually got there ;=)) I think you should for sure say somewhere to add the option --carrier=Vinson when running fgfs, either via fgrun, or on the command line... Of course this is implied, but my first attempt was without this ;=(( And it would also be good to mention the aircraft is the --aircraft=f_14b-uas option... if not using fgrun, or 'Drone f-14b' in fgrun... Again implied, but not stated... So - 1. Backed up, and unzipped into f-14b 2. Loaded drone --aircraft=f-14b-uas 3. Deselected Nimitz, and selected Vinson 4. Exit and restart Attempt 1: -- But am placed on runway 10L at KSFO... with a view of my wheels... so ok, I launch, and it starts to circle KSFO at a very low altitude... Then click Go Home, and it heads and finds Vinson out to sea... but refuses to land... It looks like it is lining up, but on each approach, after it changed the flight task to 'downwind', it circles there... many circles, and circles... Pushing Go Home again, changes flight task to 'gohome' but on close approach, with flaps down, it veers to the left, and switches to 'downwind' again... After a few repeats of this, it eventually switched to 'final' and crashed into the sea on a too steep right banking maneuver... A reset put me back at KSFO... At least on reset the HUD appeared ;=)) I had not particularly noticed its absence until it suddenly appeared ;=() Tried another Launch! and when circling KSFO, again GoHome... This was much better in that it went from 'gohome', to 'downwind', to 'final', to 'flare'... But the carrier approach was WILD, with too large a left and right swings over and past the center landing line... over compensating... And at 'flare' it was BELOW the carrier deck level, and crashed into the behind of the carrier... Exit fgfs to think... Attempt 2: -- Then eventually thought of, and found the --carrier=Vinson option, so this 2nd attempt initialized on the Carrier... PHEW ;=)) But after Launch, circle a bit, then Go Home, crashed into the sea on 'downwind'... in a too steep bank... so reset 2nd takeoff, circle, and click gohome, and eventually, had a good landing ;=)) From downwind - final - flare - touchdown - shutdown - end - and HAPPINESS... Attached below is the usage and console output... Answers and comments: Yes, eventually got it 'working', but see the suggested clear addition of the --aircraft=f-14b-uas and --carrier=Vinson to the instructions somewhere... Having also played a little with auto line up and landing code logic I do understand this is a time consuming 'art', but was quite shocked by the multiple CRASHES before one good landing... Wild left and right crossing, steep banking and losing altitude into the sea, and crashing 'below' deck level need to be worked on... And these are strange, in that the final good landing was VERY smooth indeed... Your 'Reset' seems to reset more than just your scenario... I had disabled Global weather fetch, and cleared the clouds, but after your 'reset' they returned... And just to round out the state - ... display, the 'gohome' state should be added to the output... there is nothing between - state - circle state - downwind Overall, quite some FUN ;=)) Interesting addition, so it could be put on display somewhere - an [ ] Auto-loop option, where an internal 'Launch!' is done, and after circling for say a few minutes, an internal 'gohome' done, and at the 'end', an internal 'reset', back to 'launch'... etc This 'Auto-loop' option could also vary the 'view' each few minutes ... camera - cockpit - chase - flyby - camera... HTH. Regards, Geoff. Attempt 1: Missed --carrier=Vinson option and disaster == run_fgfs.sh: Running: ./fgfs --fg-root=/home/geoff/fg/fg16/fgfs/data --aircraft=f-14b-uas --timeofday=noon Processing command line arguments Failed to find parking position at airport KSFO FGMultiplayMgr - No receiver port. Multiplayer mode disabled. Initializing Liveries HERE: crs = 149.9436573031764 dist = 148.2411422427136 loading scenario 'vinson_demo' getting flightplan: Cruise-1 AIShip: Cruise-1 initializing waypoints AIShip: Cruise-1 done initialising waypoints 0 creating 3D noise texture... DONE Pilot dual control ... initialized Initializing F-14B Systems Initializing F-14B fuel system Initializing F-14B weapons system Initializing Radar Data Initializing drone autoflight system. state - init-settle state - pretakeoff state - takeoff state - climbout state - route state - circle Scaling image '/home/geoff/fg/fg16/fgfs/data/Models/Maritime/Military/HeloPaint.png' from (700,446) to (512,512) state - downwind state - downwind state - downwind state - downwind state - downwind state - downwind state - downwind state - downwind state - final [crashed into sea] Saving F-14B fuel levels passed invalid index (0) to FGRouteMgr::jumpToIndex AIShip: Cruise-1
Re: [Flightgear-devel] Any alpha testers with a bit of extra time on their hands?
Hi Geoff, Thanks for checking it out! I was starting to get worried by the complete silence that no one would try this at all. :-) I'll tweak the instructions a bit as per your comments. And if you (or anyone else) has any other points that should be clarified or fixed, just holler. I will probably eventually post this on the DIYdrones site to see if we can pull in some of those guys to give FlightGear a try -- so I would like the instructions to be as newbie friendly as possible. With respect to the instability on the downwind and final legs of the approach, could you turn on your frame rate counter and see what kind of frame rates you are getting. In my experience the F-14b is very sensitive to low frame rates and when the frame rates drop below about 17 I have a *lot* of trouble flying manually or via autopilot. It has a pretty complex flight control system wired in and I have tried to build my autopilot on top of that rather than remove/replace it all. I originally started this process with the seahawk/nimitz, but at some point switched to the f-14b and the vinson because the models were so much more detailed. Reset: this is calling the main FlightGear reset (just like selecting it from the File menu) so yes indeed it does reset everything to original start up conditions. And just to reiterate, if anyone tries this and has a lot of trouble with stability in the autoland system, I'd be very interested in hearing what kind of frame rates they were seeing at the time. Thanks for being a bunny even though I'm not familiar with that expression (at least in this context). :-) Curt. On Thu, Sep 22, 2011 at 9:56 AM, Geoff McLane wrote: Hi Curt, Always a bunny to try NEW things, and eventually got there ;=)) I think you should for sure say somewhere to add the option --carrier=Vinson when running fgfs, either via fgrun, or on the command line... Of course this is implied, but my first attempt was without this ;=(( And it would also be good to mention the aircraft is the --aircraft=f_14b-uas option... if not using fgrun, or 'Drone f-14b' in fgrun... Again implied, but not stated... So - 1. Backed up, and unzipped into f-14b 2. Loaded drone --aircraft=f-14b-uas 3. Deselected Nimitz, and selected Vinson 4. Exit and restart Attempt 1: -- But am placed on runway 10L at KSFO... with a view of my wheels... so ok, I launch, and it starts to circle KSFO at a very low altitude... Then click Go Home, and it heads and finds Vinson out to sea... but refuses to land... It looks like it is lining up, but on each approach, after it changed the flight task to 'downwind', it circles there... many circles, and circles... Pushing Go Home again, changes flight task to 'gohome' but on close approach, with flaps down, it veers to the left, and switches to 'downwind' again... After a few repeats of this, it eventually switched to 'final' and crashed into the sea on a too steep right banking maneuver... A reset put me back at KSFO... At least on reset the HUD appeared ;=)) I had not particularly noticed its absence until it suddenly appeared ;=() Tried another Launch! and when circling KSFO, again GoHome... This was much better in that it went from 'gohome', to 'downwind', to 'final', to 'flare'... But the carrier approach was WILD, with too large a left and right swings over and past the center landing line... over compensating... And at 'flare' it was BELOW the carrier deck level, and crashed into the behind of the carrier... Exit fgfs to think... Attempt 2: -- Then eventually thought of, and found the --carrier=Vinson option, so this 2nd attempt initialized on the Carrier... PHEW ;=)) But after Launch, circle a bit, then Go Home, crashed into the sea on 'downwind'... in a too steep bank... so reset 2nd takeoff, circle, and click gohome, and eventually, had a good landing ;=)) From downwind - final - flare - touchdown - shutdown - end - and HAPPINESS... Attached below is the usage and console output... Answers and comments: Yes, eventually got it 'working', but see the suggested clear addition of the --aircraft=f-14b-uas and --carrier=Vinson to the instructions somewhere... Having also played a little with auto line up and landing code logic I do understand this is a time consuming 'art', but was quite shocked by the multiple CRASHES before one good landing... Wild left and right crossing, steep banking and losing altitude into the sea, and crashing 'below' deck level need to be worked on... And these are strange, in that the final good landing was VERY smooth indeed... Your 'Reset' seems to reset more than just your scenario... I had disabled Global weather fetch, and cleared the clouds, but after your 'reset' they returned... And just to round out the state - ... display, the 'gohome' state should be added to the output... there is nothing between - state - circle state - downwind
Re: [Flightgear-devel] Any alpha testers with a bit of extra time on their hands?
Hi Curt, A pleasure, and FUN ;=)) Yes, I know a low frame rate can play havoc when you are trying to fine control an aircraft from its attitude feedback, and I should have mentioned my rate, but is always in the high 50-70 fps range in this Ubuntu machine... so should NOT be a factor... I just did another few runs, and this time it crashed just while circling... it was in a right bank, which got too much and the nose came up, and it stalled... I am mostly in the 'chase' view... The first time this happened at 2000 feet, it caught itself - leveled a bit and bumped the throttles, and began climbing back... But a little later, 20-30 secs, it happened again, and this time was still too low to recover, and SPLASH... I had not previously let it fly in the 'circle' mode for too long, but now note if I leave it in circling mode, it will eventually end up in the water... seldom lasts more than 5 or 10 minutes... You seem to be deliberately holding its speed down around 150 - I see air-brakes come up when greater than this, and throttle back - and although flaps (I think full flap?) are still applied, 150 must be quite 'low' for this sleek bird... And I am not sure how many degrees each marking on the hud bottom bank indicator represents, and while it starts the banking in between the 1 and 2 of the 'big' marks, at the stall point it is beyond the 2nd big mark, approaching, even reaching the 3rd big mark, which is on the horizontal - ie 90 degrees! At the moment of stall it loses 1200-1400 feet in 1-3 seconds... while it can happen in a right or left turn, it does seem to happen quicker in a right turn... I now understand the 'reset' is a full sim reset, but that is not too helpful if you have set up say a particular weather, wind or something that you want to repeat... must get around to feeding that in, in the command, so a reset puts it back (I hope)... If you could describe a bit more where some of this is decided/calculated I too could try tweaking some values... I would probably bump the speed a little, and really watch the bank angle... those stubby little wings do not give much lift anyway, but the slender body gives close to none ;=)) As mentioned, I too have more than a passing interest in automated flight control... Regards, Geoff. PS: OT: I too searched a little for the expression to be a 'bunny', but could not really find anything ;=(( I am sure it comes from my Australian origin, and has the meaning to take the rap, take the medicine, sort of to be the guinea pig... Why poor little bunny rabbits feature I just do not know ;=)) Maybe from when Australia had a big war on rabbits _MANY_ years ago, and put out millions of traps for the bunnies, as well as other methods, like poisons - myxomatosis... So to be a bunny was to be trapped ;=(()) Maybe other Australian's have a better memory than me, and can explain it better, but meantime I will blame my parents, or the Australian educational system, for giving me such a stupid expression ;=() On reading up on 'to be a Guinea Pig', another very confusing expression - not really a 'pig' and not from Guinea! - I found a reference that in Johnston's Natural History, they go by the name Spanish Coney. And 'coney' was the old name for a rabbit, a bunny... Huh! Maybe the early immigrants to Australia decided to mix it up even more! ;=)) Or got it confused on the long boat ride half way around the world... On Thu, 2011-09-22 at 11:00 -0500, Curtis Olson wrote: Hi Geoff, Thanks for checking it out! I was starting to get worried by the complete silence that no one would try this at all. :-) I'll tweak the instructions a bit as per your comments. And if you (or anyone else) has any other points that should be clarified or fixed, just holler. I will probably eventually post this on the DIYdrones site to see if we can pull in some of those guys to give FlightGear a try -- so I would like the instructions to be as newbie friendly as possible. With respect to the instability on the downwind and final legs of the approach, could you turn on your frame rate counter and see what kind of frame rates you are getting. In my experience the F-14b is very sensitive to low frame rates and when the frame rates drop below about 17 I have a *lot* of trouble flying manually or via autopilot. It has a pretty complex flight control system wired in and I have tried to build my autopilot on top of that rather than remove/replace it all. I originally started this process with the seahawk/nimitz, but at some point switched to the f-14b and the vinson because the models were so much more detailed. Reset: this is calling the main FlightGear reset (just like selecting it from the File menu) so yes indeed it does reset everything to original start up conditions. And just to reiterate, if anyone tries this and has a lot of trouble with stability in the autoland system, I'd be
Re: [Flightgear-devel] Any alpha testers with a bit of extra time on their hands?
On Wed, 21 Sep 2011 22:03:43 -0500, Curtis wrote in message CAHtsj_cKv-ZEsXm-1h_+QVZtRUez6yUBHmLzccs=4jk=myr...@mail.gmail.com: I have something here that I think is kind of fun. I've been fiddling with this off and on since last fall and decided it was time to clean it up a bit and quit hording all the fun for myself. Basically I have taken the F-14b and created a high performance Navy drone out of it. It can auto-launch from a carrier, auto fly a route (if you've input one) and can do circle holds (compensating for wind.) I've added a simulated gyro stabilized camera that will point at anything you click on and then hold that view steady no matter what the airplane does (similar to what real uav's can do.) ..you saw these? TDL allows tracking moving targets, like your A380: http://www.youtube.com/watch?feature=player_embeddedv=1GhNXHCQGsM http://info.ee.surrey.ac.uk/Personal/Z.Kalal/ http://www.engadget.com/2011/03/31/zdenek-kalals-object-tracking-algorithm-learns-on-the-fly-like/ I put together a quick web page that includes more of an explanation and description of what the demo does. I have a link to a zip file you need to download. This must be extracted over the top of the existing f-14b as per the installation instructions on the following web site: http://www.flightgear.org/uas-demo/ ..now, will FG run on a pee wee eeepc? Thanks! Curt. -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Any alpha testers with a bit of extra time on their hands?
On Thu, Sep 22, 2011 at 1:25 PM, Geoff McLane wrote: Hi Curt, A pleasure, and FUN ;=)) Yes, I know a low frame rate can play havoc when you are trying to fine control an aircraft from its attitude feedback, and I should have mentioned my rate, but is always in the high 50-70 fps range in this Ubuntu machine... so should NOT be a factor... Ok, 50-70 should be perfect. I just did another few runs, and this time it crashed just while circling... it was in a right bank, which got too much and the nose came up, and it stalled... I am mostly in the 'chase' view... This is really strange. I have seen nothing like this except when I inadvertantly applied external control inputs through a strange combination of linux virtual desktops and flightgear capturing the hotkey to come back to the FlightGear virtual desktop. So two thoughts here. If you have a joystick connected, could you try unplugging it to see if that helps? Could you also press 5 on the numeric keypad to make sure all the flight control inputs are centered. Because of the way the F-14b FCS is wired together in combination with the yasim flight surfaces, you can still input elevator and aileron and trim and cause conflicts that you might not see in other simpler aircraft that use aileron and elevator directly. The first time this happened at 2000 feet, it caught itself - leveled a bit and bumped the throttles, and began climbing back... But a little later, 20-30 secs, it happened again, and this time was still too low to recover, and SPLASH... I had not previously let it fly in the 'circle' mode for too long, but now note if I leave it in circling mode, it will eventually end up in the water... seldom lasts more than 5 or 10 minutes... You seem to be deliberately holding its speed down around 150 - I see air-brakes come up when greater than this, and throttle back - and although flaps (I think full flap?) are still applied, 150 must be quite 'low' for this sleek bird... Normal landing approach in the real aircraft I believe is about 120 kts? I fly 135 kt approaches in the simulator. It should be able to hold 150 kts with the flaps down pretty easily. The point of slowing way down when circling is to keep the circle radius small enough so you can see what you are looking at. If you fly the circle at 600 kts, your radius will be 20 miles (just guessing) :-) and you won't be able to see anything. And I am not sure how many degrees each marking on the hud bottom bank indicator represents, and while it starts the banking in between the 1 and 2 of the 'big' marks, at the stall point it is beyond the 2nd big mark, approaching, even reaching the 3rd big mark, which is on the horizontal - ie 90 degrees! At the moment of stall it loses 1200-1400 feet in 1-3 seconds... while it can happen in a right or left turn, it does seem to happen quicker in a right turn... I now understand the 'reset' is a full sim reset, but that is not too helpful if you have set up say a particular weather, wind or something that you want to repeat... must get around to feeding that in, in the command, so a reset puts it back (I hope)... Well complain to the developers if a reset resets too agressively. :-) If you could describe a bit more where some of this is decided/calculated I too could try tweaking some values... I would probably bump the speed a little, and really watch the bank angle... those stubby little wings do not give much lift anyway, but the slender body gives close to none ;=)) As mentioned, I too have more than a passing interest in automated flight control... Regards, Geoff. PS: OT: I too searched a little for the expression to be a 'bunny', but could not really find anything ;=(( I am sure it comes from my Australian origin, and has the meaning to take the rap, take the medicine, sort of to be the guinea pig... Ok, I can understand that. Here we test cosmetics on little bunnies (so I'm told) but I'm sure we have to shave all their hair off first. Why poor little bunny rabbits feature I just do not know ;=)) Maybe from when Australia had a big war on rabbits _MANY_ years ago, and put out millions of traps for the bunnies, as well as other methods, like poisons - myxomatosis... So to be a bunny was to be trapped ;=(()) Maybe other Australian's have a better memory than me, and can explain it better, but meantime I will blame my parents, or the Australian educational system, for giving me such a stupid expression ;=() On reading up on 'to be a Guinea Pig', another very confusing expression - not really a 'pig' and not from Guinea! - I found a reference that in Johnston's Natural History, they go by the name Spanish Coney. And 'coney' was the old name for a rabbit, a bunny... Huh! In Peru Guinea Pig is a delicacy ... cui ... never had it myself that I'm aware of. Maybe the early immigrants to Australia decided to mix it up even more! ;=)) Or got it
Re: [Flightgear-devel] Any alpha testers with a bit of extra time on their hands?
On Thu, 22 Sep 2011 20:42:58 +0200, Arnt wrote in message 20110922204258.605fc...@nb6.lan: On Wed, 21 Sep 2011 22:03:43 -0500, Curtis wrote in message CAHtsj_cKv-ZEsXm-1h_+QVZtRUez6yUBHmLzccs=4jk=myr...@mail.gmail.com: I have something here that I think is kind of fun. I've been fiddling with this off and on since last fall and decided it was time to clean it up a bit and quit hording all the fun for myself. Basically I have taken the F-14b and created a high performance Navy drone out of it. It can auto-launch from a carrier, auto fly a route (if you've input one) and can do circle holds (compensating for wind.) I've added a simulated gyro stabilized camera that will point at anything you click on and then hold that view steady no matter what the airplane does (similar to what real uav's can do.) ..you saw these? TDL allows tracking moving targets, like your A380: http://www.youtube.com/watch?feature=player_embeddedv=1GhNXHCQGsM http://info.ee.surrey.ac.uk/Personal/Z.Kalal/ http://www.engadget.com/2011/03/31/zdenek-kalals-object-tracking-algorithm-learns-on-the-fly-like/ I put together a quick web page that includes more of an explanation and description of what the demo does. I have a link to a zip file you need to download. This must be extracted over the top of the existing f-14b as per the installation instructions on the following web site: http://www.flightgear.org/uas-demo/ ..now, will FG run on a pee wee eeepc? ..yes, @ 3fps, so the C172p is landable even without rudder control, I overshot 28R and used 28L instead, centerline touch down at taxiway N, aiming straight for full stop 'n exit on taxiway P. ;o) ..I'm on FG-1.9.1 with 3fps, what frame rate can I expect with FG-2.4? -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Any alpha testers with a bit of extra time on their hands?
Arnt, you have hijacked my thread, but if you are at 3fps with v1.9 then I'd recommend spending $10 on ebay to get yourself a decent video card and maybe $35 to get yourself a decent computer. :-) :-) :-) On Thu, Sep 22, 2011 at 2:28 PM, Arnt Karlsen a...@c2i.net wrote: On Thu, 22 Sep 2011 20:42:58 +0200, Arnt wrote in message 20110922204258.605fc...@nb6.lan: On Wed, 21 Sep 2011 22:03:43 -0500, Curtis wrote in message CAHtsj_cKv-ZEsXm-1h_+QVZtRUez6yUBHmLzccs=4jk=myr...@mail.gmail.com: I have something here that I think is kind of fun. I've been fiddling with this off and on since last fall and decided it was time to clean it up a bit and quit hording all the fun for myself. Basically I have taken the F-14b and created a high performance Navy drone out of it. It can auto-launch from a carrier, auto fly a route (if you've input one) and can do circle holds (compensating for wind.) I've added a simulated gyro stabilized camera that will point at anything you click on and then hold that view steady no matter what the airplane does (similar to what real uav's can do.) ..you saw these? TDL allows tracking moving targets, like your A380: http://www.youtube.com/watch?feature=player_embeddedv=1GhNXHCQGsM http://info.ee.surrey.ac.uk/Personal/Z.Kalal/ http://www.engadget.com/2011/03/31/zdenek-kalals-object-tracking-algorithm-learns-on-the-fly-like/ I put together a quick web page that includes more of an explanation and description of what the demo does. I have a link to a zip file you need to download. This must be extracted over the top of the existing f-14b as per the installation instructions on the following web site: http://www.flightgear.org/uas-demo/ ..now, will FG run on a pee wee eeepc? ..yes, @ 3fps, so the C172p is landable even without rudder control, I overshot 28R and used 28L instead, centerline touch down at taxiway N, aiming straight for full stop 'n exit on taxiway P. ;o) ..I'm on FG-1.9.1 with 3fps, what frame rate can I expect with FG-2.4? -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Curtis Olson: http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://gallinazo.flightgear.org -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Any alpha testers with a bit of extra time on their hands?
On Thu, 22 Sep 2011 14:00:49 -0500, Curtis wrote in message CAHtsj_crOGWDX43J5oKw7F6g12AWsRePoceNGW=a1b0txod...@mail.gmail.com: On Thu, Sep 22, 2011 at 1:25 PM, Geoff McLane wrote: You seem to be deliberately holding its speed down around 150 - I see air-brakes come up when greater than this, and throttle back - and although flaps (I think full flap?) are still applied, 150 must be quite 'low' for this sleek bird... Normal landing approach in the real aircraft I believe is about 120 kts? I fly 135 kt approaches in the simulator. It should be able to hold 150 kts with the flaps down pretty easily. ..the Navy guys fly approaches using AOA, not speeds, AFAIK. -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Any alpha testers with a bit of extra time on their hands?
On Thu, 22 Sep 2011 14:36:23 -0500, Curtis wrote in message CAHtsj_dh0m6BJ8k8gOEB0uzC5EpGARUTz=h1dgc5-+1d0z+...@mail.gmail.com: Arnt, you have hijacked my thread, but if you are at 3fps with v1.9 then I'd recommend spending $10 on ebay to get yourself a decent video card and maybe $35 to get yourself a decent computer. :-) :-) :-) ..have decent gear in my semi trailer storage, I'm on the road with an eeepc and a bad bios battery wire on my decent laptop. ;o) ..now, how about TLD and tracking moving targets? ;o) On Thu, Sep 22, 2011 at 2:28 PM, Arnt Karlsen a...@c2i.net wrote: On Thu, 22 Sep 2011 20:42:58 +0200, Arnt wrote in message 20110922204258.605fc...@nb6.lan: On Wed, 21 Sep 2011 22:03:43 -0500, Curtis wrote in message CAHtsj_cKv-ZEsXm-1h_+QVZtRUez6yUBHmLzccs=4jk=myr...@mail.gmail.com: ..you saw these? TDL allows tracking moving targets, like your A380: http://www.youtube.com/watch?feature=player_embeddedv=1GhNXHCQGsM http://info.ee.surrey.ac.uk/Personal/Z.Kalal/ http://www.engadget.com/2011/03/31/zdenek-kalals-object-tracking-algorithm-learns-on-the-fly-like/ -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Any alpha testers with a bit of extra time on their hands?
Le 22/09/2011 22:04, Arnt Karlsen a écrit : On Thu, 22 Sep 2011 14:00:49 -0500, Curtis wrote in message CAHtsj_crOGWDX43J5oKw7F6g12AWsRePoceNGW=a1b0txod...@mail.gmail.com: On Thu, Sep 22, 2011 at 1:25 PM, Geoff McLane wrote: You seem to be deliberately holding its speed down around 150 - I see air-brakes come up when greater than this, and throttle back - and although flaps (I think full flap?) are still applied, 150 must be quite 'low' for this sleek bird... Normal landing approach in the real aircraft I believe is about 120 kts? I fly 135 kt approaches in the simulator. It should be able to hold 150 kts with the flaps down pretty easily. ..the Navy guys fly approaches using AOA, not speeds, AFAIK. And a max 6000 lbs fuel in the tanks. FG's f-14b is quite tricky to fly with what is *supposed* to be the right AoA for approach. Side departure happen easily if your aren't smooth enough in your final turn. Curt, I didn't test yet, sorry, lake of time, but the last mods on properties in engines.nas and instrument.nas should be comited soon. Happy to see you all playing with the beast :-) Alexis -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Any alpha testers with a bit of extra time on their hands?
On Thu, 22 Sep 2011 22:36:45 +0200, Citronnier wrote in message 4e7b9c5d.6080...@gmail.com: Le 22/09/2011 22:04, Arnt Karlsen a écrit : On Thu, 22 Sep 2011 14:00:49 -0500, Curtis wrote in message CAHtsj_crOGWDX43J5oKw7F6g12AWsRePoceNGW=a1b0txod...@mail.gmail.com: On Thu, Sep 22, 2011 at 1:25 PM, Geoff McLane wrote: You seem to be deliberately holding its speed down around 150 - I see air-brakes come up when greater than this, and throttle back - and although flaps (I think full flap?) are still applied, 150 must be quite 'low' for this sleek bird... Normal landing approach in the real aircraft I believe is about 120 kts? I fly 135 kt approaches in the simulator. It should be able to hold 150 kts with the flaps down pretty easily. ..the Navy guys fly approaches using AOA, not speeds, AFAIK. And a max 6000 lbs fuel in the tanks. FG's f-14b is quite tricky to fly with what is *supposed* to be the right AoA for approach. Side departure happen easily if your aren't smooth enough in your final turn. ..and it does not like to T/O and climb on idle power, all Launch!!! button action I see is wild pre-crash oscillations, the Reset button tosses me into the cockpit rather than in the camera. ..Curtis, any reason your demo needs the USS Vinson, rather than a renamed USS Nimitz copy? ..Alexis, any changes to the f-14b since FG-1.9.1? Curt, I didn't test yet, sorry, lake of time, but the last mods on properties in engines.nas and instrument.nas should be comited soon. Happy to see you all playing with the beast :-) Alexis -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Any alpha testers with a bit of extra time on their hands?
I went with the Vinson because it is spiffier. Everything should (theoretically) work the same and just as well from the Nimitz. I believe the deck geometries are identical in FlightGear (conveniently.) ;-) Curt. On Thu, Sep 22, 2011 at 5:02 PM, Arnt Karlsen a...@c2i.net wrote: On Thu, 22 Sep 2011 22:36:45 +0200, Citronnier wrote in message 4e7b9c5d.6080...@gmail.com: Le 22/09/2011 22:04, Arnt Karlsen a écrit : On Thu, 22 Sep 2011 14:00:49 -0500, Curtis wrote in message CAHtsj_crOGWDX43J5oKw7F6g12AWsRePoceNGW=a1b0txod...@mail.gmail.com: On Thu, Sep 22, 2011 at 1:25 PM, Geoff McLane wrote: You seem to be deliberately holding its speed down around 150 - I see air-brakes come up when greater than this, and throttle back - and although flaps (I think full flap?) are still applied, 150 must be quite 'low' for this sleek bird... Normal landing approach in the real aircraft I believe is about 120 kts? I fly 135 kt approaches in the simulator. It should be able to hold 150 kts with the flaps down pretty easily. ..the Navy guys fly approaches using AOA, not speeds, AFAIK. And a max 6000 lbs fuel in the tanks. FG's f-14b is quite tricky to fly with what is *supposed* to be the right AoA for approach. Side departure happen easily if your aren't smooth enough in your final turn. ..and it does not like to T/O and climb on idle power, all Launch!!! button action I see is wild pre-crash oscillations, the Reset button tosses me into the cockpit rather than in the camera. ..Curtis, any reason your demo needs the USS Vinson, rather than a renamed USS Nimitz copy? ..Alexis, any changes to the f-14b since FG-1.9.1? Curt, I didn't test yet, sorry, lake of time, but the last mods on properties in engines.nas and instrument.nas should be comited soon. Happy to see you all playing with the beast :-) Alexis -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Curtis Olson: http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://gallinazo.flightgear.org -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Any alpha testers with a bit of extra time on their hands?
On Thu, 22 Sep 2011 17:20:51 -0500, Curtis wrote in message cahtsj_cjgngbynczckm2e8fhnct50lmi0yefatxjygtn+_y...@mail.gmail.com: I went with the Vinson because it is spiffier. Everything should (theoretically) work the same and just as well from the Nimitz. I believe the deck geometries are identical in FlightGear (conveniently.) ;-) Curt. ..aye, I've had one succesful T/O and climb out, found a ship to orbit, but could not fetch it due to the roll wobbling, the demo UVS eventually dove into the drink. ..the other T/O's emulates those 1902-1903 house boat attempts. Nimitz has catapults and afterburner restistant deck? I pass the bow @ ~80kts, then dives in. Autopilot settings dialogue has an AOA setting, which is the optimum T/O AOA for the f-14b? ..divide by zero errors in lines 78 or 114?: arnt@nb6:~$ fgfs --geometry=1024x600 --enable-fullscreen \ --carrier=Nimitz --aircraft=f-14b-uas [1] 1417 arnt@nb6:~$ FGMultiplayMgr - No receiver port, Multiplayermode disabled Initializing Liveries HERE: crs = 149.9436573031764 dist = 148.2411422427136 Initializing F-14B Instruments System Initializing F-14B fuel system Initializing Radar Data OpenAL error (AL_ILLEGAL_COMMAND): set_volume OpenAL error (AL_ILLEGAL_COMMAND): set_volume Initializing drone autoflight system. state - init-settle state - pretakeoff state - takeoff state - climbout state - route Nasal runtime error: nil used in numeric context at /usr/share/games/FlightGear/Aircraft/f-14b/Nasal/uas-demo.nas, line 78 called from: /usr/share/games/FlightGear/Aircraft/f-14b/Nasal/uas-demo.nas, line 114 AL lib: ALc.c:1420: alcDestroyContext(): deleting 4 Source(s) AL lib: ALc.c:1818: alcCloseDevice(): deleting 165 Buffer(s) [1]+ Donefgfs --geometry=1024x600 --enable-fullscreen --carrier=Nimitz --aircraft=f-14b-uas arnt@nb6:~$ On Thu, Sep 22, 2011 at 5:02 PM, Arnt Karlsen a...@c2i.net wrote: On Thu, 22 Sep 2011 22:36:45 +0200, Citronnier wrote in message 4e7b9c5d.6080...@gmail.com: Le 22/09/2011 22:04, Arnt Karlsen a écrit : On Thu, 22 Sep 2011 14:00:49 -0500, Curtis wrote in message CAHtsj_crOGWDX43J5oKw7F6g12AWsRePoceNGW=a1b0txod...@mail.gmail.com: On Thu, Sep 22, 2011 at 1:25 PM, Geoff McLane wrote: You seem to be deliberately holding its speed down around 150 - I see air-brakes come up when greater than this, and throttle back - and although flaps (I think full flap?) are still applied, 150 must be quite 'low' for this sleek bird... Normal landing approach in the real aircraft I believe is about 120 kts? I fly 135 kt approaches in the simulator. It should be able to hold 150 kts with the flaps down pretty easily. ..the Navy guys fly approaches using AOA, not speeds, AFAIK. And a max 6000 lbs fuel in the tanks. FG's f-14b is quite tricky to fly with what is *supposed* to be the right AoA for approach. Side departure happen easily if your aren't smooth enough in your final turn. ..and it does not like to T/O and climb on idle power, all Launch!!! button action I see is wild pre-crash oscillations, the Reset button tosses me into the cockpit rather than in the camera. ..Curtis, any reason your demo needs the USS Vinson, rather than a renamed USS Nimitz copy? ..Alexis, any changes to the f-14b since FG-1.9.1? Curt, I didn't test yet, sorry, lake of time, but the last mods on properties in engines.nas and instrument.nas should be comited soon. Happy to see you all playing with the beast :-) Alexis -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Any alpha testers with a bit of extra time on their hands?
I have something here that I think is kind of fun. I've been fiddling with this off and on since last fall and decided it was time to clean it up a bit and quit hording all the fun for myself. Basically I have taken the F-14b and created a high performance Navy drone out of it. It can auto-launch from a carrier, auto fly a route (if you've input one) and can do circle holds (compensating for wind.) I've added a simulated gyro stabilized camera that will point at anything you click on and then hold that view steady no matter what the airplane does (similar to what real uav's can do.) Finally, you can command it to return home and it will find the carrier, setup a reasonable approach and nail the landing perfectly every time (factoring in wind, carrier speed, etc.) I put together a quick web page that includes more of an explanation and description of what the demo does. I have a link to a zip file you need to download. This must be extracted over the top of the existing f-14b as per the installation instructions on the following web site: http://www.flightgear.org/uas-demo/ I'm hoping to get a few people that would like to try this and report back on a couple things: - were you able to get it to work? Were there any missing files or major blunders in the .zip file package? - are there places where my web page instructions stink, and can you help me write better or more accurate instructions, especially for the Mac - I already know my instructions for setting up the vinson demo aren't good, but it's been so long since I tried to do this on windows I forget all the fgrun details. Maybe there is an easier way now? - finally, what do you think? general impressions? things you thought were especially cool, or especially stupid? You probably can think of a dozen feature requests, and I have some things in the pipeline already. (For instance I have a refueling mode that is currently disabled, but almost is close to working. And I've done some preliminary work on adapting all of the auto-land logic for runway landings.) - if you happen to go look at the nasal code that does all the magic, please don't judge me (quoting Eskeletor from nacho libre) -- that was actually a fun sub-project (for a former computer scientist.) :-) - Oh, and eventually I'd like to add pictures to the instructions. If you happen to catch an especially cool looking view (weather, clouds, time of day, sun, sun glint, scene composition, etc.) then please feel free to send me a picture or two (or even a youtube movie) so I can make the instructions prettier and more exciting. :-) If I can get this demo all cleaned up and generally running pretty well, I have another UAS demo that is similar, but centered around the ATI Resolution-3 airframe (which is a 92 2.33m composite marinized flying wing.) Then if that all goes well, I have actual embedded C code to do much of these same sorts of things that can run on a gumstix embedded computer (or similar.) This code is able to talk directly to flightgear via udp packets, and has actually flown in a couple different UAV airframes using real sensors and real actuators. So you might see a progression developing here from pure simulation with all the logic prototyped in nasal, to software in the loop running pure C/C++ code, to the same software running on actual embedded hardware (using FlightGear as reality), to the end result of an actual real life UAV. (And I've been using drone, UAS, and UAV pretty interchangeably here.) Thanks! Curt. -- Curtis Olson: http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://gallinazo.flightgear.org -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
