* Erik Hofman -- Sunday 15 April 2007:
So it's indeed required not to use the aggressive RLE option for the
splash screen images [...]
Umm ... but $FG_ROOT/Aircraft/bo105/splash.rgb *is* aggressively
compressed. Does it crash fgfs for anyone? I also tried other such
textures -- no crashes.
Hi all,
I just finished a fresh compile of FG and OSG today, then I've found a
bug (which I've been told to be solved in the past): I can pilot not
only one, but two airplanes ;-) it is quite a funny bug, so I took some
snapshots: http://seb.marque.free.fr/fichiers/flightgear/double/
on MP
Sébastien MARQUE schrieb:
Hi all,
I just finished a fresh compile of FG and OSG today, then I've found a
bug (which I've been told to be solved in the past): I can pilot not
only one, but two airplanes ;-) it is quite a funny bug, so I took some
snapshots:
You've got me interested.
I (finally) took a look at the splash.rgb file...
I don't have kde, but I do have imagemagick installed, and using
# identify -verbose
I get a long list of technical specs, that only differ from bo105-splash.rgb
or danube-splash.rgb in a couple areas:
Image:
Hi Melchior,
I had tried getting the ufo from cvs last month, had trouble, and didn't have
time to dive in...
From the ufo_20060710.zip dated 2006-Jul-11 25134 bytes:
Using arrow keys gives
Nasal runtime error: non-objects have no members
at /usr/local/FlightGear/data/Aircraft/ufo/ufo.nas,
Hi all.
Here I am, again, still with plib compilation problems...
I'm still having the following error when running the configure script:
...
checking for shmat... yes
checking for IceConnectionNumber in -lICE... yes
checking for pthread_create in -lpthread... no
checking for glNewList in
On Fri 27 April 2007 21:22, Syd Sandy wrote:
Sébastien MARQUE wrote:
Hi all,
I just finished a fresh compile of FG and OSG today, then I've found a
bug (which I've been told to be solved in the past): I can pilot not
only one, but two airplanes ;-) it is quite a funny bug, so I took
* leee -- Thursday 26 April 2007:
I've got to confess that I have always tended to write simple but verbose
code
on the basis that the the simplicity should make human misinterpretation less
likely and the verbosity is only in the /source/ code
In this case it's different. The verbose
* leee -- Thursday 26 April 2007:
Another thing about that particular code snippet is that it is resilient
insofar as it ensures correct data values whereas the technique you suggest
relies upon a valid value in the node to work - if it gets corrupted the
function may not work or may be
I just finished a fresh compile of FG and OSG today, then I've found a
bug (which I've been told to be solved in the past): I can pilot not
only one, but two airplanes ;-) it is quite a funny bug, so I took some
snapshots: http://seb.marque.free.fr/fichiers/flightgear/double/
Hi.
10 matches
Mail list logo
