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.
P.S. By the way, when we could reach FMOD STUDIO? I’m really excited!!!
- Sohn asked 7 years ago
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)
Did you mean, System::set3DListenerAttributes let System knows ?
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.
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.
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.
- Both ways’re exactly same when we use ‘built-in’ rolloff model(Log. & Lin.).
- We must call EventSystem::set3DListenerAttributes when using ‘Custom’ 3D rolloff model with ‘Add 3D distance parameter’ for automatic-distance-update.
Please login first to submit.