Defrag

MX518. Cheap, excellent shape and the tracking is as good as you'll ever need. I had an MX510 before that, and the MX518 is basically the same. Why mess with perfection? Also bought another of these for my work PC. Only downside is the stupid sensitivity changing buttons. I always disable those because they're a pointless gimmick.

I'd bin some of that 3D stuff, as a few of the stills look ropey. Basically, go through your site and be brutally honest about what your finest work is. Don't show anything else. I'll add a note to your linkedin because you were very dependable and level-headed on FF

On the topic of portfolio sites, this is an excellent article (I got the link from mapcore ages ago, can't remember who originally posted it): Your Portfolio Repels Jobs

The sooner folk ignore this clown the better

Very cool, but they've got to be very careful with that sort of 'protection'. I've read about similar things before and there was a lot of negative word of mouth about it. In particular, I remember reading about one game which included several deliberate crash bugs in the pirated version; the game soon gained a (totally unfair) reputation as being really buggy because of it! Furthermore, the more features you add, the bigger the risk of adding more bugs and/or introducing the sabotaged feature in a legitimate customer's copy. Subtly destroying a pirate's enjoyment of the game is pretty funny though, and I'm guessing since it's buried in the game mechanics it'll be a little harder for the pirates to find & fix. Not that much harder, though...

Cool stuff, but I noticed a few things: 1. Show bigger previews for your maps. One slim, blurred letterbox screenshot tells me nothing about what I'm about to look at. 2. Show bigger thumbnail shots, and make them include the full picture. Zooming in on one pipe in a thumbnail makes it a mystery guessing game I much prefer larger thumbnails that contain the entire scene (or at least a large amount of it). 3. Bigger screenshots would be nice. The stuff you're showing looks really nice, but the screenshots are tiny! Anyway, those are my nitpcks!

"- ugly color palette especially out doors" I agree that the outdoor areas aren't the prettiest (bland, flat green ), but I really like the rest of the colours. The cool prison greens + warm orange contrast gives me a nice HL2 prison nostalgic glow The sewers in particular have some really nice colours going on. Those areas strongly remind me of the colours found on various "abandoned" photograph websites. There was one tunnels shot on one of those sites that was an exact match, but I'll be damned if I can find it.

It's even better towards the end when you get new toys and can solve a lot of the riddles that were inaccessible at the start. I just finished collecting all of the riddles, and it was way more fun than it has any right to be The challenge maps are way more addictive than you'd think, too.

very good Also good to see the CV boys dropping in.

I'm not a fan of regen in most games, either. I like rollin' with my squad in BF2 and having to stick together so I can get ammo/health

I'm split between Hessi + Hourences' views. The biggest disappointment I had at university was that many of the lecturers appeared to know little more than the students. That may sound harsh and I'm sure most of them did know a fair bit, but it didn't come out in the teaching. Yes, we got a broad overview of many subjects and the lecturers were useful in other capacities (e.g. project management advice), but most of the bread and butter stuff was a waste of time -- there was nothing I haven't already seen covered on forums (gamedev.net) and in books. It's not like we had John Carmack waiting in the wings, working on mad crazy technology and pushing us on to do great things. We had a fairly basic syllabus and plenty of time to do the hand-ins. The best thing was that I had time to find my own way and learn about the things that interested me, but you can do that without going to university! I guess what I'm saying is that, when taught by folk who do not have industry experience and/or a deep understanding of the material, university could be a lot better.

If the menu system is anything like GRID, then I'd probably strangle someone, too. Really, really cool and slick, but so so very grating after about 3 minutes of it.

It's taken some of my L4D buddies! They're all on vent flying about in formation, honking like geese.

If you can, I'd recommend teaming up with some local (even national) games companies and asking them for their feedback on your syllabus. You can't really get much better than straight from the horse's mouth If your course has a chance of producing graduates they will hire, they ought to care.

This game kicks ass. The voice acting for the main characters (the Joker in particular) is really good, too. * Edit - Also, if anyone is struggling to get a feel for the combat, definitely acquire + practice on the first challenge map (you get it by doing riddler's challenges). Once you figure out the rhythm for striking, blocking and building up combos, it's a lot more satisfying. I was button mashing for the first couple of hours, but I just figured out that you just orient the camera and then press once per attack; this gives you much more control + damage. You can then build up huge combos that span the entire round and perform lots of critical strikes + throws etc. It's awesome

Time to take the covers off my trusty AH-1Z then

BF2 was awesome. I played it for about 3 years, it was so good that I kept playing despite all the bugs, crashes and imbalances, but in the end I got fed up of waiting for a patch to fix a lot of the issues and stopped playing. This is definitely welcome news. Time to get back in my chopper I hope it works on Windows 7 these days.

Just ordered it. I hope they fix that joystick issue because it's really irritating

Unplugged my joystick and it's pretty kickass. Nice to see a game with some real weight to the animations and combat; I particularly enjoyed gliding around and kicking people in the face

Tried the PC demo on steam and gave up because the camera keeps spinning. I think it's because I have a joystick plugged in, but seriously, wtf? Since when is it acceptable for a game to assume you're using a joystick with no option to choose your controller ingame? Really stupid oversight on the part of the developers; I imagine it's a holdover from the console version that's not been suitably tailored for the PC version. I get really annoyed by niggles like this -- I'm not going to buy a game that forces me to go down the back of my PC and start pulling out cables every time I want a go.

I loled.

After graduating, I spent about 6 months grinding away trying to get a job. Curiously enough, a little over 18 months later, I've been fortunate enough to be helping out on the other side of the interview table (albiet probably only because I do a fairly uncommon programming job, so I only have one person in my department who is senior to me). It's interesting to see both sides. Unsurprisingly, my advice mirrors Carmack's (even though I am but a peon in comparison). What follows is more programmer related than art, but someone may find some use from it. Use your time wisely Remember that when in full time education, you have a shitload of time to burn. I reckon I spent only 10-15% of my waking hours engaged in university work; the rest of my time was free time. I could do whatever I wanted with it. Now, you can spend it playing games, getting drunk, watching daytime TV etc... or you could spend it improving your skills. Remember that, at the end of your college/university period, there will be scores of graduates just like you with the same coursework deliverables and accreditations, so what do you have to offer that distinguishes you? Learn through doing Make lots of stuff. It doesn't matter what it is, who it's for or why you're making it; just make it. You learn so much more when actually making stuff compared to theorising about it. Theory is definitely important and it's worth doing a degree etc., but you only cement and further your understanding through doing. In my first year of commercial programming (9 'til 5 every day) versus 6 years of sometime coding (maybe a couple of hours every other day), it felt like I learned just as much again. Code that I had considered to be good a year ago suddenly appeared, in hindsight, to be a pile of steaming shit. And long may it continue. To further underline why 'doing' is important: I.e. the more time you spend doing something, the better your chances are of becoming good at it. Practice makes you better. If you want the job badly, then you can improve your chances by always creating new works. You could set yourself a goal of "implement small feature x in my program this week" or "create, unwrap and texture a new mesh this week". I personally got the most out of my learning when I was setting repeated, incremental goals each week. Finish what you start Don't worry about perfectionism. It's easy to start thinking that everything you do and show to prospective employees must be perfect. That's not the case. You should endeavour to finish what you started; even a rough, finished version is better than a polished fragment. Companies understand that you are young, raw and will require support, mentoring and encouragement. The code I submitted that helped secure an interview should have by all rights been set on fire, detonated and then buried in a lead-lined mine shaft. It was pretty horribly designed, but it demonstrated that I could finish a project. In my opinion, the most important thing is that you can demonstrate that you get things done. Junior members of staff are not hired as read-made geniuses who slot into the production machine firing on all cylinders. Yes, these people exist, but they are few and far between. As long as you demonstrate that you're a decent person, you have potential and that you will find a way to achieve your goals, you have a chance. The reason I say this is that, in the modding scene in particular, I encountered way too many people who had portfolios full of half-finished levels, models, texture sets etc. The moment I see this I automatically think "flake". The hardest part is finishing something; pulling things apart and optimising them, then rebuilding them. Reducing the texture memory usage, fixing alignment and clipping issues etc. There is little creative fulfilment involved in this step, there is no artistic merit or craft in fiddling with it and there will be nobody to offer you a compliment on your collision and clip optimisations. It takes guts, pure and simple. Any time I saw scores of "cool looking room in never finished level" or "half an awesome gun model" images on websites, I just closed the page. Do not want. If you can't even finish your own personal work, work that involves a subject matter that is of your own choosing, then why would a company have any faith in you finishing something you may not have a particularly strong affinity for? Chances are you won't be working on Rage or Bioshock 2... If you can't find a way to finish to a standard you're happy with then limit the scope. Remove functionality from the program, cut out areas of the level or reduce the complexity of a scene. Remember that once you finish the first version, you are now in a good position to iteratively improve it Finish version 1 and go from there. The sense of achievement from finishing something is also a great feeling! It's much better than leaving the work to languish in "C:\work\wip\", never to be viewed again. Keep up with new technology and techniques Read a new book. Learn a new language. Read blogs. Write a blog. Write articles. Discuss stuff with like minded folk. I've learned a lot of really interesting and cool ideas from blogs; my google reader has about 50 entries in it, including programming, art, modelling and technology blogs + podcasts. Most only get updated once every week and a lot of them are sporadic or inactive, but you get the odd gem now and then. If you spend a few hours a week reading, it will be a few hours well spent. MOD MOD MOD Yeah. I've already talked about this at length before, so I'll spare you the rant again. Mods are basically smaller versions of real companies. You have the same people issues, conflicts of opinion, fun times, hard stretches etc. You can make mistakes in mods and then learn from them. You also make a shitload of contacts if you're a decent guy. Contacts and string pulling can be instrumental in landing an interview, so don't pass on modding. My modding with FF was instrumental in getting an interview; it distinguished me from a lot of my peers by the way of proving that I have the passion to make something in my spare time. I guess different companies view modding in a different light, but it was great for me. Create a non-generic CV CVs should be grounded in what you've actually done. Don't smother it in buzzwords or over-egg the pudding. Don't oversell or overcomplicate something you've finished to try and make it look better than it is. Don't pad your CV with terminology and 'skill' bullet points that add nothing. My first attempts at CVs both suffered from these problems -- I was simply spamming phrases, technologies and buzzwords instead of talking about what I'd actually achieved with my most important skills. Bullet point-driven skill-heavy CVs tend to be impersonal and anonymous. There is nothing to distinguish one from another. E.g. "Fluent grasp of C++, Direct3D, OpenGL, TDD, OpenAL, LINQ" = noise. Compare that to, "In my spare time, I developed a small C++ game featuring ; the rendering was implemented using D3D using features, including to drive a particle system". I.e. give your skills with plenty of context, not as some detached list of headless bullet points. Luke Halliwell has some really good articles on CVs, so I'll redirect you to his post rather than ape it. Don't talk a load of balls This is more for programmers, but when it comes to interviews, less is often more. Be prepared to have your CV grilled. If you talk a good game on your CV, be prepared to be called out on any and every detail (this is why you should never embellish your CV with skills you don't have...). You should think about your decisions and be able to justify them. E.g. if someone asks you why you used language x for assignment y, you should be able to say why. "Since the application wasn't required to be fast, I used Java as it freed me from having to track memory allocation, meaning I had more time to concentrate on feature development" is better than "because I always use Java". If you cannot justify yourself due to making a poor decision and you learned something from the process, this is the ideal time to talk about it. It's not the ideal time to defensively trot out excuses. Self-awareness and the ability to reflect on projects (successful or otherwise) are very important things. If an answer should be explainable in 3 sentences, use 3 sentences. Don't keep on talking until your course is gently steered on to the next topic. There's nothing wrong with being nervous, but try not to ramble because it just gives the impression that you're vainly groping for the right phrase. If you don't know the answer or you're unsure as to whether your point was understood, just say so. It's much better to say "does that answer your question?" than to talk for 3 minutes solid, hoping you ticked some box. Finally, have faith in your own opinions. Don't flip flop based on what you think the interviewer wants to hear. Bosses aren't interested in hearing their own opinion parroted back at them -- they want to hear what you think. If at first you don't suceed Try try try again. If you attended an interview but didn't make it, politely ask if the company can offer you any feedback on your application. Then, work like crazy for months and re-apply when you feel it is appropriate. It took me many months to get my foot in the door, but if you genuinely want it, you can most likely beat the door down through sheer persistence.

I'm still at Realtime but I'm shifting roles. Going from a Software Engineer in Test => Software Engineer. So now I'm gonna be writing game code, hurrah!

That's a fair point, FrieChamp I did watch Carmack's keynote at QuakeCon, btw. Interesting stuff as ever -- particularly the bit about the back end of Quake Live being a train wreck. I did not know about that!

I doubt they are publishing the game in the traditional sense. Lots of companies partner with EA as a promoter/distributor; they're very good at it. If it's good enough for Valve...