James Turner wrote:
Excellent news. My biggest two requests would be to get the sound code
out of main.cxx, and proper support for positional sources - i.e AI or
MP traffic. Being able to position sounds on the airframe would be
good too - engine and gear noises especialy.
Tom P
Hi John,
John Denker wrote:
That's a good thing to work on. Thanks for the heads-up.
Here's one more thing to think about in this context:
text to speech. AFAICT the status is:
1) The existing home-brew TTS system (involving
ATC/default.vce and ATC/default.wav) is very limited.
It
Hi Durk,
Durk Talsma wrote:
That sounds pretty awesome. (Sorry for the lame pun). :-)
:)
Seriously, though, since you mention that this is something you're working on
for the longer term, do you think this planned update should be included in
the new release (planned beta release around
On 20 Sep 2009, at 08:18, Erik Hofman wrote:
Both will be adressed. The problem Tom describes has something to do
with improper doppler effect and a nasty way to fix it. I Think I've
found why doppler didn't work properly in the first place.
That's fantastic news!
Let me know if I can help
James Turner wrote:
Let me know if I can help at all. One thing I thing I would strongly
suggest on the FG side, would be to ensure the SG side uses Mathias'
excellent basic types (SGVec3d/f, SGQuatd, etc) to express positions,
vectors and orientations to the code. The SG layer itself
On 20 Sep 2009, at 09:25, Erik Hofman wrote:
I might need some help to understand quads, but I am converting it to
SGVec3f where ever possible.
No problem, I'm sure Mathias / Tim / myself can oblige.
One other I've remember from looking at the code - for some reason we
always positioned
James Turner wrote:
On 20 Sep 2009, at 09:25, Erik Hofman wrote:
I might need some help to understand quads, but I am converting it to
SGVec3f where ever possible.
No problem, I'm sure Mathias / Tim / myself can oblige.
Thanks!
One other I've remember from looking at the code - for
On Sun, Sep 20, 2009 at 6:23 AM, Erik Hofman e...@ehofman.com wrote:
One other I've remember from looking at the code - for some reason we
always positioned the listener at (0,0,0), and do a lot of work to
transform world positions into a listener-relative basis. As I
understand it,
On 20 Sep 2009, at 10:23, Erik Hofman wrote:
True, and I expect it's also the reason why doppler didn't work
correctly (besides that the listener velocity wasn't updated while
OpenAL needs both the listener velocity and the source velocity for
proper calculation of the doppler effect).
Hi John,
I just fixed what appeared to me as a bug:
mixing altitude_ft and altitude_m and wrong sign when computing temperature at
sea level from temperature at altitude.
Can you check and confirm that this is correct and reflects your original
intention?
Thanks, Torsten
On 09/20/09 08:52, Torsten Dreyer wrote:
Hi John,
I just fixed what appeared to me as a bug:
mixing altitude_ft and altitude_m and wrong sign when computing temperature
at
sea level from temperature at altitude.
Can you check and confirm that this is correct and reflects your original
11 matches
Mail list logo
