Re: [Flightgear-devel] Sound System debugging

2009-10-26 Thread Erik Hofman 

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 should be easy.

Erik

--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Sound System debugging

2009-10-24 Thread Erik Hofman 
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.
>> What this means: no distance attenuation, no relative position to the 
>> listener but only sources emitting sounds.
>>
>> 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.
>>
>> I would appreciate it if at least a few people want to test it and 
>> report the results for them. In the mean time I'm trying to see if I can 
>> fix it for the F-16 locally.
>> Oh and no point reporting a segmentation fault at exit, I'm aware of it.
>>
>> Erik
>> 
>
> As of this morning I'm still seeing an fpe at initialization:
>
>   
Yes that' s because no one has stepped up to help me out on the 
positioning and orientation code,even after multiple requests. The code 
gets  executed but it's results s just not used at this time.

Eerik

--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Sound System debugging

2009-10-24 Thread Ron Jensen 
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 attenuation, no relative position to the 
> listener but only sources emitting sounds.
> 
> 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.
> 
> I would appreciate it if at least a few people want to test it and 
> report the results for them. In the mean time I'm trying to see if I can 
> fix it for the F-16 locally.
> Oh and no point reporting a segmentation fault at exit, I'm aware of it.
> 
> Erik

As of this morning I'm still seeing an fpe at initialization:

gdb --args fgfs --airport=KHIF --disable-real-weather-fetch --timeofday=noon   
--multiplay=out,10,mpserver07.flightgear.org,5000 --enable-fpe
GNU gdb 6.7.1-debian
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(gdb) run
Starting program: fgfs --airport=KHIF --disable-real-weather-fetch 
--timeofday=noon --multiplay=out,10,mpserver07.flightgear.org,5000 --enable-fpe
[Thread debugging using libthread_db enabled]
[New Thread 0xb62cf6e0 (LWP 28983)]

Program received signal SIGFPE, Arithmetic exception.
[Switching to Thread 0xb62cf6e0 (LWP 28983)]
SGSoundSample::update_absolute_position (this=0xd690c40) at 
../../simgear/math/SGVec3.hxx:327
327v1(0)*v2(1) - v1(1)*v2(0));
(gdb) bt  
#0  SGSoundSample::update_absolute_position (this=0xd690c40) at 
../../simgear/math/SGVec3.hxx:327
#1  0x085e9de8 in SGSoundSample::set_relative_position (this=0xd690c40, 
p...@0xbfe29870) at sample_openal.cxx:212
#2  0x085f1845 in SGXmlSound::init (this=0xd691168, root=0x8860080, 
node=0xd6905b8, sgrp=0x8d30248, pa...@0x885fff0) at xmlsound.cxx:262
#3  0x0852ece4 in FGFX::init (this=0x8d30248) at fg_fx.cxx:94
#4  0x084c8dca in FGAircraftModel (this=0x8d40100) at acmodel.cxx:53
#5  0x0806f55c in fgIdleFunction () at main.cxx:644
#6  0x080c3a2c in fgOSMainLoop () at fg_os_osgviewer.cxx:172
#7  0x0806ed6d in fgMainInit (argc=6, argv=0xbfe29be4) at main.cxx:897
#8  0x0806ce35 in main (argc=6, argv=0xbfe29be4) at bootstrap.cxx:229
(gdb) cont
Continuing.




--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Sound System debugging

2009-10-24 Thread Alasdair Campbell 
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 should be fixed by now.
> 
> Erik
> 
Already found it.
Sound back to normal :), but immediate segfault if atis is tuned.

Alasdair


--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Sound System debugging

2009-10-24 Thread Erik Hofman 
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

--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Sound System debugging

2009-10-24 Thread Erik Hofman 
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 testing Scott.

Erik

--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Sound System debugging

2009-10-24 Thread Scott Hamilton 
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 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 sources emitting sounds.
> 
> 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.
> 
> I would appreciate it if at least a few people want to test it and 
> report the results for them. In the mean time I'm trying to see if I can 
> fix it for the F-16 locally.
> Oh and no point reporting a segmentation fault at exit, I'm aware of it.
> 
> Erik
> 
> --
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay 
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> ___
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Sound System debugging

2009-10-24 Thread Alasdair Campbell 
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 attenuation, no relative position to the 
> listener but only sources emitting sounds.
> 
> 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.
> 
> I would appreciate it if at least a few people want to test it and 
> report the results for them. In the mean time I'm trying to see if I can 
> fix it for the F-16 locally.
> Oh and no point reporting a segmentation fault at exit, I'm aware of it.
> 
> Erik
> 
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
Error reading panel: 
Failed to open file
 at /opt/FlightGear/FlightGear_cvs/data/Panels/Default/default.xml
Error reading new panel from Panels/Default/default.xml
HUD: Error 
Problem reading file
 at line 1, column 0
FGMultiplayMgr - No receiver port, Multiplayermode disabled
Nasal runtime error: nil used in numeric context
  at /opt/FlightGear/FlightGear_cvs/data/Nasal/dynamic_view.nas, line
167
  called
from: /opt/FlightGear/FlightGear_cvs/data/Nasal/dynamic_view.nas, line
420
Nasal runtime error: container index not scalar
  at /opt/FlightGear/FlightGear_cvs/data/Nasal/view.nas, line 215
  called from: /opt/FlightGear/FlightGear_cvs/data/Nasal/view.nas, line
625
Nasal runtime error: non-scalar in string context
  at /opt/FlightGear/FlightGear_cvs/data/Nasal/screen.nas, line 394
  called from: /opt/FlightGear/FlightGear_cvs/data/Nasal/globals.nas,
line 100
KI266 dme indicator #0 initialized
Nasal runtime error: non-objects have no members
  at /opt/FlightGear/FlightGear_cvs/data/Aircraft/c172p/Nasal/kr87.nas,
line 121
  called
from: /opt/FlightGear/FlightGear_cvs/data/Aircraft/c172p/Nasal/kr87.nas,
line 108
  called
from: /opt/FlightGear/FlightGear_cvs/data/Aircraft/c172p/Nasal/kr87.nas,
line 181
creating 3D noise texture... Segmentation fault
alasd...@executrix:~$ 


Regards,
Alasdair


--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Sound System debugging

2009-10-24 Thread Erik Hofman 
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

--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

[Flightgear-devel] Sound System debugging

2009-10-24 Thread Erik Hofman 

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 sources emitting sounds.

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.

I would appreciate it if at least a few people want to test it and 
report the results for them. In the mean time I'm trying to see if I can 
fix it for the F-16 locally.
Oh and no point reporting a segmentation fault at exit, I'm aware of it.

Erik

--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel