Wwise Source and Effect Plug-in Troubleshooting Guide

Problem: At startup, Wwise displays an error message stating that two plug-ins have the same Company ID and Plug-in ID.

Each plug-in must have a unique Company ID / Plug-in ID combination. Refer to WwiseObject Elements for details on how to define these IDs.

Verify that your plug-in description file specifies the right type of plug-in. The file should use the SourcePlugin tag for source plug-ins and EffectPlugin for effect plug-ins. Refer to WwiseObject Elements for more information. This category must be matched in both the XML file and PluginRegistration class in your engine-side code.
Verify that your plug-in description file specifies the appropriate supported platforms. Refer to PluginInfo Element for more information.
Verify that the Company ID and Plug-in ID specified in your plug-in's XML file match those used by the AkCreatePlugin() function in your DLL and in the PluginRegistration object. See Wwise Sound Engine Plug-ins Overview for an example of PluginRegistration. Refer to Wwise Plug-in XML Description Files and Exported Functions for more details.
If Wwise displays an error message on startup stating that two plug-ins have the same IDs, refer to Problem: At startup, Wwise displays an error message stating that two plug-ins have the same Company ID and Plug-in ID..
Verify that your XML and DLL have the same name
Verify that your XML and DLL are in the Plugins folder, for both x86 and x64 flavors.

Your plug-in needs to be a 32-bit DLL. Wwise authoring only runs in 32 bits on Mac.
Your plug-in XML and DLL were not included in the Codeweaver Crossover list. See Installation on Mac OS X for instructions.

Verify that the property name specified in the control's text in the resources (for example Prop=SineFrequency) is the same as the name specified in your plug-in description file (for example Property Name="SineFrequency"). Refer to "Prop" Control Attribute and Properties Element for more information.
Verify that the control class (for example Class=SuperRange) is suitable for the property's type. Refer to "Class" Control Attribute and Properties Element for more information.

Make sure the Class attribute is properly set in your dialog resources. Refer to "Class" Control Attribute for more details.
Make sure your code doesn't change the control's text before the dialog is fully created. In this case Wwise doesn't have access to the Class attribute when required. Note that you should never change the text on a control that is bound to a property. Refer to "Prop" Control Attribute for more information.
Refer to Other Control Attributes and verify that the various control attributes are properly set.
Refer to How to Add Regular Controls to Your Dialogs and How to Add Wwise Property Controls to Your Dialogs for information on the two types of controls available in your plug-in dialogs.

Verify that the AudioEnginePropertyID specified in your plug-in definition file is in the 0-32767 range. Refer to Properties Element for more information about the AudioEnginePropertyID tag.
Verify that the AudioEnginePropertyID specified in your plug-in definition file matches the ID you use in your implementation of AK::IAkEffectParam::SetParam(). Refer to Properties Element for more information about the AudioEnginePropertyID tag, and AK::IAkPluginParam::SetParam() for details about implementing AK::IAkEffectParam::SetParam().

There are two possibilities:

If your game statically links the effects, make sure you link the plug-in library and include the corresponding factory header file in one of the CPP files.
If your game uses dynamic libraries (such as DLL, SO, and PRX), make sure your effect DLL is copied in the same folder as the executable. Or set AkInitSettings::szPluginDLLPath to add a DLL search path, if they are not in the same folder.

Here are a few points to validate for new plugins in Unity.

Plugins loaded by Wwise in Unity must be copied to \Assets\Wwise\Deployment\Plugins\[Platform]\DSP. Usually this is the Release version.
There must be a Windows\x86, Windows\x86_64 and a Mac version of the plug-in so the plug-in can work in the Unity Editor.
The standard Unity integration will detect the plug-in usage from the PluginInfo.xml that is created when generating the banks. The "DLL" tag in PluginInfo.xml comes directly from the "EngineDllName" tag written in the XML file describing the plug-in in the Wwise authoring folders. Make sure your DLL has the same name.

Des questions ? Des problèmes ? Besoin de plus d'informations ? Contactez-nous, nous pouvons vous aider !

Visitez notre page d'Aide

Enregistrez votre projet et nous vous aiderons à démarrer sans aucune obligation !

Partir du bon pied avec Wwise