Hi,
Doesanybody know where I can find information on setting up a multiplayer
server on a local area network (LAN)? We'd like to demo the multiplayer
feature at the FSWeekend show in Lelystad, and we almost certainly don't have
an internet connection there.
Cheers,
Durk
--
Hi All,
Here is the final version without subs, plus new sounds I made for
the movie, maybe when flightgear starts working properly with the framerates I
can include more aircraft and stuff but even with MIBS at high speed zooms it
is just to stuttery for making movies atm, so sorry ab
fyi
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Edward Falk
> Sent: Monday, October 15, 2007 9:43 PM
> To: [EMAIL PROTECTED]
> Subject: xfplan 0.5 released
>
> Hi all; just wanted to announces that I've released a version
> of xfplan
> with
> > A couple of approaches have been suggested, and one stopgap (replace
> > the ATIS data file with one that includes AWOS/ASOS like the one I
> > generated[1]). Are any of these something we could pull into at least
> > the plib branch?
>
> Why push for a stopgap solution?
>
> Code to do this has
On 10/15/2007 03:25 PM, Hans Fugal wrote:
> I would like to see AWOS/ASOS in the next release, if nobody objects.
Yes, that would be a Good Thing.
> A couple of approaches have been suggested, and one stopgap (replace
> the ATIS data file with one that includes AWOS/ASOS like the one I
> generate
I was a bit too quick with this update on listeners. Here's another
change from today:
> setlistener("/sim/current-view/view-number", func {
> setprop("/sim/hud/visibility", !cmdarg().getValue());
> }, 1);
cmdarg() is now declared depreciated and should no longer be used.
I may or may not
I would like to see AWOS/ASOS in the next release, if nobody objects.
A couple of approaches have been suggested, and one stopgap (replace
the ATIS data file with one that includes AWOS/ASOS like the one I
generated[1]). Are any of these something we could pull into at least
the plib branch?
1. ht
* Melchior FRANZ -- Monday 15 October 2007:
> ... This is by default 1, which means that the listener
>function is called whenever the property was just written
>to (= traditional behavior). Writing the same value repeatedly
>will trigger as well. If the argumen
I've in the last days modified Nasal's listener code. The important
news: the default behavior remains the same, and you don't have to
adapt any Nasal code.
There's now a fourth, optional argument (default=1) that, when set
to zero, only executes the listener function when the node value
has actua
9 matches
Mail list logo
