Updated Game-play Video

So here’s the latest footage of game-play, very close to complete, just bug fixes left really.

Change list:

• Fixed UI elements to make them sharper, particularly for up-scaling on the PS3.
• Lasers now have a short “power up” window, before then  extending until they hit the player or a shield block.
  This means you have a chance to avoid them.
• All controls are now more responsive:
  Inertia is reduced, player control is less “floaty”
  Button presses are now handled better, some times single button presses for things like the shields or target swap weren’t being picked up, they are now.
• Firewall power-up now protects against lasers.
• Menu elements have been fixed up to be clearer and consistent in appearance and position.
• Enemies now take a very small knock back when damaged.
• Enemies now display their health bars briefly when damaged, indicates that your actually doing something.
• Hit boxes have been adjusted to account for some previous problems with bullets missing.
  Same goes for lasers, but they were actually hitting too often. reduced the hit-box width.
• Point blocks now track towards the score bar, rather than the player.
  In almost all play testing the player was initially afraid of the point blocks, they thought they were enemy bullets.
• UI now displays relevant controls
  Triangle always displayed as the Shield Toggle
  Square displayed for draining, when no powerup is active/ready
  Circle is displayed for activating abilities when one is ready.

Not Seen/Inprogress:

• Bosses are now working, currently testing and bug fixing them before i grab some footage of them.
• “Stun” power-up works, but could do with some edits in terms of visuals, current state could be confusing to the player.

Monday Update

Changes since Friday:

• More actual levels –
  The game now has more levels, rather than just defaulting to the first one.
• Endless mode –
  The endless mode now actually works, but not well…
  The spawning and difficulty algorithms will need a lot of work before release.
• Endless mode screen and saves –
  The screen from which you select the endless mode.
  This also displays your highest score.
• Fixed the fuzzy box on the menu screen –
  This was bugging me!
• Completed the save functionality –
  Now includes save data for endless mode.
• Updated the Icons and Images of the game description –
  Added the new, more exciting, game description images.
  Added the correct icon for save files.
  Included a missing descriptor image for the PSP version.

The home buttons.

Buttons? Plural?
But I thought the playstation systems only had one?
So did I until I tried doing anything with them!

The issue:
Pressing the home button doesn’t pause the game while the system screen is up
My Aim:
If you are mid game and hit the pause button when you return to the game it will have paused and display the pause menu just like you had hit the Start button
Problem 1:
I don’t have access to the home button!
Problem 2:
The behaviour surrounding the different home buttons on the psp and ps3 means my psp solution doesn’t work on the ps3!
The first I managed to eventually get around by adding a function to the Steel Engine to check the “Controls Intercepted” bit
The second I have no clue… Apparently the same bit isn’t being used for the ps3 implementation.

Non of this is part of the submission requirements at least, it’s just a design feature I particularly want to implement.
At least on the ps3 you can see that the game is still running in the background.

Tonight’s to do list:
Sort out a couple of missing system images for the game.
Adjust some of the existing ones to look better.
Touch up some of the fuzzier in game sprites.
See if I can find anymore nice free music loops

PS3 PLAYABLE!

IT WORKSSSS

The problems solved to get it working:

A certain npdrm file had to have the “minis” setting set to true for it to work on PS3
The sdk had to be 6.2.0 or less… i’d been working with 6.6.0… oops
The game code has to set the file usage to UMD and NOT set to Network…

Technical Requirements Checklist

So i’m now very close to submitting my game to Sony!

This isn’t the same as releasing the game however…

It will most likely fail the first time, and in fact we are counting on it!

Why?

Well it gives a little more time for play testing, but also we doubt that everything will be 100% to the letter for the submission requirements, its VERY easy to fail them, but at least we’ll have the feedback to know where we fell short.

This could be anything as minor as having the wrong version number in my submission, or as major as the game hard crashes.

The latter is what I definitely don’t want to happen, the first is just kind of annoying.

There is a huge list of requirements to meet for my game to be published, and this list is called the Technical Requirements Checklist (TRC).

Turns out all games with auto-saves MUST have these, Sony’s rules.

Luckily as i am producing this game as a Minis Title, a lot of the sections are irrelevant, the Minis program doesnt allow for network or game sharing elements, so the requirements for those aspects can be ignored.

The big items that i am in the process of ticking off are to do with warnings, save games and memory cards.

There are also sections relating to branding and image for any elements to do with Sony.

Thankfully I’ve not had to make any changes to meet these standards, keeping a consistent and recognizable design in terms of tutorials and controls display helped.

That’s all for now, ill try and get a new video up soon too.

Timing and Update functions

Time for a wordy post, as pretty much my whole day has been focused on converting code and very little visual work.

The short of it:

My game’s update mechanics are now time based! Fluctuations in fps should now impact game-play far less if they happen, and u also values are more meaningful and easier to balance!

The mistake i realized while writing this post:

I was using the time elapsed since the last frame, NOT the time since the last update.
Now that ive swapped to using the time since last update (which is updated with the time since last frame) the game play is soooo much smoother across the board.

The longer of it:
Originally my code used a very simple and fast method of timing, integers, each frame I would subtract 1 from the relevant timer(s). Zero meant something happened, or if I wanted to I could check other whole numbers for an event.
This worked great if every thing ran at a constant 30fps and I used multiples of 30 as seconds.
But it doesn’t work well in practice, more often than not I’m running at more than 30, I was running at roughly 90 most of the time, un capped.
So with my 60fps cap all the speeds were off.
But if I adjusted the integers for 60fps then any drop slows down the game…
For example the tutorial text rendering drops the fps to around 30on the psp.

The solution, track everything as seconds (suddenly all the values make sense in your head) and store them in floats.
These floats, instead of ticking by an arbitrary value each frame, are actually adjusted by the time since the last frame, meaning if a frame is slower or faster than average it doesn’t matter to the calculations.
Similar to the timers I did the same thing for movement, objects now move based of distance per second rather then distance per 30th of a second.
Backgrounds too are now uniform across the different menus, regardless of how much additional UI is being rendered ontop

Picture Time:

Move Tutorial

Shields Tutorial

New Levels Screen

Tutorial Progress

So the tutorials now work!

But like everything they still need some tweaking, pretty minor stuff however.

They did require a couple of new assets in addition to the display messages, below are the new “Training Bots”

A small bot designed to set your weapons and shields.

 

A larger, laser wielding, bot to test the drain and special ability features.

As well as adding these bots, i also reversed my decision to not have a movement lesson. Partly to just be sure that everyone knows all the controls, but also as it helped in coding the flow of the tutorial.

Other stuff…

As well as the tutorial setup i have also made the planned changes to the level selection screens.
Buttons are now smaller as to accommodate more, which are a new button for the tutorial level, and a button to go onto the next screen.

There is also space for a feature in the centre that displays the highest score of the selected level (or “Tutorial”/”Next” for those buttons).

Frame limiter: the game is now limited to 60fps, this doesnt make a huge difference on the PSP, but on the other platforms locking it is important to not have a game running insanely fast and being unplayable!
This change is what caused the vast majority of issues i now need to tweak as the current balance is a little off in terms of speed, everything needs to be sped up a little, but that wont take long to change.

Save games

So another addition that i haven’t blogged about yet despite doing a while ago is the save functionality.

Saving.

The game uses auto-saves that save at the end of each level or when you die;

If you complete a level that you hadn’t beaten previously it updates your save to show that progression, and update the highest score if it is a new record.

If you die, but have a higher score than previously, it updates your highest score for that level.

Loading.

If you haven’t already loaded a game from the main menu you are given the option to load a game, doing so will load the save, unlocking any levels that you have progressed too, and their highest scores.

If you have loaded a game and return to the main menu for any reason then you will see the “Load Game” button has become a “Continue” button, this will take you back to the level menu.

New games.

If you have no save games available the New Game option will be your only choice to play the game, Load Game will not be select-able.

If you do have a save game choosing new game will start a new game, and warn you, that the auto saves will over write the old save file.

If you have loaded a previous game and return to the menu, New Game will function as above, warning you, wiping the current state and taking you to the levels menu from which point any saves will be a fresh save, wiping the old progress.

Demo.

The demo video lacks the warnings of the final version, should hopefully have those working tomorrow depending on how busy i am.

Nearing the end

The first post in along time… sorry.
Expect a lot more over the next two months however! As the project is getting close to the end!

I don’t want to say the final stretch as it’s certainly not there yet, there still needs:

• Testing and then balancing.
• Checking to see it meets standards.
• Levels finished/tweaked.
• PS3 version testing.
• Digital storefront stuff.

For now here’s a first pass of some of the store stuff!

Icons for the PS3 and PSP respectively.

And the game description (just a draft for now), this one is the PSP version.

More updates to come soon! Really!

Update drought

So apologies for the lack of posts this past week or so, i have been very busy, just not on this title…

It has been nice to have a week or so working on other things and now i can continue development of Retro Fusion with a clearer mind and more objective goals.

What i’ve been doing:

Games Britannia! 

https://twitter.com/gamesbritannia

http://gamesbritannia.com/

This great educational event has been running for 3 years now, and i’ve enjoyed being involved everytime, especially in the schools game jam.

Monday:

Oh the joys and stress of turning a schools design into an almost complete game.
We use Game Maker for this. Very fun, and very stressful if you get into it as much as i do.

Tuesday:

With the help of the kids who designed your entry you finish the game in about 4 and a half hours for it to then be judged.
You then try to not freak out too much about bugs and errors ’cause at the end of the day the judging is based on the kids’ designs rather than the “finished” game.

Sadly the entry i worked on didn’t win this year (the design i developed for last year won! it was such a good design and im proud of the win, especially for the team that came up with it)

I loved the idea the kids had, as an idea i personally think it was best, but as with the real world and idea isnt enough, you also need a good design, and this year the competition was stronger in that regard.

Wednesday:

The workshops begin, many many workshops for school groups covering well… everything
You can see the list here.

I took this as an actual day off… spent abit of time working on designs for my own game and sleeping

Thursday:

The second and last day of workshops

This time i was involved in helping with the Game Maker workshop, a great introduction to the making of games created by Griffin Warner and Tom Sampson of Sumo Digital, both graduates of my course here at Sheffield Hallam
http://outbreak2013.wix.com/home

I helped out with this workshop in particular as i have a background in game maker and in 2 weeks i will be taking over the running of this workshop for Games Britannia Live!

 

Friday/weekend:

Family, party, chilling.
Probably the closest to a holiday i’m going to have, made the most of it and now to focus on my game ’til release.

Now:

Back to business!

First thing i’m working on is fixing the long lost of minor problems i’ve been picking up as i worked.
Stuff like…

• The score not being central in the score box;
• Shield drones not looking like they are going towards the player ship;
• Some enemies ignoring the respawn pushback;

Just minor things like that, nothing game breaking.

And while working on these issues i’m also going through the code and tidying up a lot of messy code, pushing segments into their own functions and moving towards a more data driven structure.

---

More frequent updates will be coming again now that GB is out of the way, stay tuned.