Showing posts with label demo. Show all posts
Showing posts with label demo. Show all posts

Saturday, 31 August 2024

Anniversary 10 Years On Steam

  

Airship Dragoon has been on Steam for 10 whole years. Even Albert Spier only got 30 years in Spandau ...

To celebrate this monumental event I put the game on discount of a whoppinh 95% ... but Steam only allowed a 94% discount due to transaction charges converting into US dollars. So 94% it was, slightly odd number that it is.

One of the interesting things that I found was that the Far East of Korea, Japan and China did make the top 10 for sales. This was especially gratifying as I knew there were plenty of pirated copies in the early days floating around China due to the amount of traffic my website got to download the additional map pack.

In other news, August draws to a close. A month of scorchio sunshine, sitting out by the veg patch, absorbing vitamin D in non-capsule form and sewing myself a medieval bag hag (summer pattern), going to make a winter one with felt to ward of hypothermia later. 

Alas the baking sun meant that the veg patch was going bone-dry, especially as the water barrels had been emptied. Roll on some rain, in fact after the utter soaking for the first half of the year, if it could just have kept a bit back for mid-August instead of swinging from "I need to build an Ark" to "I need a Thumper to distract the sandworms", it would have been appreciated.

Behold my mighty carrot crop! That was it ...

 When it finally did rain it did at 3.30am, so I was outside changing water barrels over with a coat over my jim-jams. If anyone has a working weather control machine who is not CIA, please could I have some more rain.

I also updated the demo for Monsters Loot Swag, to the most modern working build of the game. The old version of the demo had been removed due it being built with Ye Olde game engine version which predated Torque3D 4.0 and the fancy asset system and PBR (Physical Based Rendering) materials.

In other indie game dev news, I finally fixed all the networking jitter I had previously been fighting ... by simply ripping out the custom player class code I had written and using an actual seperate camera system. I had always had a sneaking suspicion that trying to go through the player class and directly use the player object's own cam/eye node might not be the best way of doing things, and in the end, said sneaking suspicion was more jumping up and down suspicion with total loss of stealth abilities.

I decided to use the Open Source 3D Action Adventure Kit camera system as a base, and after a bit of modding I got it to work with my existing lock-on target system. Behold - moving AI who have been locked on by both hosting client and remote client - now without any jitter!

So that was August, and now we will be onto September, named after the Greek "sept" meaning seven, because it's the seventh month ... or at least was until two despots added new months after the sixth one, and conveniently named said months after themselves ...

Anyway, next up on the dev frontier, Monsters Loot Swag only needs 1 more level with enemy boss, and 2 more unlockable players making, before a bit of tidying up to finish it off. I am not in a rush however, as I would rather ship in early to mid 2025, and thus give myself time to get the next game concept furthered more, hopefully to the point of having some real gameplay and a store page available for coming soon™.

As my previous attempt to drum up interest with the Monsters Loot Swag early access release didn't achieve any support, I might try an open beta next time.

Thursday, 29 February 2024

Leap Into The Future

Monsters Loot Swag Now With HDR And PBR

February has arrived ... and by the time you are reading this, it has also gone. But not before Monsters Loot Swag got a huge update on Steam, and has been ported to a completely new engine build.

This included finally retiring the old engine build and replacing it with the latest game engine build, complete with all of those 21st Century shiny things like an asset system, HDR lighting, Physical Based Rendering of reflections and so much more. The changlog itself ran to some 36 items.

In other game development news, I also ported my old "Aeronauticals" proof of concept demo to the latest engine version. You can download and play that here and watch me do just that below.


 February 2024 is a Leap Year! And soon to be leaping are what is in this pond! 🐸

However since this arrived there has not been much froggy activity due to the weather reverting to being bloody freezing for the last few weeks. Thankfully it looks set to become milder and much croaking was heard earlier.

So that was the month with a strange number of days, and all because two despots mangled the perfectly working 10 month calendar by inserting their egos into new months and totally throwing time out of order every 4 years.

Sunday, 31 December 2023

That Was The Year That Was: Space Year 2023

 


2023 comes to an end ... and if I am honest, it was kinda non-descript ...

So what actually happened? I have no idea, but it did include me porting Monsters Loot Swag to the latest version of the game engine - available here for FREE under MIT license - and all it's glorious new fangled stuff like asset systems and Physical Based Rendering (PBR).

Have you seen this PBR'd catgirl?

You have now!

So, anyhow, the latest engine version of Monsters Loot Swag got a BETA, whilst I fixed a few things up on that version to bring it more into line with the default v.3.x which I had initially uploaded to Steam - not that I got the feedback and testing which I was hoping for, but hey, that's just one of those things. The v.4.x Beat build did come with it's own script compiler which was invaluable to finding scripting issues which the the default version would not. I will probably retire the default Steam version and replace it with the Beta as standard moving forwards. 

Have you seen how to opt into the Beta?

You have now!


 I also beat Micro$oft at it's own game when it locked me out of the source code for Airship Dragoon, and managed to finally put out a new update with the latest version of Steam.

Have you seen this Airship Dragoonette?

 You have now!

Have you seen this Sparrowhawk?

Well he spotted me first ... I mean what did he want? It's not like I can just feed him juicy blackbirds, which judging from the carnage near the veg patch, is his sole diet.

In other news I managed to survive five (5) whole decades on God's blessed earth, I think wearing a sallet for the whole time helped.

In other news I have made good progress with my GAMBESON which I have designed specifically to survive Winter with when heating prices go through the roof, or someone Kalibrates the UK gas pipeline, and yes, season should have caps. I am currently messing around with the edging at the moment and need to sort the arms out and some strapping for the front which is double layered in a slightly eastern fashion. No prizes for the sewing aesthetic but it will hold together. 

It's surprising how sore my finger and thumb has got just from holding a needle.

Once I get chance, I will return to my medieval hack-and-slash-cum-RPG idea which I have already coded combat up for, but really now need some 3D artwork and animations, and I'm thinking of a lowpoly aesthetic with that. 

I also intend to port my old aeronauticals air combat game demo to the latest version of the game engine and release it for testing. To be honest if I go back to that I might make it low-poly too as that seems to be faster with production. It's a style which certainly did not do Valheim et al any harm.

Another 365 days are gone, so you for the next 365 ... unless it's a leap year some time ...

Happy New Year!

Thursday, 30 June 2022

New And Improved Mouse Aiming

So it turned out nobody liked the original mouse aiming system

This was not entirely a surprise as literally nobody had previously said that they did like the mouse aiming system, but at least I got some feedback and examples of games which had good mouse aiming schemes. What people actually wanted was not the direct input control system to player character rotation, but for the player character to turn towards a visible mouse based cursor or aiming reticle.

And their wish was my command! Had a bit of trouble networking it in multiplayer co-op mode at first but got an example of setting up a net event that would send the client input directly to the server object rather than having to wait for standard client/server updates.


 It was also Steam Next Fest, were a thousand desperate indie devs got harvested for demo downloads so that gamers could get a badge and 55XP off Valve.

 I ran two livestreams with varying amounts of success and terrible audio until I ironed those problems out - even though I had ironed those problems out in testing previously. Was hoping for 10% wishlist but got 1%, which is at least better than Sweet FA%.

Monsters Loot Swag will ship as an Early Access title on Friday, July 28th, 2022 - which gives me four weeks to get it into a shippable state. eg: make more boss monsters for the compeleted levels.

Tuesday, 31 May 2022

Demonstarting Demo Steam Next Fest

Brilliant Advertising That Gets Straight To The Point

Steam Next Fest is a thing where desperate indie devs big and small plead with Joe Public to notice their upcoming game and add it to their Wishlist. It runs for a whole week from Monday the 13th of June and Monsters Loot Swag will be there, with a playable demo - that I am still hammering the bugs out of ...

At some point during this Steam Next Fest, I will be streaming on the Monsters Loot Swag Steam Store Page (if I can get it to work - even Valve say it's awkard as hell in their documentation) to demonstrate the game and I dare say ramble incoherently about things ... probably 8pm BST on Tuesday 14th, and again for a late night comfy playthrough at 11pm BST on Thursday 16th.

 The playable demo has the first level available in Single Player, or Online Multiplayer (or LAN for those strange folks who have physical friends in the real world) and now features THREE player Co-Op (4 in the full game) and the new character "Bikaver".

Melee Based Wine Drinking

 Bikaver is a close-range, melee based character. She likes long walks in the rolling hills, eating grey cattle salami, drinking red wine and dealing out blunt force trauma.

Bikaver has a trio of hand-to-hand standard attacks, features high mobility, with high strength for knocking monsters out of the way. Her special attack is a low damage but wide area attack which stuns all enemies, whilst her evasion is the fearsome - and instantanious - Huzzar Charge, propelling herself through multiple ranks of monsters, both stunning and damaging all in her path.

 She also got a character profile redesign because I didn't like the first one.

 Monsters Loot Swag even runs on Valve's new handheld console Steam Deck ... apparently, I mean I don't actually have one.


And here is the first glimpse of Multiplayer Co-Op mode in action - with low audio because I forgot to turn the volume up for recording ... and then I forgot to turn off the video after we both got killed so half of it is a character screen whilst I was chatting on discord.


Plz wishlist Monsters Loot Swag on Steam!

Tuesday, 17 September 2013

I Am The One Percent: Airship Dragoon is Released

Today I enter the hallowed corridors of those amateurs, tinkerers, modders and aspirers (aspirers? is that even a word?) who have actually finished and commercially released an indie game. I am the one percent.

After 2 years and 3 months (note to self, we have got to shorten the blinking heck out of development length next time around) of what seems somewhat akin to self-flagellation ... and even more disturbingly - 5 years and one month after deciding to make some sort of indie game - I have finally managed to release my first commercial indie game.



There she blows! A box shot of ... a box which doesn't exist obviously ... because it's a virtual product.

---------------------------------------------

But you can't have a release ... without a trailer .. so here's one of those ... looks best in HD but you knew that already.




Also, www.yorkshirerifles.com is now a thing.

A retweet of this, would be appreciated.

It's early days on the whole shipping front. I've set up my own site shop with FastSpring (as used by numerous indies including Frozen Synapse's mode7games - and the soon to be released FriendZone American Robot Hand-Egg Simulator ... does that joke ever get old? ... er yes ... :S ).

I am negotiating with Desura at the moment, and once that is sorted out, it's time to mount an assault on Greenlight and spam the gaming press with review copies. Slowly, slowly, catchy monkey - or embarazi as they used to say when I lived abroad.

I have set up an IndieDB for Airship Dragoon, for anyone who may use it.

The whole shipping/e-commerce/desperately seeking attention thing is all a bit new to me ... and like everything else ... in life as well as development ... I'm making it all up as I go along.

Eventually I will get around to doing - what is likely to turn out to be a huge - post mortem of the last 2 years and 3 months of development.

In the meantime, you may want to play Airship Dragoon which of course has a free demo.

----------------------

So, amongst all of this, I might actually get around to porting my old Valkyire Chronicles Style Action-Tactics-Hybrid over to the new Torque3D MIT version, and start umming-and-ahhing about which of the various projects whirling around inside my head will be my next game.

Softly softly catchee monkey ...

Thursday, 16 August 2012

Short Campaign: 96 Battles Later ... Not So Short Then ...

 So Short Campaign turns out to be ... er ... not so short after all. But was ruddy good fun, especially after I fixed the usual gazzillion bugs that you find during a month of extensive playtesting.

I played through my Short Campaign ... and it took 96 battles to win.

... so ...

... err ...

Short Campaign turned out to be not so short after all.

It's been a solid month of playtesting ... with the accompanying solid month of fixing a huge number of bugs that a solid month of playtesting throws up, and an equal amount of tweaking.

For my Campaign test, things started off well, a little too well. Then after 30 or so battles, I found a bug that meant the Ai was never deploying any of it's veteran forces. Whilst my force of veterans and equipment was growing, I was still fighting againstthe halfwit conscripts who can barely hit an elephant at close range. That fixed and things began to be a bit more challenging.

The Ai had a few issues with finding cover under certain circumstances - fixed. The Ai had difficulty re-equipping from the dead when they ran out of ammunition - fixed. Enemy gunners didn't have the correct amount of ammunition on deployment - fixed.

And also made a whole load of tweaks. Some of the most expensive equipment didn't seem to have the firepower to justify the cost - fixed. You get what you pay for but no one piece of equipment tips the balance decisively. I also redid a number of Guis to make them somewhat more ergonomic. The deployment screen now has battle terrain, weather, conditions, objectives and modifiers viewable with less clicking. Conscripts can be added to the deployment force singularly or en masse now.

I also added range-based-passive-phase-fire to the classes. So gunners and snipers could only return fire on the enemy's turn if the target is over 200m away. Recce and Fusilier can only return fire up to 100m, and Sapper, Grenadier and Militia (Conscript) get 100-200m. I found it creates another tactical decision, both in deployment - low visibility prevents Gunny and Marksman using passive fire - but also in battle - do you leave a Fusilier to cover the other classes incase an enemy walks around that hedge just in front of your Sapper and is too close for him to defend himself? Or do you move the Fusilier up doing his own job?

I had started off with the concept of limiting the number of veterans to just 16 as a way of acting to create a further strategic variable. You've got a lot of one class, say a class which can only return fire in the passive phase at long range, and when some conscripts survive they get promoted to a close combat class which you are short of. Do you sack one or more of your experienced veterans to make room for the new - but inexperienced - guys?

And then there was the actual gameplay, and the type of interesting procedural stories you get from unscripted gameplay. Just throw in a bazzillion variables and watch it go.

---------------------

Late on in the Campaign, after I'd fixed all the bugs I had found, my mixed force of veterans and conscripts was attacking a large enemy base on a hill. Numerically I had the slight advantage, experience wise they probably shaded it and equipment wise we were equal. This was the third or fourth time I had attempted to win this particular hexagon shaped territory on the Strategic Campaign Map, and I needed it to allow for an extra avenue of attack on the final series of enemy territories to win the not so short campaign. Previously I'd mainly used conscripts in the attacks due to poor weather conditions and a lack of close-quarter combat troops. Now I had sunshine and clear weather which favoured my available types of veterans.

   I'd moved my force up to a low bank which gave them cover and split my troops into Support  (Marksmen and Gunners) and Assault groups (mostly conscripts with some veteran Grenadiers). I also had a Recce and a Sapper for spotting boobytraps, and Sapper dualed as a mule carrying lots of aidkits and spare ammunition. I only had one of each of these classes available

   I'd had everyone pouring a bit of fire from behind this bank to suppress the enemy, Recce and Sapper had been spotting and diffusing boobytraps. I'd started moving my Assault team round to the side so that they could run up the hill and attack, when a sniper round critically wounded my Recce. Luckily Sapper was near enough to despense first aid and medivac him. Unluckily it meant he wasn't part of the assault anymore.

   My Assault team broke cover and rushed halfway between the objective and the bank, taking cover behind a series of hedges whilst Support group peppered the enemy. All good so far ... right up until I set my first trooper out. He spotted a large number of enemy that had been obscured and took fire from the far side of the map. I decided to throw my flanking manoeuvre out wider to avoid a crossfire and that's when my lead officer was vapourized by an IED. Sapper was still back with the Support group, Recce had been medivaced, so no one in the Assault team could spot boobytraps. And that's when the conscripts which made up the bulk of my Assault squad freaked out, taking a massive morale loss from the officers death right in front of them.

   Most of them fled blindly in panic back towards the bank, narrowly missing an earlier detected but not diffused IED. A couple stood in the open impotently firing at enemies either to well concealed to be hit or out of range. And then it was the enemies turn to pick a few of my panicked troops off ... which made the surviving conscripts freak out even more.

   Eventually I ended up back where the assault had started, behind the bank with the Assault team. Sapper used the last of the aidkits to heal the wounded, the conscripts had regained their composure. Now the real problem was a distinct lack of ammunition. I spent some time dividing up the remain rounds and added a now unarmed Marksman to the Assault team as there were no more 50cal rounds left. Most of my dead troops still had plenty of ammunition, but they're corpses were stuck in a crossfire.

   Not wanting to fallback to the Deployment area and have a dirigible rescue my guys, I tried again, this time heading for the smoking earth where my lead officer had died. There wasn't going to be an IED left there now so it was a safe route up the side of the hill.

   I headed out of cover, much wider than the first ill-fated attack, and had everyone sprint through the enemy fire, past the scorch blast left by the boobytrap, and scavenged equipment from the deceased. My Support team chewed their way through the last of the ammunition to give covering fire, and I suddenly had half my men sitting behind that bank playing cards and checking Twitter feeds for the rest of the battle. So it was all down to my increasingly small and barely armed Assault force.

   Storming up the hill I noticed a lack of incoming rounds, infact, I could see some of the enemy Ai starting to loot their dead for spare ammunition and weapons. As I'd never had a battle last long enough for both myself and the Ai to run dry of bullets I was pretty bally chuffed to see this in action in real-live gameplay rather than laboratory conditions of dev testing. As my Assault team's ammunition dwindled to naught there was a sudden close-range grenade duel on the hill but I was to the enemy dead first and rearmed. A final push to the top cost another dead conscript from wherever the hell that damn sniper at the other side of the map was hiding, but I seized the enemy's colours and won the battle.

-------------------------------

It had all been rather exciting, and nerve wracking, but showed me that my whole gameplay idea and the methodology of how I had been creating it was just what I had been after, 14 months ago when I first started.





And here is the final Campaign map. As you see I had tried my best to avoid cities as much as possible as they always have the largest number of enemies to face. I'd started off from the left, worked my way right up to the last few which are protected by the enemy Citadel's influence (more troops per hex). And that was when I got a bit stuck. Each hex captured which borders the hex you attack gives 4 troops, and for the final attack I just never seemed to have enough and so had to open up a new front all the way up the right side to attack from all available angles. If those 3 cities in the top(ish) centre had been other types of terrain I would have gone through them instead, but they simply were too much of an obstacle.




And here is the final tally. As you can see Sapper survived! Recce recovered from his medivac but was killed later. Out of all 77 victories, half of them were  aided by the bug mentioned above when the Ai only fielded basic forces. Total War Cost is blank because it was an idea I had at the end and thus only just implemented it - it shows exactly how much you spent over the whole war. Tax payers like to know these things ...

And finally, a short video demonstrating starting the campaign and then saving mid-battle and then reloading it with progress restored.


Monday, 30 May 2011

Dubious Demo 2.1 Released! Vow of Sobriety Ends!

Dubious Demo 2.1 is out! My vow of sobriety is over ... but it's 4am and there's no liquor in the house ... this is what happens when you don't plan ahead ...

... WINNING ... TIGERBLOOD ...
... but enough about Omroth and Frozen Synapse ...

Dubious Demo 2.1 is released! Finally! And considering it was 2 years between my first and second demos, this one has been a mere 6 months.

So, whilst you twiddle your thumbs - perhaps as an Indy Dev waiting for the release of Torque3D 1.1 Final (and the opening up of a new bug forum for it :P ), and if you can pull yourself away from Frozen Synapse for a moment, have a little go on Stevie's new demo.





It's had quite an overhaul, new info sections on the GUIs, an intro system, the start of the Narrative Campaign mode featuring level 1 single player scripted level. This has a checkpoint system for saves in-game (not to an external file, gotta work that out yet) so you'll respawn on death at the last checkpoint, and all static pickup items will also respawn to help you out.

PLOT! Not just the sound of a pig diving into mud ...

It's also got a vague narrative to the action some meaning ... you probably don't need meaning to blow aliens to bits ... but nonetheless it has a world beyond shooting to ground the action. Cue cutscenes! Some are player driven with next/back buttons, some are automated to music, these have countdowns telling you how long you have to wait ... all have skip buttons. Nothing worse than not knowing how long a cutscene is gonna take ... except for not being able to skip it!

And now there are 2 levels to play through on the randomized battle mode, and now you've a proper enemy - "The Thing From Ur-anus" ... hordes of nasty little alien beasties desperate to stick the tentacles where you don't want tentacles sticking ... shudders.



And of course my perchant for jokes ...


There's flares, airstrikes, and loads more "stuff". Catchick gets joined by the East Riding of Yorkshire Constabulary, and 3 types of seriously unfriendly alien menace over 2 different, huge levels, 1 narrative campaign mode and 2 randomized battle modes featuring 6 different gameplay mode/styles.



Anyhow, it's in the same place and has the same name as before - yorks.deta.in , weighs in at 170mb download - just click the picture of CatChick and read the info on installing (best not to install to program files as I've not sorted the UAC out yet).

And if you're really lazy - here's the direct download: http://yorks.deta.in/download/YR_demo2_setup.exe

Many thanks to Admiral Akba... er ... Ronny for the webspace and bandwidth. :)

Anyhow, this demo gives off a much better "feel" of how I want things to be and a general direction that I am aiming for.

And that's enough rambling ...

Here's some action showing the 2 main set-piece areas of the scripted Campaign Mode (level 1). Look at that tracer fly!

Saturday, 14 May 2011

Move Rock - Circumnavigate Rock - Go Off On Tangent

Those pesky rocks eh? We all have our rock ... some of these rocks might even be real rocks ... but for most of us it's a metaphycisal rock ... or at least it's not real anyhow.

Okay ... enough about rocks, real or imaginery.

Game development is a bit like a Japanese RPG - everyone is slightly squashed and absurdly cute ... no wait ... that's not right! There's a lot of GRINDING and leveling up can get to be a real pain in the derriere. Everyone gets burned out after a while, especially when your on an "all hours the Great Magnet sends" routine.


It's even worse if you're making an MMO!

So rather than spend ALL week down the pub or ALL my time reading mildly interesting but mostly inane Wikipedia articles about what someone I've never heard of was rumoured to have done on a particular date in the 17th Century, I decided to have a look at the RTSprotoype information in the stock documentation and see how the camera system and screen-to-terrain input worked - two things which I didn't know anything about.

And from there I decided to build another Tutorial series, detailing how to create a 3rd person, turnbased, squad tactics/action hybrid gametype which follows the gameplay style of "Valkyria Chronicles" ... which I've never actually played, but have watched the whole game streamed. Originally I was thinking of writing a Tutorial for full turnbased tactical game but thought that Valkyira Chronicles" mix of turns and action was quite novel.

The whole tutorial is complete in theGarageGames Resources Section here and also in the T3D Tutorials Section of TDN.

And here's a video of what it looks like:




So, the next time you hear somebody say that :

Torque can only make Tribes style FPS games

Link them with that.


Oh hi, Catchick ... who still doesn't have a real name and maybe will always be known by what a certain Mr.Kiss first refered to her as ...

... so back to getting this demo out ... which I could've finished a month ago if I hadn't been looking for something else to do instead ... cue pub and wikipedia. The demo itself is nearly finished, it's "that close" - but you cannot see me holding my thumb and finger a little way apart to demonstrate, so you'll have to take my word that it's about four inches or ten centimeters in new money. And the demo is going to get finished and then released.

It's been a long time and a shed load of work involving a shed load of assets, but that's kinda what a FPS narrative campaign is about, and because of this I've also been thinking of "procedural content" more. In my GarageGames profile it reads:

One Bloke ... In His Bedroom ... Trying To Make Computer Games ... eventually ...


... Trying To Make Computer Games ... eventually ... was kinda in there as a joke about how long it takes to actually complete anything, but someday I'd like to edit it to read ... Making Computer Games. So to that aim, post next demo release, FPS project is going on the back burner, and an old skool (I hate that phrase!) turnbased, tactics game featuring an entirely procedurally driven campaign system will come to the fore with the intention of shipping before the year is out - in other words, six months. I did previously moot the idea in a previous blog about an X-Com style game idea I had, and my recent "Valkyria Chronicles" style game Tutorial gave a rough proof of concept for the combat/gameplay control system.



It'll still be massive - I just won't have to script every single fart an Ai makes ... but first, finish off Dubious Demo 2.1, cos this time, it's got the start of a Narrative Campaign ..

Tuesday, 25 January 2011

Post Demo ... Another Year ... Where do they come from!?

Another year, I'm not exactly certain why they keep arriving or where the hell they come from in the first place, but the damn things just keep coming. Also back to the grind post tech demo release.

GarageGames has been reborn as ... GarageGames ... which is nice, 'cos now all of those bug reports I filed on the engine are getting fixed.

In other news I've been loafing. Post demo of my "randomized FPS gameplay idea and test of how much I could world size, complexity, view distance and still have something playable" (still available for download hither 120(ish)mb )I loafed. And loafed I did.

It was Xmas time and a certain amount of loafing was required but that appeared to spill over somewhat into me not really working for month. And from reading other peoples blogs I've noticed that I'm not the only person who seems to have hit the seasonal speedbump with a sudden wane in enthusiasm.

This only got amplified with a sudden urge to make a "strategy and tactics" game. Think sort of in the vein of the original X-Com (not the forthcoming X-Com as a 1950s First Person Shooter ... I mean, who thought ...

"You know what X-Com should really be about? A First Person Shooter set in the 1950s! Fund it!"


... and I think I need a close bracket here).

With an overall strategic map that gives way to individual battlezones for turnbased squad tactics, but ditching the isometric view for a mixture of overhead map and over-shoulder cam for the actual action. With multiple playable factions and a sort of steampunk setting. Steampunk not about matching a leather bodice up to a tophat with a couple of cogs on it, but strapping a deathray to a zeppellin and invading Antartica ... For the glory of a cybernetic Queen Victoria, cos if the British Empire doesn't, the Kaizer will, or worse still ... Americans ... with their preposterous ideas of Republic, freedom, democracy and all people being equal ... I mean they don't even have a goddamn royal family, powerless figureheads who have been specially developed through a thousand years of inbreeding ...

I had a very brief um-and-ah about the logistics of doing it all in psuedo-script, and wondered if I'd make a quick demo as a basic playtest ... and the answer was no. Or at least, not now ... regardless that "commercially" I reckon it's likely to hold a far better time->work->possible profit ratio, though that might just be the "familiarity breeds contempt" thing - I've been learning on the job for 2 years, and refining the narrative idea/levels progression concept for 3-4.

I had replayed my demo and rather enjoyed, though need to sort out the armour->damage effect on the player as I think it's overly harsh now.

Back to the grind of my original gameplan, namely one first person shooter, single player narrative campaign with associated replays of all levels in randomized all-action mode.

Anyhow, I wanted an intro sequence, something set to music, why not, everything else has. And I figured long ago that drawing the damn things as comics would be a lot better than disasterously animated 3D manikins with poor voice acting - cos that was the only alternative one bloke in his bedroom can come up with. So I figured that I needed a system of doing full colour drawings, and being able to knock them out fairly quickly ... hence the new avatar.

Actually I despised everything about it initially ... but after staring at it on the forums for a couple of weeks I've "grown accustomed/given up caring/find it less hateful" to it.



But it took me over9000 hours in MSPaint ...

Which isn't so great. And as I'm going to have a fair few of these liberally scattered about as cut sequences, time is of the essence. So, after much practise ... it's not really got any faster ... and nowhere near the 30 minutes I was hoping for. So post completion of intro sequence, we'll be cutting back on the number drawings - though I was already of the mind to make them "reuseable".



Which brings me to the logistics of actually doing the intro sequence. Initially I thought that I should just script a GUI sequence but have now decided that video is the probably the way to go. Hyperthetically speaking - the player starts the campaign, theora video plays inside a gui. There is a "skip" button, because no one likes intros or cut scenes that can't be skipped, and there is a countdown timer telling the user exactly how long they have to sit there if they don't want to skip - because nobody likes watching cut scenes when they need the loo and aren't sure how long they are going to have to hold it in for ...

---------------------------------

And that's enough reading for you, me thinks.

Intro Sequence isn't completed and still needs some more drawings, then it's sort out the action for my "premade many moons ago" corridor crawl, which was always supposed to be level one ... actually the demo level was supposed to be level one originally, done as a full exploration no shooty-shooty level but I thought I'd throw in 2 earlier ones for a more varied all action beginning (with short range and long range based gameplay respectively), so level one is now level three.



Remember this? Wow, that was a long time ago ...

Thursday, 9 December 2010

Dubious Demo 2 Released!

I won't pretend that it hasn't almost killed me ... but after a gazzillion issues ... it's up. A fast and long gametype to play, doubled by having day and night missions. Entirely randomized enemy and tactics, should be good for a few replays.

Dubious Demo 2 ... this time ... it's random ...



Function creep appeared, and instead of a fast and long game ... you've got 2 fast and 2 long games. Technically it's the same level, but now there are also night missions.

Talking of function creep, I also came up with a basic hit detection for close range which I wasn't originally planning.

Anyhow, it goes like this:

You've 2 gametypes, night and day, night is short ranged weapons only

This is a demo of a randomized gameplay concept, it's a first person shooter, and the idea was to make it somewhere inbetween the all action silliness of "Call of Lawyers" and the unfair realism of Arma/Operation Flashpoint". Weapon ranges go out to 400m and bullets are dangerous than in most Shooters.

There are 4 availabe gametypes:
Clear Area
Clear Area Night
Fast Assault
Night Assault

Clear Area is split into 5 areas, each one must be cleaered of enemy before you can proceed to another. Start area is random, after that each area is chosen by the player by entering it - check your map. Inside each area there is a random playtype - "Clearance" (enemy randomly placed throughout area), "Strongpoint", enemy are all around one building (or sometimes 2), and "Counterattack", as "Clearance" but the enemy will aggressively defend and counterattack. Even without counterattack, all short ranged enemies will defend around their area.
Player starts with random weapons, one longrange, one shortrange.

Night missions are the same, but with reduced vision and shortranged weapons only.
Player starts with random weapons, one shotgun, one smg.

...

... infact ...



There's a readme ... so read it ... there's also a license on install with tips ... read them too ... also there's info in the game on how to play it ... it should all be fairly straight forwards ... hopefully. And if you spam me with issues which I've listed in the readme ... I will kill you ... to death! (flares nostrils)

Many thanks to orb for the bandwidth. There's a full list of credits in the readme, and also in the Credits page of the game which details pretty much everything I've used in constructing this.

Download page.
http://yorks.deta.in

And the direct link.
Dubious Demo 2 (125mb)
Windows only ... I'm not fashionable enough for a Mac ...



I was about to go to a little country pub to celebrate ... but there's black ice all over the drive and after a bit of wheel spinning I'll be staying in with a beer and chilli.

Thursday, 18 November 2010

Splosh Screens, Selection Screens, Demo Screens

With construction of a vaguely working alpha demo in progress, I was hammering away at the splash screen license obligations ... a glance to irc and wtf everybody's just got sacked that worked on the engine tech I use ...

So, it's been user interface work recently, and additional gametype ... err ... types.

I'd been quite chuffed with my implementation of a randomized gametype, and had expanded on the initial idea. There were 5 open areas of a 2km level, the player was randomly equipped and initially randomly spawned at one area and each area had to be cleared in any order the player fancied. Random numbers of Enemy Ai were randomly spread through each area, and randomly armed with either short or long range weapons depending on what sort of view they had. Hiding inside a house = short range, view from a window or rooftop = long range.

I figured I could throw in a few more random ideas to increase gameplay, and so came up with strongpoints and counterattacks on top of clearance ... which happen ... randomly. Thus each area could be a standard clearance operation where the player had to hunt down each Enemy spread throughout the area, but now it could also be an assault against a randomly chosen building crowded with hostile Ai, or the enemy Ai would come looking for trouble when they heard allies shooting ... but only halfway from their defensive position to player spawn area to prevent spawnkills. Regardless of random tactic type, all short-range weaponed Ai always counterattacked over a very short distance to prevent themselves being picked off at range, that way long-ranged Ai would stay put to provide supporting fire whilst short-ranged would be mobile around the goal node.


First attempt at Ai pathfinding in level

And I'd managed to fit in my "anti last man standing" idea, where the allied Ai swarm over the location of the last remaining enemy, thus preventing those frustrating "can't find the last bad guy to finish the level" type issues which can occur with such things.

I gave the player 3 respawns per area, and had dead Ai drop either ammunition, grenades or a small health pack. Each area took me around 20 minutes to play through, and taking down all 5 areas of the map could take 2 hours. So I made a "fast gametype".


Level Selection and Fast Game Mode

Fast gametype was a random strongpoint attack in a single area, with a slightly more beefed up number of random enemies to guarentee plenty of action. This made me think of a few variations for additional gametypes ... but ... y'know ... one thing at a time.

As ever, I found a gazzilion issues with everything I did, great swathes of script wrote at 5am that were never going to function properly in the cold light of day, and various other bugs that got stomped on and features that got relentlessly tweaked.

All this new stuff needed a user interface. Not just for mission selection, but also the type of instructions and info that you'd expect, such as what the controls are and what the differences between the various weapons are.

First Attempt at user interface that vaguely makes sense

I also thought that it might be a good idea to explain what the hell the whole thing is ... plus I then had to look through all of my stuff to see what I'd used. Now, I have attempted to do as much as I can almost all of the audio is my own - but I couldn't get a good fire/burning loop, but everything else is self done. All of the models are hamfistedly made, rigged, textured, animated by myself. I used various self shot photos for base texture templates and tiled them myself ... and then got the rest of the templates from on-line. Fonts and music weren't even worth my attempting and so were straight off licensed from the start. I haven't even looked at Fmod Ex yet, having just thrown in the audio dll. And that's all this stuff takes so much time.


Credit Page attempt 2

And then there were some annoying issues. My pathfinding is based on a waypoint resource, though it hasn't scaled well to such a large and open environment. I've got a level with a lot of changes in height and direction and the sheer number of waypoint style objects for the Ai to navigate around the whole thing has eaten 25 percent of my performance - which is annoying ...

But currently ... that's how my alpha demo will be going out. Afterwards I'll have to take a look at nodegrids and maybe other solutions as a replacement.

Also I need to do a bit of 2D artwork to "tart" it up a bit, and 2 of my buildings are still placeholders. And there's some functions hacking I think I might try as a performance test ...

But all in all, we're well on our way ... and ... allegedly ... I should be able to crank out a rough but playable demo full of issues by the end of November. Which is 12 days away ... awww hell ...