- gen1 recomp voxel mod adds a separate voxelized 3D presentation to the native Gen1 Recomp recreation.
- Base setup first: Confirm Red, Blue, or Yellow boots correctly before importing visual modifications.
- Safe installation: Use the built-in Mod Manager and match the voxel package to your Gen1 Recomp release.
- Best starting view: Test the standard camera before trying first-person or close-camera features.
- Recovery plan: Back up saves, user data, and the working mod profile before changing graphics settings.
gen1 recomp voxel mod: What It Adds
The gen1 recomp voxel mod refers to the separate DramaticShape Voxel Mod, a community project that runs on top of Gen1 Recomp. It presents the familiar Kanto maps with voxelized 3D geometry instead of the standard tile-focused display. The modification can also add configurable camera views, three-dimensional battle presentation, experimental first-person features, and optional model support.
Gen1 Recomp itself is a native Lua and LÖVE2D recreation. It does not emulate the Game Boy or distribute the original game files. The voxel project is not part of the base application, so install it only after the unmodified program launches successfully with legally obtained Red, Blue, or Yellow game data.
The safest reference points are the Gen1 Recomp GitHub repository, its official Releases page, and the DramaticShape Voxel Mod repository.
Voxel Overworld
Replaces the standard tile presentation with a three-dimensional interpretation of indoor and outdoor Kanto maps.
Camera Modes
Offers different viewpoints, including standard angled views and experimental close or first-person perspectives.
3D Battles
Adds a three-dimensional battle presentation that can be tested separately for wild and trainer encounters.
Optional Models
May support additional model-based features when the required assets and configuration are prepared correctly.
| Feature | Base Gen1 Recomp | DramaticShape Voxel Mod |
|---|---|---|
| Main presentation | Native recreation of the original game structure | Voxelized 3D visual layer |
| Installation | Standalone Gen1 Recomp release | Separate community mod |
| Required game data | Legally owned Red, Blue, or Yellow ROM | Compatible Gen1 Recomp installation |
| Camera options | Standard application controls | Additional camera, zoom, and view settings |
| Battle display | Standard Gen 1 presentation | Optional 3D battle presentation |
Do not describe voxel visuals, first-person views, or optional Stadium-style models as built-in Gen1 Recomp features. They belong to the separate DramaticShape community mod.
Requirements and Compatibility Checks
Before downloading the voxel package, prepare a stable Gen1 Recomp installation. The base application should reach the title screen, recognize your legally owned game data, and create a normal save without other modifications enabled.
Compatibility depends on more than the operating system. Check the voxel mod’s supported Gen1 Recomp release, package format, dependencies, and any version-specific notes in its project repository. A package designed for another recompilation project, emulator, or conventional ROM hack should not be assumed to work.
| Check | What to confirm | Why it matters |
|---|---|---|
| Base release | Gen1 Recomp launches without mods | Establishes a working recovery point |
| Game version | Red, Blue, or Yellow is supported by the installed build | Prevents mismatched game-data imports |
| Mod version | Voxel package supports the current Gen1 Recomp release | Core updates can affect mod systems |
| Archive format | Prepared player package is used when available | Source archives may lack ready-to-use structure |
| Save backup | Current save and user-data folders are copied | Allows recovery after crashes or invalid changes |
| Dependencies | Required framework components are installed first | The main voxel package may rely on them |
Use a separate test save or copied user-data folder for the first voxel installation. This makes it easier to identify whether a problem comes from the renderer, an existing save, or another mod.
Recommended Compatibility Order
- Install or update Gen1 Recomp from the official release page.
- Import a clean, legally owned Red, Blue, or Yellow ROM.
- Boot the unmodified game and create a test save.
- Back up saves, configuration files, and the current mods folder.
- Compare the voxel mod requirements with the installed release.
- Disable unrelated visual or gameplay mods before the first import.
The Gen1 Recomp Wiki is the best place to check current application workflows, while the DramaticShape Voxel Mod repository should be used for mod-specific instructions.
Step-by-Step Installation and First Launch
Follow this sequence to install the voxel layer without replacing the base game files or losing your existing progress.
Confirm the Required Gen1 Recomp Release
Open the official Gen1 Recomp Releases page and read the notes for the version supported by the voxel mod. Download the release asset for your operating system rather than a generic source-code archive. Keep the older working build available until the new profile has been tested.
Boot the Unmodified Application
Launch Gen1 Recomp with no visual or gameplay mods enabled. Import the legally owned Pokémon Red, Blue, or Yellow ROM through the normal setup flow, then verify the title screen, movement, menus, audio, and saving.
Back Up Saves and User Data
Close the application and copy the active save directory, configuration files, and installed-mod data to a separate backup location. Keep the backup outside the installation folder and label it with the release or profile name.
Download the Voxel Package
Obtain the DramaticShape Voxel Mod from its project repository. Prefer a prepared release package intended for players when one is provided. Read the included compatibility notes and leave the archive intact until it is imported.
Import Through Mod Manager
Open Gen1 Recomp’s built-in Mod Manager and select the import or add-mod option. Choose the voxel package, review its detected name and version, and install any required dependencies before enabling the main package.
Restart and Verify the Mod
Restart Gen1 Recomp if requested, load the test save, and enter an indoor or outdoor map. Check map transitions, collision, camera tracking, doors, stairs, and interface visibility before changing advanced settings.
Configure One Feature at a Time
Start with the standard voxel camera, then test 3D battles, performance options, controller bindings, and experimental views separately. This creates a clear troubleshooting path if a setting causes visual errors or instability.
| Installation stage | Recommended action | Avoid |
|---|---|---|
| Before import | Test the unmodified application and make backups | Installing several mods at once |
| Package selection | Use a player-ready archive matching the required release | Using an unrelated source archive |
| Mod Manager | Import dependencies before the main voxel package | Repacking internal files without instructions |
| First test | Load a copied save and inspect basic map behavior | Testing on the only active save |
| Update process | Keep the old working profile until verification | Deleting the previous build immediately |
The installation is ready for customization when the voxel overworld loads, normal movement works, map transitions function, and the game can save and reload without errors.
Camera, Battles, Controls, and Performance
The voxel mod changes how Kanto is displayed, so the best settings depend on map type, hardware, and personal preference. Start with the recommended default preset before increasing visual complexity.
Camera Modes
A standard angled view is usually the best baseline because it preserves map readability while showing the new depth of the voxel environment. Increase rotation or zoom gradually, especially in narrow interiors where walls and objects can obstruct the character.
First-person and close-camera features should be treated as experimental. They can offer a different perspective, but tight maps, scripted scenes, collision boundaries, and precise navigation may be easier to manage with the standard camera.
| Setting area | Starting recommendation | Adjustment use |
|---|---|---|
| View angle | Default or recommended preset | Improve depth while preserving map readability |
| Zoom | Moderate distance | Increase visibility in narrow interiors |
| Rotation | Small changes first | Explore angled views without losing orientation |
| First-person mode | Test only after standard view works | Try an experimental character-focused perspective |
| Battle camera | Default 3D battle view | Compare wild and trainer battle behavior |
| Interface scale | Keep menus readable | Adjust only after scene performance is stable |
Three-Dimensional Battles
Enable 3D battle presentation only after the overworld is stable. Test a wild encounter and a trainer battle separately because camera placement, models, transitions, or effects may behave differently. Confirm that battle menus, dialogue boxes, and target information remain readable.
If battles stutter, reduce expensive visual effects before changing the interface scale. Return to the standard battle view when checking whether a problem is caused by the voxel renderer or by another installed package.
Controls
Review keyboard and controller bindings after enabling the mod. Keep movement, Confirm, Cancel, Start, and Select separate from camera rotation, zoom, and view switching. On handheld devices or Android, test touch and controller input independently.
| Control group | Actions to test | Troubleshooting note |
|---|---|---|
| Game controls | Movement, Confirm, Cancel | Required for normal map and menu navigation |
| Original buttons | Start and Select | Important for classic Game Boy menus |
| Camera controls | Rotate, zoom, switch view | Keep separate from movement inputs |
| Battle controls | Menu selection, target confirmation | Verify readability and input response |
| Controller profile | Gamepad and remapped buttons | Layouts can vary by operating system |
When frame rate drops, lower render distance first, then disable lighting or shadow effects, reduce visual detail, and close other graphics-heavy applications. Test one change at a time.
Troubleshooting and Safe Mod Management
Most problems can be isolated by returning to a minimal profile. Disable the voxel package and confirm that the base Gen1 Recomp application still launches. If the base game works, re-enable the voxel dependencies and main package individually.
Common Problems
| Problem | Likely cause | Recommended fix |
|---|---|---|
| Game will not launch | Damaged package, duplicate mod, or incompatible release | Disable the newest mod and verify the required version |
| Voxel view is missing | Package not enabled or dependency absent | Check Mod Manager status and load order |
| Black or broken visuals | Unsupported renderer setting or conflicting visual mod | Restore default graphics settings and test without other visual mods |
| Map collision feels incorrect | Camera or experimental mode issue | Return to the standard camera and test another map |
| Battle transition crashes | Incompatible 3D battle feature or asset | Disable 3D battles and compare wild and trainer encounters |
| Save fails to load | Invalid edited data or wrong save directory | Restore the latest backup and test without mods |
| Controls stop responding | Binding conflict | Reset camera and game controls, then remap separately |
| Update breaks the profile | Old mod does not support the new release | Check compatibility and reinstall only supported packages |
Recovery Workflow
Before Keeping a Voxel Profile:
- Confirm the unmodified Gen1 Recomp build launches and saves normally
- Back up saves, configuration files, and the complete mods folder
- Verify the voxel package matches the installed Gen1 Recomp release
- Test the overworld, map transitions, menus, and one battle
- Record the working mod order and graphics settings
If the application crashes after an update, install the newer release separately instead of immediately overwriting the working build. Test the new version without mods, import the ROM again only when requested, and then restore compatible packages one at a time.
For a broken save, preserve the failed file for comparison, restore the last known-good backup, and confirm that it loads in an unmodded profile. Do not distribute copyrighted ROMs or model assets while reporting a problem. Provide the operating system, Gen1 Recomp version, voxel mod version, enabled mods, and repeatable steps through the project’s official issue channels.
Keep the original save and working mod profile until the edited or updated setup has loaded, played, and saved normally. A backup is most useful before the problem occurs.
Q: Is the DramaticShape Voxel Mod built into Gen1 Recomp?
No. It is a separate community project that runs on top of Gen1 Recomp. The base application and the voxel package should be tracked and updated independently.
Q: What game versions can I use with the gen1 recomp voxel mod?
Gen1 Recomp supports Pokémon Red, Blue, and Yellow when the legally owned ROM is accepted by the installed release. Always check the voxel package notes for version-specific compatibility.
Q: Should I enable first-person mode immediately?
No. First confirm that the standard voxel overworld, movement, map transitions, and saving work correctly. Then test first-person or close-camera features on a copied save.
Q: What should I do if the voxel mod causes a crash?
Disable the voxel package and confirm that the base application launches. Restore default graphics settings, remove duplicate packages, compare release versions, and re-enable dependencies one at a time.