Whenever I call play on a mediaplayer asset through blueprint (running the editor from VS2013), I get the following in my console log:
The thread 0x4200 has exited with code 1 (0x1).
The thread ID isn’t always 0x4200, of course. But this message appears every single time I call Play on the MediaPlayer asset through blueprint, and whenever the movie finishes a loop and starts over. The error does not crash the game immediately, but if we let the mediaplayer play for too long, it will crash the game with an error pointing to some code in FOutputDevice.
Is the MediaPlayer framework supposed to have these bad exit codes? If not, how can it be fixed?
The media player is still considered an experimental feature and is currently undergoing constant improvements and edits. The documentation for this feature can be found via the links provided below. Hopefully you can pull some additional information from these sources that will give you a hint as to the bad exit codes.
Media Player Asset Framework
Media Framework Forums Thread
Let me know if you have browsed through these sources and were still unable to determine a viable solution/workaround.
Thanks so much for the quick response! I’ve pored over the docs and all available resources on the web about MediaPlayer/MediaFramework, to no avail. Does this bug happen on any other projects?
There are a few others who are reporting this issue happening as well. They leave a video playing for a while until it eventually causes a crash. As you can imagine, this issue can be hard to reproduce, so if you have a test asset or some reproducible steps so I can get this to occur in a fairly empty project, that would be helpful.
As for the crash, that is probably a different issue. Could you post a callstack for it? The crash is most likely an assertion that is caught in FOutputDevice.