Last night I spent a lot of time going through the RuneEngine V2 source code, updating documentation and reviewing the source for poor organization and garbage code left behind. This is a good practice to act on with some regularity, but isn't always necessary.
Going through this I had quite a few thoughts. Absolutely none of them involved considering change. I found that for 210 code files currently they all seem to be in pretty good order and have great readability. But that is aside from the point. The real point is an issue of mentality gained from reviewing the source.
I have spent a lot of time over the past few months procrastinating about not working on the engine. I am getting heavy back in development with it so I decided a cleanup pass was in my best interest. I had been procrastinating because of "how much is left." Well, this review showed me quite a it in the direction of how inaccurate that really is. There are still plenty of unfinished areas and new features that need implementation, but reminding myself that there are systems and features already implemented that push into professional grade quality affected my opinion of where I am at. It would appear that by the end of the week I could have any loose ends taken care of and begin development of new features next week. By new features I specifically mean building the editor.
Now, I've spoken here about the goals of the engine as far as features, but here's a list of what I found that gives me such a confident outlook on the status.
- Deferred Rendering
- Post Processing System
- Dynamic Content system
- Custom material format
- User defined geometry system capable of working to the extent of a simple modeling utility
- Extendable file IO system
- Extendable XNA content resource extensibility (This is small, but huge at the same time, specifically it is built that shaders with custom structs used can be applied via the material file format with some extension to this area)
- Input System, with plugin capabilities
- Updateless and per-frame draw call removed system (huge optimization)
- Custom SpriteBatch which renders into a deferred scene with textures that support the multiple channels.
- Architecture in a way that almost every part of the engine is 100% self reliant.
- Low-Level and High-Level implementations for most features
As a foundation, RuneEngine V2 has all the necessary pieces to be something really impressive. Nearly the entire engine is designed for extendability. This design is going to make moving forward significantly easier than it was in past iterations.
Very soon, after the loose ends are tied up I will be making a post here and on the RuneEngine V2 facebook page. This post is going to be a demonstration of development with RuneEngine V2. I want to showcase, how some of this stuff is compartmentalized and how, as a coder using it, things are going to be done. In many cases a test project only consists of a few RuneEngine lines of code. If it's much more then it is due to setting up parameters of objects for a less "defaulted" test.
Anyways, happy coding.
No comments:
Post a Comment