Hi Ron.
I've applied the patch you've sent and now I have the radiostack on my
pannel.
Strange... I have FG 0.9.10 and pa28-161 I'm using is the one that comes
with the original package.
Thanks for your help.
Thiago
Ron Jensen wrote:
On Thu, 2007-02-08 at 13:32 -0200, Thiago Drechsel wrote:
Hi Ron,
Ron Jensen wrote:
Truly bizarre, I fired up this aircraft and saw the radiostack, complete
with DME and though, what is Thiago talking about, its right there...
Then I looked at my CVS repository and realized my Cherokee is modified.
Don't remember doing that, but then I'm old. My
On Thu, 2007-02-08 at 18:55 -0500, John Denker wrote:
On 02/07/2007 02:14 PM, Andy Ross wrote:
So if there's a design flaw here, it's at a higher level. Maybe
what's really needed is a digit extractor animation instead.
Good news: The /design/ is not as flawed as it looks.
All
On Friday 09 February 2007 02:54, Dave Perry wrote:
On Fri, 2007-02-09 at 00:25 +, leee wrote:
Just checked again, with current cvs osg/simgear/flightgear, and I still
got the same problems. As before, re-setting the A/P via the menu seems
to kick everything into life. There also
On Friday 09 February 2007 01:54, Dave Perry wrote:
On Fri, 2007-02-09 at 00:25 +, leee wrote:
Just checked again, with current cvs osg/simgear/flightgear, and I still
got the same problems. As before, re-setting the A/P via the menu seems
to kick everything into life. There also
On Friday 09 February 2007 17:07, Roy Vegard Ovesen wrote:
On Friday 09 February 2007 02:54, Dave Perry wrote:
On Fri, 2007-02-09 at 00:25 +, leee wrote:
Just checked again, with current cvs osg/simgear/flightgear, and I
still got the same problems. As before, re-setting the A/P via
On Friday 09 February 2007 18:24, leee wrote:
Hi Roy,
I am getting this with the SU-37 and I believe the version in cvs displays
the problems. This is a pretty complex A/P setup with cascading up to
three levels and it also includes filters to un-tie some tied nodes so that
I could use
On Fri 9 February 2007 18:07, Roy Vegard Ovesen wrote:
On Friday 09 February 2007 02:54, Dave Perry wrote:
I believe that the problem Gérard and Lee has seen is not specific to the
KAP140 autopilot. apInit in kap140.nas _only_ initializes the properties
that belong to the KAP140 autopilot.
On Friday 09 February 2007 18:14, Roy Vegard Ovesen wrote:
On Friday 09 February 2007 18:24, leee wrote:
Hi Roy,
I am getting this with the SU-37 and I believe the version in cvs
displays the problems. This is a pretty complex A/P setup with cascading
up to three levels and it also
On 02/09/2007 11:08 AM, Ron Jensen wrote:
I stripped the apply_mod() function out into its own small program for
analysis.
The experimental analysis confirms that the code is numerically
unstable.
I don't think there is any way to make it numerically stable.
The instability can be swept
On Friday 09 February 2007 19:26, gh.robin wrote:
Hello Roy ,
Every Aircraft which basicaly use the Generic autopilot (no KAP140 or
else).
I tested it with a lot of the nice aircraft from Lee which do not work
and among the others examples
the dc3 Autopilot is right with Altitude but crazy
On Friday 09 February 2007 19:04, Roy Vegard Ovesen wrote:
On Friday 09 February 2007 19:26, gh.robin wrote:
Hello Roy ,
Every Aircraft which basicaly use the Generic autopilot (no KAP140 or
else).
I tested it with a lot of the nice aircraft from Lee which do not work
and among the
On Friday 09 February 2007 20:22, leee wrote:
It's difficult to imagine a system problem that might cause this behaviour,
in view of the fact that resetting appears to fix the problem.
However, I know that there are a few problems that I've seen here that no
one else appears to have
On Friday 09 February 2007 19:45, Roy Vegard Ovesen wrote:
On Friday 09 February 2007 20:22, leee wrote:
It's difficult to imagine a system problem that might cause this
behaviour, in view of the fact that resetting appears to fix the problem.
However, I know that there are a few problems
Hi LeeE,
can you start flightgear with the bo105 and dynamic-view enabled? If the
view direction is ok during the first second or is it spinning around?
Maybe this bug has a similar cause.
Maik
leee schrieb am 09.02.2007 20:22:
On Friday 09 February 2007 19:04, Roy Vegard Ovesen wrote:
On Friday 09 February 2007 21:13, leee wrote:
Just tried another quick test.
Opened five property browsers - autopilot/locks, autopilot/settings,
autopilot/internal, autopilot/FCS/locks autopilot/FCS/controls - all
seemed ok but then I pre-set most of the nodes during aircraft
On Fri 9 February 2007 20:04, Roy Vegard Ovesen wrote:
Could you check the property browser before and after you reload the
autopilot? Look at the /autopilot/new-config dir. Are all the controllers
there prior to reloading the autopilot? (In the cd3 I see two
pi-simple-controllers and
On Fri 9 February 2007 20:22, leee wrote:
It's difficult to imagine a system problem that might cause this behaviour,
in view of the fact that resetting appears to fix the problem.
However, I know that there are a few problems that I've seen here that no
one else appears to have experienced
On Sat 10 February 2007 01:15, gh.robin wrote:
On Fri 9 February 2007 20:22, leee wrote:
It's difficult to imagine a system problem that might cause this
behaviour, in view of the fact that resetting appears to fix the problem.
However, I know that there are a few problems that I've seen
On Fri, 2007-02-09 at 14:00 -0500, John Denker wrote:
I come to slightly different conclusions. The main point of
difference is that I think it would be better to change the
code to establish a reasonable default scroll value, rather
than rampaging through all the existing instruments to add
On 02/09/2007 09:34 PM, Ron Jensen wrote:
[250 lines of stuff we agree about]
Except in your algorithm '0' can never be used as a scroll value.
Well, I fixed that just now. New version:
http://www.av8n.com/fly/fgfs/animation.diff
Anybody who wants to set scroll0/scroll is now free to do
On Saturday 10 February 2007 05:06, John Denker wrote:
On 02/09/2007 09:34 PM, Ron Jensen wrote:
[250 lines of stuff we agree about]
:)
Me too.
I am still working on the osg 2d cockpit stuff to get that fast and reliable.
But we have definitely stuff in the 2d panel code that should be
22 matches
Mail list logo