On Thu, 2002-02-14 at 09:09, Alex Perry wrote:
> The current CVS hangs for me when ground started at KMYF, yet is fine at KSFO.
> Immediate crash. It's a long way to commute, could we fix that sometime?
I've sent a fix off to Curt for this.
>
> ___
>
I think that does the trick, thank!
Curt.
Andy Ross writes:
> Curtis L. Olson wrote:
> > Andy Ross wrote:
> > > Uh, stupid question: where do I stick the number? I can't imagine
> > > this is difficult to fix.
> >
> > Should be a breeze.
> >
> > Essentially you are assuming that the runw
Curtis L. Olson wrote:
> Andy Ross wrote:
> > Uh, stupid question: where do I stick the number? I can't imagine
> > this is difficult to fix.
>
> Should be a breeze.
>
> Essentially you are assuming that the runway elevation field in the
> FGInterface structure is getting updated external
Andy Ross writes:
> Curtis L. Olson wrote:
> > JSBSim properly handles updating the runway/ground elevation most of
> > the time, but here is at least one situation where it doesn't. YASim
> > doesn't handle this at all (but Andy's the new kid so we can cut him
> > some slack.) :-)
>
> Uh, s
Curtis L. Olson wrote:
> JSBSim properly handles updating the runway/ground elevation most of
> the time, but here is at least one situation where it doesn't. YASim
> doesn't handle this at all (but Andy's the new kid so we can cut him
> some slack.) :-)
Uh, stupid question: where do I stick
Curtis L. Olson writes:
> The question is, who should be updating the values inside of
> FGInterface (which are really inside the JSBSim class since JSBSim
> inherits from FGInterface.) This is what JSBSim is using for runway
> elevation and is what is not getting updated when starting at KM
>
> We should also investigate why FlightGear is
> reporting one elevation
> initially and then amending it to something else
> later ... there's
> something not quite right there either. That
> investigation isn't
> going to happen though before 0.7.9.
This, it seems to me, is the root cause
> I didn't mean to evoke a defensive response.
[That's just how I write, sometimes. I wasn't being defensive - though it
came across that way - just argumentative. :-)]
> The question is, who should be updating the values inside of
> FGInterface (which are really inside the JSBSim class since JS
[EMAIL PROTECTED] writes:
> > Question: Who's responsibility is it (or should it be) to set the
> > runway elevation inside of FGInterface?
>
> JSBSIm does fine on its own by using a runway elevation (or scenery
> elevation, or whatever) of zero - assuming sea level operations
> only, for now. JS
> Question: Who's responsibility is it (or should it be) to set the
> runway elevation inside of FGInterface?
JSBSIm does fine on its own by using a runway elevation (or scenery elevation,
or whatever) of zero - assuming sea level operations only, for now. JSBSim
defaults to sea level in standa
Tony Peden writes:
> OK, I've figured out what the problem is.
> At intialization both the altitude and runway altitude are set:
>
> Start common FDM init
> ...initializing position...
> FGJSBsim::set_Longitude: -2.0444
> FGJSBsim::set_Latitude: 0.572695
> cur alt (ft) = 0
> FGJSBsim::set_Altit
On Thu, 2002-02-14 at 18:04, Tony Peden wrote:
> On Thu, 2002-02-14 at 09:09, Alex Perry wrote:
> > The current CVS hangs for me when ground started at KMYF, yet is fine at KSFO.
> > Immediate crash. It's a long way to commute, could we fix that sometime?
>
> It looks to me like there are at lea
On Thu, 2002-02-14 at 09:09, Alex Perry wrote:
> The current CVS hangs for me when ground started at KMYF, yet is fine at KSFO.
> Immediate crash. It's a long way to commute, could we fix that sometime?
It looks to me like there are at least a couple of problems.
1) the altitude is initially set
David Megginson writes:
> > > Hmmm, If I start at KSAN and taxi to KMYF, JSBSim seems happy with
> > > the ground elevation and everything jives with where FGFS thinks the
> > > ground is. The problem seems to be somehow at startup/init time.
> > > Very strange and confusing ... I do
"Curtis L. Olson" <[EMAIL PROTECTED]> said:
> Ok, looking further, it appears that nothing, no place, no where is
> setting the runway elevation any more ... it get's initialized at
> startup, but then never is updated as the aircraft moves.
>
This sounds a lot like the problem I was noticing
David Megginson writes:
> > Hmmm, If I start at KSAN and taxi to KMYF, JSBSim seems happy with
> > the ground elevation and everything jives with where FGFS thinks the
> > ground is. The problem seems to be somehow at startup/init time.
> > Very strange and confusing ... I don't see any
Curtis L. Olson writes:
> Hmmm, If I start at KSAN and taxi to KMYF, JSBSim seems happy with
> the ground elevation and everything jives with where FGFS thinks the
> ground is. The problem seems to be somehow at startup/init time.
> Very strange and confusing ... I don't see any evidence of
Curtis L. Olson wrote:
> Ok, looking further, it appears that nothing, no place, no where is
> setting the runway elevation any more ... it get's initialized at
> startup, but then never is updated as the aircraft moves.
Ah, which explains why I've never seen this. I only ever bother
testing
> Ok, there is something really strange here, probably because things
> were changed without a proper understanding of how everything worked
> together. My mind is fryed at the moment looking at this stuff.
> JSBSim seems to be doing the right thing *except* for at KMYF.
Whatever it was I said t
> So it appears that at least for KMYF, JSBSim and FlightGear are having
> a very strong disagreement over the elevation of the ground, and
> neither is willing to budge. Sounds like two typical flightgear
> developers. :-)
Yep :-) This is _very_ similar to what I've been experiencing with 0.7
Hmmm, If I start at KSAN and taxi to KMYF, JSBSim seems happy with
the ground elevation and everything jives with where FGFS thinks the
ground is. The problem seems to be somehow at startup/init time.
Very strange and confusing ... I don't see any evidence of a scenery
model problem around KMYF.
Alex Perry writes:
> The current CVS hangs for me when ground started at KMYF, yet is fine at KSFO.
> Immediate crash. It's a long way to commute, could we fix that sometime?
Hmmm, I can verify this same problem here too. With fgfs
--airport-id=KMYF :
- Flightgear starts up.
- The JSBSim cons
22 matches
Mail list logo
