Search Issue Tracker
Fixed in 5.3.6
Votes
49
Found in
5.3.1p2
Issue ID
761548
Regression
Yes
[MovieTexture] FMOD error when trying to play video using WWW class
Repro steps:
1) Open the project and only scene in it
2) Play - notice that the movie texture and the sound works correctly
3) Notice the errors in the Console: "Error: Cannot create FMOD::Sound instance for resource (null), (An invalid parameter was passed to this function. ) "
Reproduced in: 5.4.0b2; 5.3.1p3; 5.3.0f4
Not reproduced in: 5.2.3p3
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
- No data received in Profiler when connecting to WebGL Player without "Autoconnect Profiler" option enabled
- Screen Space Ambient Occlusion is ignored when toggling "Post Processing" visibility in the Scene window overlay
- “RenderTexture.Create failed: requested size is too large.” errors are thrown and the Inspector window is black when selecting a CubemapArray texture
- Crash on AMDUnityPlugin.DLL in specific built project when using FSR2 upscaler
- RenderObjects does not have any Depth texture bound when Event is set to AfterRenderingPostProcessing
RealWorld
Mar 03, 2016 16:55
Please reopen. This is still broken. In fact its worse
ShoaibGhaffar
Mar 01, 2016 18:06
Not Fixed in 5.3.3
ShoaibGhaffar
Mar 01, 2016 18:06
Not Fixed in 5.3.3
jianmingyong
Mar 01, 2016 16:31
Definitely not fixed in Unity 5.3.3.
juan-jo
Feb 28, 2016 20:16
Not fixed:
It shows the "Cannot create FMOD::Sound instance for resource (null)" error in the editor console, but the build crash at this point:
Receiving unhandled NULL exception
Obtained 29 stack frames.
#0 0x00000100f8cac1 in BaseVideoTexture::InitVideoMemory(int, int)
#1 0x00000100f8b203 in MovieTexture::ReadyToPlay()
(…)
AShim-3D
Feb 26, 2016 15:29
It has not fixed in 5.3.3p1 too.
This causes two errors:
- LoadMoveData got NULL!
- Error: Cannot create FMOD::Sound instance for resource (null), (An invalid parameter was passed to this function. )
IkkewSan
Feb 23, 2016 16:59
It is marked as fixed in Unity 5.3.3.
But it has not fixed in 5.3.3f1. (;_;)
fredmg
Feb 11, 2016 20:05
yes , here Also.
:(
bsawyer
Feb 11, 2016 12:54
Confirming exists in 5.3.2f1.
VISIONSBOX
Feb 10, 2016 09:41
I'm also receiving this error with the 5.3.2f1.