Hi All,
Thanks very much for the additional feedback.
As before, I've compiled the feedback since the last version, and included
a new version (v1.3) at the bottom of this email.
Any final comments?
-Stuart
Vivian wrote:
>Typo?
>
>... at not cost from ...
Fixed.
>Awkward tautology?
>
>... we
John Denker wrote:
> That's fine as a long-term strategy, but it doesn't
> work in the short term, especially given how rarely
> FG updates its copy.
I don't mean to push this idea since we've already taken 'sufficient'
scolding for doing so in the past. Nevertheless I'd like to mention
that ship
Pete Morgan wrote:
> Is nav.dat supposed to be updated from robin X-plane database?
Yes.
>> If nobody else is going to do that, I'll be updating the file from
>> Robin's most current package during our pre-release phase (however this
>> is going to be defined ).
>>
>>
> Can't the data be
Correction in red, below.
Otherwise, it looks good, I think.
> FlightGear is an open-source flight simulator that was started in 1996.
> It is released under
> the GNU General Public License v2, and as such, it is free to use,
> modify and distribute with few restrictions. It has been
> developed
On 12/19/2009 07:40 AM, Martin Spott wrote:
> ... Robin's current set of navaids ...
> contains navaids for airfields which are otherwise unknown to
> FlightGear,
On the opposite side of the same coin, the last time
I looked, the scenery database listed huge numbers of
airports that were unknow
On Fri, 2009-12-18 at 14:35 -0500, Peter Brown wrote:
> Hey all.
>
> Does anyone know of a way to provide more realistic braking power?
> The deceleration rate seems to be an across-the-board-standard between
> all aircraft, and from a user point of view I'm not sure it takes
> weight, mass, or an
Hi All,
While updating The Manual to include all the command-line options listed by
"--help --verbose", I discovered that "--help --verbose" itself wasn't up to
date.
I've just checked in some changes to options.xml and the default set of
translated strings, so --help --verbose is now consiste
Hi Ron,
I did find the bindings and nasal properties as you mentioned here, but thank
you for the additional explanations. For the time being I'm going to look at
some more normalized braking forces per aircraft based on the following
criteria.
- individual aircraft "average" landing weights p
On 19 Dec 2009, at 16:19, John Denker wrote:
> Maybe the code should be made more robust so that this
> is not a fault condition.
>
> This is not the first time in history that code has
> needed to perform a join on two databases that are
> not in one-to-one correspondence.
Well I wrote the co
On Sat, 2009-12-19 at 12:07 -0500, Peter Brown wrote:
> Hi Ron,
>
> I did find the bindings and nasal properties as you mentioned here,
> but thank you for the additional explanations. For the time being I'm
> going to look at some more normalized braking forces per aircraft
> based on the follow
* James Turner -- Saturday 19 December 2009:
> + HASHSET("ils-frequency-mhz", 3, naNum(rwy->ILS()->get_freq() /
> 100.0));
FAIL
m.
--
This SF.Net email is sponsored by the Verizon Developer Community
Take advan
Even better.
Thanks Ron, I'll take a look at that.
Peter
On Dec 19, 2009, at 12:57 PM, Ron Jensen wrote:
> On Sat, 2009-12-19 at 12:07 -0500, Peter Brown wrote:
>> Hi Ron,
>>
>> I did find the bindings and nasal properties as you mentioned here,
>> but thank you for the additional explanations
On 19 Dec 2009, at 18:38, Melchior FRANZ wrote:
>> + HASHSET("ils-frequency-mhz", 3, naNum(rwy->ILS()->get_freq() /
>> 100.0));
>
> FAIL
Onwards and upwards (in CVS, now). Shortest code review I've ever had (so far!)
James
* James Turner -- Saturday 19 December 2009:
> - HASHSET("ils-frequency-mhz", 3, naNum(rwy->ILS()->get_freq() /
> 100.0));
> + HASHSET("ils-frequency-mhz", 17, naNum(rwy->ILS()->get_freq() /
> 100.0));
Still wrong. Since when do we use minus signs in variable names?
m.
--
* James Turner -- Saturday 19 December 2009:
> Onwards and upwards (in CVS, now). Shortest code review I've ever had (so
> far!)
Well, since people have taken over who pretend to know better (and I don't mean
you), I can't be bothered to write verbose reports. :-P
m.
--
Melchior FRANZ wrote
>
> * James Turner -- Saturday 19 December 2009:
> > - HASHSET("ils-frequency-mhz", 3, naNum(rwy->ILS()->get_freq()
> / 100.0));
> > + HASHSET("ils-frequency-mhz", 17, naNum(rwy->ILS()->get_freq()
> / 100.0));
>
> Still wrong. Since when do we use minus sign
On 19 Dec 2009, at 18:55, Melchior FRANZ wrote:
> Still wrong. Since when do we use minus signs in variable names?
Ah, that's annoying. Can't map property names to Nasal, since '-' is a token in
Nasal.
Hmmm.
ilsFrequenceyMHz?
ils_frequency_mhz?
If there's a Nasal convention here please let
On 19 Dec 2009, at 19:03, Vivian Meazza wrote:
> Hey guys, don't we test code/scripts nowadays before stuffing it into CVS?
Well the C++ code works - for this kind of thing I was lazy and hoped the
person who requested the feature will test it and let me know if they encounter
problems. I also
Ron,
Take a look at this and see if you think this would be a good route to go with
this.
The time and subjective part of course is the number of landings needed to dial
in the aircraft model.
Mfg reports that I am aware of seem to publish landing distances on both dry
and wet surfaces using a
Back in the 2nd week of September there was discussion of
reversible ILSs.
Maybe I missed something, but I thought there was rough
consensus around the following ideas:
a) FG behavior should be reasonably realistic. We should
not make artificial assumptions that make approaches
unflyable, whe
+1. Reversible approaches should be configured like any other ATC controlled
ground system - such as runway lighting. I have no objections to an automatic
selector for which ILS end to enable, but it should be based on surface wind
(for example) and not the aircraft position.
John Denker wr
On 05/24/2009 02:58 AM, Torsten Dreyer wrote in part:
> Step #2
> Add an option --metar=
> - this implies --disable-real-weather-fetch and set scenario to METAR
> - make the metar string editable in the weather_scenario dialog
> This option needs some changes in the logic of real-weather-fetch and
22 matches
Mail list logo
