idTech4A++ (Hamadan Edition v1.1.0) supports running Doom 3, Quake 4, Predation (2006), Doom 3 BFG Edition, Quake 1-3, Return to Wolffel Headquarters, Dark Module, GZDoom, Jedi series, Hero Sam, Urban Horror and many other classic games on Android 4.4 and above, Windows or Linux platforms. The engine is equipped with OpenGLES rendering, multi-threading optimization, soft shadows, PBR physical lighting, global illumination, AI robots, full-body perspective perception and full module support, which replicates the classic id Tech engine shooting game on the mobile terminal while taking into account smooth running performance and modern image quality upgrades.
You can download the engine from GitHub or F-Droid, put the original game file on your PC into the /sdcard/diii4a directory, and select the corresponding game in the launcher to start playing directly. Experience the nostalgic shooter anytime, anywhere, without relying on a PC, bringing the classic id Tech series back to life on portable devices.
Running a full PC-era triple-A shooter on a mobile device was almost unthinkable a decade ago. The project com.n0n3m4.diii4a is an attempt to turn this “impossible” into reality.
Its core goal is clear: to port classics based on the id Tech 4 engine to the Android platform. The initial focus was on the 2004 classic Doom 3. This project is not a simple emulator, but is ported directly based on the open source id Tech 4 engine code, refactoring the rendering interface so that it can run properly on Android devices via OpenGL ES.
From a technical point of view, this is a pretty hardcore project. The original id Tech 4 engine was designed for the PC platform and relied on desktop OpenGL, keyboard and mouse input, and relatively generous hardware resources. On Android, everything is different: graphics APIs become OpenGL ES, input methods become touch and controllers, and memory and performance budgets are tighter. What diii4a does is essentially to compile this C/C++ engine core through the Android NDK and encapsulate it with JNI and Java layers to achieve a mobile running environment.
What’s even more interesting is that this project is not limited to Doom 3. Essentially, id Tech 4 is a general-purpose engine, so it is theoretically compatible with other games developed based on this engine. With the continuous maintenance of the community and the expansion of the derivative branches, the project has gradually gained the ability to run a number of classic titles, such as Quake 4 and Prey. These expansion capabilities are more reflected in the augmentation branch, but the source of the technology still comes from the original DIII4A porting project.
It is important to emphasize that this repository does not contain any game resource files. It is just an engine operating environment. To run the game, you must have the original game data file (e.g. pk4 file) and put it in the specified directory (usually /sdcard/diii4a). Once started, the program loads these data files and executes the engine logic. In other words, this project offers an “engine shell” instead of the game itself.
At the experience level, it supports touch screen virtual buttons, external controller mapping, resolution adjustment, and graphic parameter settings. For those who like to toss and turn, this is not just “playing Doom 3 on mobile”, but also a technological experiment: how to replicate the full PC gaming experience on mobile platforms.
If you zoom in a little more, this project represents a broader trend – the mobile rebirth of classic game engines. Similar ports have appeared throughout history, such as various Android ports based on Quake III Arena. What these projects have in common is that they use open source engine code to break away from the original platform constraints and continue to exist on new devices.
This is also where the meaning of diii4a lies. It is not a commercial release or an official port, but rather a community technical practice. It proves that platform migration is always theoretically possible as long as the engine source code is open. The continuous improvement in mobile device performance has only made this possibility more realistic.
If you’re interested in game engines, Android NDK, OpenGL ES, or cross-platform porting, this project itself is a good sample of research. It’s neither a huge modern business engine nor a simple teaching example, but a real engineering in between: complex enough, and readable enough.
When you enter the gloomy corridors of a Mars base on your phone, it’s not just a nostalgic experience, it’s an echo on a technological level – an engine from the golden age of PC, resounding on mobile devices.
Classics are often classics not only because of the games themselves, but because their technical architecture is strong enough to continue to exist across time and platform constraints. diii4a is a concrete example of this technological vitality.
Github：https://github.com/glKarin/com.n0n3m4.diii4a
Tubing: