Jump to content
  • Advertisement


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


questions reguarding engine design...

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

Hiya Im working on my first game engine right now and although its primarely for learning reasons, I plan to add quite a lot to it. Some things such as doors, lifts, AI and various other things will have a script attached to them that you will be able to edit and add to. This will be an extreme case however because I plan to add most things that you would need to script in a properties menu. In this menu you will have a list of major settings for systems such as collision, movement, display, lighting etc. All objects will use the same properties manu so it will be up to the designer to edit the correct ones. Question 1: Should all objects use the same properties menu... it seems to be the best idea to me. Basicly this is where my questions come from. Question 2: For one thing, for the properties in hardcode, there will be several classes that all have different booleans and such (the same as the properties) all of these classes are then added to the main actor class then in turn, all sub classes automaticly have access to them. Anyways, now should I simply make a script interface for these classes or should they use a basic file loading system instead of scripted? And Question #3: Is it best to have the base class call a global function such as "DisplayAllObjecs( )" or should you just use it such as... CActor *g_actorlist = new CMesh( ); In the second, all you would have to do is in the mesh class have a function for loading data... CMess::CreateNew(char *classname, vector3 pos, vector3 rot etc) { CActor pActor; if(classname == "player") { pActor = new CPlayer( ); } etc... g_ActorList.push_back(pActor); } Well, got to go. Thanks VERY MUCH!!! ~yodaman

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.

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!