Just adding to the list of issues which might need attention:
I've recently noticed a weird behaviour of rain - was okay on the ground,
but it faded out 300 ft above ground in spite of /environment/rain-norm
being set to some number. After some thinking, I think I understand why:
The current
Martin Spott wrote:
We're not yet there. On a first test earlier today, 'genapts' ended in
a segfault with the recent changes but I ran out of time, thus I
have not yet verified if the source change in 'simgear' really was the
culprit,
Confirmed here. And I thought first it was the
Martin Spott wrote:
We're not yet there. On a first test earlier today, 'genapts' ended in
a segfault with the recent changes but I ran out of time, thus I
have not yet verified if the source change in 'simgear' really was the
culprit,
Confirmed here. And I thought first it was the
Jason Cox wrote:
I am hoping to try your changes as I was constantly blowing up the
scenery around YWLM by using osm residental data [...]
OSM residential is quite ambitious - I'd be a happy man if I
succeeded building tertiary without triggering GPC segfaults in
'fgfs-construct'
I think
Whil I was trying to catch up with old *Terra*-EMail, I found this
one:
Geoff McLane wrote:
Maybe you missed my 'little' question buried deep
in my, as usual ;=(), quite log posts, but I was
asking about the 'content' of mapserver
simgear-cs git...
simgear-cs had been a requirement for
Csaba Halász wrote:
Also note, installing libgdal1-dev would have pulled in most of these
automatically.
BTW, for those who are running Debian, I'd recommend to pull the
respective GIS packages from:
http://debian.gfoss.it/
Cheers,
Martin.
--
Unix _IS_ user friendly - it's just
Geoff McLane wrote:
I am sorry Martin. I read your post MANY times,
but you will have to provided more clues for this
old brain to cotton onto ;=)). I do not quite catch
what you can mean by scenery root node?
In order to tell FlightGear where to find its Scenery we're currently
feeding a
Hi Muad
just to make sure: You know the wiki
http://wiki.flightgear.org/Joystick ??
I did use that to set/reset my Saitek X52 with no problems.
joe
Hey Joe!
Yes I did consult it. It solved the issue of calibrating the Yoke.It seems that
some aircraft have a dead zone in reacting when
Am 15.10.11 10:53, schrieb Martin Spott:
I think the only solution is to make GPC obsolete - either by replacing
GPC by something different but functional equivalent or simply (TM ;-)
by avoiding any polygon clipping in 'fgfs-construct' overall.
Martin.
Hi Martin
Are there any
You may have guessd what this is about: FGDATA and GIT.
When we last spoke about it, everything had been prepared to the utmost
convenient state possible. I had prepared a script which basically only
has to be run, to migrate the truckload of planes, ranging from fine
stuff to utter junk, into
On 15 Oct 2011, at 15:22, HB-GRAL wrote:
I think the only solution is to make GPC obsolete - either by replacing
GPC by something different but functional equivalent or simply (TM ;-)
by avoiding any polygon clipping in 'fgfs-construct' overall.
Martin.
Hi Martin
Are there any
Hi James
Thank you very much (and Martin of course) for diving into. I am just
curious how you go to replace GPC.
Cheers, Yves
Am 15.10.11 17:20, schrieb James Turner:
On 15 Oct 2011, at 15:22, HB-GRAL wrote:
I think the only solution is to make GPC obsolete - either by replacing
GPC by
Cedric Sodhi wrote:
Developers have buoyantly indulged in their lethargy as ever before and
passionately ignored the topic wherever it came up.
I don't know everybody's favourites but, anyhow, maybe it's also a
matter of preferences. Personally I'd hate having to pull dozends of
repositories
I know of another project who's main git repository contains a script,
that manages the other git repositories, this allows them to split the
gigs of data they have in to more sensible chunks, without having to
pull every repository individually.
Though the current state will be annoying for new
Am 15.10.11 22:41, schrieb Christopher Baines:
I know of another project who's main git repository contains a script,
that manages the other git repositories, this allows them to split the
gigs of data they have in to more sensible chunks, without having to
pull every repository individually.
Christopher Baines wrote:
Though the current state will be annoying for new developers on average
speed internet connections as afaik, git cannot clone, stop half way,
then continue.
Someone's providing a starter-package containing just the bare
repository for download via HTTP. I don't
On Saturday, October 15, 2011 02:41:15 PM TDO_Brandano - wrote:
Really, couldn't we just split off all the aircrafts to a separate SVN
repository? Or to several GIT repositories? That way they could be checked
out individually. I don't think we need the level of detailed history that
GIT
HB-GRAL wrote:
Am 15.10.11 10:53, schrieb Martin Spott:
I think the only solution is to make GPC obsolete - either by replacing
GPC by something different but functional equivalent or simply (TM ;-)
by avoiding any polygon clipping in 'fgfs-construct' overall.
Are there any concrete
Am 16.10.11 00:30, schrieb Martin Spott:
HB-GRAL wrote:
Am 15.10.11 10:53, schrieb Martin Spott:
I think the only solution is to make GPC obsolete - either by replacing
GPC by something different but functional equivalent or simply (TM ;-)
by avoiding any polygon clipping in 'fgfs-construct'
19 matches
Mail list logo
