|
IN THE BEGINNING: History- March 18th On 17th Jan 1998 my brother decided to buy a Playstation. At the time I was very sceptical, considering that games were 40 quid a go. However, having spent the last couple of years playing quality PC games like Doom, Duke and Quake, to name a few, I thought, let's see what this thing can do. When we loaded up that dino program, the proverbial jaw hit the floor. The other demos on the disc were also very impressive and I couldn't believe that this machine was capable of so much (I mean 33 Mhz, 2 Megs Ram, 3 yr old tech). So how come I now own a Yaroze? (Long) I subscribed to the Official Playstation Magazine and heard about this Net Yaroze thing. At this time I was in my fourth year at Strathclyde Uni, studying Computer Science (good course too), but at 550 smash I just couldn't afford it. Incidentally, I wouldn't have had any time to use it and we had just purchased a new playstation, but that was my first thought about owning a yaroze. My initial interest in games programming only surfaced in the second year at Uni where I was spending copious amounts of time web-surfing, and it just seemed the more I read about games and the industry, the more it started to appeal to me as a possible career. I mean, from my perspective, a career in the games industry vs a career programming databases - what would you choose? So I decided to write a game for the PC, using Borland C++ for DOS. Using good old Borland C++ I learnt the basics of 2d game programming, but I must admit that for six months effort the game I produced (called Vyrmain - don't ask) was utter mince - a half finished shoot em up effort, a truly awful thing, still lurking on my PC somewhere, with source code I think. After that effort I basically gave up on the idea of game programming, that was until I obtained Visual C++ in 3rd year. I spent all of 2 days skimming over Direct X 3D and thought hmmmm... not for me, not at the moment anyway. I wanted to program a game for a standard platform (ala C64, Amiga). So third year was a non-event is terms of writing games - although playing networked quake was good - trying not to get caught was even harder. Then in fourth year, the individual project came along. We had to give a list of six preferences from about 100 possible projects. I had the following list :-
The reason Connect-N was only fourth in my preference list was because I was thinking about an interview situation where " What did you do for your final year project?" - " Ah, I wrote a wee game" would put a dampener on things, and also the man who was supposed to be supervising the project taught Scheme(Lisp) - imagine writing a game in that. But guess what, I was lumped with the Connect-N monstrosity after all. Oh dear - I was depressed just thinking about it. However, after discussions with the project supervisor it began to sound better and I didn't have to use Scheme; I ended up using JAVA having thought about C, but I wanted an excuse to learn JAVA. Six months later, and after considering deferring UNI a couple of times in the process, I finished my coding, wrote up the final report, handed the damn thing in and - drum roll - the project acheived a mark of 83%, the HIGHEST in the year. But guess what, the program wasn't even that good - yes, it was a variation of Connect-4 using some nifty techniques, but still, there was a helluva room for improvement. It achieved that mark down to the whole project - the report, the methods used, the testing approach, etc etc. But let me give you some advice - do not jump into coding without proper research and planning - At the beginning of Connect-N I done this (going against good practice), and my hash bash approach (call it eagerness) meant that my progress ground to a halt. I even considered repeating the year because of the brick wall I had hit. However, I scrapped version 1 and started the proper development cycle the way I usually do so, with proper planning. That's not to say this approach is the way all projects (especially something as creative as yaroze games) should be done. There are situations (and deadlines) where the old hash-bash approach is the only approach - the key is trying to avoid those situations. After exams etc, and after I got a degree, I thought, time to look for a job. Did I consider the games industry at July 98? nope. I decided I needed to take things fairly easy, feeling burnt out after four years at uni, before looking actively for that graduate job. So in August 98 I took a six month contract with Scottish Power as a Business Acceptance Tester (pay was poor, but the job was only 10 minutes walking-distance from my house). Six months later, I was actually in a position (as of Jan 99) to start a proper career in the Testing field (hell, I got offered a 3-month contract with a reputable company to do testing - with damn good money - but the job just wasn't right and so I took some temporary work helping in a lawyers firm. At the end of that job I had to take stock of where the hell I was going. I had a damn good degree, I now had some valuable work experience, so what do I now do. I'll finally tell you what I do - I write out a 300+ cheque for Yaroze early February and then think what the F*** am I doing. Can I really consider a career in the games industry, after all I ain't a coding genius, but am I good enough to make it (even as a Tester to begin with?) Late Feb 99, after some nervousness I walk by my door and notice a sheet of paper on the ground - AMTRAK - dated yesterday - whit, nobody had noticed this vital bit of paper - hmm, so I have to get the guys to deliver it next day. At 1pm I get the NET YAROZE, open it all up, fiddle about a bit, wondering if I should dive straight in, but I read the manuals a fair bit then look round the back of the PC (A 4 year old DAN P75 - damn excellent machine - highly recommended (DAN that is)) only to find that I need a damn 9-25 pin converter - DOH!. After finally getting a converter I manage to plug everything in, and turn it all on, seems working. Ok, now I try to download the demo program hello world and siocons refuses to work. After 20 minutes of manual madness and swearing profusely at Siocons, CodeWarrior, PC, yaroze and TV, I discover that the cable wasn't fully in - DOH!. (Having swore blind I checked it twice before). The machine then works, and the demos are pretty impressive - the dino demo code is hugely convoluted and I totally panic at the amount of obscure funtions involved and trying to understand them in the manuals. I wish SONY had included a fully documented dummy's tutorial, cos I even found a lot of functions and terminology pretty damn confusing to begin with. Anyway I obtained a few games from members sites over the next few days to guage a feel for their quality. I had already played all the net yaroze games from the playstation mag cover discs. Below is my list of current top 10 yaroze titles. To give you an idea of scoring - I rate Gran Turismo 10 and would give both Rascal/Psybadek/ about 3/10, in my opinion, taking into account these games are done in spare time and usually by one person.
So What Are My Plans
|
Site/Code/Graphics © 1998 Robert Paul. Rob's World |