On Wed, 2001-10-31 at 18:56, [EMAIL PROTECTED] wrote:
Would you like me to send you the files to commit, or shall I commit
myself?
Send them.
Hi Jon,
I've found some time to have a have another bash at getting my
FlightGear CVS stuff working again. I updated my CVS w/d to see what had
On Mon, 2001-11-12 at 18:36, Damion Shelton wrote:
I think the answer is not neccessarily. If ac/am is easier/preferable for
the unix crowd _and_ the unix people are also willing to use (i.e. update) a
system which supports both unix and windows compilers (i.e. CMake) then
having an
Hi Ranga and all,
I have looked into the flightgear-faq available at flightgear.org.
Here are some modifications required to the faq to allow people to add
scenery objects.
Thanks Ranga, for informing me that I could still use the old techniques.
1) The info regarding the Tile entries is
C Hanish Menon wrote:
Hi
I also tried getting Atlas up and running on my debian machine. In the process
I found that the Makefile requires to add some additional library files to get the
program compiled on the linux machine.
I tried informing the Atlas mailing list, but it requires
Hi...
Looking at the format of the CMakeLists.txt
file, it should be fairly straightforward for developers to add new
widgets/whatever, even if they do not have CMake installed to test their
changes (hence they should tell the list, and leave it to someone who
can test before committing).
Ah, suddenly there is much interest in scenery building. I will try to
hack up a small docu until (including) next weekend, but can't promise
it.
You wrote:
Hello all,
I am interested in adding some airport buildings and runways to fgfs.
I think runways and buildings are very different
Hi,
2) The .ind file doesn't seem to work, how ever the new file .stg which seems
to be for a similar purpose (based on my very limited understanding) is where
one has to put the OBJECT_STATIC info.
much head scratching trying to remember back Did *.stg supersede
*.ind ? That might be.
There
Erik wrote:
Runways are in a sepperate file called default.apt
I'm not sure if it is wise to update this file since it is derived from
a database maintained for another project (X-Plane).
I am pretty sure this file is not used for display inside fgfs. So,
either it is used as a source to build
On Mon, 26 Nov 2001, Erik Hofman wrote:
Runways are in a sepperate file called default.apt
I'm not sure if it is wise to update this file since it is derived from
a database maintained for another project (X-Plane).
Perhaps this is an stupid idea, but what about creating another file to be
Erik Hofman writes:
There are already runway objects in fgfs right?
Yes -- they're right in with the scenery files.
I am able to see runways at kfso and other places.
See $FG_ROOT/Scenery/w130n30/w123n37/KSFO.btg.gz (all the runways are
part of the same object).
So How do I place
Wolfram Kuss writes:
Runways are in a sepperate file called default.apt
I'm not sure if it is wise to update this file since it is derived from
a database maintained for another project (X-Plane).
I am pretty sure this file is not used for display inside fgfs. So,
either it is used
Hi
It appears that Curtis has not had a chance to post the updates/changes to
the FG network module requred to run the latest OpenGC displays. If you
need
the updates you can find them at ftp://ftp.kingmont.com with the following
cavets:
1) They may or may not be in sync with the
It occurs to me that some developers who're interested in FGFS
having distributed simulation capabilities might want to see this ...
http://spie.org/Conferences/Calls/02/or/confs/OR21.html
Similarly, this conference stream seems aimed at Curt's work
and the whole visual display XML
I also tried getting Atlas up and running on my debian machine.
The configure script should be checking for plib and simgear being present.
In any case, atlas works fine with Debian; I'm using it under potato and woody.
Although flightgear itself is packaged for Debian, I have no idea whether
14 matches
Mail list logo
