Fixes from the issues reported since 0.21.1: Virtual Desktop no longer holds up the game, no more crash at the end of 2-2 above 60 frames a second, no picture too large for the graphics card's memory, the American release, and crash messages that reach the log.
Fixed, on the PC
- Virtual Desktop no longer holds up the game (#30, #33). Its runtime was handed the graphics queue the game draws with. A picture it held on to kept the game's own work waiting the whole time: 100 ms at times and 500 ms now and then, in every log posted. That showed as a hitch, and on one PC as a game that fell to 30 frames a second while the headset got 88 pictures instead of 120. Where the graphics card has a second queue (NVIDIA's do), the runtime now gets that one. The log's
Headset:line counts the times ending a picture took 50 ms or more. - The crash at the end of 2-2 above 60 frames a second (#23). The soccer robots count how long they stay in each state in the console's frames, and the game turned those into seconds with the length of the current frame. At 90 frames a second their states ended before their animations did, the game's own check failed, and it crashed. They count 1/60 s frames now, whatever the frame rate. On the Quest at 30 frames a second they had waited twice as long as on the console: that is right now too.
- A picture too large for the graphics card's memory (#37). On a card with 8 GB, a picture of 2160x2304 an eye made every frame take seven times as long, for minutes. The picture no longer grows while the card's memory is more than 80% in use. Every 10 seconds the log says how much is used.
- What stopped the emulator now reaches the log (#38). Virtual Desktop's runtime throws and catches errors of its own while it works. The emulator took the first one for a crash ("Unhandled Exception code 0xe06d7363"), and after that the reason for a real stop was lost. Now such an error is a warning with its text, and the reason for a stop is always written. The launcher's window shows it, and says what to do when Windows had to reset the graphics card.
Added
- The American release, CUSA12431 (#35), is taken for the same game, on the PC and on the Quest. It gets the same fixes as the European one wherever its build is one the emulator knows from inside. The console window (or
core.logon the Quest) says so:CUSA12431 in a build known from inside: .... - README-PC-VR.md: how to keep Steam from taking the PS button's chords for itself (#34).
Files
AstroQuest-0.22-Quest3.apk: the app for the Quest 3 (adb install -r; it installs over 0.20 and later and keeps your saves).AstroQuest-0.22-PC-VR-Windows.zip: the PC version. Unzip it into a folder with a short path and startPlay Astro Bot VR.bat.
How to install and play is in the README.