Android Adventure Rendering Issue
- Dominant language
- Java
- Stars
- 2.7k
- Forks
- 1.1k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 163
Description
**The Bug**
I have experienced an odd rendering issue that looks like corrupt memory or jumbled asset references. The game doesn't start this way, but is normal for a time and eventually looks as imaged below. A restart of the app seems to help reset whatever causes the issue... for a time. I hadn't experienced this before until the forge-android-2.0.15-SNAPSHOT-08.22 version was issued.
**To Reproduce**
Unfortunately, I haven't found a truly repeatable series of steps.
Best I can estimate is normal play involving overland travel to a few towns, perusing each card there, then battling roaming enemies until visiting the next town. It's usually under 4 town visits in this pattern that I see it.
**Expected Behavior**
The maps, towns, and cards render accurately.
**Screenshots**
**Smartphone**
- Device: Samsung Galaxy S23
- OS: Android 16
- Current App Version: forge-android-2.0.15-SNAPSHOT-08.24
**Additional context**
None at this time.
Contributor guide
Research direction
Start by reproducing the issue on a Samsung Galaxy S23 or comparable Android device using forge-android-2.0.15-SNAPSHOT-08.24, following the described town, card, travel, and battle sequence. Compare the screenshots with the in-game maps, towns, and cards; done means rendering remains accurate during normal play without requiring an app restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- game-dev, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100