embedding video into Quest 5.9

[vurt834]

I was trying to embed video like I was doing before with 5.8. But, in 5.9 nothing was working. The only way I got it to work was by using a webm file. mp4 and ogv weren't working. here's the code I ended up using, centers the video, no controls, and it loops...ClearScreen command clears it just fine:

Untitled.txt

I added webm to the list of formats to compile into the quest file, like so:

[KVonGit]

Hello.

The desktop player uses the Chromium browser. The list of supported codecs is sort of misleading:

https://www.chromium.org/audio-video/

And it seems OGV support was removed not too long ago: https://chromestatus.com/feature/5158654475239424

I hadn't made it around to testing this yet. OGV definitely works in 5.8. I just double-checked to make sure I wasn't imagining things, haha.

Anyway... they list VP8 and VP9 as video, but that's only for WEBM.

It lists Vorbis and Opus under audio, but they seem to actually only be supported in WEBM files or as standalone audio files.

Also, Chrome will play MP4. CEF is just Chromium, though. So, that kinda sucks.

---

So, as you have found, we are stuck with WEBM in the Windows app.

...and I don't think Safari (iPhone's default browser) supports WEBM, by the way. So, if your game doesn't end up too big to upload to the site due the file size after including video(s), the video(s) might not work at all on mobile for some people.

Due to the max file size on the site and cross-browser limitations, it seems that the best approach is to host the video as mp4 and webm externally, using the webm as a fallback source in the HTML video element (or just put one format on YouTube and link to it).

---

Note

We lost OGV functionality with the 5.9 update, but we did gain MP3 functionality in HTML audio elements, if that's any consolation.

[KVonGit]

First off: any time I read these posts on mobile, I overlook something. I now see that you already had it set to Windows 10. Maybe this will help:

I got it working on Ubuntu.

First (for those of you at home), be sure you've downloaded Quest 5.9's Windows installer to your Downloads directory. Then...

WINEPREFIX="/home/$USER/Games/Quest" winetricks -q windowscodecs gdiplus corefonts speechsdk dotnet48 vb6run d3dcompiler_47 d3dx9 dxvk vcrun2019

WINEPREFIX="/home/$USER/Games/Quest" winecfg -v win10

WINEPREFIX="/home/$USER/Games/Quest" wine ~/Downloads/quest590.exe

WINEPREFIX="/home/$USER/Games/Quest" wine "/home/$USER/Games/Quest/drive_c/Program Files/Quest 5/Quest.exe"

---

Linux Mint 22.1 Cinnamon
wine-9.0 (Ubuntu 9.0~repack~4build3)
winetricks 20240105

[vurt834]

I tried those winetricks. I did atleast get rid of the black part of the main menu, but when opening games, I get this error, no matter what tweaks I've tried

[KVonGit]

I couldn't even get that far on an Arch Linux installation with the default kernel (and wine-v10). In fact, I couldn't even get to the black screen. There was a new error as soon as Quest opened, with an empty log. Wouldn't let me do anything at all.

It works following the same steps on my old Arch install with the LTS kernel on my older laptop. I have to use the 64bit architecture and --force to install speechsdk, but everything works perfectly after that.

On Ubuntu 22, I follow those steps using wine64, and it works fine.

...but I swear the only time I've seen your specific error is when I was trying to run Quest from the actual Windows 7 OS or Wine set to win7. And my winetricks tends to change the win version when installing certain things sometimes without me noticing.

[KVonGit]

Well... Mine's a little different on Windows 7 itself. The editor and everything works fine, but I get this when I try to play anything:

---

On Ubuntu (wine-9.0), it doesn't care if I switch to win7 using winecfg. It works either way.

...but the old Arch laptop (wine-9.2) will throw the same error it does on Windows 7 after changing to win7 using winecfg, and changing it right back to win10 makes it work.

[KVonGit]

You know what? Try installing vcrun2022. I can't try right now, but I bet should have put that instead of vcrun2019. That will cause that error, too, I think.

[vurt834]

I've been working on it extensively, and all the tricks I've done haven't worked...I've tried different engines, different winetricks (including yours), etc. This is on a Mac Silicon mind you, so it could be a different ballgame. I've been working with wineskin winery.

[KVonGit]

I hope you get it running soon. I have three different Linux installations; all three behave differently; and I wish I knew why.

On Ubuntu, I had to install d3dcompiler_47, d3dx9, and dxvk with winetricks to get rid of the black window content, but that stuff is throwing errors when trying to open Quest on the Arch install with the default kernel. So, you might keep an eye on those.

---

Until there is a solid solution:

• Quest 5.9 games will run on 5.8, but:
  • don't use the CurrentDateUTC function in your game
  • MP3 will not work in <audio> elements, but the Play sound Quest script will play mp3 and wav in any version of Quest
  • don't use the "newer" JS stuff, like let or () = > {}
  • the transcript might cause problems, but hopefully not
• Quest 5.8 games will run in 5.9 (of course), but:
  • don't use the GetExternalFileData or SetExternalFileData functions in your game

When Quest was updated to 5.9, CEF was updated from v39 to a current version, and the current version doesn't run on Windows 7 (and this is why quite a few apps all stopped working on Win 7 around that time).

Also, .NET was updated to 4.8, which comes "stock" in Windows 10.

Also also, Win 10 will be euthanized in October, and Win 11 is 64 bit only. So, that's why he made that change in 5.9.

Oh, and I don't know if the file size will be an issue, but we can install docker-compose (or Docker, Docker Desktop, etc) to run the Quest Viva web player from any OS. There are config settings to use our own game files from the local drive. One of the settings allows us to load the ASLX file from the folder, and I wouldn't think file size would be an issue that way. It would be pulling the resources one by one instead of them being included in the .quest archive. I can't remember how all that works, but the Quest Viva site has examples of the config files.

Quest Viva WebPlayer

The best non-Windows approach right now seems to be creating games with 5.8 and either playing from 5.8 or possibly Viva.

[KVonGit]

https://github.com/KVonGit/quest/releases/tag/v5-x86_64

This is a fresh build of the current v5 branch, but I created an x86_64 installer for Wine (and for my Win 10 tablet thing). I didn't make any changes to the code, except for the ISS setup file.

I installed this using a 32 bit architecture on Arch Linux with Wine 10.6 and winetricks 2025-01-02.

WINEARCH=win32 WINEPREFIX="/home/$USER/Games/Quest" winetricks -q windowscodecs gdiplus corefonts vb6run speechsdk

WINEARCH=win32 WINEPREFIX="/home/$USER/Games/Quest" winecfg -v win10

WINEARCH=win32 WINEPREFIX="/home/$USER/Games/Quest" winetricks -q  --force dotnet48

WINEARCH=win32 WINEPREFIX="/home/$USER/Games/Quest" winecfg -v win10

WINEARCH=win32 WINEPREFIX="/home/$USER/Games/Quest" wine ~/Downloads/quest590-x86_64-installer.exe

It will prompt to restart Windows after installing. Just close the session and it should work.

NOTE: This built-in Chromium browser takes a minute to load when you first open a game to play. It will do that every time you close Quest and reopen it, too. It is creating new tmp files for CEF storage each time we first run a game, and closing Quest deletes those tmp files. That is a 5.9 thing, not specific to this mod.