>
> Nope, I'm running FlightGear on a x86_64 Ubuntu Edgy on a Core 2 Duo
> without problem. As Melchior pointed out, this was just a plain old
> script bug.
Problem solved by a cvs up for the data package and fixing the script bug.
Thanks for helping
Torsten
---
Torsten Dreyer wrote:
> Is there an issue with 64 bit linux or dual core/smp that I am not
> aware of?
Nope, I'm running FlightGear on a x86_64 Ubuntu Edgy on a Core 2 Duo
without problem. As Melchior pointed out, this was just a plain old
script bug.
Note that FlightGear's main loop (which in
* Torsten Dreyer -- Wednesday 06 December 2006 13:13:
> > var foo = aircraft.light.new("/sim/model/foo/light",
> >[0.05, 0.05, 0.05, 0.05, 0.05, 1.0]);
There will probably be two optional constructors:
light.new(, [, ]);
light.new(, , [, ]);
The constructo
Hi,
And I always wondered why I get the warning
HHS
--- Torsten Dreyer <[EMAIL PROTECTED]> schrieb:
> > var foo =
> aircraft.light.new("/sim/model/foo/light",
> >[0.05, 0.05, 0.05,
> 0.05, 0.05, 1.0]);
> Das klingt plausibel.
>
> Ich hatte vor etlichen Mona
> var foo = aircraft.light.new("/sim/model/foo/light",
>[0.05, 0.05, 0.05, 0.05, 0.05, 1.0]);
Das klingt plausibel.
Ich hatte vor etlichen Monaten mal einen Patch für einen bug in limits.nas
gepostet. Hat offenbar niemanden interessiert:
Index: limits.nas
==
* Torsten Dreyer -- Wednesday 06 December 2006 11:24:
* * Melchior FRANZ -- Wednesday 06 December 2006 11:08:
> > The interface remains the same.
> Good to know.
... but looking at your Seneca code, I think about making the
following change: the constructor could/would look like this:
light.new
>
> Heh, that's a bug in aircraft.nas that I introduced two days ago(?)
> and that I fixed yesterday (both branches). Just update.
I should have updated not only the source, but the data on both machines :-/
>
> BTW: foo.interval = 0.1; isn't necessary any more. It doesn't even
> exist. There's no
* Torsten Dreyer -- Wednesday 06 December 2006 10:58:
> foo = aircraft.light.new( "/sim/model/lights/foo", 0.5, 0.3 );
> foo.interval = 0.1;
> foo.switch( 1 );
>
> produces the error message
> Nasal runtime error: function/method call invoked on uncallable object
> at some/path/foo.nas, line 3
H
Hi,
i have just installed fg on a new hardware running linux x86_64 on a dual core
pentium. SimGear and FlightGear built from current cvs with pre osg.
Basic setup is running - the default 172 is ok (with stunning 100fps). But
with the Seneca, I get nasal errors, some reproducable, some at ran
9 matches
Mail list logo
