0
0

Hi.

I’m looking into the source code of 3ddemo (in "FMOD Programmers API Win32\fmoddesignerapi\examples\bin").
It uses "System::set3DListenerAttributes" to place & tracking user(listener)’s movement, not "EventSystem::set3DListenerAttributes"

I thought it uses "EventSystem::set3DListenerAttributes" before open source code because it’s FMOD Designer API’s example, not FMOD Ex’s.
So, I’m dying to know what’s the difference(s) between setting 3DListenerAttributes from System and EventSystem.

Thank you.

P.S. By the way, when we could reach FMOD STUDIO? I’m really excited!!!

  • You must to post comments
0
0

Yeah! Good to know that!
Maybe many people are waiting for updates of docs & examples…including me ๐Ÿ˜€

Thanks.

  • You must to post comments
0
0

Yep, that’s exactly right. In general there is no harm in using EventSystem version so it’s probably better practice to do it that way regardless. I’ll make a note of it and hopefully we’ll get around to looking into updating the examples soon.

  • You must to post comments
0
0

Thank you for your kindness, Peter.

Well…I thought built-in rolloff models(Logarithmic & Linear) already have 3D parameters internally (distance, listener angle & event angle)
which are need to be updated by programmer.

To summarize:

  1. Both ways’re exactly same when we use ‘built-in’ rolloff model(Log. & Lin.).
  2. We must call EventSystem::set3DListenerAttributes when using ‘Custom’ 3D rolloff model with ‘Add 3D distance parameter’ for automatic-distance-update.

Any Correction?
Thanks.

  • You must to post comments
0
0

In this specific case it doesn’t make a difference because the only event used in that example is 3DSoundEmit which does not have and distance parameters.

  • You must to post comments
0
0

Hi Peter. Thank you for your explanation.

If only EventSystem::set3DListenerAttributes tell EventSystem to update distance parameters, then is that more suitable to use set3DListenerAttributes from EventSystem, not from System? (in main.cpp of 3DDEMO)

or

Did you mean, System::set3DListenerAttributes let System knows ?

Thanks.

  • You must to post comments
0
0

Hey guys, there is one slight difference between the two. Calling EventSystem::set3DListenerAttributes will let the EventSystem know it needs to update distance parameters, other than that they are the same.

[quote:24m7iown]May I know what made them ‘absent’ ?[/quote:24m7iown]
Our attention has been focussed on developing FMOD Studio, so we haven’t had the time to give proper attention to the forums.

  • You must to post comments
0
0

Yes. I guess they’re same but I couldn’t be sure.
Anyway, thanks !!! martin ๐Ÿ˜€

[quote="martinrobinson":18wtxnv3]In the absence of some firelight guys…[/quote:18wtxnv3]

May I know what made them ‘absent’ ?

  • You must to post comments
0
0

In the absence of some firelight guys… I think these just refer to the same settings. The EventSystem version is just there to save you from having to dig in to get the System object in order to do this stuff.

  • You must to post comments
Showing 8 results
Your Answer

Please first to submit.