David Megginson said:
> Lee Elliott wrote:
>
> > I'm pretty sure that information/data can't be copyrighted - but the
design of
> > the presentation of the information/data can.
>
> I hope not, but every country has its own (bizarre) laws about this kind of
> thing -- for example, in Commonwea
OK, Melchior helped to debug this via chat while I was working on cell
phone UI bugs at work. :)
It turns out to have been a pair of typos in fuel.nas that were
causing all the problems. What I *read* wasn't what the code was
actually doing, which explains all the confusion.
This one, though, is
David Megginson said:
> Chris Metzler wrote:
>
> > Is there an official announcement of this somewhere? I've looked all
> > around the NGA and NACO sites but haven't found anything. How did he
> > hear about this? Is there any kind of timetable? Were there reasons
> > stated?
>
> According t
Melchior FRANZ wrote:
* Erik Hofman -- Thursday 12 August 2004 19:00:
Vivian Meazza wrote:
Then windsocks and radio towers will magically appear in Europe. Or anyway,
they do for me :-).
Are you sure about the radio towers?
Curtis uses an US only database for that ...
He probably means the beacons.
* Erik Hofman -- Thursday 12 August 2004 19:00:
> Vivian Meazza wrote:
>
> > Then windsocks and radio towers will magically appear in Europe. Or anyway,
> > they do for me :-).
>
> Are you sure about the radio towers?
> Curtis uses an US only database for that ...
He probably means the beacons.
Vivian Meazza wrote:
Then windsocks and radio towers will magically appear in Europe. Or anyway,
they do for me :-).
Are you sure about the radio towers?
Curtis uses an US only database for that ...
Erik
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
Melchior FRANZ wrote:
> Yes, I've seen these annoying bugs in both the Spitfire and the
> p51d. Vivian's changes to fuel.nas fix them. I haven't seen any
> negative side effects.
>
> Could someone please replace fuel.nas?
Could someone *PLEASE* explain, from scratch, exactly what is wrong
with the
Vivian Meazza wrote:
> This is, I believe, due to a bug at line 67 of the script
> ~/data/nasal/fuel.nas which improperly sets the tank property
> "kill-when-empty".
Haven't we already been here and thrown out this explanation? Here is
line 67:
if(t.getBoolValue("kill-when-empty")) { outOfFuel
* Vivian Meazza -- Thursday 12 August 2004 16:20:
> Unfortunately, there are three problems with this release:
>
> 1. With both fuel cocks open, when the fuel in the Upper tank runs out, the
> engine stops, despite the lower tank having fuel available and being
> selected. [...]
> 2. If both fuel
Hey guys,
For all of you who have emailed me and still haven't received a
response, I just wanted to let you know that I haven't forgotten about
your messages. They are still in my pending/inbox. I was out of town
over the weekend and this has been a tougher than average week here. My
wife s
Erik Hofman wrote:
> Sent: 12 August 2004 14:59
> To: FlightGear developers discussions
> Subject: Re: [Flightgear-devel] terrasync and terrain/scenery
>
>
> Matevz Jekovec wrote:
> > Does terrasync download terrain only or scenery objects as well.
> > Because
> > the current terrasync reposit
Eric has kindly uploaded the most recent release of the Spitfire model to
cvs. If you haven't already noticed, this release adds a fuel system with
Upper and Lower tanks (which are interconnected), priming pump, fuel cocks,
and a fuel gauge.
Unfortunately, there are three problems with this relea
Matevz Jekovec wrote:
Does terrasync download terrain only or scenery objects as well. Because
the current terrasync repository still has the old structure IMO. (I set
the terrasync root dir to fgfs/data/Scenery/Terrain to get it work, but
this doesn't include objects download, as they are in
f
Does terrasync download terrain only or scenery objects as well. Because
the current terrasync repository still has the old structure IMO. (I set
the terrasync root dir to fgfs/data/Scenery/Terrain to get it work, but
this doesn't include objects download, as they are in
fgfs/data/Scenery/Objec
Norman Vine wrote:
David Megginson writes:
Since I updated FlightGear a few days ago, my X Windows mouse has been
frozen after exiting whenever FlightGear is in full-screen mode (there is no
problem in window mode). Switching to a text console and back does not help
-- I end up having to res
David Megginson writes:
>
> Since I updated FlightGear a few days ago, my X Windows mouse has been
> frozen after exiting whenever FlightGear is in full-screen mode (there is no
> problem in window mode). Switching to a text console and back does not help
> -- I end up having to restart X.
>
Since I updated FlightGear a few days ago, my X Windows mouse has been
frozen after exiting whenever FlightGear is in full-screen mode (there is no
problem in window mode). Switching to a text console and back does not help
-- I end up having to restart X.
Any suggestions on where I should sta
17 matches
Mail list logo
