Summary
A VideoClip in Assets/Resources/Video/ plays correctly in the Unity editor, but
is silently missing from builds produced by the game-ci/unity-builder action.
No runtime errors — the video simply never plays.
Environment
- Action:
game-ci/unity-builder@v5
- Unity: 6000.4.6f1
- Target platform: StandaloneWindows64, StandaloneLinux, StandaloneOSX
Reproduction
- Place an
.mp4 in Assets/Resources/Video/
- Load and play it at runtime via
Resources.Load<VideoClip>(), or via PlayOnAwake in the editor
- Works in the editor; produces no video in the CI build
Relevant build log
Start importing Assets/Resources/Video/Tutorial.mp4 using Guid() (VideoClipImporter)
Error: Can't create LinuxVideoMedia, format 0 not supported
What I ruled out
- Disabling Transcode in the VideoClip import settings — no change
- Re-encoding the source with several different codecs — no change
- No errors at runtime, so nothing surfaced until I read the build logs
Question
Is this expected behaviour when importing video assets inside the Linux-based
builder image, or is it a missing codec dependency in the container? Either way,
it might be worth a note in the docs; the failure is silent and cost me two days.
I found a workaround and I'll post it as an answer below.
Summary
A VideoClip in
Assets/Resources/Video/plays correctly in the Unity editor, butis silently missing from builds produced by the
game-ci/unity-builderaction.No runtime errors — the video simply never plays.
Environment
game-ci/unity-builder@v5Reproduction
.mp4inAssets/Resources/Video/Resources.Load<VideoClip>(), or via PlayOnAwake in the editorRelevant build log
Start importing Assets/Resources/Video/Tutorial.mp4 using Guid() (VideoClipImporter)
Error: Can't create LinuxVideoMedia, format 0 not supported
What I ruled out
Question
Is this expected behaviour when importing video assets inside the Linux-based
builder image, or is it a missing codec dependency in the container? Either way,
it might be worth a note in the docs; the failure is silent and cost me two days.
I found a workaround and I'll post it as an answer below.