Hello,
We recently updated our Google Resonance Audio plugin in FMOD Studio 2.03.06
After updating I have found that some of our existing events no longer allow for the Min and Max Distance in the Event Macro box to be changed, the slider is now greyed out
However, if I set automation by right clicking on the distance attenuation FMOD lets me set constant values for Min and Max, and the change is reflected in the Event Macro box, like so:
It seems that any new events I create now have the option greyed out as well, I haven’t been able to identify why some events are affected and some are not,
Any help in solving this would be greatly appreciated
Thank you for the reply
I think I found the issue,
Even though we had updated the .dll in the project folder, I had not updated the corresponding .dll in my FMOD installation
I suspect Alcibiade’s guess is the correct one: Min and max distance are only editable in events that make use of them. Things that make use of min and max distance include built-in distance (normalized) parameters and spatializer effects not set to override.
In any case, I’m glad you were able to get the behavior you wanted.
Hi
I’m running into this problem again,
We are using a plugin spatializer, but FMOD does not consider this to be “using” the event macro min and max distance
To change those values, I have to add a default FMOD spatializer and then the option becomes non greyed out
Any ideas to get around this limitation? To remedy the effect this is having on our project will require us to manually go through our events and add a default spatializer just to be able to manipulate the min and max distance of the event macro, only to then immediately delete the spatializer again
For a plug-in effect to automatically enable the min/max distance sliders of the event, it must feature a FMOD_DSP_PARAMETER_DATA_TYPE_ATTENUATION_RANGE data parameter. If you are able to edit your plug-in effect, you should be able to add a data parameter of that type to it without difficulty. Doing so will ensure that the min and max distance properties of any event that uses the effect become editable.
If you do not have the ability to edit the plug-in spatializing effect that you’re using, you will have to use a workaround. I recommend making the plug-in spatializer effect a shared effect, and automating one of its properties on a built-in “distance (normalized)” parameter. The automation doesn’t have to do anything meaningful; it can just be a flat line. (If the plug-in spatializer effect has no automateable properties, you can instead add it to a shared effect chain that also includes a gain effect, and automate the property of the gain effect.) Because the parameters used to automate a shared effect are automatically added to any event that uses that shared effect, and because a distance (normalized) parameter uses the event’s min and max distance, this will ensure that any event that includes the shared spatializer effect will have editable min and max distance. The resource cost of an automation curve is extremely close to zero, so this is unlikely to have significant impact on your game’s performance.
