Quest 5.10 is now available. The main update in this release is a refreshed UI for the Editor - it now works much better on high DPI screens, and has new toolbar and menu icons. The embedded Chromium version has been updated to v147. There are also a large number of bug fixes - see the full release notes.
I did say over a year ago in the Quest 5.9 announcement that “bigger changes are coming”, and that bigger change is Quest Viva which I haven’t posted much about here yet. This is a project to finally bring Quest fully cross-platform, with a new Player and Editor that can run everywhere fully offline.
We’ve already got a version of the Player which can run cross-platform in a Docker container, but there is more work to do to get that running under WASM so that any browser can play a Quest game without there needing to be a server component.
I’ve also made a start on a version of the Editor which will also run offline in a browser using WASM.
The ultimate goal is that you’ll be able to create and play Quest games using an offline browser-based web app (or the same thing packaged with Electron etc), which should address a lot of the historic pain points (connection issues, servers going down…). Hopefully should have something to play with in the next few months.
Yep I wouldn’t expect 5.10 to run easily under Wine. I know some people got previous versions working (5.8?) but the architecture has changed since then (Quest is now an x64 app not an x86 one).
I’m not a big fan of electron apps, but screw it, I’ve got 16 gigs of ram in this laptop, I’ll give it a go and return when I have something to say about accessibility. The last version I tried was 5.8, which was… Meh. It was fine with JAWS, but with NVDA (the more popular screen reader of choice, and my own), the results were… Hit and miss.
I’m not sure if it’s just that I’m getting old, but I find the ui font used in the windows desktop app to be incredibly small. This isn’t an issue with most other apps, where one can easily increase the size of the ui font by a point or two, but I cant find any obvious way to do that in Quest 5.10.
It’s a shame, because I’ve been thinking about using Quest to develop something parser based, but half an hour of using the app leaves my eyes feeling strained.