On Mar 06, Arnt Karlsen wrote:
..that means you have /home/plib, /home/OpenSceneGraph,
/home/simgear, /home/fgfs, /home/flightgear, /home/fgdata etc?
.._dead_ wrong, you have users plib, simgear et al fight turf
wars over things you should have in your own /home/guy/FG tree.
Arch etc
On Wed, 9 Mar 2011 21:13:56 +0100, Guy wrote in message
20110309201356.gv2...@unistra.fr:
On Mar 06, Arnt Karlsen wrote:
..that means you have /home/plib, /home/OpenSceneGraph,
/home/simgear, /home/fgfs, /home/flightgear, /home/fgdata etc?
.._dead_ wrong, you have users plib,
Hi all,
I have a long standing issue with my installation of FlightGear. Here is
how it's set up:
* git cloned sources under /home (i.e. /home/{simgear,flightgear,fgdata})
* compilation of simgear and flightgear from the sources
cd /home/{simgear,flightgear}
git pull
On Sat, 5 Mar 2011 15:09:08 +0100, Guy wrote in message
20110305140908.ga2...@unistra.fr:
Hi all,
I have a long standing issue with my installation of FlightGear. Here
is how it's set up:
* git cloned sources under /home
(i.e. /home/{simgear,flightgear,fgdata})
..that means you
On Thursday 15 January 2009 18:18:05 Melchior FRANZ wrote:
* Stuart Buchanan -- Thursday 15 January 2009:
[+26 liveries]
My view is that they should be kept with the aircraft.
Of course, liveries should generally be kept with the aircraft.
But how many? Do 50 liveries for an aircraft make
On Sat, Jan 17, 2009 at 9:58 AM, Durk Talsma d.tal...@xs4all.nl wrote:
One thing to consider is that with OSG, we can consider merging real
aircraft, and their AI counterparts back into a single aircraft (IIRC, LOD
management is much better in OSG than it was in PLIB).
I am all for that. It
Hi,
I've collected 26 liveries, put them in one file and added the livery selection
dialog. Melchior asked me to put this on the mailinglist, as we have to discuss
if it's really helpfull to put 26 liveries for one plane in CVS. At the moment
we
have around 130 liveries (click) available
Gijs de Rooy wrote:
I've collected 26 liveries, put them in one file and added the livery
selection
dialog. Melchior asked me to put this on the mailinglist, as we have to
discuss
if it's really helpfull to put 26 liveries for one plane in CVS. At the
moment we
have around 130 liveries
* Stuart Buchanan -- Thursday 15 January 2009:
[+26 liveries]
My view is that they should be kept with the aircraft.
Of course, liveries should generally be kept with the aircraft.
But how many? Do 50 liveries for an aircraft make sense? Or 100?
200? Liveries are quickly made but can be quite
IMHO , I think maybe 2-4 liveries could be included with cvs aircraft , but
another site to download extra liveries , similar to the aircraft download
page ...
cheers
--
This SF.net email is sponsored by:
SourcForge
On Thu, Jan 15, 2009 at 6:18 PM, Melchior FRANZ mfr...@aon.at wrote:
* Stuart Buchanan -- Thursday 15 January 2009:
[+26 liveries]
My view is that they should be kept with the aircraft.
Of course, liveries should generally be kept with the aircraft.
But how many? Do 50 liveries for an
* Csaba Halász -- Thursday 15 January 2009:
How about we work out a way to transfer liveries (and maybe whole
models) over MP?
As long as I can turn it off, I don't have a problem with it. But
I think it's a rather bad idea. First, because lagging and freezing
is already bad for loading
Gijs de Rooy wrote:
we have to discuss if it's really helpfull to put 26 liveries for one plane in
CVS
My two cents...
For a select few aircraft models which are very, very popular in the real world
(including the 737 of course, but also the C172, 747, B1900, others in other
categories?), I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I like this idea (as an int, string may use too much bw at least if it is
transmitted once / update and not only when it changes). Though a way for each
aircraft to list a few extra properties it want to transmit would be even better
/AnMaster
Am Dienstag, den 02.10.2007, 20:40 -0700 schrieb SydSandy:
Hello all ,
Im putting forward the idea of transmitting a /sim/model/texture string
property with the name of a texture for individual MP aircraft , with the
idea that each MP aircraft can show its own livery without the need for
Hi,
I think transmitting a string for defining the texture of the models
livery is the wrong way. It costs much memory and all you get is just
one texture. Many models have different liveries, and the differences
are not only just one texture. The way to define the livery with just
one int
There's a TODO message in multiplaymgr.cxx that says:
// A static map of protocol property id values to property paths,
// This should be extendable dynamically for every specific aircraft ...
This static list grows and grows and that's becoming a problem. I
hardly ever take part in MP,
Hi List,
Melchior FRANZ schrieb:
There's a TODO message in multiplaymgr.cxx that says:
// A static map of protocol property id values to property paths,
// This should be extendable dynamically for every specific aircraft ...
This static list grows and grows and that's becoming a
* Maik Justus -- Wednesday 03 October 2007:
The actual MP code does not send all properties of the static list. It
only sends those properties, which are existing at initializing of the
MP-code. Thats why you need to define some properties within the
-set.xml file [...]
Ahh, thanks for the
Hello all ,
Im putting forward the idea of transmitting a /sim/model/texture string
property with the name of a texture for individual MP aircraft , with the idea
that each MP aircraft can show its own livery without the need for multiple
-set files, or a separate texture-path folder for each
I meant to reply to this yesterday...
On Mon, 9 Jul 2007, JOSHUA WILSON wrote:
I have made some more changes to the 787 model.
Your timing is excellent, as Boeing rolled out the 787 Sunday (7/8/'7):
http://seattletimes.nwsource.com/html/businesstechnology/2003780379_787main09.html
21 matches
Mail list logo
