Open datramt opened 6 years ago
This is going to be an issue with both Unity 2017.3 and the newly released 2018.1. We will fix it in the Resonance plugins that are built into Unity in 2018.1 and in this SDK here soon. Fortunately, there is a work-around that you can do right away. After importing this SDK into your Unity project, search through your project's files on disk to Assets/ResonanceAudio/Plugins/x86_64/audiopluginresonanceaudio.bundle.meta. Open that file in a text editor, search for "Standalone: OSXUniversal". Four lines below that should read "CPU: AnyCPU" instead of "CPU: x86_64". If you make that change and re-start the Unity Editor, your Mac standalone builds should work again. Sorry for the inconvenience!
That work-around did indeed work, thanks a bunch!
Hello,
Machine: 2016 macbook pro 16-inch OS: Mac OS High Sierra version 10.13.3
On Unity version 2017.3.1f1, when I create a scene using ResonanceAudioForUnity_1.2.1 to 3d-spatialize gameobjects, the spatialization works as expected running directly in the unity engine, but when I build the project, it is no longer 3d-spatialized. In fact, when the player moves, the spatialization seems a bit glitchy, and seemingly reverts to standard panning.
I am quite confident that my scene settings are correct; when my colleague who is working on the same game builds on his machine (a PC), it is correctly spatialized.
I can't tell if it is a user error building on my end or some bug with this combination of os/unity/resonanceaudio versions. Let me know if you need more information.
Other than this build issue, I am LOVING this sdk 👍