Showing posts with label Project. Show all posts
Showing posts with label Project. Show all posts

Saturday, 11 May 2013

P.U.N.C.H


So this is the showcase for the game we've been working on for our 2nd semester project. The team is called Good Lord! What a lot of biscuits! The team name has a long story about it, maybe a story for another post. P.U.N.C.H is a product of 7 programmers, 1 artist, 1 designer and a producer and was developed using the Havok physics engine.





Saturday, 30 March 2013

Elephant Algorithm: They Never Forget


At the moment the elephant memories are represented by a 2 dimensional array but I was actually thinking I might put different types of geographical locations in other that just the oasis, and use a 3 dimensional array for the elephant memories. The 3rd index being a 'tag' to distinguish between the type of location. This might end up as polish though as I want all the basics in by the end of this weekend so I can start on the crowd  algorithm.

Elephants can now store information on where the oasis' are located. This is done by calling a remember function on collision, which stores the current x and y position. An elephant will continue to store coordinates as long as there is collision. The result is the storage of not only the geographical location but also its partial coverage (the area in which the elephant travelled). Originally only one coordinate was going to be stored but this way has given the memories more depth and given the algorithm more functionality, without increasing the complexity. I'm very pleased with how this has worked out even though it isn't as planned. However it is currently using arrays 3600 in size, eventually this should be changed to a vector to increase efficiency.  

I would also rather the arrays size was set on the fly at run time based on the number of various locations, which would be randomly placed and in randomly set quantities. Probably with a limit to the amount of locations present based on the screen resolution. The amount of elephants could be generated at run time too. It's likely that these features won't be in the build I hand in in May but I have enjoyed working on this project and so I will carry on working on next semester.

PS2 Project Proposal


I handed in my project proposal for the PS2 module. I plan on allowing the player to 'cast spells' by shooting a fire ball at enemies and the enemies will catch fire too. I'll need a model of some kind to represent the enemies and ill need a chase function so they chase the player, then some kind of collision detection, box probably, nothing fancy. The fire ball will be the main feature as I want it to be an animated texture on a sphere model. I've done this before in my Direct X module last semester so I understand the theory. I need 3 textures of varying opaqueness and layer them on top of each other over the sphere. Then I have to cycle each texture across the surface at different speeds.

Sunday, 24 March 2013

Elephant Algorithm Project


It was my intention to finish the 1st algorithm for my innovation project by the end of the month. This leaves me with this weekend and next weekend to complete it (at least the code, write up can come later). Managed to get the collision between elephants and oasis in with no problems. Elephants now know when they are at an oasis or not, they just don't do anything with the information. Next I have to store the information so the elephants can use it.

Tuesday, 12 March 2013

Elephant Algorith Project


Started on my innovation project, it's all going to plan so far. I've got the basics for the elephant based algorithm demo in. Elephants move around on screen on their own and the geographical locations (oasis) are in too. The next step is to give the elephants a memory back which will probably be made out of an array. Once that's done I have to work out how to transfer data both ways when two elephants have collided. This shouldn't be too hard anyway as the elephants have their own class and so a change to one will change them all. It's more a case of, arrays can confuse me a lot and collision can be a nightmare. Once these two features are in though the rest should be straight forward. Then that's one algorithm and demo down and one more to go. The aim is to get this one finished by the end of this month, and the second one finished by the end of next month, leaving me 17 days until the hand in for polish, paper work and to work on the 4 other modules that are due in on the same day.

Monday, 11 March 2013

DirectX Terrain Smoothing


If added smoothing into my DirectX. The theory behind it is quite simple. Work out each points height by averaging the neighbouring heights. The problem i had was that the framework works out the height terrain with a single dimensional array instead of a multi dimensional array. So i had to use a triple nested for loop just to get it to work.  One for each pass through the smoothing (the more passes you make the smoother the result is), one for the height and one for the width.

Friday, 1 March 2013

Havok Project


This week we started working on the new prototype for the house wrecking game. I worked on making objects randomly drop a coin when it’s smashed. This code will then be used to update the score when a coin is collected. I had to wait to put my code into the project because it relied on a function that someone else was writing. Rather than waiting I went ahead and wrote the code as I knew it wouldn't take long. I then translated it into Lua as I didn't know if the code I was waiting on would be in a component or a script.  Testing ended up being peer programmed because of version control issues, but largely remained the same. I'm not required too but I'm doing to go beyond my task and try to make a ‘COIN’ object actually appear when an object is smashed rather than it just displaying ‘COIN’ to the screen. I have no idea how to create objects from the code alone without using the engine but it seems like it would be something were going to do a lot of and this feature would be needed anyway so it would save time if I did it now.


Lua, from the little I’ve done, seems to be quite a nice language. I was expecting to find the syntax difficult and to get confused between languages as I am working with two. The version control however seems unnecessarily complicated. I’ve never used any version control before so I am unfamiliar with it. But setting it up was a real hassle and I still doing really know how to use it. A lot of us are having problems using the interface.

Friday, 22 February 2013

PS2 Development


This week I started on PS2 development. I've only been doing the controls so far but I'm really enjoying it. I've covered all the all the buttons, analogue sticks pressure and vibration, but what I really want to do is make a small framework with all the controller features mapped so I can use it for my project. I have to wait until the room is free though. I don’t like not having the equipment available for me to do it at my desk or at home, I'm not use to it. There is one thing now ingrained in my memory though. At the end of the program the controllers don’t automatically unlock from the mode they've been set in (analogue/digital). So you have to remember to unlock it at the end of the code. Whilst implementing the vibration controls I hadn't yet found this out. I ran the program and the controller started to vibrate. But because the controller was locked in analogue mode when I closed the program it carried on vibrating. There was an awkward 15 mins involving 3 people working out how to stop it vibrating and me constantly holding the controller in the air to stop it making a noise against the desk. 

Thursday, 21 February 2013

DirectX Framework


I also got given the new framework the PC and Xbox module. I’ve gone through half of it to make sure I understand what’s going on and made my own comments etc. I noticed the controls were, at least to me, very counter intuitive. So I’ve started converting them over to a more FPS look-move style control. Putting mouse control in was easier than I expected. The camera now points at the mouse curser but now I have to get forward to go in the direction that the camera is facing. There are two tutorials I’ve found but they look really complicated. It looks like I’d have to modify and add a lot of code to make it work. I think I might have under estimated the task and it might never actually get implemented. This means I could end up taking the camera look controls out too.

Monday, 11 February 2013

DirectX Randomized Terrain Generation


Started implementing procedurally generated terrain when the space bar is pressed for my directX module. I wrongly assumed that the code to procedurally generating stuff would be long and complicated. But you can produce basic mountains with only 2 functions. Randomly generating the terrain was literally as obvious as using a random number generator on the y axis.  Mine are really spikey/ridged mountains so I want to add some smoothing to make them look more realistic.