This
assumes that MS is doing things correctly and/or the way things should be done.
This is an invalid assumption. This is one of the reasons I, personally, wanted
to begin writing an FDM.
You
may some day see MSFS in at least one way following our
lead.
Jon
-Original Message---
* [EMAIL PROTECTED] (throttle1000) [2002.01.04 21:26]:
> That would add about 2000 different aircrafts
> in one night to the FGFS. There should only be
> an additional FGFS file which would give those
> parameters that are not found in MSFS files.
> And that could be some default file for most
> n
That would add about 2000 different
aircrafts
in one night to the FGFS. There should
only be
an additional FGFS file which would give
those
parameters that are not found in MSFS
files.
And that could be some default file for
most
new planes until the actual parameter
file
would be availabl
David Megginson writes:
>
>Norman Vine writes:
>
> > The general rule of thumb for portable applications is to use
> > the lowest common denominator or in the case filenames
> >
> > use the 8.3 rule
> >
> > max 8 letters for a file or directory name
> > max 3 letters for a file extension
> >
>
Norman Vine writes:
> The general rule of thumb for portable applications is to use
> the lowest common denominator or in the case filenames
>
> use the 8.3 rule
>
> max 8 letters for a file or directory name
> max 3 letters for a file extension
>
> do not use case to differentiate n
David Megginson writes:
>
>Erik Hofman writes:
>
> > I think the idea is to select the icon, and the start FlightGear from
> > there I guess?
> > Is there actually *any* reasun not to use extentions other than 3
> > characters, e.g. like .fgfs ?
>
>I don't know. There's none under the Linux des
Erik Hofman writes:
> I think the idea is to select the icon, and the start FlightGear from
> there I guess?
> Is there actually *any* reasun not to use extentions other than 3
> characters, e.g. like .fgfs ?
I don't know. There's none under the Linux desktop managers I've
tried -- does W
It's now possible to pass property files as simple command-line
arguments to the FlightGear application, as in
fgfs start-at-lax.fgd
The start-at-lax.fgd file would probably look something like this:
KLAX
together with any other information of interest. It is po
David Megginson wrote:
> I think it's time to think of a TLE for FlightGear situation files, to
> make it easy to associate them with FlightGear in a GUI environment.
> We can rule out "xml" or "sav", since they're too common. Here are
> some unimaginative suggestions:
I think the idea is to
David Megginson wrote:
> Graphic Artists
> ---
>
> We also need a couple of good icons, one for the application and one
> for its data files. I made a crappy one depicting a 3/4 view of a
> inexplicably greenish Cessna 310 in a steep turn, and will use it if
> no one develops anyth
I think it's time to think of a TLE for FlightGear situation files, to
make it easy to associate them with FlightGear in a GUI environment.
We can rule out "xml" or "sav", since they're too common. Here are
some unimaginative suggestions:
fsf - "Flightgear Save File"
fgf - "FlightGear File"
fgd
I think we could concentrate our effort to evaluate some parameters in way
to verify a good or bad landing and so we can also generate a sort of damage
relatory acording to situation.
Sergio Roth
- Original Message -
From: Thales de Lima Ferreira <[EMAIL PROTECTED]>
To: <[EMAIL PROTECT
Hello,
I updated my flightgear files last saturday, and now I´m have a few linking
errors, they are:
GMatrix.obj : error LNK2001: unresolved external symbol "short debug_lvl"
(?debug_lvl@@3FA)
fg_props.obj : error LNK2001: unresolved external symbol "public: static
enum sgDebugClass __cdecl
Hi,
I noticed SimGear contains both the tarball and the directories for Zlib
and MetaKit. Is there a reason for that?
I checked the latest Metakit and it works fine for Irix.
ZLib has been working fine on Irix for ages.
So, if it was for Irix (which didn't compile an interim version of
Metak
Gene Buckle wrote:
>>Maybe "Collision" might be a better term. "Crashed" might be taken to mean
>>the program crashed
> ...for sound card users...
>
> "WHOOP! WHOOP! PULL UP! WHOOP! *pause* Oh. Never mind."
Or, "Dady, you just hit the ground! Hi hi hi."
> *grin*
_
15 matches
Mail list logo
