- gen1 recomp anbernic handhelds require a compatible official release asset and supported device configuration.
- Use your legally owned ROM because Gen1 Recomp does not distribute Pokémon Red, Blue, or Yellow game files.
- Test the base build first before adding mods, voxel graphics, or custom control profiles.
- Back up saves and user data before updating the application or changing major settings.
- Match versions for Link Play because different builds or gameplay mods can cause synchronization problems.
Gen1 Recomp on Anbernic Handhelds: What to Expect
Gen1 Recomp is a native Lua and LÖVE2D recreation of Pokémon Red, Blue, and Yellow. It is not a traditional emulator, and it does not transpile the original Game Boy assembly code. The application uses data extracted from a legally owned ROM while providing its own runtime and modern features.
For Anbernic owners, the most important distinction is between a specifically supported handheld target and a device that merely runs a similar operating system. The project information identifies RG34XXSP among its supported targets, while broader Anbernic compatibility depends on the release package, operating system, processor, input layer, and available storage permissions.
Treat each Anbernic model separately. Do not assume that a Linux build for one handheld will work on every RG, XX, or SP device. Confirm the exact model and release asset before transferring files.
| Compatibility Area | What to Check | Recommended Approach |
|---|---|---|
| Device model | Exact Anbernic model and hardware family | Record the full model name before downloading |
| Operating system | Linux-based firmware or Android | Match the official release asset to the active system |
| Game data | Red, Blue, or Yellow ROM from your own copy | Keep a clean backup outside the application folder |
| Controls | D-pad, face buttons, Start, Select, shoulder buttons | Test every binding before starting a long play session |
| Storage | Accessible application and save directories | Use a dedicated folder and preserve backups |
| Mods | Gen1 Recomp-compatible packages | Add one mod at a time after the base build works |
The handheld experience is best approached as a focused portable setup rather than a generic emulator installation. A clean directory, reliable controls, and a tested save backup matter more than visual upgrades during the first launch.
Native Recreation
Gen1 Recomp uses a handwritten Lua and LÖVE2D engine instead of emulating the Game Boy hardware.
Supported Data
Import compatible Pokémon Red, Blue, or Yellow data from a legally owned copy. The project does not provide ROM files.
Portable Controls
Configure movement, confirm, cancel, Start, and Select before adjusting optional shortcuts.
Expandable Setup
Add compatible mods, Save Editor tools, Link Play, or the separate voxel project after testing the unmodded build.
Download and Install on an Anbernic Device
Use the official Gen1 Recomp GitHub repository and its GitHub Releases page as the primary sources for application files. The official project warns that unrelated websites should not be treated as authorized download locations.
The current reference information lists v0.1.69, released on August 4, 2026, with supported targets that include RG34XXSP. Release assets can change, so select the package shown for your exact device or operating system rather than relying on an old filename.
Do not download ROM files, repacked builds, or modified archives from unrelated sites. Use the official repository and keep your own game dump separate from the application package.
Identify the Exact Handheld
Check the model printed on the device, its firmware menu, or the system information screen. Note whether the handheld is using a Linux-based firmware or Android, because the installation method and file permissions differ.
Open the Official Release Page
Review the latest release notes and locate an asset intended for the exact handheld target or its supported operating system. A source-code archive is not the same as a player-ready release package.
Transfer the Complete Build
Copy the full release folder or package to the handheld storage. Preserve its internal libraries, data folders, and executable structure. Do not launch the application directly from inside a compressed ZIP file.
Import Your Game Data
Start Gen1 Recomp and select a clean, legally owned Pokémon Red, Blue, or Yellow ROM when prompted. Choose the matching version and wait for the initial data process to finish.
Test Before Customizing
Reach the title screen, start a temporary game, check audio and controls, and create a test save. Only after this works should you add mods, custom graphics, or a permanent playthrough.
| Installation Stage | Linux-Based Anbernic | Android-Based Anbernic |
|---|---|---|
| Package type | Device-compatible Linux build or supported target package | Official Android APK when provided |
| File transfer | SD card, USB connection, or network transfer | File manager, USB transfer, or Android storage access |
| First launch | May require executable permissions or firmware-specific placement | May require temporary sideloading permission |
| ROM access | Select from accessible storage | Use the Android file picker or granted storage access |
| Main risk | Missing libraries, incorrect folder structure, or permissions | App storage restrictions or data loss during reinstall |
If no release asset clearly identifies your Anbernic model or operating system, do not treat a generic package as guaranteed support. Review the release notes, project Wiki, or official community channels before moving a long-term save.
Controls, Display, and Save Management
Anbernic handhelds are well suited to the original compact control scheme, but the default mapping may not match your preferred layout. Start with movement and menu navigation, then assign shortcuts only after the basic inputs behave correctly.
The original games rely heavily on directional movement, confirm, cancel, Start, and Select. A comfortable layout reduces accidental menu actions and makes long routes, battles, and inventory management easier.
Before beginning a permanent save, verify movement, dialogue confirmation, menu cancellation, Start, Select, audio, screen scaling, and normal save behavior.
| Control Function | Suggested Input Role | Test Location |
|---|---|---|
| Up, Down, Left, Right | D-pad | Opening room and first route |
| Confirm | Primary face button | Dialogue, item selection, battle menu |
| Cancel | Secondary face button | Menus and move selection |
| Start | Dedicated menu button | Main menu and pause behavior |
| Select | Dedicated utility button | Original menu shortcuts |
| Fast-forward | Optional shoulder or hotkey | Low-risk walking or battle test |
For display settings, prioritize readability over maximum effects. Integer or pixel-correct scaling is useful when available because it keeps the original-style image sharp. If a fullscreen mode crops menus or creates unstable behavior, return to windowed or default scaling.
Save data should be treated as a separate asset. Gen1 Recomp stores saves outside the original ROM, and the exact location depends on the device and operating system. On a handheld, identify the active user-data folder before beginning a serious playthrough.
Anbernic First-Launch Checklist:
- Confirm the exact handheld model and operating system
- Use the official Gen1 Recomp release page
- Import a clean legally owned Red, Blue, or Yellow ROM
- Test all core controls and screen settings
- Create and copy a working save backup
| Save Task | Safe Practice | Why It Matters |
|---|---|---|
| First save | Create a test save before customization | Confirms the build can write data |
| Routine backup | Copy the complete save or user-data folder | Protects progress from storage errors |
| Application update | Back up before replacing files | Allows rollback if the new build fails |
| Mod installation | Use a separate backup from the unmodded save | Gameplay mods may alter persistent data |
| Device transfer | Copy saves after closing the application | Reduces the chance of incomplete writes |
Avoid deleting the older installation until the new build loads the ROM and save correctly. On Android-based handhelds, pay special attention to uninstall behavior because app-specific storage may be removed during replacement.
Mods, Voxel Graphics, and Compatibility
Gen1 Recomp includes a built-in Mod Manager, but not every Pokémon modification is compatible. A package made for a conventional emulator, ROM hack, or another recompilation project should not be imported automatically.
The safest workflow is to keep the base game stable, back up the save, and test one package at a time. Cosmetic changes are generally easier to isolate than mods that alter Pokémon data, maps, scripts, battle rules, or progression.
Run the unmodded Gen1 Recomp installation until it reaches the title screen and creates a valid save. This gives you a reliable comparison point when a mod causes a crash or visual problem.
| Mod Category | Typical Impact | Handheld Advice |
|---|---|---|
| Interface or cosmetic | Changes menus, sprites, or presentation | Test after confirming native controls |
| Gameplay changes | Alters rules, encounters, moves, or progression | Use a separate save backup |
| Data or script changes | May affect maps, events, or persistent flags | Verify version and dependencies carefully |
| Voxel graphics | Adds a separate 3D presentation layer | Check performance and camera controls |
| Experimental camera | Changes viewing angle or perspective | Return to default view during troubleshooting |
The DramaticShape Voxel Mod is a separate community project, not a built-in feature of the base recreation. Its documented feature set includes voxelized environments, configurable camera modes, 3D battles, experimental first-person viewing, and optional Pokémon Stadium model support. Use the DramaticShape Voxel Mod repository for its own compatibility notes.
On Anbernic hardware, begin with the standard voxel view rather than experimental camera features. If performance drops, lower render distance, effects, shadows, or other graphics options before changing the control layout.
| Mod Setup Step | Action | Recovery Option |
|---|---|---|
| Prepare | Confirm the mod targets Gen1 Recomp | Remove incompatible archives |
| Import | Use the built-in Mod Manager | Recheck ZIP structure |
| Enable | Activate one package at a time | Disable the newest package |
| Update | Match mod and application versions | Restore the previous profile |
| Troubleshoot | Test the base build without mods | Re-enable packages individually |
Do not distribute copyrighted ROM or model assets with a mod package. Keep optional visual assets separate and follow the project’s stated installation requirements.
Performance, Updates, and Common Fixes
Portable hardware benefits from a conservative configuration. Start with the standard presentation, confirm stable input, and then raise visual settings gradually. This approach makes it easier to identify whether a problem comes from the application, firmware, storage, or a community mod.
The project reference lists Windows, Linux, macOS, Android, iOS, RG34XXSP, and Switch among its recorded running targets. That list should be read as a project-supported target record, not as a guarantee for every Anbernic model.
Install a new release separately when possible. Keep the older build, saves, configuration, and mods until the updated version has passed a clean ROM and save test.
| Symptom | Likely Area | Recommended First Fix |
|---|---|---|
| Application does not start | Incomplete extraction or permissions | Recopy the complete official package |
| ROM is rejected | Wrong version or modified dump | Test a clean Red, Blue, or Yellow ROM |
| Controls feel incorrect | Input mapping | Reset and remap core buttons |
| Menu is cropped | Scaling or fullscreen mode | Use default or windowed display |
| Save is missing | Wrong user-data location | Check the active application-data folder |
| Mod causes a crash | Version or load-order conflict | Disable the newest mod and test base build |
| Voxel view stutters | Graphics workload | Reduce effects, distance, or shadows |
| Android install fails | Sideloading or storage access | Recheck permissions and official APK |
When reporting a bug, include the Anbernic model, firmware or operating system, Gen1 Recomp release, active mods, and repeatable steps. Do not upload copyrighted ROM files. The project’s official GitHub Issues page is the appropriate place to check existing reports and submit technical details.
Q: Can every Anbernic handheld run Gen1 Recomp?
No. The project identifies specific targets, including RG34XXSP, but compatibility depends on the exact model, operating system, release asset, input layer, and storage permissions.
Q: Does Gen1 Recomp include Pokémon Red, Blue, or Yellow ROM files?
No. Gen1 Recomp provides a native recreation and requires game data from a legally owned supported ROM. It does not distribute Nintendo game files.
Q: Should I install mods before testing my Anbernic setup?
No. Confirm that the unmodded build launches, imports the correct ROM, recognizes controls, and creates a working save before adding any mod.
Q: Can I use the DramaticShape Voxel Mod on an Anbernic handheld?
Only when the handheld, Gen1 Recomp release, and voxel mod version are compatible. Treat it as a separate community project and lower visual settings if performance drops.