Jump to content
  • Advertisement


This topic is now archived and is closed to further replies.


Engine Arrangement

This topic is 5728 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

Hi All How have you arrangend your engines? I''ve read in an article, that one of the best ways would be to make en executable engine and put the applications which use the engine in DLLs. But where would you put modules which would be used in the engine and in the app(for example logfiles). Would you make a static lib with these modules and link it to the engine and to the app? Isn''t that a bit bad? How have you organised your engine? Maybe you now an article about engine design/arrangement? thx phyl0men0

Share this post

Link to post
Share on other sites
I chose the other way around : the engine is a DLL, and the game is an exe. I then do everything using virtual functions on inherited objects.

The engine has a series of headers that provide the base classes for inheritance. You then derive the "object" class to a car class, a plane class, a plasma-teapot-gun class or whatever in your game, and give it to an object manager owned by the engine, that will "render()" the object, "update()" the object, regardless of its real type (seen as exObject *, could be gamePlasmaTeapotGunAmmoPack_TeaForTwo *), and so on, using the virtual functions you provided when you created the object.

Extatica - a free 3d game engine
Available soon!
Click here to learn more

Share this post

Link to post
Share on other sites

  • Advertisement

Important Information

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

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!