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 EffectPlugin and SourcePlugin Tags for details on how to define these IDs.

Problem: My plug-in is not available to the user in Wwise.

• 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 EffectPlugin and SourcePlugin Tags for more information.
• Verify that your plug-in description file specifies the appropriate supported platforms. Refer to PluginInfo Tag 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() and AkGetSoundEngineCallbacks() functions in your DLL. 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..

Problem: One of the controls in my plug-in's user interface is empty or disabled.

• 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 Tag 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 Tag for more information.

Problem: One of the Wwise controls in my plug-in's user interface does not appear correctly.

• 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 which 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.

Problem: My plug-in doesn't recognize property changes in the UI.

• Verify that the AudioEnginePropertyID specified in your plug-in definition file is in the 0-32767 range. Refer to Properties Tag 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 Tag for more information about the AudioEnginePropertyID tag, and AK::IAkPluginParam::SetParam() for details about implementing AK::IAkEffectParam::SetParam().

Problem: My plug-in works in Wwise but not in my game

• Your game must register all the plug-ins it uses. Refer to Plug-in Registration for more details.