Youtube Quality: show

I’ve also uploaded a released version of the game, which was compiled for my portfolio CD. I’ve zipped the demo up to 25mb from 130mb. Download the demo here: AGT Prototype Game Demo Note that this version of the demo was compiled from revision 16 and not the latest revision. Also the sound has been disabled and files associated removed to free up some space. This was due to size limitations when I was burning my work to a small 330MB dvd.

Here are some of the screenshots I’ve taken. At this point there’s still no need for movie clips until revision 17, where I have enough gameplay to record to the clip.

Title screen screenshot.

For the scene editor I added the ability to drag mesh object created through the console by moving the arrows that extrude from the center to the mesh:

Mesh objects are created through the command console using “add_mesh” command and setting up additional paramaters. What happens is that each command is linked to a function which is called when ever that command has been entered. The information written in the command line is also pass in as a vector of characters which is then parsed separating each word into separate array locations. This check finds a spaces between the each words.

The next few screenshots are some from the prototype game:

The textures especially the player character models are temporary. Although it will be submitted for the assessment, in future work, this texture will be replace eventually.

https://agtengine.bountysource.com/development/log

http://svn.bountysource.com/agtengine/trunk/log_change.txt

As far as the game is going in AGT is concerned here are a couple of screenshots of the new scenes in the game:

If you can figure out somehow from the image I’m designing a simple action-adventure game prototype with at least 2 scenes. The first of these scenes (the first screenshot) will have the player character talking to various NPC’s in the area. Now the image doesn’t show this but eventually it will be populated. There is a main quest within the area that will lead to the second screenshot scene, again not populated as of yet. This area is the arena where the player must take on numerous rounds and defeat the enemy or enemies. All of these have been modified by adding components, simple as that.

What the arena is, is to allow the player take on as many enemies and gain ranks up the leader board. If you have played ElderScrolls: Oblivion then there’s a similarity in this prototype. One of the enemies in this arena, which you’ve already seen alot of, are the putties, and will be found in the initial rounds of the arena. There will be a case where you won’t be just fighting one putty but more than 3 at a time.

So that’s what will be done during the coming weeks and eventually with more posts on these updates.

Anyways you can read the update logs here: http://svn.bountysource.com/agtengine/trunk/log_change.txt or https://agtengine.bountysource.com/development/log which is also linked up in the description section of the AGT page. As I have explained, using SVN is my means on tracking down all the changes/updates/additions I’ve made to the project.

One of the main updates is that I’ve being doing my first scenes after implementing the physics system into the engine, as I want to have the physics engine drive the my character’s movements in the game. After that I integrated Caelum Day and Night lightning system into the project. Go here to know more about this awesome system: http://www.ogre3d.org/phpBB2/viewtopic.php?t=24961.

I’ve replaced my usual test “Raz” character with my own modelled and animated character: The Putty. A couple of pics below showing how “Putty” was made and then how it’s appearance in game.

Putty in the making:

Putty modelled, rigged and animated in XSI. (click on image to enlarge)

Then the putties in the game engine:

The screenshot below is the initial layout of the first game scene

So that’s them for my initial scene shots. I’ll have more to update on the game in the future. To continue testing on the sound manager that I’ve added into the engine and eventually have a tune playing in the scene. A camera component will be made to allow camera to be attached to an object and simply follow it. A very easy implementation, and then to implementing the first stages of the AI system.

Well I’ll leave you will a couple more screenshots I’ve taken.

Putty Checking out Caelum *smile*

Putties Attack!!

The choices are that either I stick with the engine implementation and get the scenes up after adding the physics, sound, AI, scripting and maybe the networking subsystem. I have began the initial phase of creating scenes, by adding console command to my core system.

The console can be brought down using the F1 button. I’ve yet to figure out what “tilde” is for OIS. The commands are binded to their static functions, and I can easily access all the other systems by simply calling their main singleton manager. I’ve also made sure that through only accessing the singleton class, there’s enough functionality to do what you need. This will come very handy when I’m binding these systems to Lua.The image above shows some of the initial commands I have added to the scene.
The reason for console is mainly for debugging purposes. I have placed numerous exceptions catches in the code, error can then be passed through to the console rather than having the program terminate.As for the commands themselves I have added a void pointer function which takes in a vector of strings. So calling the binded functions to a specific command will also pass the information on what has been typed in. The first element of the vector is always the original command. The rest can be parsed.

As an example below “add_mesh” has other parameters such as the name of the mesh to add, the new name and its position on the scene.

Code-wise you can check this implementation here:
https://agtengine.bountysource.com/svn/!source/5/trunk/AGTCore/Console.cpp#348
The static functions for each commands are found here:
https://agtengine.bountysource.com/svn/!source/5/trunk/AGTCore/CMD_Functions.cpp
where you can check how I have made “add_mesh” commad working with additional parameters (line 46). Current one links to version 5.Other things that will be worked on:

• Add command to add an basic game object. Eventually scripted template classes of objects that contain components will be available instead creating objects and adding components to them.
• Command to add components to objects. These components are either in Lua scripts or in code, usually the fundimental components such as “mesh_component” will be done in code
• Adding command to export scene into a file. This file will be in XML format.
• Making first step into a playable scene. An interaction between playercharacter component object to another object; maybe a object with a trigger component, which trigger’s some sound or a GUI change.

The image below just shows an object “dog”, with a component “mesh_component” attached to it. Without that component, its obvious that you won’t see any dog, but in object storage it will be there.

Things I will be considering in the future implementations pretty much consists on making scene editor as easy as possible, by adding some GUI implementation rather than typing into the console command.