I believe there may be a bug in the haptic plugin in version 2.04.
After the migration, some sounds were being heard from extreme positions (mostly from the right side). I spent several hours tracking down the cause, and it turned out to be the haptic plugin.
Here’s what I found: when a track containing a haptic plugin instrument has its output set to Surround 4.0 or higher (rather than mono or stereo), the sound plays from an incorrect position instead of from the attached socket.
As a temporary workaround, I’ve changed the output setting of the events containing haptics from Automatic to Stereo. I’d appreciate it if you could look into this and fix the bug as soon as possible.
Got it, I’ll get that ready soon. Before I do, I have a question. Whenever an event containing a haptic instrument is played, the following warning message always appears: “The plugin has reserved its input format and it cannot be changed.” Do you know why this happens? I’d never seen this warning before migrating to 2.04, so I wanted to ask. (For reference, the warning appears no matter what the track’s input or output is set to.)
I can reprdouce this warning in FMOD Studio when I play a Haptics Instrument- it seems to be spurious in this instance, since the runtime ignores the error and continues down its normal course, but I will talk to the dev about downgrading that warning to a log. Thanks for letting us know!
Just following up on this - have you managed to resolve the issue? If not, as previously asked for by Jeff, could I get you to upload a repro event to your FMOD user profile?
I’ve uploaded haptic_bug_test.fspackage to my profile.
As a temporary workaround, I’ve changed the output of every haptic instrument track used in our project to Stereo. However, the warning “The plugin has reserved its input format and it cannot be changed.” still appears every time a sound containing a haptic instrument is played. The warning appears no matter what I change the input format to.
I’ve also included a profiler session called “haptic_problem” that captures the issue. If you play it back, the first two hit sounds are from the sfx_combat_hit_body event with its Haptic track output set to Automatic, and the following three hits are with the output set to Stereo. As you’ll hear, the first two sounds come from slightly to the left rather than from the center.
Unfortunately, it seems that the package is missing the recorded .wav file and api commands - if you could reupload, ensuring that both those files are present in ./Metadata/ProfilerSession/{your-profiler-session-here} in the package, that would be great!
With your workaround, the warning should be benign. That said, a fix for this issue should be included in the next minor release.
I’ve unfortunately been able to reproduce the issue. That said, I suspect the channel format isn’t actually the issue here, and I have a few followup questions:
What version of Microsoft GameInput do you have installed? You can find out from Control Panel → Programs → Programs and Features by searching for GameInput.
What type of controller are you using? i.e. DualSense, XBox, 3rd party, etc.
When haptics play on your controller, do you feel the haptics equally from the left and right? Or as to distinct sizes of motors i.e. a big motor and a little motor? If you adjust the Left and Right properties on the Haptics instrument, what happens to the haptics?