Jump to content
  • Advertisement
Sign in to follow this  
frankanbailin

Engine Structure advices plz!

This topic is 4854 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Well, I am just a beginner.After working out some features,such as Skeleton Animation&SkinMesh, ShadowMap,BSP Tree, some collision detection and so on, I tried to organized them into an engine and made it grow up with new tiny games developed on it. But I have no idea about the engine core and the resource management.And got few things from google. And as a beginner, reading the source code of some open source engine is really a huge project for me,especially with no idea of how the engine core and resource management were developed. Any WebSites or articles on this? or any advices? thx in advance!

Share this post


Link to post
Share on other sites
Advertisement
Try drawing out a diagram that shows the relations between your objects/structures and how execution should flow through various components. Break down the functionality of those components and determine what information they will need and how they will get it. That will help you to see the best organization for your particular implementation instead of trying to shoe-horn someone elses implementation to fit your project.

Share this post


Link to post
Share on other sites
Furthermore, research some patterns. Some of the most common include:

Bridge
Mediator
Chain of Command

Finally, download the Irrlicht Engine, and study how it's put together. It's at least a decent starting point.

Share this post


Link to post
Share on other sites
Engines are designed to be run on by games correct? So what we have is a basic hierarchy so far. The game runs on the engine. If you leave it there, it could get very hard to create both. So let's look at the engine. Lets say you have some high level objects such as Character, Level, AI, Car, etc... All these have something in common, they need something else to build off of? What could that be? Well, a character could need AI and a Level. It would also need a collision detection system, textures, and model data. We can use collision detection, textures, and model data for the level and the car too. So what does that mean? It means that those objects are re-usable. So we create texture classes, model data classes, collision classes that we can use them for all the objects. The hierarchy keeps going down until your at basic things like memory management, vector math, and more simple stuff like that... Now that we have the whole data section of the engine covered, you have to encapsulate the functionality of the engine, or the part that makes it work. So you create a process manager, which runs different subsystems. These would include phsyics, audio, input, rendering, etc... Hope that gives you some stuff to chew on.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

GameDev.net is your game development community. Create an account for your GameDev Portfolio and participate in the largest developer community in the games industry.

Sign me up!