W.U. 0x03

-
I just wrote last week update and here come another :] , How this time passes quickly. 

This week I spend mostly on fixes in work from weeks before. I recovered almost all base functionality of game and editor. This wasn't easy but was worth it :] right now it's look like performance return on acceptable level, everything in code has more clear structure and it's easier to use.

What else ... hmm... right now I started to reexporting models to new format and step by step recovering locations. I thought about posting some screenshot's from how it look right now but after moment of thinking I decided to wait for about two weeks when everything will take some more interesting form. Maybe I will try make then some video how this everything looks in move.

On the end of course like always what I plan do to next wednesday. 
I think that on this week I will take something easier than before because I'm pretty tired after last two weeks. So I will probably step by step recover locations and gameplay so game started to look like game and not only presentation.

Comments

Post a Comment

Popular posts from this blog

Query commands execution

-
So like always start with problem description: I have some pool of command represented as enumerator. Each of command can have unique data that size can be different. I wanted to create system that allow me in easy way iterate over them and execute.  After some time I created this implementation: template<ECommands::enum cmd> bool execCommandTemp(ECommands::ENUM a_cmd, void* a_data) { if (a_cmd == cmd) { SCommand<cmd>::execute((SCommand ::SData*)a_data); return false; } return execCommandTemp<(ECommands::ENUM)(cmd+1)>(a_cmd, a_data); } template<> bool execCommandTemp<ECommands::WRAP>(ECommands::ENUM a_cmd, void* a_data) { return true; } bool execCommand( ECommands::ENUM a_cmd, void* a_data ) { return execCommandTemp<(ECommands::ENUM)0>(a_cmd, a_data); } where SCommand look in example such a way: template <> struct
Read More »

W.U. 0x20

-
Image
And as I said last time new preview is available: As you can see a lot has changed. Right now I mostly focus on gameplay so I do test of AI (some of them you can see on end of movie), changes in fight, items managing, fix some problem with physics and many other things. To say truth I don't remember them all :P So I'm going back to work and till next week.
Read More »

How this all works: Part 3

-
Image
This time some more details about architecture of engine. First thing that I need to mention W.R.E. is not engine for L.B.A. project, I create tools that will be use in next productions. Because of that I take some decision that make it's structure more complicated but in the same time more flexible. In this moment W.R.E. is based on four modules: But as you see there is five elements :] Why ? Exe is only wrapper to game dll and do nothing else so I don't count it as module. Ok, so from begin: W.R.E. - Is main part of engine it's managing window, taking care of rendering, physic, sounds, file, materials and things like that.  Game Engine - It's the frame of game. Contain all templates for objects i.e. Models, Characters, Action objects. Other important function of this module is editor functionality. Editor GUI - It's interface of editor based on Qt. It's mostly call function that are inside Game Engine. Game - This is DLL so it could be simple connected
Read More »