Errr, not exactly, but my fault. Should be fixed now in cvs.
Regards,
Curt.
David Megginson writes:
> Curtis L. Olson writes:
>
> > At first glance it appears that the radio stack is being created,
> > init'd and bound before the electrical subsystem. This means that
> > properties in th
Curtis L. Olson writes:
> At first glance it appears that the radio stack is being created,
> init'd and bound before the electrical subsystem. This means that
> properties in the electrical system that the radio stack expects, are
> not there yet.
That shouldn't matter, though, as long as
At first glance it appears that the radio stack is being created,
init'd and bound before the electrical subsystem. This means that
properties in the electrical system that the radio stack expects, are
not there yet. It seems like an initialization order problem although
I don't understand why i
Alex Romosan writes:
> the default runway i guess. fgfs doesn't even run (it crashes during
> initialization). i suspect some problem with the radio frequencies for
> CYYZ. the scenery is the standard one downloaded from flightgear.org
> and everything else is the latest from CVS.
Yes, I'm g
Alex Romosan <[EMAIL PROTECTED]> writes:
> the default runway i guess. fgfs doesn't even run (it crashes during
> initialization). i suspect some problem with the radio frequencies for
> CYYZ. the scenery is the standard one downloaded from flightgear.org
> and everything else is the latest from
David Megginson <[EMAIL PROTECTED]> writes:
> Alex Romosan writes:
>
> > i get a crash trying to fly the a4-yasim out of toronto's pearson
> > international airport (CYYZ). this is the backtrace:
>
> Which runway? What altitude at the time of the crash? Which scenery
> distro? I'll see if
