Skip to content

Crash Twinsanity Android – test build (Mali)

Latest

Choose a tag to compare

@JoseXD2 JoseXD2 released this 30 Oct 12:09
· 2 commits to android since this release

Temporary build for testing on phones with a Mali GPU (MediaTek, Exynos, Tensor).
Tested so far only on the Poco X7 Pro (Dimensity 8400, Mali-G720).

What's new

  • Vulkan renderer (optional): Options > Display > Renderer > Vulkan. Takes effect the next time you open the game.
    Needs a Vulkan 1.3 driver; if the device doesn't support it, the game falls back to OpenGL on its own.
  • Automatic settings: on first launch the game picks the resolution, renderer and filters for your device.
    To redo it: Options > Display > "best settings for this device".
  • Visible game folder: CrashTwinsanity on the phone's storage (accept "all files access" when asked).
    Settings, saves and logs go there. If you decline, they stay in Android/data/org.twinsanity.native/files.
  • Touch controls now show PlayStation button icons in menus and tutorials.
  • Fixed an FPS drop with Vulkan (the screen was being recreated every frame).

How to install

  1. Install the APK (allow unknown sources).
  2. Pick your own PAL disc image (SLES-52568) in the launcher.

Reporting bugs
Please open an issue at https://github.com/JoseXD2/Crash-Twinsanity-Android/issues and include:

  • Your phone model and chip (e.g. Poco X7 Pro, Dimensity 8400)
  • Renderer (OpenGL or Vulkan) and resolution (1x-4x)
  • What happened and where in the game (a screenshot or video helps)
  • The log files: log.txt and drops.txt from the CrashTwinsanity folder
    (play the problem part for about 2 minutes, close the game, then attach both files to the issue)
    One issue per problem, please. Check the existing issues first in case it's already reported.

If it crashes on launch

  • If the game closes on launch with Vulkan, the next launch switches back to OpenGL automatically.
    To force OpenGL: create an empty file named force_opengl.txt in the CrashTwinsanity folder.
  • Attach log.txt and log.previous.txt to the issue (the second one is the run that crashed).

Known issues

  • At 4x some heavy scenes still drop below 60 fps; 3x is recommended.
  • Leaving and returning to the game with Vulkan hasn't been tested on every device yet.
  • Phones with Adreno (Snapdragon) GPUs are still under performance investigation.