Search Issue Tracker

Fixed in 5.3.6



Found in


Issue ID




[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

Comments (63)

  1. 96bfee44a135f3d4f42fd2236bd24237?d=mm


    Mar 19, 2016 07:16

    Receiving the error in 5.4.0b10

  2. Dc841bbf51b93801f984691d36b9a291?d=mm


    Mar 18, 2016 12:30

    Any news on this one? Is it fixed in the 5.4 beta?

  3. 46d9c98f31e18eba56504e1622ca7303?d=mm


    Mar 09, 2016 00:56

    Sorry, forgot to add that I'm using the 32-bit version of 5.3.3f1.

  4. 46d9c98f31e18eba56504e1622ca7303?d=mm


    Mar 09, 2016 00:55

    I'm getting this as well in Unity 5.3.3f1. A clue though: My .ogv files do not have audio tracks, they are purely video. The offending line in my code is:

    segmentMovie[id] =;

    If think what is happening is that the first time the .movie accessor gets called it tries to init some audio data, which isn't present in my movie files, so the fmod is trying to init a null pointer. The game continues on however, and doesn't crash, so this is more of a nuisance message spamming my console log.

  5. Dc841bbf51b93801f984691d36b9a291?d=mm


    Mar 08, 2016 14:42

    I can confirm. This is not fixed in 5.3.3f1.

  6. C23f4641b881ab931c636d59296ca46a?d=mm

    Harrison Dias

    Mar 08, 2016 14:21

    Not Fixed in 5.3.3f1.
    I am still getting the same errors:

    LoadMoveData got NULL!


    Error: Cannot create FMOD::Sound instance for resource (null), (An invalid parameter was passed to this function. )

  7. 03f8cf23b9061783e33f369eec18aa40?d=mm


    Mar 08, 2016 00:33

    Not FIXED in 5.3.3.p2 !!!
    Just a new error: LoadMoveData got NULL!

  8. 48bbb5695fa888e4d97c9531d104bad1?d=mm


    Mar 07, 2016 15:39

    I also received same error using 5.3.2f1 too

  9. 1cb1fd93eafe8024140e17833e178a69?d=mm


    Mar 07, 2016 05:42

    Please reopen this issue, still exists on 5.3.3f1

  10. 21ec4fe40faefee5364c919980071550?d=mm


    Mar 05, 2016 18:28

    Not working in 5.3.3f1

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.