Syndicate co-op and sp = different games? What?

I, like many, have been playing Syndicate quite a lot since it got released. I was a skeptic to begin with, but Jeff's review pushed me over the edge, and to be honest it's the best pure first person shooter I've played since the original FEAR. This is a game that really gets gunplay and the flow of movement, and I had just tons of fun playing through the campaign, and still having tons of fun now in co-op. It's a remarkably unpretentious game, with a pure focus, and it comes out like a real well cut diamond. It's just one of those games that knows what it is and trims away anything else.

So after a particularly nice online session today, I actually got kind of mad (I never get upset about games, right? ;-P).

The thing is, people love to knock this game's single player campaign. Penny Arcade even went as far as to call the campaign and the co-op game "two separate games" asking "which came first" as though the difference is huge. I just can't wrap my head around that point of view. The entire reason Syndicate is a game that stands up to scrutiny is because its mechanics, report and moment to moment gameplay are incredibly well crafted. This is a game where the story as a whole to be totally honest was not part of what I paid for. Of course it WAS, but in enjoying the package, I quickly came to love simply moving about and using the weaponry. That is what Syndicate is about, not the hero's journey.

So, please, critics, explain to me how a single player game, and a co-operative version of it with identical mechanics, can see such disparaging opinions? Are people so unaccustomed to playing alone that the mere introduction of other human beings is enough to wholly elevate the entire experience to the point that some will call it a whole other game? You are still shooting the same guns, at the same AIs, in simpler levels with less production value. Is it the progression that's doing it for you? Is that process of filling up all those progress bars what makes it a "different game"?

I just don't get it. It's as though the critics don't fully understand what it is that they are criticising; I know I can't have been playing the same game, because Syndicate plays 100% the same in both modes, barring a few more progress bars to fill.


If you were curious about getting into DCS A-10C...

...hop on in. The water's fine. :)

I know there's this kind of macho attitude where the complexity of the sim is like a badge of honor, but truth be told you don't have to know half the shit that's going on in the cockpit to join a flight online and have fun. In fact, I'd say the biggest fun I'm having with the game right now is flying with other people and just enjoying the cooperative experience. It's really quite cool.

Most recently I've been flying a Ka-50 in missions otherwise dominated by A-10s, and it's fun to try and coordinate or help each other out in such different aircraft. It goes without saying that teamspeak is a must.

I can't do much but heartily recommend the curious, or those who picked the game up and cooled on it, to join the community at and get into a multiplayer session or two; You wouldn't believe how friendly and lenient people are, or how willing they are to help when you have worries or questions.

These are games where learning and improving pretty much *is* the game; I'd go as far as to say it's close to Starcraft for me, or Street Fighter 4, or any other technically dense game. That moment where you spot a target and put a missile on it just as your wingman does the same on another adjacent to it, you feel like a real boss.

So come on over to FSF! We need more giant bombers ;-)


God damnit Vinny, NOLF is NOT like Austin god damn Powers

Vinny needs to go replay NOLF and NOLF2. Yes they are goofy, but they are not straight up goofball. I fucking hate the Austin Powers movies, and NOLF are some of my favorite games ever made. Since when did colors, globetrotting, gadgets and fake british accents go out of style Vinny? Tell me!

I hope to dear god Monolith revive NOLF at some point. Been playing Gotham City Impostors a lot lately, and that game proves just how damn good that studio can be when they loosen up a bit and have some fun.


Notch, Tim Schafer and the public funding of video games

First up, if Notch and Double Fine can work something out, it feels like a pretty big deal. One thing is doing a Gearbox and purchasing game assets to bolt together a "game" to publish, another is to take profits from an indie game and funding a totally separate AAA studio. I know Notch is "new to this huge money thing" and probably is a lot more whimsical because he can, to an extent, afford to, but it doesn't make it any less stunning. That is, if it happens.

Now, time for a potentially stupid discussion.

I know this joke was thrown around a bunch, but somewhere in the back of my head a studio like Double Fine starting Kickstarter projects with some proper publicity behind it feels like it just might actually work. I'd pledge so many dollars to have games made. Being a consumer is so reactive so much of the time. We are given a palette of games to choose from, and we commit our dollars to them after the fact, so to speak. We hear stories of games that studios would like to make, but can't because publishers don't believe in them, or some other similar story.

Now with digital distribution and the mechanisms for crowdsourcing or public funding pretty much formalized, would it be that unthinkable really for consumers to be able to "vote" with their dollars for the games they would like to see made, rather than have to pledge their dollars after the fact and rely on an industry of census takers to decide what the public wants so as to justify the investment?

I know this would likely result mostly in project that wouldn't happen, but at the same time, that's how things are already anyway. In terms of value to pledgers, being able to play a game you would like to, as well as being credited as a pledger would be more than enough, and when the game is done it would still be for sale as usual, so everybody wins, no? Perhaps royalties for high pledgers? I dunno, there are probably bibles of legal ramifications.

But still, is crowd funding games given a properly announced and publicised campaign and a simple reliable payment scheme really be so unthinkable?


Messing with DCS Black Shark 2

This is what going from the A-10C to the Ka-50 feels like
This is what going from the A-10C to the Ka-50 feels like

I've had a lot of fun with DCS A-10C, but it was the second DCS sim I bought. I originally got Black Shark when it was released, and immediately hit a brick wall with it. It was easily as complex as the A-10, everything was labelled in Russian, none of the tutorials were interactive, and in general the whole experience of learning was really painful, to the point where I just decided I wasn't up to the challenge.

Now, having gotten to know the A-10 fairly well, and given that Black Shark just got its 2.0 upgrade making it multiplayer compatible with DCS A-10, I decided to give it another spin.

On the upside, Black Shark 2's interface is generally analogous to DCS A-10's, so the mission editor etc are all the same. Additionally, the voice work has been translated to English, along with all the cockpit labels; This might seem like a copout, but I honestly didn't sign up to learn Russian; The language is a stylistic choice rather than a real facet of the aircraft, so I welcomed the change.

The tutorials were still a bit shit though, if not even worse this time around, being replaced with a bunch of grainy videos that refer to videos that don't even exist (yet..?), so back to the manual, and back to the notebook.

Remember! You must think in Russian!
Remember! You must think in Russian!

The thing is, knowing how to cold start the A-10 made figuring out how to cold start the Ka-50 kind of a breeze. I felt like such a badass going into that cockpit and knowing what battery ac/dc, the inverter, what the APU did and so on, even without looking at the manual I managed to get the engines running and fumble my way off the ground (and into a building). This was already aeons beyond how I fared with Black Shark 1, so it was very encouraging!

Second, I now possessed a nice HOTAS stick/throttle set, as well as the TrackIR5, ready to assign all the useful axes and buttons to. All in all, I felt like everything was there for me to figure out how to fly the thing.

Well, let me tell you, if it wasn't obvious.. For as complex as the A-10 is, the aerodynamics and general maneuvering of a jet is a fairly intuitive thing. A helicopter is something entirely different. Whereas flying a plane around is something you can figure out in minutes, simply making a helicopter stay still is a challenge. The Black Shark has thoroughly humbled me.

Ridiculously ugly things.
Ridiculously ugly things.

A big part of the difficulty is understanding the difference between an inherently stable platform, like a fixed wing aircraft, and a totally unstable one, like a helicopter, where changes in attitude are exponential, and you must learn to compensate in reverse for everything you do. The simplest comparison I can think of is balancing a chopstick on your palm. The "big deal" with the Ka-50 is its degree of automation, however, and god, this thing has one of the most aggressive autopilot solutions I've come across. It's all there to let you perform the roles of both navigator/pilot and weapons officer (whereas the AH-64 has a crew of two to do the same), but the result is an aircraft that feels unusually argumentative.

Theoretically, this means you have a vehicle you "order around", rather than fly by the seat of your pants, and the shift between governing what the helo should try to do, versus what you want to do in the exact moment, can be super frustrating. In the A-10 you may have engaged the autopilot to hold your current heading, but when you take charge, the AP disengages itself. Not so on the Ka-50. You'll be heading in one direction, then try to bank to the left. Forgetting to hold the trimmer button, you come out of your turn with a helicopter that gently urges you to bank to the right, back to your original heading. The AP is designed to constantly be engaged, with you rather temporarily disengaging it during a maneuver before re-engaging after, to give the AP a new set of "orders".

But I really want to learn how to work around this stuff, even come to love it, because as a weapons platform the Ka-50 is kind of amazing.

First of all, a helmet mounted sight (HMS) system lets you simply look at a tank to slew your missile/gun onto it. In the A-10, this process, while not complicated, is book-keeping 2 or even 3 sensors. In the Ka-50, you simply look at a thing and push a button. By constantly slaving the gun to the HMS, you can track a moving target with your head movement while shooting at it. It feels like total science fiction. If the A-10 gets the HMS (as rumored), that plane is frankly going to be terrifyingly effective.

Additionally, there is a directness and simplicity to the Russian design that makes the A-10 seem a little convoluted sometimes. The sensor slew in the A-10 feels endlessly slow when compared to how quickly the Shkval targeting pod lets you scan and move the cursor on a target. While the A-10 TGP is clearly superior, the Shkval still "feels" better to use, and less argumentative than the Litening pod.

I'm going to stick with the Black Shark for a while; I miss the A-10 constantly, but there is something "dirty" and alien to this Russian helo that really makes me want to feel confident in it.


Dubstep soundtracks

I'm not AGAINST dubstep or anything, but man has that genre become easy to define, and man does most of the stuff sound within two degrees of exactly the same. With the amount of dubstep in games these days, those games have become incredibly easy to date. I keep thinking 2 years from now we'll remember those games and be like, damn, that music sure was dumb, all with the same overcompressed snares and weasly kicks over Massive vowel oscillator "bass". There's barely any fucking bass in that music anymore, just a constant tuned sine sub ducked by the kick, bleh.

Then again, who the fuck cares about games older than a year and a half anymore.


Learning to see

There's a totally underestimated challenge to playing DCS A-10. I have a looong way to go, but I want to share some of the things that have made me feel more confident, and also some of the things I just think are plain cool about it.

DCS is a "game" on several levels. First of all, obviously, you are given tasks to complete. You can bumble your way through some of these and come out with a mission complete. My first few campaign missions were like that. Just remembering how to fire a maverick and using mavericks until i had none, then throwing some mk82s around and pretend like i knew what i was doing, all the while largely ignoring the JTAC or radio chatter, because damn if I could understand a word of what those dudes were saying anyway. In this way, you can kind of subjectively enjoy the experience, but you will feel like an idiot all the while you're doing it.

This is kind of "it" with a sim like this, I feel: The REAL challenge is self-imposed; Can I do this kind of stuff correctly? Can I be legitimately good? Merely getting by will never be satisfying, but with no real "scoring system" beyond a binary success/failure, the quality of your skill is largely something you either judge yourself, by the goals you set for yourself and how efficiently you attain them by your own standards.

This is cool, because paired with a simple understanding of the mission editor you are allowed to ramp up the difficuly and thus the learning curve according to your own standards. This is a game that, right out of the gate, has no problems thoroughly humbling you, and as a result you get this kind of fear of failing. I spent weeks just starting up, taking off and just flying around, never mind learning any of the avionics properly beyond that. Just getting off the ground felt like a feat.

(note. I'm typing this on my laptop; When I get back to my gaming box I'll edit in some screenshots for illustration.)

The mission editor

The mission editor can look incredibly dense if you boot it up, but all you really need to know to make some scenarios for yourself and your own practise routines is how to create an A-10, outfit it, put yourself in it and create some other units to interact with. So, step by step:

1. To scroll around the map, right click and drag. To zoom in and out, use the mouse wheel. Around the map are a bunch of airfields, most marked with a long arrow along their runway and a geomagnetic heading, as well as a name. Pick one you want to start from.

2. On the far left is a vertical row of icons representing various unit classes. Pick the one that looks like a fighter jet. Then click on the airfield you picked on the map. An icon marked 'A' will appear.

Gallery image 1Gallery image 2Gallery image 3Gallery image 4Gallery image 5

3. The default plane at any point is the last one you had selected from the plane group. The default at the start is an USA A-10C, which is what we want. On the top right is the property inspector for the currently selected mission object, which will list the group the plane is assigned to, the plane type and more. From the "skill" dropdown, you want to pick "player".

4. At this point, you've already got a mission that will put you in an unarmed A-10C mid flight over the airfield of your choice. This might be all you need to have some simple flight. To fly, click on the blue check mark button on the middle left.

5. To change the initial state of your plane, for instance setting it up for takeoff from the runway, you need to select the plane icon again, and look at the very bottom of the right column. This contains 4 tabs, and the ones we care about are the first two; the first is the "waypoint" tab, and the second is the "ordnance" tab. With the plane selected, the waypoint tab will be containing info on the initial position of the plane. From the "type" dropdown, given that the plane is near an airfield, you can pick "takeoff from ramp" if you want to cold start the jet, or "takeoff from runway" if you want to be ready for takeoff immediately. In either case, the editor will move the plane to a position that makes sense.

6. Clicking the ordnance tab will bring up a full screen view with a vertical list of various loadouts you can pick and customise. This is a pretty intuitive screen; Just pick one from the list, or right click a hardpoint to change its load.

7. Bam, you have a plane with guns on it. For some simple practise, take off and shoot up your own airfield ;-)

8. If you want "real" stuff to shoot at, mess with the other object categories and create some tanks or trucks. Of course scripting a proper mission is much more involved, but this should get you started. Also, don't forget the "encyclopedia" you can bring up from the top menu bar. Very handy.

On being inside and being outside

There's a lot going on inside that cockpit, and while you're juggling your targeting pod, map and ordnance, it can be easy to lose track of what's going on on the outside. Most MFD pages have an attitude indicator in the lower left of the display to help you make sure you're not pointing at mother earth while you've got your head down trying to move your TGP onto some tank to your west, but that doesn't necessarily aid your sensory awareness to any large extent.

One term I picked up from the book Warthog was the dichotomy between being "inside", where your attention is focused on the interior of the cockpit, and being "outside", where you are actively looking out of the canopy while maneuvering. Let me tell you, no manner of careful use of the moving map display is going to make you as aware of where you are at in relation to your target as simply looking out the window.

While these two will blend together sometimes, I feel it's helped me a lot to consciously move between the two. For instance, I'll be "inside" when I'm observing the area, looking for targets, setting up mission markpoints for targets I want to hit etc. This typically takes place at "angels 15" (which is a fancy way of saying 15000ft) or higher, where I'm relatively safe from most AAA, and I can set the plane in an autopilot-assisted orbit, letting me focus on the office work of observing and preparing. Then, when I'm going in, I've already done all the time consuming work, and I can do most of my attack work through the HUD, assisted with glancing at the TGP. Ideally, once you're "outside", you shouldn't have to be doing any complex strategic decisions, only split second tactical ones.

A key here is that no matter how well versed you are with the HOTAS controls, when "inside" you will still need to click on buttons with your mouse. You do NOT want to be doing this while things are firing at you. Knowing when to be "inside" and when to be "outside" is probably the single best advice I can give. When you've been circling a town for 20 minutes, it helps to have a good visual idea of its layout beyond the map.

From markpoint to waypoint

The first thing you will be doing when attacking an area is to make sure there is no active mid to long range AAA. The worst thing you want to conceivably have to deal with is machine gun fire, and you'd rather not deal with that either. This is why the A-10 carries long range mavericks, so you can get rid of all that crap before you drop your bombs or apply the gun. The thing is, when you're looking for AAA, and you spot a Shilka or SAM site, are you going to attack immediately as soon as you can, or are you going to build a comprehensive understanding of the situation?

When you are working with others in a multiplayer game or with JTAC or other allied support, you'll have a lot of assistance in building this information, but in this case, the challenge is in handling the situation alone with no support. Could you do it?

What I like to do is hold off my attack. I'll use my targeting pod and get a nice coordinate that I'd be happy to use for a firing solution, then I'll hit TMS right short to create a "markpoint". Markpoints are "disposable" coordinates stored in your CDU, sequentially labelled A through Y, with Z being automatically updated from your current position every time you fire a weapon. Every time you create a new markpoint, the next available ID in the sequence is used, so your first is A, then B, then C and so on. If you should hit Y, the sequence will start over, overwriting A and so forth.

When you've created a markpoint, your CDU will display its data. From here, you can copy that markpoint data into a mission waypoint. Waypoints are more permanent, and you can label them yourself so you can remember what that point represents. On the CDU when looking at a markpoint, one of the options on the right looks like a question mark next to a number, for instance ?8. When you hit that button, a new waypoint with the numeric id 8 will be created. The default name for this waypoint is MSN8, but you can change that easily by typing in a new name on your scratchpad (the keypad up front or on your lower right console) and hitting the button next to the existing name. Bam, you've created a new named waypoint from your markpoint.

Gallery image 1Gallery image 2Gallery image 3Gallery image 4Gallery image 5Gallery image 6

(Sidenote, any field on any display with a pair of brackets [] next to it is a field you can input your own data in via the scratchpad. Type something in, then hit the button next to the brackets.)

Now, by turning the left rotary below the CDU from "FLT. PLN" to "MSN" (the topmost position), you can cycle through your created waypoints just as easily as any other mission waypoint. Say you've spotted an artillery line. Create a mark point in their midst, save it to a waypoint, name it "Art". Spot a Shilka? Mark, save, label it "Shk1". Spot another? "Shk2". Now, when you're attacking just set your SPI to default to your current waypoint, cycle to the targets you want, and watch your TGP and Maverick automatically slew right onto the targets. From here on all you really have to do is walk down the list by priority. It takes so much work out of the moment, and gives you a clear perspective on the moving map as to where you are in relation to your targets.

Customising the MFDs

There are so many god damn options per MFD screen, but one of the built-in features of each MFD is changing what screen each button on the bottom row will take you to. To get to this screen, hold in one of the buttons for a second. This takes you to a blank screen with every possible MFD page listed on either side. Pick one, then push the button you want assigned to that page. Sometimes you will have to do this. For instance, say you take fire and lose your right MFD. If you want to look through your maverick seeker, you have to reconfigure the left MFD to display the MAV page. I typically sacrifice the status page first.

Get used to redundancy

The A-10 is kind of shockingly tough. It can take punishment that you wouldn't believe. I made a successful landing the other night without undercarriage. That said, things WILL stop working as you're taking fire. Coming out of a mission unscathed is a matter of both skill and luck; Sometimes you'll have failed to spot that BMP and take machine gun fire that somehow manage to take out your hydraulics. Maybe a tank manages to get some MG rounds on you before your bomb hits. It happens.

The good news here is that for every thing that might break, you're likely to have some system capable of filling in. With all the fancypants stuff you get through the moving map and TGP, it really helps to understand the more "boring" systems, such as the heading indicator (the compass circle below the artificial horizon sphere on your center dash). When you've lost your CICU and CDU, being lost without a way to navigate is a real pain.

Even better news is that it can be quite fun to fly this way. Flying mostly visually is a real challenge, but with some practise you feel like a real boss making your way home with no HUD and making a half-decent landing.

Bottom line though, is it can be real embarassing to only have lost your MFDs and feel incapable of making your way home. You can fly home and land just fine, but you have to challenge yourself to do it.

TGP and MAV slewing efficiency

This is an obvious one, but remember to zoom the TGP out when you want to slew faster, and zoom in when you want to slew with more precision. Conversely, slewing the Maverick seeker can be a real pita; You only have two degrees of "zoom" (in reality a wide angle and a tight angle), and the slew rate, while adjustible, is never perfect.

The trick here is to do all your slewing with the TGP, designating a SPI, and then slaving the maverick to the SPI. This lets you effectively target mavericks with the TGP, switch to the MAV page, then "poke" the mav seeker with TMS up short to make it lock on to whatever it's pointing at. The less you have to slew the maverick, the better, if you ask me.

Conserving energy

This is probably a bad metaphor, but a lot of flying in DCS A-10 feels like doing halfpipes in Skate. I like to think of every dive as the start of a climb, so you need good speed on the way down, enough to maintain speed when you're going back up. In the same way, when you are turning, you are bleeding energy, which is unlikely to leave you with enough to make a good dive, which again is going to make climbing a pain. This is bad when that tank you missed is shooting at your ass.

I don't have any real "tips" here but I think it helps to keep this in mind,and try to keep a good speed at all times, around 200kts. Dropping below 180 at a low altitude is going to leave you very vulnerable. Practise turning without losing too much speed, and using energy from a dive to power a smooth climb. Flying will feel better, and you'll take less fire.

On the note of energy, flying with a full complement of ordnance and a full tank is a pain in the arse. For the sake of your own sanity, fly a little with no ordnance and little fuel: You'll be shocked at the difference. This is more impetus to use all your ordnance before returning to base, as landing lighter gives you more leeway as to your landing speed.


So, let's not buy any more inXile games

Oh Choplifter HD... Bad shooting, time limits, boring levels, no personality of design whatsoever, and fricking zombies on top of that. Locked at 30fps. If there was a way they could fuck this game up, they exploited that opportunity to its fullest.

This game is a layer cake with a fundamentally fun design at the bottom, and a series of craps taken on top of it. Two thumbs down.


EA, Origin and Steam

I think EA's gamble is fundamentally misguided. I can sum up very easily why Steam is my go-to vendor. I've already committed years ago. I own hundreds of games on that service, and my Steam account is intractably bound to my online identity, not just publically, but in terms of the experience of moving from one computer to the next, and not having to worry about the game collection.

It's a very effective and admittedly kind of devious lock-in tactic, much like how my Google apps account is now how I publish Android apps, purchase Android apps, store my contacts, my email, my work documents... My Google account kind of IS how I use the internet now, and my Steam account has become how I use games on the PC.

It goes beyond the sale of the game, and comes down to the game's effective integration with and inclusion in my lifestyle. I've bought duplicate copies of games just to have them on Steam. The convenience is just too great a factor.

Origin is not only a clumsy piece of software, but it carries the ambience of cruftware. It's not necessarily poorly made; It's just that it is so obviously and shamelessly attempting to usurp a position already taken by a vastly superior product. Every time I boot up Origin, I do so begrudgingly; "This is so unnecessary".

I kept Impulse around for Sins of a Solar Empire. When that game was made available on Steam, I got the Steam version and ditched Impulse. When I stop playing Battlefield, I'll ditch Origin. I have no interest in Mass Effect 3 on PC *because* of Origin at this point. It's one unwanted step too many, and I can't imagine Origin is going to improve EA's PC sales of any game that isn't Battlefield 3.



Ace Combat on the 3DS is actually, very, very nice. It strikes a very happy balance between what made the old games fun, and what few good ideas Assault Horizon on, er, other consoles had. Two thumbs up from me.