Jump to content
  • Advertisement
Sign in to follow this  

Game Engine Architecture Overview

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

I recently stumbled onto this article and have a few questions:

It seems that Engine Framework is using these Universal Scene (UScene) and Universal Object (UObject) concepts to loosely couple objects that are maintained by each of the systems of the engine so that data can be easily shared/exchanged in some fashion. At one point in the article, the following paragraph is mentioned in 3.1.2:

Another thing to point out is that the universal scene and universal object are responsible for registering all their extensions with the state manager so that the extensions will get notified of changes made by other extensions (ie: other systems). An example would be the graphics extension being registered to receive notification of position and orientation changes made by the physics extension.[/quote]

I cannot seem to visualize exactly how the above along with the comments in 5.2.1, 5.2.2, and 5.2.3 all correlate to handling the inter-system communication. It seems somehow the UScene/UObject get extended by the objects maintained inside the systems.

Anyone have any idea how that relationship looks?

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.

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!