Search Issue Tracker
Fixed in 5.3.0
Votes
9
Found in
5.1.0f2
Issue ID
698724
Regression
Yes
FMOD::Sound instance for resource error
To reproduce:
1. Open GLTest.zip project
2. Open GameLoader scene
3. Run custom builder in top of Editor menu. Build->Game build and select temp folder
4. Copy file from AssetBundles.zip to temp folder
5. Press play
6. Notice "Error: Cannot create FMOD::Sound instance
for resource..." error
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
Haze-Games
Feb 02, 2016 13:08
This is not fixed. In Unity 5.3.2f1, I get it on Android, if:
- Split application binary is enabled
- Delete .obb file from device
- Launch the game
Before Unity 5.3, the OBB download started correctly using the Unity OBB Downloader plugin. Now, the game stays on infinite loading on the Splashcreen, never calls the OBB plugin to download missing data, and this error occurs.
A huge problem for me :(
Thanks for fixing it.
pgeorges
Feb 01, 2016 20:08
This is still happening for us in Unity 5.3.1p1. Has been happening since we upgraded.
iwaldrop
Jan 29, 2016 00:00
I'm getting this error in the editor (v5.3.2f1).
```
WWW www = new WWW (url);
clip = www.GetAudioClip(false, true);
clip.name = title;
```
Iwanowski
Jan 26, 2016 14:02
This appears also in 5.3.1p4 it's massive problem for us! We can't release game for Apple Tv...
charming_fox
Jan 26, 2016 08:14
Also having this still in 5.3.1.f... huge problem for us!
TheLAMP
Jan 08, 2016 13:05
Started to get this when I upgraded my project from Unity 5.1 to 5.3.1. Clearly not fixed in 5.3.0.
DoubleDox
Dec 26, 2015 22:46
Started to get this issue since 5.3
glenwatkinson
Dec 22, 2015 21:09
Also having this issue.
TheAntronach
Dec 22, 2015 15:10
This issue still exists for me in both 5.3 and 5.3.1... so why is it marked as fixed?
BoldBigflank
Dec 18, 2015 23:43
I have this too.