Alright, thanks to FGViewer::recalcLookFrom I think I've nailed down the
position and orientation stuff. I did not yet check whether the
positions and orientations and velocity vectors are correct relative to
each other, but if the current code still generates sounds for everybody
that part sh
Ron Jensen wrote:
> On Sat, 2009-10-24 at 10:39 +0200, Erik Hofman wrote:
>
>> Ok, I've reserved the next two days to try to pin-point the problem. For
>> that I've taken drastic measures now; All sounds and the listener are
>> located at 0,0,0 and all orientations are omni-directional.
>> Wha
On Sat, 2009-10-24 at 10:39 +0200, Erik Hofman wrote:
> Ok, I've reserved the next two days to try to pin-point the problem. For
> that I've taken drastic measures now; All sounds and the listener are
> located at 0,0,0 and all orientations are omni-directional.
> What this means: no distance att
On Sat, 2009-10-24 at 13:01 +0200, Erik Hofman wrote:
> Alasdair Campbell wrote:
> > After cvs update (SG,FG,data):
> >
> > alasd...@executrix:~$ fgfs
> > Error reading properties:
> > not well-formed
> > at /opt/FlightGear/FlightGear_cvs/data/preferences.xml,
> > line 56, column 2
>
> That sho
Alasdair Campbell wrote:
> After cvs update (SG,FG,data):
>
> alasd...@executrix:~$ fgfs
> Error reading properties:
> not well-formed
> at /opt/FlightGear/FlightGear_cvs/data/preferences.xml,
> line 56, column 2
That should be fixed by now.
Erik
--
Scott Hamilton wrote:
> On Sat, 2009-10-24 at 10:39 +0200, Erik Hofman wrote:
>
>
>I did a cvs update on simgear and flightgear, and I now have engine
> sounds, click sounds, flap transit sounds,
>everything is back again...
Looks like we're starting to get somewhere now.
Thanks for tes
On Sat, 2009-10-24 at 10:39 +0200, Erik Hofman wrote:
I did a cvs update on simgear and flightgear, and I now have engine
sounds, click sounds, flap transit sounds,
everything is back again...
S.
> Ok, I've reserved the next two days to try to pin-point the problem. For
> that
On Sat, 2009-10-24 at 10:39 +0200, Erik Hofman wrote:
> Ok, I've reserved the next two days to try to pin-point the problem. For
> that I've taken drastic measures now; All sounds and the listener are
> located at 0,0,0 and all orientations are omni-directional.
> What this means: no distance att
Erik Hofman wrote:
> I was hoping this could lead to (for example) a NaN problem but ... I
> discovered this triggered the same bug for me that others have for the F-16.
That was spoken too soon, the sound file couldn't be read which is why
there was no sound :-/
Eirk
-
Ok, I've reserved the next two days to try to pin-point the problem. For
that I've taken drastic measures now; All sounds and the listener are
located at 0,0,0 and all orientations are omni-directional.
What this means: no distance attenuation, no relative position to the
listener but only sour
10 matches
Mail list logo
