Is CubeEvil4-ios free?

Check its license. It has its own license: read it before using it for work.

Is CubeEvil4-ios still maintained?

Yes, active. Last change yesterday.

Can I trust CubeEvil4-ios?

New, little track record. 0 stars, 1 months old. Look at the code and the owner before running it.

CubeEvil4 - native Android port of the Resident Evil 4 GameCube prototype (G4BE08 Nov 2004 debug build), with controller support and OpenGL ES 3 / Vulkan (experimental).

Shell scripts

Before you start

Is it free?: Check its licenseIt has its own license: read it before using it for work.
Still maintained?: Yes, activeLast change yesterday.
Can I trust it?: New, little track record0 stars, 1 months old. Look at the code and the owner before running it.

Contributing

The tree is complete: every unit compiles to the original bytes. Work now is on readability (names, comments, notes) and on tooling. The one rule that covers everything: the bytes do not change.

Build

Follow "Building" in README.md. You need the native SN GCC (built once from SN's GPL source drop) and your own images of the debug discs in orig/G4BE08/. python3 configure.py && ninja builds and verifies. After that, run ninja only; it reruns configure.py itself when a config file changes.

Verify

Three checks. A change is done when all three pass on a clean rebuild.

Byte identity of the binaries:
```
find build/G4BE08 -path '*/obj/*' -prune -o -name '*.o' -print | xargs rm -f
ninja
build/tools/dtk shasum -c config/G4BE08/build.sha1
```
Every line must be OK; the number of lines is wc -l < config/G4BE08/build.sha1 (one per binary your discs provide). The clean rebuild matters: the ProDG compile rule has no dependency file, so an incremental ninja after a header edit can leave stale objects in place.
One unit, while you work on it: python3 tools/bytecmp.py <mod>/<unit> must say IDENTICAL (game/item, em10/em10, lib/adx_amp). python3 tools/fdiff.py <mod>/<unit> <symbol> shows the side-by-side for one function when it does not.
No instruction from an asm template: python3 tools/asmcheck.py --all must report the same total and the same per-unit hits as before your change (the hardware kernels listed at the end of README.md, "What matching means here"). A single unit: python3 tools/asmcheck.py <mod>/<unit>.

Working on a unit

docs/matching.md has the workflow: "Workflow for one unit (game/foo)" for the DOL, "Workflow for one module unit" under "REL modules" for a REL, and "Conventions" for the rules the tree follows. The "Lever catalogue" maps a byte difference to the compiler mechanism behind it and to the source shape that reproduces it. Read it before changing a function's body; most differences you can produce by reformulating C have a known cause and a known non-asm fix.

tools/research/kit/variant.sh <unit> <variant-src> [FUNC] compiles a variant of one unit and judges it without touching build/ (about a second per variant).

Rules

Bytes never change. Not for a rename, not for a comment, not for a refactor. The clean rebuild and dtk shasum are the judge; bytecmp.py IDENTICAL per unit is the working check.
No asm that emits an instruction. The only inline assembly allowed is what the vendor also had to write in assembly (paired-single, GQR, cache, SPR, the exception handler) and the codeless MWCC pins. Every other register or schedule difference is steered from C, tagged // COMPILER-DIFF: <n> with the mechanism, and the tag's mechanism is written up in docs/matching.md or docs/research/. asmcheck.py enforces it. No .s bodies for functions the vendor wrote in C.
Names. docs/naming.md says where every class of name comes from. Vendor names (from the symbol files or the PS2 debug symbols) keep the vendor's spelling. New names follow the surrounding struct. Placeholders xNN/pad_NN are renamed only with evidence (below).
Constants. A magic number at a typed call site or in a flag test is spelled with the PS2 enum (docs/naming.md, "Structs, fields, enums") and a pG flag bit with the XxxFlagChk/On/Off(pG, NAME) macros of include/global.h. Do not introduce a #define or a local enum for a value the PS2 dump names; do not rename an imported enumerator.
Plain member stores. pG->x = v, pPL->pos.y = f, work->field = p. The compiler patch (docs/matching.md, "Compiler") reproduces the vendor's pointer reloads from that form. Do not reintroduce reference-view setters (U32Set, FSet, PSet, ...), struct views of a global pointer (pGS) or one-member XxxWorkPtr wrappers; the few BitOn/BitOff16/U16Set helpers that remain in global.h are register-choice levers, not aliasing workarounds.
#line directives and // COMPILER-DIFF: tags stay where they are. Both are load-bearing; docs/naming.md explains each.
Notes. Per-unit observations go in docs/unit-notes.md; a compiler mechanism you worked out, with the evidence, goes in docs/research/ (one ### section, so the lever catalogue can cite it by title); the conventions and the catalogue live in docs/matching.md. Source comments say what the code does and, at a tag, which mechanism it steers; the long argument goes in the docs.
Formatting. New game code follows .clang-format (4-space indent, function brace on its own line, T* x, 110 columns). Do not run the formatter over existing files: a whitespace-only diff across half a million lines hides real changes and gains nothing. The vendor-style src/lib/ sources (tabs) stay as they are.
Commit messages. One line, factual, present or past tense, what changed and that bytes are unchanged when that is the point: em10: name the Em10Work motion tables from the PS2 symbols (bytes unchanged). No trailers, no signatures.

Proposing a rename

Open an issue with the "Struct or field name" template or send a PR. Either way the rename needs evidence, and the class of evidence is stated:

PS2 debug symbols: python3 tools/ps2sym.py --struct <Name> shows the field aligned to a PS2 field with its confidence. Confidence 1.00 with a name match on the neighbours is enough on its own. Lower confidence needs a second argument (a use site whose meaning agrees).
Usage: the function(s) that read and write the field, what they do with it, and why that fixes the meaning. Quote the file and function, not line numbers (they move). The new name follows the surrounding struct's spelling. Say in the field's line comment which use the name was taken from.
Another vendor artefact (a debug menu string, a format string, a file format spec): quote it.

A rename PR changes the declaration and its use sites, nothing else in those files, and passes the clean rebuild with every OK. The rename tool (ps2sym.py --apply, --fix-errors) follows the compiler's error list rather than a text search; do the same, or check every hit by hand. A name that also appears in a mangled symbol (config/G4BE08/sym_map.tsv) cannot change: the link would fail.

Pull requests

One topic per PR (a rename set, a doc, a tool fix).
The description states what changed and how it was verified. For a source change: the clean rebuild command above, every line OK, and asmcheck.py --all unchanged.
No generated files, no build/, no orig/.

You need

An Android device with Android 6.0 or later, OpenGL ES 3.0 and a 32- or 64-bit ARM processor (details and recommendations: Requirements).
A game controller (built in, USB or Bluetooth) or the touch screen: the touch controls appear on their own when no controller is connected, and after a tap on the screen (app menu → Touch Controls: Auto, Force or Suppress).
Your own disc images (ISO, GCM or RVZ) of both discs of the GameCube debug build from November 25, 2004 (G4BE08), of the European retail release (G4BP08), of the US retail release (G4BE08) or of the Japanese retail release (G4BJ08, also the Korean fan translation), and enough free storage to import them. Both discs must be of the same release.

First start

Install the APK and open CubeEvil4.
Choose Import Disc 1 and Import Disc 2 and pick the image files. The game starts only once both discs are imported. The import checks every file against the original disc and reports a damaged image right away.
Choose Start game. If your controller's face buttons are labelled the other way round, tick "Swap A/B and X/Y" on the start screen.

SELECT button

Press SELECT (with touch controls: MENU): the app menu, in your phone's language where there is a translation (English otherwise; Arabic, Chinese (simplified), French, German, Hindi, Indonesian, Italian, Portuguese, Russian and Spanish so far; on Android 13 and later also per app under Settings → Apps → CubeEvil4 → Language); with the European discs also the game language (a change restarts the game); graphics (resolution Dynamic or 1×–4× in half steps, anti-aliasing, texture filter, picture 4:3 (GC), 4:3, 16:9 or Stretched, depth of field, FPS display, 60 FPS (experimental), Force Performance: Default or Use performance cores, Potato mode: weather and special effects off), sound (music and sound effects volume), controls (touch controls Auto, Force or Suppress, button style RE or GC; comfort controls: Alternate Controls, gyro aiming with its sensitivity and inversion, knife by swipe, Latch L and R, Latch B, Auto aim, Always run; Controller Configuration), cheats (infinite health, infinite ammo, one-hit kill, a fully upgraded Killer7, the attaché case L, +1,000,000 PTAS), memory card (export and import saves as .gci for Dolphin and the GameCube) and the error log (send or save a report; R3 = graphics capture). B returns to the game.
Hold SELECT for a second (debug discs only): the game's own debug menu (use with care, see Status: some of its options can break the game in ways the port has nothing to do with).

Buttons

| Controller | GameCube | In the game | Alternate Controls | |---|---|---|---| | A, B, X, Y | A, B, X, Y | by their labels | A, B as before; X Ashley; Y map | | Left stick | Control stick | move | move | | Right stick | C stick | | aim while L1 or L2 is held | | D-pad | D-pad | | as before | | START | START | | as before | | R2 | R | ready weapon | fire, or slash with the knife ready | | L2 | L | knife | ready weapon (aim) | | R1 | Z | map | inventory (weapons and recovery) | | L1 | – | | ready the knife | | SELECT | – | app menu (hold: debug menu, debug discs only) | as before | | R3 | – | graphics capture for error reports (only when "R3 = Graphics capture" is on) | as before |

Controller Configuration (app menu → Controls, with a controller connected): X, Y, L1, R1, L3 and R3 can each take any function or none; A, B, L2, R2, START, SELECT and the D-pad keep theirs, so the game's button prompts and menus always match. Giving Ashley, the inventory or the map to another button swaps the two buttons. With Alternate Controls on, their own layout applies.

Touch controls

On screen: A, B, X, Y, Z, L, R, START, MENU (= SELECT), the D-pad, a move stick and a look zone (the C stick). App menu → Touch Controls: Auto (shown without a controller; a tap on the screen shows them, a button hides them), Force (always shown) or Suppress (hidden while a controller is connected). In the inventory you can tap items, files and the map, and swipe left or right to change the tab. When a quick-time prompt flashes up (L+R, A+B, mash A …), a tap on it (or anywhere on the picture) presses its buttons; tap again and again to mash. The editor (gear) can add an R3 button (graphics capture for error reports, as on a controller). Button style (app menu → Controls → Button style, or the style button in the editor): RE (the default: a symbol for what each button does, in dark brown and gold) or GC (the letters in the GameCube's colours, as before); the switch takes effect at once and keeps your layout.

Comfort controls (app menu → Controls)

Alternate Controls: the second layout of the table above.
Gyro aiming: turning the device left, right, up or down moves the aim while you aim a gun, look through a scope or aim the harpoon i

…

Contact

alexbatistaribeiro777-cpu/CubeEvil4-ios

Before you start

Not sure yet

Start here

Development setup: `CONTRIBUTING.md`

Contributing

Build

Verify

Working on a unit

Rules

Proposing a rename

Pull requests

1 steps on macOS

Clone the repository

From the README: How to use?

Did you get it running?

Still stuck? Get a written guide

Not sure yet

Start here

Development setup: CONTRIBUTING.md

Contributing

Build

Verify

Working on a unit

Rules

Proposing a rename

Pull requests

1 steps on macOS

Clone the repository

From the README: How to use?

Did you get it running?

Still stuck? Get a written guide

Development setup: `CONTRIBUTING.md`