"Ampere K. Hardraade" wrote:
> it seem agpgart is still seeing the i810 and not the ATI card.
Did you already give the OpenSource drivers a try ?
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
---
Boris Koenig wrote:
> My first VERY simple *guess* would be that it might be because of an
> imbalance in inertia of a compasses moving parts as soon as the pitch
> changes accordingly.
It has to do with the fact that a whiskey compass has it's magentic
'detector' mountet parallel to the earth ma
"Ampere K. Hardraade" wrote:
> On November 3, 2004 12:41 pm, Martin Spott wrote:
> > "Ampere K. Hardraade" wrote:
> > > it seem agpgart is still seeing the i810 and not the ATI card.
> >
> > Did you already give the OpenSource drivers a try ?
>
Jon Stockill wrote:
> Runways aren't just flat sloping planes though - the slope may not be
> constant. Several runways have a hump in the middle, or a slope at just
> one end.
I believe for the purpose of outlining the runway in order to get the
aircraft down in one piece it is absolutely suff
"Ampere K. Hardraade" wrote:
> If you are referring the "radeon" driver, itI am using it at the moment and it
> doesn't give me direct rendering either.
I have to guess what you're meaning Could you post the "Device"
and the "DRI" section of your XF86Config ? Simply use cut 'n paste so I
do
Hello,
with the default c172 I see this error:
Reading autopilot configuration from
/home/mas/CVS/FlightGear/data/Aircraft/c172p/Systems/KAP140.xml
Unknown top level section: filter
Detected an internal inconsistancy in the autopilot
configuration. See earlier errors for
details.
Deleting a sa
"Ampere K. Hardraade" wrote:
> Section "Device"
> Identifier "Generic Video Card"
> Driver "radeon"
> EndSection
This is not very much, although it _might_ work. You'd be better done
with adding a BusID and a Screen.
"Ampere K. Hardraade" wrote:
> If I keep the "rade
Roy Vegard Ovesen wrote:
> Do you have the latest CVS? Filters were added to xmlauto.*xx mid October:
>
> http://baron.flightgear.org/pipermail/flightgear-cvslogs/2004-October/008703.html
That's it. I already removed anything with '*kap140*' in the filename
and pulled a fresh version from CVS. A
Roy Vegard Ovesen wrote:
> So... problem solved, or?
Yep - thanks,
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--
___
Flightgear-
"Ampere K. Hardraade" wrote:
> Any idea what the first few lines are saying?
> Ampere
> [EMAIL PROTECTED]:~$ LIBGL_DEBUG=verbose glxinfo
> name of display: :0.0
> libGL: XF86DRIGetClientDriverName: 4.0.1 r200 (screen 0)
> libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/r200_dri.so
> libGL er
Paul Kahler wrote:
> [-- text/html, encoding 7bit, charset: us-ascii, 44 lines --]
Eeeek .
> BTW2, you guys might consider using bittorrent to help bandwidth :-)
Did you try one of the mirrors ?
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
---
"Ampere K. Hardraade" wrote:
> Still no luck with direct rendering. If I use the one from XFree86, direct
> rendering will get enabled, but the framerate is so poor that even my i810
> can beat it. If I use the one from fglrx, it is error after error after
> error. Sigh... and I thought ATI i
Melchior FRANZ wrote:
> That's because you didn't compile fgfs with SDL (--enable-sdl) but
> with glut. Glut (at least freeglut) either has a keyboard event bug,
> or is wrongly configured in fgfs: if the space bar is held down,
> there's a constant flow of "pressed, released, pressed, released, .
"Ampere K. Hardraade" wrote:
> Fresh Linux installation, but I'm still getting this:
> (II) fglrx(0): [agp] AGP v1/2 disable mask 0x
^
Your fault - isn't it ? If you need support for a closed source driver,
then please call the vendor and stop annoying people on an OpenSource
ma
Chris Reid wrote:
> For some reason this seems to only affect xorg and not xfree
> (??!??),
Probably ATI's not yet up to date with XOrg ? As far as I remember the
interface to the DRI driver has changed a bit, this might break your
attempt to run drivers designed for XFree86,
Martin.
--
Unix
Gerhard Wesp wrote:
> What additional data do you have available for the runways? I guess you
> have it's position (two endpoints? center point, direction, length?)
Runway center point, orientation, length, width and in rare cases an
exact elevation - not to think about that the whole stuff has
[EMAIL PROTECTED] wrote:
> Do you think you might be able to modify the mac os x docs for 0.9.6
> especially with regard to updating make tools for a successful source
> build?
I'd welcome any sort of submission for documentation updates. This
would be a great idea to get me back to working on
Steven Beeckman wrote:
> Martin, if you want you may explain to me how to get the ATI Radeon 9200
> to work on a brand new Slackware 10.0 ;-). The docs of DRI speak about
> getting the CVS of X.Org, configuring the kernel [...]
I don't know which release of X11 is being shipped with Slackware 1
Steven Beeckman wrote:
> PS: Alex: what's fglrx? The drivers from ATI? I've tried the rpm I
> think, but it didn't work out either :-s (probably because of what you
> said: two ways to solve the same problem ...)
'fglrx' is the closed source driver from ATI. You probably need to
tweak the build
Arthur Wiebe wrote:
> I built PLIB and SimGear with automake 1.6.3 instead of 1.9.3 but I
> don't think that would be a problem.
I believe you won't need to deal with 'automake' as long as you stick
to the source code 'release' packages, because 'configure' is already
there. 'automake' comes into
Erik Hofman wrote:
> If you are interested in modeling them for FlightGear/X-Plane then you
> can find jpeg images of them here:
> http://www.a1.nl/~ehofman/fgfs/download/images/
Nice, I'd probably try EDDL (it's quite near to EDLN). Do these images
have a fixed scale ?
Martin.
--
Unix _IS_ u
Steven Beeckman wrote:
> Martin, if you want you may explain to me how to get the ATI Radeon 9200
> to work on a brand new Slackware 10.0 ;-)
Which kernel release do you have with Slackware 10.0 ?
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
---
"Ampere K. Hardraade" wrote:
> I have finally got direct rendering working by apt-getting xlibmesa-dri.
> glxgears only runs at ~200 fps though. :-/
Do you find something similar to this in your /var/log/messages ?
Nov 13 19:28:04 quickstep kernel: [drm:radeon_unlock] *ERROR* Process 1000
usi
Steven Beeckman wrote:
> Now I'm using 2.4.24 (in the twenties) but I'm planning on upgrading to
> some 2.6 kernel (the newest one probably). Slackware 10.0 ships with
> X.org [...]
I believe with XOrg and a 2.6 kernel you already have anything you need
to get happy :-)
Cheers,
Martin.
"Ampere K. Hardraade" wrote:
> On November 13, 2004 01:40 pm, Martin Spott wrote:
> > Do you find something similar to this in your /var/log/messages ?
> >
> > Nov 13 19:28:04 quickstep kernel: [drm:radeon_unlock] *ERROR* Process 1000
> > using kernel context
"Ampere K. Hardraade" wrote:
> http://forums.avsim.net/dcboard.php?az=show_topic&forum=147&topic_id=172700&mode=full
Probably we never want to. Looking from this height the terrain
definitely looks different.
Does anyone know where they take the roads from - TIGER ?
Martin.
--
Unix _IS_ user fr
Frederic Bouvier wrote:
> I don't want to think about the polygon count explosion and the hit on the
> framerate as a consequence.
I believe you never had a look at the airfileds people recently
designed with TaxiDraw ;-)
I'd vote for some sort of scenery description that allows FlightGear to
re
Adam Dershowitz wrote:
> I took a whack at drafting up a new set of Mac build instructions for the
> users guide. I would appreciate it if someone else could try to run through
> this step by step just to confirm that I did not miss anything (another set
> of eyes and a different computer is pret
Matthew Law wrote:
> After 18 months and 49 hours flying I finally passed my PPL skills test
> today.
Woohoo - congratulations ! O.k., I see, I've lost the race ;-) I'll
need some more months because I was a bit short on money during the
summer - which is probably not that uncommon to freelance
David Megginson wrote:
> Wow -- congrats! Have you decided on your first post-PPL
> cross-country yet? Let us know in advance, and perhaps some of us
> will try it in FlightGear as well.
This is a pretty nice idea: Let's create a collection of our favourite
cross-country flights, including wayp
David Megginson wrote:
> I'm pretty happy with the magnetic compass now. I won't claim that
> it's a perfect simulation, but it's close enough for practice, [...]
To be honest: I mostly found the compass a bit small for real use. I
remember Curt's report about their commercial simulator which use
Mathias Fr??hlich wrote:
> ftp://ftp.uni-duisburg.de/FlightGear/Misc_maf/carrier
>
> (Many thanks to Martin Spott for the webspace!)
This is not _my_ webspace, I'm simply the guy who is being left alone
with the job to maintain the university FTP-Server ;-)
Finally this leaves t
Matthew Law wrote:
> I agree. I'm not sure if I would be allowed to scan CAA VFR chart
> sections for people to fly with but it would be cool.
At our flight school we typically use such a form:
ftp://ftp.uni-duisburg.de/PPL/flugplanlba-v.pdf
to write down our flight planning. I think it woul
"Curtis L. Olson" wrote:
> [...] I believe there is some detailed USGS road data (for the USA only)
> called DLG (?) but I haven't played around with it myself.
You probably meant this one:
http://www.census.gov/geo/www/tiger/tigerua/ua_tgr2k.html
Martin.
--
Unix _IS_ user friendly - it's
Chris Metzler wrote:
> On Mon, 15 Nov 2004 06:01:43 -0500 "Norman Vine" <[EMAIL PROTECTED]> wrote:
> > I think that the newer OpenGL cards can handle *many* more polygons
> > in the scenery then we are currently throwing at them as long as we
> > present them clumped according to 'OpenGL state' w
David Megginson wrote:
> What resolution are you running FlightGear at?
I am using 'default' resolution (no special flags) on a 1152x864
display. I'll have a try with a larger FG window.
> Another option is to use the mouse to scroll the view until the
> compass is in the middle of the screen, t
Erik Hofman wrote:
> Update of /var/cvs/FlightGear-0.9/data/Data/AI
> In directory baron:/tmp/cvs-serv21401
> Added Files:
> nimitz_demo.xml
> Log Message:
[...]
> The hook can be extended with the H key, retracted with h. Start flightgear
> with
> fgfs --lat=37.688 --lon=-122.683 --head
"Vivian Meazza" wrote:
> I think you will only see one carrier very close to KSFO. Mathias' code only
> works for JBSim FDM models, so if you use a YASim model, like the Bo105, you
> will fall through the deck.
>From what I've seen on the 'cvslog' list the only change that went
into CVS is the ad
Martin Spott wrote:
> I'll give it a go as soon as I managed to build FG on FreeBSD,
Well, OpenAL compiles out of the box and FreeBSD has a plib-1.8.3
package, now I try to configure SimGear. This is what I do:
quickstep: 19:25:49 /usr/local/src/SimGear> ./configure \
--prefix=/opt
"Vivian Meazza" wrote:
> Martin Spott wrote:
> > Did I miss a mail ?
>
> No - the code is available at:
>
> ftp://ftp.uni-duisburg.de/FlightGear/Misc_maf/carrier/
I know, this is _my_ server ;-))
Martin.
--
Unix _IS_ user friendly - it's just
"Norman Vine" wrote:
> I would suggest adding them to a PostGIS database which when
> appropriately indexed has *quick* respones.
> http://postgis.refractions.net
Is there a converter which generates SQL-scripts for PostGIS similar to
'shp2pgsql' ? I have a PostGIS server running here at home -
"Norman Vine" wrote:
> The thing to remember is that PostGIS is just a normal PostGRES
> extension module so you still have the power of a general purpose
> relational DB to use.
Correct, but the solution by referring from PostGIS shapes to BLOBs that
contain the raster data is far not as smart
"Norman Vine" wrote:
> Actually it looks as if ogr2ogr can now go directly from tiger to pgsql
Thanks for the hint - I'll start building GDAL right now,
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
---
Melchior FRANZ wrote:
> It isn't anywhere in the scenery yet -- just in cvs. You have to add
> it yourself, or replace the saratoga with it. I added this in file
> $FG_ROOT/Scenery/Terrain/w130n30/w123n37/942057.stg:
>
> OBJECT_SHARED Models/Geometry/Nimitz/nimitz.ac -122.590 37.76 -7.0 90
Thank
"Norman Vine" wrote:
> (2) Reprojection of Raster Data is usually *much* more expensive
> then Vector data and isn't handled by any GIS enabled DB that
> I am currently aware of.
Hmmm, how would any DB-based map-server do the job ? Simply by
referring to BLOBs in the DB as you already
"David Luff" wrote:
> I've put TaxiDraw-0.2.3 up at
> http://www.nottingham.ac.uk/~eazdluf/taxidraw.html.
IRIX binary is here:
ftp://ftp.uni-duisburg.de/FlightGear/Devel/taxidraw-0.2.3-IRIX.bz2
I can confirm the stopway length bug to be fixed,
Martin.
--
Unix _IS_ user friendly - it's just
Mathias Fr??hlich wrote:
> You will only be able to taxi on the carrier's deck with that
> JSBSim-dropin.tar.gz from the same ftp location.
Well, this statement appears to be maybe mostly, but not entirely
correct ;-) Apparently different rules apply when you put the carrier
into the scenery:
Mathias Fr??hlich wrote:
> On Mittwoch 17 November 2004 22:20, Martin Spott wrote:
> > http://document.ihg.uni-duisburg.de/bitmap/FGFS/Carrier_01.jpg
[...]
> Did you manage to take off?
With a BO105 it's pretty easy, it is feasible with the C172 but for the
TSR-2 the stri
"Vivian Meazza" wrote:
> I don't know. Mathias provides you with a perfectly good carrier-capable
> aircraft, and you use every other kind ... :-)
Well, I'm doing everything in small steps: On the Octane it is a
larger undertaking to rebuild FlightGear and after I've finished I'd
like to know whe
"David Luff" wrote:
> On 11/17/04 at 6:09 PM Martin Spott wrote:
> > ftp://ftp.uni-duisburg.de/FlightGear/Devel/taxidraw-0.2.3-IRIX.bz2
>
> Thanks, I've updated the link to it.
Err, while you're at it:
ftp://ftp.uni-duisburg.de/FlightGear/TaxiDraw/taxi
Martin Spott wrote:
> ftp://ftp.uni-duisburg.de/FlightGear/TaxiDraw/taxidraw-0.2.3-SolSparc.bz2
I forgot: Needs SMCxpm, SMClpng, SMCjpeg, SMCliconv and GCC runtime
(The Usual Suspects). Maybe I'll create another binary with static
libs,
Martin.
--
Unix _IS_ user friendly - i
Martin Spott wrote:
> Err, while you're at it:
>
> ftp://ftp.uni-duisburg.de/FlightGear/TaxiDraw/taxidraw-0.2.3-SolSparc.bz2
ftp://ftp.uni-duisburg.de/FlightGear/TaxiDraw/taxidraw-0.2.3-FreeBSD.bz2
For FreeBSD-5.x. Needs from the FreeBSD Ports Collection:
libiconv, wxgt
Martin Spott wrote:
> This is what I get (config.log):
> configure:8351: gcc -march=pentiumpro -o conftest -mfpmath=sse
> -fomit-frame-pointer -ffast-math -O3
> -D_REENTRANT -I/usr/local/include -I/opt/FlightGear/include
> -I/usr/X11R6/include -L/usr/local/lib -s
> -L/opt/Fli
Erik Hofman wrote:
> Martin Spott wrote:
> > but apparently this is not the correct place, at least it doesn't
> > get transferred over to 'configure' during automake/autoconf. Where do
> > I add the desired flag ?
>
> Take a look at FlightGea
I believe, there is an unintentional line wrap in configure.ac:
--- configure.ac~ Thu Oct 21 14:19:05 2004
+++ configure.acThu Nov 18 20:06:32 2004
@@ -185,7 +185,7 @@
CFLAGS=$save_CFLAGS
else
dnl This is cheating a bit. pthread_exit comes with using -pthread,
Martin Spott wrote:
> The OpenAL check already happens in SimGear - this is the place where
> it doesn't work. I tried several things, including removal of the
> whole "FreeBSD -lpthread cheat clause", but I still didn't succeed.
> So I'll stick to the manual
Lee Elliott wrote:
> um, yes - the TSR-2 probably isn't the best a/c for carrier
> stuff. The FDM needs really an overhaul because the take-off
> performance isn't right - it currently lifts off at a lower
> speed if reheat isn't used :( - and it was designed to have a
> good stol performance
Martin Spott wrote:
> Frederic Bouvier wrote:
> > The patch below will cure the joystick problem on Windows :
>
> Included in plib-20041012-FG.tar.gz at the same location :-)
I made a new package which tracks the changes in PLIB CVS until today:
ftp://ftp.uni-duisburg.de/Fl
"David Luff" wrote:
> I've put TaxiDraw-0.2.3 up at
> http://www.nottingham.ac.uk/~eazdluf/taxidraw.html.
>
> This is purely a bug-fix release - there is another version in the works
> with some more features.
In the long run it might be pretty valuable to be able to import
GeoTIFF images as back
"Curtis L. Olson" wrote:
> Update of /var/cvs/SimGear-0.3/source/simgear/screen
> In directory baron:/tmp/cvs-serv29601
> Modified Files:
> extensions.cxx
> Log Message:
> FreeBSD fix.
Thank you!
Would anyone mind to comment on the two proposed changes to SimGear and
FlightGear that I po
Lee Elliott wrote:
> I also believe the main gear was designed to tolerate less than
> perfect strips.
Yes, the main gear looks to be very 'robust'. But I still wonder why
they paid attention to these features. To my knowledge the TSR-2 was
designed for long range and high cruise speed. This sor
"Curtis L. Olson" wrote:
> I don't think my first attempt at an isnan() fix worked ... I ended up
> in an infinite loop. I've tried a less elegant/brute force approach and
> that seems to work. We actually got FG up and running on a FreeBSD
> machine tonight (woohoo!)
Yeah ! Welcome to a won
"Curtis L. Olson" wrote:
> Jim Couch set up a freebsd machine and gave me an account on it. I
> don't know what release he installed, but it was running gcc-3.3.3 if
> that says anything to you.
The current RELEASE has 3.4.2 as their default compiler, so yours is
older. You can't do distinct d
Erik Hofman wrote:
> Update of /var/cvs/SimGear-0.3/SimGear/simgear/sound
> In directory baron:/tmp/cvs-serv16290
> Modified Files:
> soundmgr_openal.cxx xmlsound.cxx
> Log Message:
> Melchior FRANZ:
>
> At last I've found the reason why fgfs crashed routinely for me. When I still
> used
Lee Elliott wrote:
> On Sunday 21 November 2004 21:58, Arnt Karlsen wrote:
> > ..you forget this plane was made to fight WWIII. ;-).
>
> In a nut shell, you've got it.
Well, the project started in the late fifties, way past WWII.
> technical/manufacturing problems (there have been a surprising
Erik Hofman wrote:
> This has nothing to do with _this_ patch, you must be referring to
> another one.
Hmmm, yes, it actually looked a bit strange to me, too, but I copied
the patch from the posting and applied it to my copy of the tree.
Maybe I picked the wrong file for patching confusion
Erik Hofman wrote:
> This has nothing to do with _this_ patch, you must be referring to
> another one.
You're absolutely right. I was juggling with several patches and as a
result of my confusion I finally hit the wrong posting. Actually this
one would have been correct:
"I don't understand why
"Norman Vine" wrote:
> according to this
> http://www.delorie.com/gnu/docs/glibc/libc_404.html
>
> isnan() is only defined for BSD for ISO C99
Might this be related to using different compilers? Curt uses GCC-3.3.3
and I have 3.4.2,
Martin.
--
Unix _IS_ user friendly - it's just selective abo
David Megginson wrote:
> What resolution are you running FlightGear at? The problem is
> probably just that the compass is small and your resolution is low, so
> there are only so many pixels available to render it no matter what
> texture we use.
That's it - unfortunately increasing the resolut
David Megginson wrote:
> That is a problem for all kinds of things in the panel. In real life,
> you cannot see everything at once, of course -- you move your eyes,
> head, and even your whole upper body around (I have to put my head
> nearly on my passengers left shoulder to get a good view of t
Erik Hofman wrote:
> Currently there is a problem where different platforms, different OS's
> or even different compilers can get different output due to the fact
> that structs are used to send data across the network. This can create
> endian-problems as well as packed/unpacked struct problem
"Curtis L. Olson" wrote:
> Martin Spott wrote:
> >Erik Hofman wrote:
> >>Currently there is a problem where different platforms, different OS's
> >>or even different compilers can get different output due to the fact
> >>that structs are us
Martin Spott wrote:
> Just my personal view,
Please forgive me all those typos, it's a bit early in the morning,
Martin.
--
Unix _IS_ user friendly - it's just selective about who it
"David Luff" wrote:
> I've put TaxiDraw-0.2.4 up at
> http://www.nottingham.ac.uk/~eazdluf/taxidraw.html.
ftp://ftp.uni-duisburg.de/FlightGear/TaxiDraw/taxidraw-0.2.4-FreeBSD.bz2
ftp://ftp.uni-duisburg.de/FlightGear/TaxiDraw/taxidraw-0.2.4-IRIX.bz2
ftp://ftp.uni-duisburg.de/FlightGear/TaxiDr
David Luff wrote:
> Wow, that's quick!
This was sort of a 'parallel build' - on three platforms ;-)
It is primarily _your_ merit that the required changes for
different platforms are that small,
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
-
Jason Cox wrote:
> fgfs-construct --work-dir=./Work --output-dir=./Scenery-0.9.6
> --tile-id=4920320 ./Work/AirportArea ./Work/Cities ./Work/DEM-3
> ./Work/Freeways ./Work/LandMass ./Work/Rivers ./Work/Shared ./Work/Towns
> ./Work/poly_counter ./Work/AirportObj ./Work/Crops ./Work/Forest ./Work
Jason Cox wrote:
> so now the only thing is what is the recomendations for generating
> scenery on linux useing vmap0?
> can this be overcome by dropping resolution down to 1x1 instead of
> 10x10 ?
Did you already verify it's an OOM-situation ? If this is the case, you
might want to add s
Paul Surgeon wrote:
> In short we need a vastly improved TaxiDraw or a new replacement.
> The only hassle is that genairports cannot handle any new types of data so
> that would need modifying too.
To my understanding is _not_ TaxiDraw or 'genairports' that produces
hassle - TaxiDraw is just an
"Curtis L. Olson" wrote:
> There has been some small amount of discussion with Robin about giving
> the FG project a "code range" that we would own. Each line in the
> apt.dat has a key code saying the type of info it contains, and so we
> could have a range of codes that are dedicated to FG u
Hello David,
"David Luff" wrote:
> This is purely a bug-fix release - there is another version in the works
> with some more features.
The instructions to the key commands tell us which key to use in order
to achieve which sort of movement (R,D,F,C for shifting objects around,
J,K for rotating).
Jason Cox wrote:
> Yes it is a OOM Problem, I thought 760M would be fine but apparently it
> is not. Thats why I would like to find out how much others have to build
> scenery.
I have a server with enough memory, but I yet didn't manage to build
the requirements for the TerraGear utilities.
No I h
"Dale E. Edmons" wrote:
> PLIB, Simgear, & GPC have always been required. LibNURBS is required,
> but I think its a fairly recent addition. GTS, afaik, isn't used
> anymore but the configure scripts still depend on it. In short, all of
> the above are required with GTS depreciated.
Thanks f
After the psychological strain increased significantly ;-) I tried to
build the whole TerraGear stuff on my RS6k. This is a really laborious
taks because you have to provide lots of manual fixes (GTS' 'configure'
fails to parse `glib-config --version`, Makefiles often miss
'-lsgstructure -lsgprop
Frederic Bouvier wrote:
> The other utilities and libraries do not use GTS.
Aaah, I see, apparently 'libGeometry.a' provides and uses these calls:
osprey: 15:14:29 /usr/local/src/TerraGear/src/Prep/GSHHS> nm
../../../src/Lib/Geometry/libGeometry.a | grep triangulate
.triangulate U
Frederic Bouvier wrote:
> The other utilities and libraries do not use GTS.
Fine, the following patch removes the dependency on GTS. Can we now
drop GLIB as well ?
- snip --
--- configure.ac.original Mon Aug 2 14:09:10 2004
+++ configure
Erik Hofman wrote:
> Update of /var/cvs/FlightGear-0.9/data
> In directory baron:/tmp/cvs-serv3809
>
> Modified Files:
> preferences.xml
> Log Message:
> Comment out the nimitz for now.
Hm ? I thought Curt just made it working with stock PLIB - is it still
broken ?
Martin.
--
Unix _IS
Frederic Bouvier wrote:
> Yes, but you need to remove ArrayFit from Prep/Makefile.am
and 'testgts' from Array/Makefile.am (which appears to be the only
reference to GTS):
--- Makefile.am.originalSat Aug 30 14:00:15 2003
+++ Makefile.am Tue Nov 30 15:50:19 2004
@@ -2,7 +2,7 @@
lib
Martin Spott wrote:
> osprey: 14:13:04 /usr/local/src/TerraGear/src/Prep/GSHHS> make
> [...]
> g++ -mcpu=604e -mtune=604e -mpowerpc-gpopt -mpowerpc-gfxopt -O3
> -L/opt/gnu/lib -L/usr/local/lib -L/opt/freeware/lib -static-libgcc -s
> -L/opt/FlightGear/lib -L/usr/X11R6/l
Martin Spott wrote:
> Problem solved: I have to add '../../Lib/TriangleJRS/libTriangleJRS.a'.
> If in manage to get this undertaking to an end then I'll post a resume.
> It would be nice if someone were willing to incorporate the necessary
> changes into the TerraGear
David Megginson wrote:
> On Tue, 30 Nov 2004 18:40:53 -, Vivian Meazza
> No, it's just a matter of stability. We don't want FlightGear
> releases to have to depend on prerelease CVS versions of plib, so we
> have to wait until the next plib official release.
I'm not convinced that this actua
"Curtis L. Olson" wrote:
> We all are busy. Steve is extremely busy. It doesn't hurt to follow up
> on these things (more than once if needed.) If done in a "sensitive"
> way, you can usually accomplish reasonable things with reasonable people.
I don't think anyone here is attempting to blam
"David Luff" wrote:
> J,K = 0.1 degrees
> Shift+J, K = 3 degrees
> Ctrl+Shift+J, K = 0.01 degrees
>
> R, D, F, C move objects 0.5 meters, or 10 meters with shift down.
Thank you! Does anyone have a current copy of Robin's 'AptNavFAQ' ?
Robin's pages on the X-Plane site have disappeared and the c
Hello Curt,
could you please revert this change and remove the whole FreeBSD
clause - it just makes life harder on the cuurrent FreeBSD RELEASE - or
change it. See below.
"Curtis L. Olson" wrote:
> Update of /var/cvs/SimGear-0.3/source/simgear/sound
> In directory baron:/tmp/cvs-serv27687/sound
>
"Curtis L. Olson" wrote:
> Ok, this sounds reasonable. I assume this means that the isnan()
> problems are fixed in newer versions of FreeBSD?
To be honest: I don't know if the current handling in FreeBSD-5.3 is
_correct_, I just can state that the clause you introduced at this
place annoyed th
"Curtis L. Olson" wrote:
> I am currently working on building the latest round of world scenery for
> FlightGear. I'm not done, so don't consider this to be the "official"
> announcement. However, for those that want to get a jump on the
> competition, you can find the new scenery here:
I had
Martin Spott wrote:
> I had a quick look at my favourite airfield yesterday and I saw that
> the modified airport generator somehow shows similarities to TaxiDraw:
> They both don't render stopways. Although the shape of the green
> boundary suggests the presence of a stopway,
Martin Spott wrote:
> I had a quick look at my favourite airfield yesterday and I saw that
> the modified airport generator somehow shows similarities to TaxiDraw:
> They both don't render stopways.
Would someone please be so kind to comment on this claim ? Did I get
things
"David Luff" wrote:
> There appear to be no stopway textures in the FlightGear base package, so
> without digging through the genapts runway generation code (yet) I'm
> guessing that stopways aren't supported by genapts yet.
Ah, fine - I already thought I'd be crazy probably I actually am
s
"David Luff" wrote:
> [...] The latest TaxiDraw
> code shows stopways as an ugly shade of yellow ochre BTW [...]
That's great ! To complete the picture, would you consider to add a
visual marker for the threshold ? Probably you could later add a
property to this marker that connects to the - if p
Erik Hofman wrote:
> I guess the SGI Prism is out of the question then:
> http://www.sgi.com/products/visualization/prism/configs.html
I think it won't run any OS but Linux
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
---
901 - 1000 of 1579 matches
Mail list logo
