-
-
Notifications
You must be signed in to change notification settings - Fork 34
Home
Dagon is a 3D game engine for D language based on OpenGL 4.0 and SDL2. It features a forward HDR renderer with clustered shading, PBR materials, an event manager built around SDL's event queue, scene and asset managers, entity-behaviour paradigm.
- Replacing DGL as an engine for Atrium. This means that Dagon is mainly targeted to first person action games, but nothing stops you from using it in a game of any genre.
- Implementing a modern, easy to use, extendable 3D game engine for D due to the lack of such. We believe that D is an excellent language for game development and it deserves more attention in this domain.
- Creating a use case for dlib for educational purposes.
Dagon is named after a god from H. P. Lovecraft's Cthulhu Mythos pantheon.
Dagon is a framework-style engine, meaning that it is controlled programmatically and doesn't provide you with an editor. How you will build your scenes is up to you. You can build them manually by loading models one by one in your code, create your own scene format, or export asset packages from Blender.
Currently Dagon supports loading OBJ and IQM models.
Dagon is written with extendability in mind, so you can easily add your own drawable objects, entity behaviours, materials and asset loaders. Drawable can be anything you want - you can manually create meshes and animate them. With behaviours you can dynamically attach custom data and functionality to game entities. Your materials can use custom GLSL shaders and parameters, and your asset loaders help Dagon understand files that you want to load from disk - these can be 3D models, levels, save files, etc.
Dagon heavily relies on dlib. It is used everywhere in the engine, from memory management and vector math to file I/O and image decoding. Actually, as stated earlier, Dagon's secondary goal is to promote dlib and illustrate its features.
Dagon doesn't use D's garbage collector and manages all of its data manually with New and Delete functions. You are also expected to do so. You still can use garbage collected data in Dagon, but this may result in weird bugs, so you are strongly recommended to do things our way. Most part of the engine is built around dlib's ownership model - every object belongs to some other object (owner), and deleting the owner will delete all of its owned objects. This allows semi-automatic memory management - you have to manually delete only root owner, which usually is an Application object. When creating objects, it is recommended to make scene's assetManager their owner.
See tutorials.