Modification Utility and File Viewer for classic Resident Evil video games of the Sony PlayStation (1994) (PS1/PSX/PSone) era

• This is an extremely early, complete rewrite, open-source version of "BioClone Redux"
• This application is currently in a prolonged "Viewer/Gameplay" development cycle. Do not expect modification abilities, yet...

• Resident Evil / バイオハザード (August 1995 Prototype)
• Resident Evil / バイオハザード (October 1995 Prototype)
• Resident Evil / バイオハザード (March 1996 Retail)
• Resident Evil 2 / バイオハザード2 (November 1996 Prototype)
• Resident Evil 2 / バイオハザード2 (August 1997 Preview / Trial Edition)
• Resident Evil 2 / バイオハザード2 (January 1998 Retail)
• Resident Evil 3: Nemesis / バイオハザード3 LAST ESCAPE (September 1999 Retail)

PC versions of all listed games are also supported

• Prerendered background and camera sprite mask images must be located in same directory as RDT

• RDT files are comprised of multiple unique data types that construct a playable area. Some games contain unique data that others do not, and others have been expanded upon with each iteration of the original developer's game engine. In this application, data is converted to specification of Resident Evil 2 (retail) and is subject to change as the engine matures

• Refer to the Room Data section for information about this file format

• (1) Support for Resident Evil 3 RDT is only partially implemented and currently inaccessible in app

• Character, Enemy and Weapon animation is fully implemented for all versions of all supported games. Gameplay testing is possible with a XInput compatible gamepad input device. Refer to the Gameplay Testing section for instructions

• (1) The EMS file container itself does not have file pointer indices; they are stored in the game executable. Almost every EMS located throughout all versions of Resident Evil 2 is unique. Support is certainly possible, but not a current priority

• (2) Resident Evil 3 character models are unique due to use of vertex binding methods (unimplemented). Character models with vertex binding will not be correctly represented and will appear disjointed. Some enemy models do not use vertex binding and will be properly represented onscreen. Future support for models with vertex binding is possible but not promised

• (3) Support for import/export of Wavefront is planned, but not a priority. Currently, all 3D modeling data is internally converted to TMD specification. Eventually, all 3D modeling file types will be interchangeable

• Must have naming convention: ROOMXYYZZ (example: ROOM20B10.PNG)

• Must have naming convention: ROOM_XYY_ZZ_MASK (example: ROOM_20B_10_MASK.PNG)

• All supported image formats can be used in the model viewers. Import/Export support is only partially available for the model viewers. All others are planned for the "modification" phase of this application's development cycle

• (1) Each game has a max limit: Resident Evil is 8, Resident Evil 2 (November 1996 Prototype) is 12, Resident Evil 2 is 16 and Resident Evil 3 is 32. In planning for future modification abilities, this app has no limit and will support RDTs that break these limits

• (2) All versions of Resident Evil 1 have camera sprite textures embedded into the RDT. They are not used in either the PC version or this application. There is one PRI per camera, which consists of individual groups of data used to place sprites onscreen to "mask" 3D models behind objects in the prerendered background to create the illusion of a full 3D environment

• (3) Lighting is fully implemented. All versions of Resident Evil 1 supports only three (3) lights per room. All others support three (3) lights per camera.

• (4) Collision data in all versions of Resident Evil 1 and Resident Evil 2 (November 1996 Prototype) is structured different from subsequent games, but function the same. They are converted to Resident Evil 2 (retail) type for upgraded abilities

• (5) Enemy Navigation Mesh is fully parsed and can be viewed. Enemy AI is unimplemented, so this data is not useful yet

• (6) Floor Sound Mesh is fully parsed and can be viewed. Full support is currently unimplemented because audio support is currently unimplemented

• (7) Scripts are loaded and processed in real-time (Resident Evil 2, only). Every game in the series uses different opcodes and bytecode to comprise this data, so support for other games will arrive later. Currently, in Resident Evil 2 rooms, the "player" can interact with nearly all AOT ("ahead of time") objects such as messages, doors, items and some events; full cutscene support is very early in implementation. Some custom (hacked) executables extend the opcode range with custom bytcode and might be supported in future versions of this app (probably via a config file). For now, custom opcodes will most definitely crash the app.

• (8) Item Avatar Textures are unique to Resident Evil 1 RDTs. They are 40 x 30 x 8bpp headerless TIM textures for use in the Inventory of the Status Screen. There is a single avatar texture for every Item Model. These textures are not unique; duplicates can be found in PSX\DATA\ITEM_ALL.PIX -- a container that holds every item avatar available in the entire game

• (9) Camera Scroll Texture is unique to Resident Evil 2 (retail) RDTs. They are 320 x 240 x 16bpp headerless TIM textures for use when the camera scrolls vertically (example: entering the RPD for the first time), and are used only in scripted events

• (10) Item Models are unique to Resident Evil 1 RDTs. Object Models are universal (all games). These 3D models are representations of collectible items. Each game stores a different file type: TMD for Resident Evil, MD1 for Resident Evil 2 and MD2 for Resident Evil 3. Item and Object models can be viewed in the Item editor tab

• (11) Effect Sprite containers hold EFF and TIM which represent 2D sprites, such as fire, broken glass, gore, etc. Resident Evil and Resident Evil 2 have a max capacity of 8, and Resident Evil 3 is 16. Effect Sprites can be viewed in the Effect editor tab

• (12) Soundbank Index and Attribute data differs in each game, but it serves the same purpose. This data is used in conjunction with Floor Mesh Data and the embedded Sony PlayStation Soundbank data (VAB) to produce sound effects, such as footsteps

• (13) Sony PlayStation Soundbank (VAB) contains audio samples, such as footsteps, fire, etc. This data is unused in PC versions; external ADPCM samples within a unique file container (SAP) located in the Common\Sound\Room directory is used instead

• Requires XInput compatible gamepad input device
• Button map assignment via main menu (View -> Controller Map)
• Character Model (EMD/PLD) and Weapon (EMW/PLW) both must be open
• Open Character and Weapon models in the Model tab's file menu
• Model and Weapon game types are not interchangeable. For example, Resident Evil EMW cannot be used with Resident Evil 2 PLD. This limitation is in-place due to different armature specifications per game. More specifically, joint indices are different for each game and do not match each other, creating incompatibilities when attempting to pair animation data between games
• Gameplay Testing is available in both 3D Layout and Model modes. In 3D Layout mode, you may interact with collisions, camera switches, lighting and more in real-time when an RDT is open. In Model mode, you may simply view and test animations

For successful script/event processing, the app needs to know where to find run time assets (not provided)

Setup via the main menu: Main Menu -> Setup -> Data Directory

• a lot :)

• Microsoft Visual Studio 2022+
• Microsoft Direct-X
• Clone the repo
• Install Microsoft.DXSDK.D3DX nuget package into the project
• Build/Link libjpeg-turbo libraries
• Compile

git clone https://github.com/MeganGrass/bioclone-remake.git

Gemini

pmandin

XProger

Dither Matrix

PSX.dev (Discord)

Resident Evil is Copyright © CAPCOM CO., LTD.

Sony PlayStation is Copyright (©) Sony Computer Entertainment Inc.

ImGui is Copyright (©) 2014-2025 Omar Cornut

Direct-X is Copyright (©) 1995-2021 Microsoft Corporation

libjpeg-turbo

libpng

zlib