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
SomeTallGy
Oct 04, 2016 20:51
Same Problem in 5.4.1f1 -- hellooooooo?
GDesmoulins
Sep 23, 2016 07:19
Same problem for me with the 5.4.0f3 version.
Everything was ok with 5.2.3p3
trying to load .mp3 files located in StreamingAssets folder
Please help us God Unity ...
rebelincontrol
Sep 07, 2016 14:08
Regressed in 5.40f3
sunxdc15
Aug 25, 2016 07:18
still have such issue in 5.3.4p4 please reopen it.
sebas86
Jul 25, 2016 14:39
I get similar error after updating from 5.3.5p5 to 3.3.6:
"Cannot create FMOD::Sound instance for resource archive:/CAB-xxx.resource, (File not found. )"
In my case problem was caused by two elements:
- sound clip with enabled streaming,
- unloaded asset bundle after getting sound clip from it.
Changing sound clip settings from "streaming" to "keep compressed in memory" or "decompress on load" solve problems. Also keeping asset bundle in memory as long as sound streamed sound clip is needed also solves problem.
mmoczkowski
Jul 21, 2016 17:26
For the love of god, this is still not fixed. Happens in 5.3.5f1 and 5.4.0f1
nezbo
Jul 13, 2016 13:53
I managed to avoid the issue in my project by delaying the loading to some frames later, so the problem is probably due to something in the engine which is not entirely ready yet at that time.
nezbo
Jul 11, 2016 12:04
And 5.3.5p7
nezbo
Jul 11, 2016 07:14
I am also still experiencing this bug in Unity Pro 5.3.5f1. Please re-open the issue :)
amelootstijn
Jul 08, 2016 11:01
I'm getting this error in Unity 5.3.5p2