# Alien vs Predator Atari Jaguar Port Reaches v1.0.0

> Native PC port of the 1994 Atari Jaguar classic Alien vs Predator hits version 1.0.0 with local multiplayer and bots.

- Published: 2026-11-12T08:34:39Z
- Score: 8/10
- Tags: port, pc
- Port / platforms: Other -> PC (Windows), Linux / Steam Deck (Port)
- Web page: https://emu-radar.customfw.xyz/news/alien-vs-predator-jaguar-pc-port-v100/
- Sources: https://github.com/Joshua-1248/Alien-V.S.-Predator-Atari-Jaguar-PC-Port

Developer Joshua-1248 has released version 1.0.0 of [Alien-V.S.-Predator-Atari-Jaguar-PC-Port](https://github.com/Joshua-1248/Alien-V.S.-Predator-Atari-Jaguar-PC-Port), a native PC port of the 1994 Atari Jaguar classic Alien vs Predator. This release brings the Jaguar shooter to modern Linux and Windows systems.

The project relies on a readable-C reconstruction based on the RE #33 R71 source baseline. It reconstructs gameplay logic, the campaign, controls, artwork, and audio while introducing optional PC enhancements. These additions include offline local multiplayer, bots, Deathmatch modes, an integrated map editor, and a pack of 51 converted prototype texture panels.

Running the port requires users to supply their own retail 4 MiB Atari Jaguar ROM (`AVP.jag`) matching the SHA-256 hash `b31ca5c2415881ce50d0c076d327297547214a6240f0058b0f225a74f7ce440b`. The port validates this hash at launch, rejecting alpha or beta ROMs. While a Windows build workflow exists, Linux distributions like Ubuntu and Linux Mint serve as the primary development environment.

To build and run the release on Linux, install the required dependencies and compile using CMake and Ninja:

```bash
sudo apt update
sudo apt install -y build-essential cmake ninja-build \
  libx11-dev libxext-dev libxrandr-dev libssl-dev zlib1g-dev
cmake -S . -B build-gcc -G Ninja -DCMAKE_BUILD_TYPE=Release \
  -DAVP_STRICT=ON -DAVP_BUILD_LOCAL_MULTIPLAYER=ON \
  -DAVP_BUILD_JAG_REFERENCE=OFF
cmake --build build-gcc --target avp_pc -j 4
./build-gcc/avp_pc --rom "/path/to/AVP.jag"
```

The Windows build and runtime have not been independently verified, and this remains an active work in progress where certain features require verification against original hardware.
