Studio will require a 32-bit dll or dylib file if running in Windows or Mac respectively. Two versions of the plug-in will usually be required - one for FMOD Studio and one for the game. The panel will be automatically populated with dials, buttons and data drop-zones for each parameter. When a plug-in module is added to a track or bus, its panel will be displayed in the effect deck.

Studio tries to load any libraries it finds (*.dll on Windows or *.dylib on Mac) and ignores libraries which don't support the API.ĭetected plug-in sounds will be available via the track context menu in the Event Editor, whereas detected plug-in effects will show up in the effect deck's Add Effect and Insert Effect context menus. FMOD Studio scans the folder and all sub-folders both on start-up and when the folder is changed by the user. Accessing Plug-ins in FMOD StudioĪ plug-in must be built as a 32-bit dynamic linked library and placed in the plug-ins folder specified in FMOD Studio's Preferences dialog under the Plug-ins tab. It is recommended you follow along with our examples found in api/lowlevel/examples/plugins as they are fully implemented working effects you can use or base your code on. This document describes how to create plug-ins and make them available to FMOD Studio and the game.

By placing plug-ins in FMOD Studio's plug-ins folder, these can be added to tracks or buses, modulated and automated by game parameters just like built-in effect and sound modules. Game studios and third-party developers can augment FMOD Studio's built-in suite of effect and sound modules by creating their own plug-ins.

Firelight Technologies FMOD Studio API FMOD Studio Plug-in SDK Introduction

Fmod studio for mac