* Ron Jensen -- Thursday 02 April 2009:
> I think we need
> double angle = atan2( y, x ) * SGD_RADIANS_TO_DEGREES;
Agreed. And that's also done just a few lines later, with the
exact same parameters. Comitted, thanks! (I also re-used an
already initialized node for altitude-ft.)
m.
-
On jeudi 02 avril 2009, gerard robin wrote:
> On mercredi 01 avril 2009, jean pellotier wrote:
> > Jon S. Berndt a écrit :
> > > Yes, the difference stems from the need to know what the wind is
> > > bringing, and the vectorial definition of where it's going. The problem
> > > was that sometimes we
I haven't looked carefully at how alpha and beta are dealt with ... perhaps
they are computed on the fly from other values and that computation
overrides anything you might load from an external file? One possible way
around this would be create a copy of the HUD configuration, modify the
property
On Sat, 2009-01-10 at 17:13 +0100, Csaba Halász wrote:
> #2 0x0080188d in FGNavRadio::update (this=0x98df490,
> dt=0.058334) at src/Instrumentation/navradio.cxx:613
> 613 double angle = asin( y / x ) * SGD_RADIANS_TO_DEGREES;
> (gdb) p x
> $1 = 3.25804509431
Vivian Meazza wrote:
> I'm not clear about how much ambient light there should be in any situation,
> but, to me right now there isn't enough with the default model. The effect
> of visibility on the diffuse and specular setting looks OK in very low
> visibility, but at high visibility it looks ver
Lee Qid wrtote
>
> Hi there,
>
> let me join this discussion:
>
> Very good summary indeed. Pretty much what I was just writing.
> If you want to get a feel of specular highlights, look at car-paint,
> and observe what is reflected on the metal that actually causes the
> highlights. You will fi
6 matches
Mail list logo
