Thought this went to the list.
Begin forwarded message:
> From: Peter Brown <smoothwater...@adelphia.net>
> Date: January 4, 2011 11:58:58 AM EST
> To: Curtis Olson <curtol...@gmail.com>
> Subject: Re: [Flightgear-devel] Fwd: Generic Autopilot works by location?
>
>
> On Jan 4, 2011, at 11:38 AM, Curtis Olson wrote:
>
>> I skimmed through that message but haven't had a chance for a detailed read
>> through. It seemed rather complicated to get to the point where the bug is
>> tickled. I was hoping I could just run ./fgfs --aircraft=someaircraft
>> --airport=someairport and then pull up the autopilot settings dialog and see
>> that things were broken? But it seems like it's much more complicated than
>> that to tickle the bug?
>>
>> Curt.
>
> aircraft = MD-81
> airport = KBTV
> --prop:/autopilot/target-tracking/enable=1
>
> Pull up autopilot settings and attempt to change.
> If unable to change heading, alt hold, or speed to user setting, change
> /autopilot/target-tracking/target-root = '/ai/models/aircraft[0]' (string) to
> any number besides [0]. AP should then work.
> This can be done sitting on the runway.
>
> Peter
>
>>
>>
>> On Tue, Jan 4, 2011 at 10:27 AM, Peter Brown <smoothwater...@adelphia.net>
>> wrote:
>> Curt,
>>
>> I assume you saw the prior email I sent directly with the screen shots
>> included? If that's what you are referring to then yes, I agree it's
>> strange, but I am unable to narrow it down further due to my lack of
>> programming knowledge.
>>
>> Thanks,
>> Peter
>>
>> On Jan 4, 2011, at 11:23 AM, Curtis Olson wrote:
>>
>>> Hi Peter,
>>>
>>> I haven't had a chance to follow through and try to replicate what you are
>>> seeing, but it is strange if there is a link between the hud and the
>>> autopilot like that. I'm not sure I've ever played around with target
>>> tracking? I've never seen a "lock on" in flightgear, but I haven't played
>>> around with some of the military features much that some of the guys are
>>> developing. It seems really strange though if nothing else?
>>>
>>> If you can condense this down somehow and still feel there is a real
>>> problem once you've played with it more, let me know. I can't vouch for
>>> how much time I'll have, but I hate having weird obscure bugs lingering
>>> around. If too many of them stack up you can end up with an intractable
>>> mess.
>>>
>>> Thanks,
>>>
>>> Curt.
>>>
>>>
>>> On Mon, Jan 3, 2011 at 5:44 PM, Peter Brown <smoothwater...@adelphia.net>
>>> wrote:
>>> Curt,
>>>
>>> In working it more and more, my general feeling is threefold -
>>>
>>> 1 - it's likely a case of my not understanding completely how it the AP,
>>> HUD, and Target tracking are/were integrated. Meaning that while I assume
>>> target tracking allows you to actually lock on to another a/c, most pilots
>>> use it as a form of "tracking" other aircraft, as a visual reference. It
>>> appears that this is no longer there in the current git, but that may
>>> change when Tat creates a 2.2 build.
>>>
>>> 2 - I have found that once I enable the target tracking, the autopilot is
>>> unchangeable _unless_ I change the mp[x] to at least [8] (at Moffett
>>> Field), and then I can change the autopilot numbers to my preference. Once
>>> I've done that, I can change the tracking [x] back to any number with no
>>> change to the autopilot. At this point none of this matters with the
>>> current git files, as enabling target tracking does not bring up the
>>> tracking rings on the HUD. Multiplayers on hand while trying this on
>>> different aircraft were in the teens.
>>>
>>> 3 - I have not tried it, but my assumption is now that this same method
>>> will work everywhere, provided I keep the current files from git. Why the
>>> target tracking is not affected at the northern and southern latitudes is
>>> completely unknown. Outside of KSFO all the other airports had no
>>> multiplayers within range.
>>>
>>>
>>> So long and short is that seems to be pretty isolated to me.
>>> Something changed along the way, for using
>>> --prop:/autopilot/target-tracking/enable=1 for tracking ring display did
>>> not use to be a problem, and still isn't a problem for another mac user
>>> using Tat's snapshot. But obviously it does in what I have set up
>>> currently, so now that I know the workaround to get it working I can use it.
>>>
>>> Sorry for taking up your time.
>>> Peter
>>>
>>>
>>>
>>> On Jan 3, 2011, at 2:37 PM, Curtis Olson wrote:
>>>
>>> > Hi Peter,
>>> >
>>> > I can't think of any reason the basic autopilot functionality would be
>>> > tied to a particular location. Could you provide a specific aircraft and
>>> > airport (i.e. command line options) that tickle this bug? Perhaps it's
>>> > something with your local build? Perhaps it's something really obscure
>>> > that no one else has noticed?
>>> >
>>> > Thanks,
>>> >
>>> > Curt.
>>> >
>>>
>>>
>>>
>>>
>>> --
>>> Curtis Olson:
>>> http://www.atiak.com - http://aem.umn.edu/~uav/
>>> http://www.flightgear.org - http://www.flightgear.org/blogs/category/curt/
>>>
>>
>>
>>
>>
>> --
>> Curtis Olson:
>> http://www.atiak.com - http://aem.umn.edu/~uav/
>> http://www.flightgear.org - http://www.flightgear.org/blogs/category/curt/
>>
>
------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
