ScummVM 2.7.1: "Stan's previously broken swords" sees the light

From the original news post:

A little while has passed since the release of 2.7.0, and we are now excited to present you with the bugfix release 2.7.1.

We have included a significant amount of fixes and small improvements, in particular:

• Added ScummVM Log file viewer, so you can easily report the problems on platforms with limited file access, e.g. Android, iOS or even modern Windows.
• Fixed the shader-based scaler loading on some platforms.
• Added multiple improvements to AGI, AGS, Cryomni3D and 12 more engines.

We also improved the detection of Broken Sword 1 & Broken Sword 2, so more original versions get properly detected. Thank you to those who submitted bug reports about this, and if you still locate a version that is not recognised, please report it to us (beware that the frankenstein versions that are floating around the internet will not be accepted, only those copied from the original media).

For the full and comprehensive list of notable changes, please refer to the Release Notes.

If you are as excited about the release as we are, you can share our joy by downloading it from our downloads page. If you are using Windows, macOS, or either of the Ubuntu Snap or Flatpack packages, the autoupdater will pick up the ScummVM 2.7.1 release automatically. For our Android app users, the update will be available on the Play Store.

Thank you very much for your continued support. Enjoy!

Nice work Cameron!

And it’s always a pleasure to see the download icon for RISC OS on the original website :)

The same issue that appeared under version 2.7.0 has returned with this later release:-

https://www.riscosopen.org/forum/forums/1/topics/17753#posts-138x

Broken Sword 2 crashes with a memory allocation error after the initial cutscene.

Reverting to ScummVM 2.7.0, fixes the problem.

I’m running ScummVM on a Raspberry Pi 3 Model B+, with the latest version of RISC OS Pi.

Broken Sword 2 crashes with a memory allocation error after the initial cutscene.

This seems like it might be an issue with Aemulor. Make sure it’s not running when you start ScummVM.

If that doesn’t solve it, could open an issue on the bug tracker so that it can be investigated further?