NOTE: THIS PROJECT IS MOSTLY INCOMPLETE
The aim of Ada Doom3 is to re-engineer the id-tech 4 engine with a clear dependency hierarchy, and robust tasking systems.
- Load and play doom 3 bfg levels
- Load Valve map workshop levels
- Native ports for Windows, Linux X Windows, Mac OS, and SDL
- Input support for generic and all major game-pads
- Multi-monitor windowing
- Threaded rendering with support for using multiple graphics cards
- SIMD math library
- Responsive multi-player
- Steam support for user accounts and achievements
To compile with GPRBuild:
gprbuild -p -P neo.gpr
Or the Gnat Programming Studio IDE may be used (email is optional): http://libre.adacore.com/download/
To compile with GPS click the gear and hammer button after ensuring the scenario drop boxes are correct.
After successfully compiling press play ▶ to run.
Github's tutorial on installing and using commandline git: https://help.github.com/categories/54/articles
git config --global user.email ""
git config --global user.name ""
git remote add origin https://github.com/AdaDoom3/AdaDoom3.git
git pull origin master
git pull origin branch
git commit -am ''
git push origin master
git push origin master:branch
Begin adding Linux/Mac support by implementing stubbed functions/subprograms
To begin developing for AdaDoom3, first examine all of the “base” system and foundation components in the /Code directory.
Each package in this folder (as all packages in Ada) consists of a specification (ads) and a body file (adb). For clarity, everything but subprogram, package, protected type, and task bodies are placed in the specification (including global variables and private function prototypes) allowing an entire overview of user-important information in one file.
It is highly recommended to examine the foundation files first as they will be included at almost every level in the design. They contain all of the basic components: data types, utilities for testing packages, and redirectable text input and output. The data types file is especially notable, because it renames all elementary Ada data types to be more descriptive by including each type’s byte size and range (i.e. renaming Integer to Integer_4_Signed). Although it is possible to use the non-renamed data types with the renamed ones interchangeably, it is not recommended.
More to come...