FEX-Emu / FEX-Emu/FEX

Angels of Death : No access to memory location

Open
#5,652 3 comments 0 reactions 0 assignees View on GitHub
android-wastelands Game related
Dominant language
C++
Stars
8k
Forks
351
Avg merge
12h 31m
Merged PRs (30d)
102

Description

**What Game**
Angels of Death
https://store.steampowered.com/app/537110/Angels_of_Death/

**Describe the bug**
When starting the game,the Unity based launcher appears, when starting one of the chapters, this launcher then starts the actual Game.exe of the selected chapter (this Game.exe runs the RPG Maker Vx Ace engine.
When the Game.exe starts, it crashes displaying the error No access to memory location.
I was able to confirm the issue is emulator related as switching to Box64 makes the game work.

**To Reproduce**
Steps to reproduce the behavior:
1. Launch the game
2. Select a chapter from the launcher
3. The launcher starts the chapter's Game.exe
4. No access to memory location error

**Expected behavior**
The game should start

**Screenshots and Video**
Here is the error produced by FEX
Image

Here is the game running properly just by switching to Box64
Image

**System information:**
- OS: Android 16 (HyperOS 3.0.301.0
- CPU/SoC: Mediatek Dimensity 7025
- Video driver version: running dxvk with SurfaceFlinger
- RootFS used: Bionic on GameNative
- FEX version: any
- Thunks Enabled: Unknown

**Additional context**
- Is this an x86 or x86-64 game: x86
- Does this reproduce on AArch64 with Radeon/Intel/Nvidia: Untested
- Is this a Vulkan game: no

This game is running on the RPG Maker VX Ace engine, as such this issue is likely to affect all games using this engine

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the crash with Angels of Death's RPG Maker VX Ace Game.exe on FEX using the reported Android and Bionic setup, then compare the result with Box64. Investigate the FEX failure around the game's launch path; done means the chapter starts without the memory-access error and the behavior is verified against the reproduction steps.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.