- gen1 recomp modernizes Pokémon Red, Blue, and Yellow with configurable visual enhancements.
- Supported game files should come from a ROM dump of a cartridge you legally own.
- Basic setup requires the recomp application, a compatible ROM, and an optional mod package.
- 3D presentation can be adjusted through Voxil settings, battle options, zoom, and environment fill.
- Troubleshooting usually starts with checking the game version, file type, mod status, and release compatibility.
What gen1 recomp Does
gen1 recomp is a fan-made project that presents the original Pokémon Red, Blue, and Yellow experience through a modern recompilation and modding framework. The core workflow is straightforward: select the matching game version, import a compatible ROM, add optional visual mods, and configure the presentation from inside the application.
The project is best understood as a flexible presentation layer for Gen I Pokémon, rather than a new Pokémon title. Your selected Red, Blue, or Yellow game file remains important because the application uses it as the foundation for the experience.
Start with the unmodified game first. Confirm that the base ROM loads correctly before adding visual packages, because this separates file problems from mod configuration problems.
Red Version
Use the R tab when importing a legally dumped Pokémon Red ROM.
Blue Version
Use the B tab for a compatible Pokémon Blue ROM and keep the version selection consistent.
Yellow Version
Use the Y tab for Pokémon Yellow when the release supports that game version.
Visual Mods
Optional packages can add voxel environments, lighting changes, battle presentation, and extra display controls.
The available visual style depends on the mod package and the release version you install. A Voxil-style package can replace the flat presentation with three-dimensional environments, configurable lighting, and additional options such as curved-world effects or time-of-day changes.
| Component | Purpose | Required |
|---|---|---|
| Recomp application | Loads and runs the selected Gen I game file | Yes |
| Compatible ROM dump | Provides the original game data | Yes |
| Visual mod ZIP | Adds optional 3D or presentation features | No |
| Device-compatible release | Matches the operating system or hardware | Yes |
| In-game save | Stores configuration changes and progress | Recommended |
The application may expose different settings as development continues. Treat the release notes and project community channels as the final reference for newly added options, compatibility changes, or experimental features.
Preparation and Legal File Handling
Before opening the application, prepare the files and storage locations you will use. The cleanest setup keeps the base ROM and optional mod ZIP in separate, clearly named folders. This makes it easier to identify the correct file when the import screen opens.
For legal preservation, use a ROM dump created from a Pokémon cartridge you own or another method permitted in your jurisdiction. Do not redistribute ROM files, share copyrighted game data, or download files from unverified sources. The recomp application and a mod package do not replace the need to obtain the original game data lawfully.
Only use game files you are legally entitled to use. Avoid downloading bundled ROM packages, and never assume that a file labeled “Red,” “Blue,” or “Yellow” is authentic or compatible.
Use the following preparation table before installation:
| Preparation Item | Recommended Practice | Why It Matters |
|---|---|---|
| Application release | Choose the build that matches your device | Prevents launch and installation errors |
| ROM dump | Keep one clean, unpatched copy | Simplifies troubleshooting |
| File naming | Use clear names such as Pokemon-Red-Clean | Reduces version-selection mistakes |
| Mod archive | Keep the original ZIP unchanged | Allows a clean re-import |
| Storage | Use a folder with easy file access | Makes importing faster |
| Backup | Copy saves and configuration files when possible | Protects progress during testing |
Check the release information before installing. A package built for one operating system or architecture may not function on another. The reference setup demonstrates a handheld Android device, but the exact installation process can differ on PC, mobile, or other supported hardware.
Choose a Compatible Release
Open the project’s official release page and select the latest package that matches your device. Read the release notes for supported systems, known limitations, and required companion files.
Prepare Your Legal ROM Dump
Locate your personally created Pokémon Red, Blue, or Yellow ROM dump. Keep the file unmodified for the first launch and confirm which version it represents.
Install the Application
Install or launch the recomp application using the normal process for your device. If your operating system blocks installation, verify the file source and security settings before proceeding.
Organize Optional Mods
Store the compatible visual mod ZIP in an easy-to-find folder. Do not extract or rename the archive unless the project documentation specifically instructs you to do so.
A clean preparation routine prevents several common mistakes. Importing a Blue ROM through the Red tab, selecting an incompatible release, or extracting a package that expects to remain compressed can all produce confusing results.
Step-by-Step ROM and Mod Setup
Once the application is ready, complete the base game setup before activating the visual layer. The menu names may change between builds, but the workflow generally follows the same sequence.
Import the base ROM first, launch it once, then add the visual mod. This staged approach gives you a reliable checkpoint before changing the presentation.
Select the Game Version
Open the Red, Blue, or Yellow tab that matches your ROM dump. Confirm the selection carefully before using the import command.
Import the ROM
Choose the import ROM option, open your file browser, and select the clean ROM dump. Wait for the application to finish processing the file.
Test the Base Game
Launch the imported game and confirm that the title screen, opening sequence, and basic controls work correctly. Save once if the application requires an in-game save before additional options appear.
Open the Mods Menu
Return to the application’s main interface and open the mods section. Look for the command used to import a mod ZIP.
Import and Activate the Visual Package
Select the compatible Voxil or other supported visual mod archive. After import, verify that the package is listed and active before returning to the selected game tab.
Use this process table as a quick reference:
| Stage | Menu or Action | Expected Result |
|---|---|---|
| Version selection | Red, Blue, or Yellow tab | Matching game profile is active |
| Base import | Import ROM | ROM appears in the selected profile |
| First launch | Play the base game | Game reaches its opening content |
| Mod import | Mods, then import mod ZIP | Visual package appears in the mod list |
| Activation | Enable the imported package | Mod status shows as active |
| Final launch | Return to the game tab and play | Enhanced presentation loads |
If the mod does not appear immediately, close and reopen the application before changing files. Some builds may refresh their package list only after restarting or returning to the main menu.
Do not import several experimental packages at once. Test one visual mod, record the result, and then add another only if the project supports stacking. Conflicting packages can overwrite shared assets or produce missing textures, unusual colors, or startup failures.
Visual Settings and Recommended Tuning
After the visual package loads, open the in-game pause menu and locate the options area. The reference configuration path includes an advanced color mode, Voxil intensity, 3D battles, back sprites, zoom, and environment fill.
The ideal settings depend on your display, hardware, and preferred balance between nostalgia and modernization. Begin with moderate values instead of immediately selecting every high-impact effect.
Use advanced colors, a moderate Voxil level, standard battle presentation, and a comfortable zoom. Add curved-world effects and dynamic time-of-day lighting after confirming stable performance.
| Setting | Lower or Standard Choice | Higher or Experimental Choice |
|---|---|---|
| Color mode | Advanced colors enabled | Adjust only after checking readability |
| Voxil level | Moderate visual conversion | Full conversion for a stronger 3D look |
| Battle display | Standard presentation | 3D battles and alternate sprite options |
| Zoom | Comfortable view of the playfield | Larger scale with less surrounding space |
| Void fill | Trees, water, or empty space | Choose based on visual preference |
| V-curve | Off during initial testing | Enable for a curved environment effect |
| Time of day | Fixed daytime setting | Real-time sync or timed cycling |
The Voxil level controls how strongly the visual package changes the original presentation. A full setting may create the most dramatic difference, while a lower setting can preserve more of the classic appearance.
Battle options should be tested separately from overworld settings. If the overworld looks correct but battles appear unusual, disable 3D battles or alternate back sprites temporarily. This helps identify whether the issue comes from a battle-specific feature.
Lighting options can substantially change the atmosphere. A fixed time of day is easier to evaluate, while real-time synchronization or timed cycling offers a more dynamic presentation. Keep in mind that lighting changes may make certain areas look darker or less readable.
Classic-First
Advanced colors, low Voxil strength, standard battles, and no curved-world effect.
Balanced 3D
Moderate Voxil strength, optional 3D battles, comfortable zoom, and a fixed daytime setting.
Immersive Display
Full visual conversion, V-curve, dynamic lighting, and environment fill selected to match the scene.
Make one change at a time and test movement, menus, battles, saving, and loading after each major adjustment. This creates a dependable configuration rather than a collection of untracked tweaks.
Troubleshooting and Progress Checklist
Most setup issues can be narrowed down by returning to the last working state. If the base ROM launched successfully before the mod was imported, the visual package or its compatibility is the most likely area to inspect. If the base game never launched, focus on the release, ROM version, and import process first.
Do not replace several files at the same time. Restore the clean ROM, test it, and then reinstall one compatible mod package so each change has a clear cause.
| Symptom | Likely Cause | First Action |
|---|---|---|
| Application will not install | Incorrect device release | Download the matching build |
| ROM is not recognized | Wrong file, unsupported format, or bad dump | Recheck the dump and file extension |
| Game loads without 3D visuals | Mod not imported or activated | Open Mods and verify its status |
| Text or colors look incorrect | Advanced color configuration issue | Reset colors and test standard settings |
| Battle view behaves strangely | 3D battle or sprite option conflict | Disable battle enhancements temporarily |
| Performance drops | High visual settings or device limits | Lower Voxil level, zoom, or lighting effects |
| Progress disappears | Save was not created or backed up | Save in-game and preserve working files |
Use this checklist after completing the installation:
Setup Milestones:
- Install the release that matches your device
- Confirm the ROM dump belongs to Red, Blue, or Yellow
- Launch the clean base game before adding visual mods
- Import and activate one compatible mod ZIP
- Save in-game after applying configuration changes
For persistent problems, compare your setup against the project’s current release notes or community support channels. Include the device type, application version, selected game version, mod name, and exact symptom. Avoid posting copyrighted ROM files or private save data when requesting help.
The safest recovery path is simple:
- Close the application.
- Back up any working save or configuration files.
- Remove the optional visual package from the active list.
- Relaunch the clean ROM.
- Re-import the mod only after the base game works again.
- Reapply settings gradually.
This method preserves a known-good baseline and reduces the chance of confusing a file problem with a graphics setting.
gen1 recomp FAQ
Q: What games can gen1 recomp support?
The setup workflow is organized around Pokémon Red, Blue, and Yellow. Select the tab that matches your legally created ROM dump, and check the current release notes for version-specific support.
Q: Do I need a visual mod to use gen1 recomp?
No. The base recomp application can be tested with the imported game file first. A Voxil or similar package is optional and adds enhanced presentation features.
Q: Why does my mod appear imported but not change the game?
Open the Mods menu and confirm that the package is active. If it is enabled but has no visible effect, restart the application, verify compatibility, and test a lower-complexity configuration.
Q: What should I do if 3D battles look incorrect?
Disable 3D battles and alternate back sprites, then launch the game again. If the standard battle view works, re-enable one battle option at a time to identify the conflicting setting.
Keep a clean ROM, a working save, and a known-good configuration as your baseline. That makes future mod updates easier to test and reverse.