Hello.
I was searching to solve why my events are not affected by the geometry occlusion created with FMOD::System. To my suprice they seems to not being even supported by Studio. Thats weird as Studio is already a framework build on top of System and could simply call system->getGeometryOcclusion internally.
My question: am I missing something and if not how I can reuse existing FMOD occlusion subsystem to incoporate with the Studio. And what is a rule of thumb guideline to support this feature ?
I was thinking of using callback event instance and add/remove them from list on every REAL_TO_VIRTUAL/VIRTUAL_TO_REAL to track “real” events and tick them every frame to adjust volume - but that sound a bit hacky.
Thanks for any suggestions 
I’d recommend using Oculus Spatializer or Steam Audio. They both have an occlusion system. Steam is more robust, with pathing/propagation.
Apologies for the delayed response.
it’s currently not possible to make use of the Core API’s geometry system when using the Studio API. This is because the two systems make use of different methods of panning; the Studio API uses the 3D panner DSP, which doesn’t support occlusion, while the Core API uses a bespoke non-DSP panner that does support occlusion.
If you require geometry-based occlusion, there’s a few options - making use of a 3rd party spatialization plugin, as @magomusica suggested, is one of them, but you can also create an “Occlusion” parameter on your events and use them to automate filtering/attenuation, and drive the occlusion by performing the requisite raycasts in your engine.
Hey, thanks for response.
I already did custom occlusion tests based on scene physics and use “Occlusion” parameter if exists.
śr., 13 mar 2024, 05:36 użytkownik Louis_FMOD via FMOD Forums <notifications@fmod.discoursemail.com> napisał: