Tag Archives: pc

The new NAS

PC parts for a custom NAS build

It’s close enough to 2023 now, and off the back of my QNAP being on borrowed time, it’s time to think about a new NAS. I’ve had a couple of NAS iterations over the years, starting off with a $200 HP MicroServer, then the aforementioned QNAP, and now, whatever I want to go with next.

I could, of course, go with another consumer-grade NAS like a Synology. Or even a QNAP if I am feeling particularly brave. Apparently, Synology units with processors that had the LPC CLK issue weren’t affected to the same degree as QNAP units were, because they implemented their LPC interfaces at 1.8V, preventing 2V over that circuit being an issue like it was in the QNAP units. That and/or in combination with a firmware update that somehow mitigated the issue, meant that a Synology unit would have been the more reliable choice at the time, and we wouldn’t even be having this discussion if I had purchased a Synology instead of a QNAP back in 2016.

Alas, I did, and we are.

Which brings us back to the original question: what kind of a NAS do I want in 2023, that will hopefully last 5-7 years, if not more?

I’ve been thinking about this for a while now. There are definite, distinct advantages to having an all-in-one unit like a QNAP or Synology. You get the smallest possible chassis, minuscule power usage, and the entire software experience that buying a QNAP or Synology gets you, which means that even if you’re going to run your own Docker containers and just use the software to manage your storage, it’s definitely a more cohesive, user-friendly experience compared to rolling your own OS. But even after all that, I’ve been drawn to the idea of building my PC to serve NAS duties for a while now.

Why? It comes down to hardware, both in terms of choice and flexibility.

Buying a consumer-grade NAS like a QNAP or Synology means you’re buying into their ecosystem, with all of the advantages and disadvantages that entails. Yes, you can upgrade the RAM and install your own drives but that’s about it in terms of upgrades. With the exception of some of their pricier units, you can’t drop-in a PCIe card to add discrete graphics, or more M.2 drives, or even 10 GbE, if that ever becomes a thing at home. Maybe it will, maybe it won’t.

There are some Synology units that let you buy a PCIe expansion card that lets you add 10 GbE as well as more M.2 slots (in addition to the ones you already have), by the time you pony up for one of the pricer Synology units and the PCIe expansion card, you’ve basically spent as much as you would have if you picked your own parts and built your own PC from scratch, with none of the benefits of having custom hardware. It’s a trade off. I think it makes way more sense to buy a QNAP or Synology NAS, compared to building your own, than it does for you to buy a pre-built gaming PC from a major computer retailer like Dell or HP, purely because you’ll get more value out of a consumer NAS that you do out of a gaming PC that uses non-standard parts and layouts. You’re far more likely to want to upgrade your gaming PC within its expected lifetime than you are your own NAS, and you’ll appreciate standard PC components at that point, way more than you would if you were to upgrade your NAS. But I digress, and that’s a topic for another time.

When you’re building your own NAS out of commodity PC hardware, you have the complete freedom to choose which standard PC components you want, and the flexibility that affords you down the line. You might not ever need to upgrade your QNAP or Synology CPU in the lifetime of your NAS — but don’t you wish you could, when something better comes along?

But if there was a single reason I wanted to build my own NAS, it comes from being able to have access to hardware transcoding. Specifically, Intel Quick Sync Video.

While video transcoding isn’t generally a problem for me right now, that’s not to say it won’t be in the future. The Celeron J1900 in my current QNAP supports Quick Sync, and I haven’t had an issue streaming most of my content to iOS devices via Plex due to the wonders of direct play and most of my content being in a format that’s compatible with my devices. But between various CPU architectures, Quick Sync support for different codecs and formats varies. My current CPU, while it supports H.264, will only support decoding HEVC H.265, not encoding it, with zero support for newer video codecs like VP9 or AV1, or even 10 or 12-bit HEVC H.265 which is sometimes used by HDR versions of those videos. I don’t currently have Quick Sync video working on my current QNAP, but that is probably a configuration issue on my part; it’s entirely possible I haven’t set it up correctly in the Plex container.

Not supporting hardware-accelerated video encoding/decoding means we’re back to software decoding. And if YouTubers are to be believed, AV1 is going to be the next big thing, so even if we have to wait for a couple of years for it to be adopted by content farms, won’t I be glad I’ll have picked a 12th gen CPU that can handle decoding AV1 in hardware, as opposed to some Ryzen chip that would have had to rely on sheer CPU grunt to do software encoding?

While this might not be a big deal right now, it’ll matter if everyone starts using the royalty free, and even more efficient AV1 format. If that happens within the remaining lifetime of my QNAP, that’ll be an issue for me because it will mean I’m back to software decoding everything. I’m using software transcoding now, and it’s an extremely poor experience on a quad-core 2.0GHz CPU, even on my local network. The good news is, only Intel Arc has access to AV1 hardware encoders, which means everyone else has to throw CPU grunt at the problem, if they want to encode their content in AV1.

The other main advantage of rolling your own NAS hardware is that you can run whatever OS you want on it. While there are technically ways you can run other OSes on QNAPs or Synology units, it’s a hack. Building my own NAS lets me choose between straight Linux, like whatever version of Ubuntu that I ran on my HP Microserver, or the more storage-focused flavours of Linux/BSD like Unraid or TrueNAS. TrueNAS in particular is interesting because it is known for natively implementing OpenZFS, which is generally regarded as the best storage-focused filesystem. I don’t currently have a need to run any of the crazier storage configurations afforded by ZFS as I’ll be limited by the hardware and case that I’ve chosen (at least to begin with), but it’s nice to know they’re an option, if I decide to do that later on down the track.

Continue Reading →

Return of the Obra Dinn

I’ve played a lot of video games in 2018. I got a taste of the grind in Destiny 2 when it was free, fought in the frontlines in Battlefield 5, taken down other drivers in the Burnout Paradise remaster, constructed mining ships of my own design in Space Engineers, explored a vast universe in No Man’s Sky, and even tried out the DayZ 1.0, alongside my usual staple of Dota 2. But besides all the well-known games that I’ve played, there have been exactly two indie games which have been great enough to capture my attention, and this post is about one of them.

Return of the Obra Dinn is from Lucas Pope, who you might better know from the immigration paperwork game Papers, Please. Return of the Obra Dinn is slightly different, in that it’s still about paperwork, but this time around you play the part of a insurance investigator. Officially, your job is to determine how much should be paid out to the crew of the good ship Obra Dinn, which in turn means figuring out all 60 crewmembers, and their fates.

To aid you in doing so, you have a magic pocket watch. And a notebook, but we’ll get to that later. One of Return of the Obra Dinn’s core gameplay loops involves finding a dead body, standing over it, and then using your magic pocket watch to go back to the moment of that person’s death. These death scene freeze frames don’t allow you to interact with anyone or anything, with the idea being that you can walk around, observe, inspect, gather clues, and hopefully identify who was present and what was happening, all from a few voice lines and a still frame of the exact time they died. Sometimes, one death scene will lead to the discovery of another body, which is another scene, and so on, until you have a little series of events.

These events, in turn, make up “chapters” within your notebook, which describes itself as the catalogue of adventure and tragedy that befell the Obra Dinn. By going around the ship, discovering more and more bodies, and more and more scenes, you’ll start to build up a depiction of the characters so you can start putting names to faces — no easy task, given the one-bit graphics and often obscure clues and hints that you’ll need to pick up on.

Make no mistake, Return of the Obra Dinn is hard. The game warns you fairly early on that in your quest to identify all 60 passengers and crew and their fates, definitive information that will let you decisively identify someone and their fate is rare. While you’ll usually have some idea of how a person died thanks to your magic pocket watch, working out who they are based only on contextual clues — what they’re doing in any given scene, what they’re saying, what they’re wearing, who they appear with — is challenging in the extreme. The game helps by blurring faces in the notebook until it thinks it has revealed all the information you’ll need to positively identify someone, but you’ll still need all of your powers of observation to do so. At times, you’ll need to jump between different scenes in order to work out who someone is, taking a look at where they are, what they’re doing, and so on.

It’s all very murder-mystery. Only instead of trying to work out who (or in some cases, what) did the deed, the real challenge is putting names to faces.

Unfortunately, that’s also where Return of the Obra Dinn falls short. There’s basically no replayability, given that once you’ve figured everything out, that’s how it is for the rest of time. It’s for this reason that I don’t recommend doing what I did and looking up a guide, no matter how stuck you are. The problem with this kind of game is that it’s hard for a guide to point you in the right direction, and they may end up just spoiling a few characters or two. Instead, I recommend using all the available clues; the game provides you with all of the details that you need to identify someone, even if they’re obscure as all hell. Once you’ve unlocked every scene, go through and review all of the scenes an individual appears in and try to work out who they are based on what they’re doing, who they’re with. In any scene, there’s usually something that gives away who someone is, even if you have to use a different scene to know what that is.

Return of the Obra Dinn is currently $28.95 (that’s Australian dollars to you, pal) on Steam, and you should absolutely buy it if you’re at all a fan of putting your observational skills to the test, feeling like a right Sherlock Holmes when one of your inferences pays off, or just lucky when you guess the identities and fates of people you have no idea how to otherwise identify. It’s a masterpiece.

Secondhand Mac Pro Pricing Is Ridiculous Now

IMG_3038If money was no object, my dream Mac would be the Mac Pro. Back in high school, we’d have these impromptu competitions to find the most expensive computer possible. And since the Mac Pro was both insanely expensive and able to be configured to an eye-watering level of performance, ticking all the boxes meant you could get your Mac Pro configuration towards the $30,000 mark without breaking a sweat.

I’ve never actually owned a desktop Mac before. No desktop Mac has really appealed to me, and as someone who’s had a separate PC for gaming for years, having two desktop machines means I lose out on any potential portability I wish to partake in. So every time I’ve had to decide on a new Mac, the only real decision that makes sense is a MacBook Pro, upgraded as much as I can afford it to be.

So here’s the deal: I use a Mac as my primary machine, and at the moment, it’s a Late 2013, 15-inch MacBook Pro with Retina display. It does everything, from composing blog posts late at night, to writing the daily new summaries in the morning. General web surfing, media playing, and, on occasion, I’ve played the odd game of Dota 2. Although it’s a portable machine, it almost never leaves the spot on my desk where it’s hooked up to my 4K external display, Thunderbolt dock, and all the other peripherals you’d expect to be plugged into your daily driver.

Which brings us to the other side of the equation, my gaming PC. I recently put together an almost-entirely new gaming rig for the purposes of upgrading to a more modern platform, but it’s been pretty lacklustre as far as upgrades go. For what I’m using it for (i.e. gaming), there hasn’t been any real noticeable difference in performance, which is kind of disappointing, and kind of makes me feel like I upgraded in order to keep up with platform changes, instead of upgrading because my old PC was getting a little long in the tooth.

PC performance (Mac or otherwise) has long passed the point where CPU performance makes a difference, which goes to explain why buying a machine from 2010 doesn’t faze me. In terms of general, day-to-day PC performance, the number one thing that matters these days is a fast SSD. Even then, you’re going to be hard-pressed to notice the difference between any modern SATA-based model or the newfangled PCIe-based ones, despite PCIe SSDs have much higher throughput. Again, it all depends on the kind of workload you’re throwing at them, and for gaming, the only thing that matters is GPU and to a lesser extent, CPU performance.

Which is just about where my dilemma begins. The portability on my MacBook Pro is nice and all, but I almost never use it that way. And having such a highly-specced PC that I only use for gaming seems like a bit of a waste. What if I could combine the two? I’d go from two separate computers to one, and I’d have the best of both worlds — a machine that runs OS X for my day-to-day, then reboots into Windows when I want to play some video games.

Continue Reading →

The Division Open Beta

10899819070983503872_2016-02-22_00011

This is going to be hard to believe, but sometimes I play other games other than Dota 21. Crazy, I know. But last weekend I played The Division, I title I’ve been looking forward to ever since it brought the hype at E3 2013, at PAX Aus 2013, and then again at PAX Aus 2014. I’m not even sure why I was looking forward to it — the snippets of information that had been given away by Ubisoft/Massive haven’t been much to go on, but the way that everyone else has been talking about the game has gotten me excited. Even after the beta has come and gone, I’m still not sure what the game is about or what the end-game is, so I guess you can say I’m well and truly riding on the hype-train.

At first I wasn’t sure about the concept of a third-person cover-based shooter on the PC. Then I realised one of my favourite games of all time was a third-person cover-based shooter: Mass Effect. And the more I thought about it, the more I saw similarities between the two games: both are cover-based shooters. Both are futuristic. Both have RPG-like elements in terms of gear and skills. While Mass Effect undoubtedly has the far stronger storyline, I’m hoping The Division’s Dark Zone, PvP multiplayer will make up for the complete lack of late-game content we’ve seen thus far and give it at least a little longevity after the main story is done and dusted.

I almost gave up on The Division. After finishing the initial intro and browsing same-ish city blocks, I wandered towards the first objective, cranked the difficulty to high, and dove in. After ten deaths in the same spot, I gave up and was ready to hang in the towel on the whole thing — and I would have, if it hadn’t been for a friend that wanted to co-op with me.

We actually ended up making it through that mission, even though we died a few times in the exact same spot, but having a friend turns out to make all the difference in the world (or at least in that particular instance of mission).

With both of the two storyline missions under our belt (for an estimated 10% story completion of the entire game) in one sitting, we did what two guys would do next and passed into the Dark Zone.

10899819070983503872_2016-02-22_00009

In the Dark Zone, not only are you fighting up much tougher AI for better loot, you’re also competing with other players for the same. Loot is instanced so you can never “steal” someone else’s loot by landing the killing blow on a big boss, but what you can steal is their loot when they go to extract the loot so it becomes available for use. Dark Zone loot isn’t usable until it’s “extracted”, which is dicey process of calling in a helicopter, waiting around for it to arrive, and then not getting killed while your character is going through the motions of attaching the loot to the zipline dropped by the helicopter. It’s all very Metal Gear Solid, only with the added threat of someone lobbing a few grenades on you as you’re going for the extract, and then raining bullets on you from the high ground.

Which is to say, the Dark Zone is pretty fun. If you’re playing solo, it’s the thill of being a lone wolf — not necessarily taking out groups of the strong AI by yourself, but contributing enough lead to share in the spoils, then either taking advantage of someone else’s extraction helicopter or calling in your own and hoping like hell someone doesn’t decide you’re a good target.

Ars Technica played through the closed beta on Xbox One a few weeks earlier, and while they say The Division is a repetitive shooter that has neither the cover-based shooting mechanics of Gears of War or the looting and gear-based aspects of Fallout or Borderlands, I disagree. The Division is different enough from all those to set it apart, and what people have to realise is that it isn’t a cover-based shooter with RPG elements, it’s an RPG with cover-based shooter elements.

Playing through the open beta taught me that the pursuit of better gear came above all else, and with the amount of weapon customisation and all the other RPG-type elements that were hinted at in the game but not actually present in the open beta (including food and managing hunger levels in a desolate, virus-ridden New York landscape, the various skills granted by unique weapons, the focus on cosmetic appearance, and more), my guess is there’s going to be playing of role-playing in The Division, whether that means going Rogue in the Dark Zone or just sticking to the streets of New York, trying to do… whatever the hell the main protagonist is trying to do. Seriously, what is this game about?

Seeing as I’ve pre-ordered the game, I guess I’ll find out soon enough.

  1. Which reminds me, I should probably write something about that again. It’s been a while, and I’ve got stuff to say. ↩

New PC: Firebolt

DSCF0895I was actually in San Francisco when Intel was hosting their annual developer forum last year. At that stage, I hadn’t really thought about putting together an almost entirely new PC, but you could say it planted the seed. After all, my current PC was over five years old, and despite a steady string of graphics cards upgrades, it was probably about time for something new and shiny, seeing as my computer didn’t even have USB 3 yet.

When I got back to Australia, I spent a few good months thinking about whether I wanted to get a new PC or not. There was nothing particularly wrong about my current rig, besides being a little long in the tooth. Depending on the games I was playing, the CPU could be a little bit of a bottleneck, but the GTX 980 meant things still hummed along just fine on screen.

By the time December came around, I had all but made up my mind. I was going to build a new Skylake-based PC, recycling only the graphics card, hard drives, and a fan controller from my current computer. Now all I had to do was decide on some parts, but here’s how it all breaks down.

Continue Reading →

Losing (and winning)

One of the things that annoys me the most about the programming is the zone of suck, and how very large and expansive it can be. Probably because I’m a mediocre programmer, at best, but a lot of the time it feels like I’m single-handedly trying to fight backdoor protection on the other team’s ancient as Faceless Void.

Losses in Dota 2 feel like that, too. Sometimes you’ll realise you have nothing to stop the other team’s push strategy, other times you’ll know that your entire team can’t deal with one hero on the other team who got a few kills early on, and by that time, the game is pretty much over. I hate calling “gg” early as much as the next guy, but fighting against a split push with little farm and little to no hope against of coming back is incredibly frustrating1.

Yes, I’ve been playing a lot of Dota 2 recently, and while it might sound like I say that a lot, it’s the truth. Last weekend, a couple of friends and I gathered at my place for some five-stack ranked shenanigans. Incredulously, we somehow managed to win 10 of the 11 games we played; an impressive win rate on a good day, a downright amazing win-loss ratio on any other.

After a warmup game, we refined the strat we were running. We’d insta-pick the heroes we wanted when All Pick came up, and tried to not get them banned in Captain’s Mode. Provided none of us got off to a particularly bad start in the laning stage, we guaranteed kills with a triple-stun trilane, a mid Drow, and solo Invoker. And even if one of us was killed a few times during the early game, we usually had enough recovery mechanisms to get back into the game; usually involving the other players making space for the fifth to farm. Split pushing, adding pressure around the map, stacking neutrals, that kind of thing. By the time late game rolled around, we would be ready.

We did have a bit of trouble against some really good Tinkers. With no real mechanism to catch him out, an enemy Tinker ended up split pushing every lane while we were taking 4v5 teamfights, which would favour us most of the time. Eventually the Tinker would make a mistake and we’d pull him up on it, securing the kill, and because not even an incredibly farmed Tinker can carry a game single-handedly, we’d go on to win the game off the back of those pick-offs.

For the most part, our strategy carried us through games. Our team hero composition allowed us to be a little lazier in terms of items; Wraith King’s lifesteal aura helped out our team early-game with HP regen, and Maiden was the same was her mana regen. By running two position threes, both with the potent carry potential, any time a game went late always favoured us. At the same time, because our Invoker was building Necronomicons and doing his best to push down towers any time he was away from a teamfight, we’d usually have such a gold lead that one or two farmed heroes on the other team didn’t matter that much. Of the 11 games we played, only four went longer than 40 minutes — and of those four, the three we won we were playing against a Tinker, master of the split push.

But despite our impressive win-loss ratio, the game we didn’t win still sticks out like a sore thumb. Thanks to some combination of the Von Restorff effect and likely some negativity bias, I remember that game more than any of the others, despite the fact we won 10 of the other 11 games we played that night. It hurts even more to know that we could have won that game, too — the scoreboard showed kills that were more or less even all the way through, and we punished them for their mistakes every opportunity we got. Every time they got greedy and tried to push for more kills or objectives after using their ultimates, we’d wipe them, but couldn’t seem to take any objectives off the back of our kills.

Continue Reading →

DotA for Recreation, Not Profit

Dat courier, though. Phwoar.

Dat courier, though. Phwoar.

Alternate title: remember when online gaming was fun?

As part of my ongoing adventures in DotA 2, I’ve stopped playing ranked matches altogether. After experiencing how much they brought out the worst in people (and I include myself in that), I decided they were making gaming less fun, so I gave them the flick. Of the online games I am playing, I stopped choosing “All Pick” as a game mode and starting choosing basically everything else: Single Draft, Random Draft, All Random, Least Played, Captain’s Mode, and Captain’s Draft. The other game modes change things up a little by not offering the full hero roster, and do a decent job of teaching me to be a better player by playing with hero and team combinations I’m not necessarily familiar with. Ability Draft, on the other hand, is just… weird, and almost seems like an arcade version of DotA.

The thing I enjoy the most isn’t sledging my teammates when the carries can’t actually carry, despite what you may hear or read. No, it’s playing DotA with friends, either in friendly 5-on-5 matches, against bots in coop, or even online, when it takes our fancy. Work and other commitments mean we hardly get to see each other and catch up as often as we’d like, but playing DotA together means we can jump in Mumble or TeamSpeak and catch up with other while participating in some truly epic teamfights.

And at the heart of it, isn’t that what online gaming is all about? Having fun with people you know in real life, online? I’m no stranger to playing single-player games, but every now and again, I enjoy playing with friends. Multiplayer games like DayZ, Wasteland, DotA, and so many others just aren’t the same when you play by yourself. You could argue that there’s a time and a place for playing single-player games by yourself, but at the end of the day, there’s no denying that online gaming is infinitely better with friends.

But you know what isn’t fun? When friends get too serious about a game. I’ll admit straight up that I’m guilty of this, but aren’t we all? Our naturally competitive nature means that a disappointing loss hits harder than any elation from a convincing victory, which leads to blaming people we’re usually on very good terms with.

Continue Reading →

Point and Click Adventure Game

Casual readers of this blog might think that this will be another post on the latest title from Telltale Games, purveyors of the finest point-and-click adventure games around. I’ve previously reviewed The Walking Dead: Season One (the video game), and plan to dive into The Walking Dead: Season Two and The Wolf Among Us very soon, but no, these aren’t about those kinds of point and click adventure games per se. At least, not the ones you might be thinking about.

I’ve played a lot of ARMA 2. Along with DotA 2, it’s pretty much all I play these days. (According to my Steam stats, DotA 2 has the lead in terms of gameplay time.) It all started with the DayZ mod a few years ago, but since then a few of us have moved on to Wasteland, which is less about scavenging for survival items as it is about simply hunting down and killing others, building bases, that kind of thing. Kind of like a realistic version of Battlefield or Counterstrike, if you will.

Anyway, we’ve been spending a lot of time on a server that doesn’t have that many powerful guns. Perhaps less than ten are are one-hit one kill, and of those, only a handful can do so at range. The M110 with NV Scope is my current favourite weapon, purely because it’s so easy to get kills with it. Provided you’ve calculated the range properly (something that comes with experience, a few map waypoints, or if all else fails, a rangefinder), it’s ridiculously easy to get kills; you can hit someone anywhere and kill them. It also has very little recoil, meaning you can fire off a number of shots in quick succession without having to re-adjust for every shot. All this means it’s a veritable killing machine, in the hands of the right operator (in ARMA 2, anyway).

Short explanation of the video below: it all starts by us hearing about a base to the West of Kamenka. Armed to the teeth, we head over to see if the rumours are true. On the way, an immobile tank objective pops up, and a short while later, we spot an SUV driving along the main road. Things happen rather fast from that point: Janson takes out a tyre with a well-timed and well-aimed shot, which causes the SUV to skid to a halt. One guy doesn’t get out of the (now on fire) SUV fast enough and dies. Strike dies as five others pour out of the vehicle, guns up. I pop up momentarily, manage to kill one with a lucky shot, and get back down. I notice they’re all gathered on the opposite side of the road, next to a wooden house, so I put my eye to the scope, pop up, and take aim. I fire a round just as the first starts to run, and he’s down. I move across to the right, and fire off five more shots. One, hit. Two, hit. Three, hit. Four, miss — I quickly compensate and fire off the last shot. Five, hit. And like any good point and click adventure game, that’s the end of that.

Nvidia’s ShadowPlay and One Angry Earthshaker

fraps movies settings

Occasionally, I put gaming-related videos on YouTube. For all of those videos, I’ve used Fraps to capture in-game footage, and as far as software-based capture tools go, it isn’t bad. I’ve been using Fraps for a few years now, and for the most part, I’ve been pretty happy with it.

That said, there are a few things about Fraps I don’t like. For starters, it creates massive files on disk — it works out to be about 1.2GB/minute for 720p footage at 60fps. There’s no option to record at arbitrary resolutions, only your display resolution or half size, whatever that turns out to be1. And enabling Fraps usually kills my FPS, which usually gets me killed in whatever game I’m playing. The frame rate drop I experience in certain (read: more recent, more demanding) games turns me off recording unless I really want to, otherwise I’d probably record far more often than I do. That, and the massive hard drive space requirements for recording.

But like any in-game capture tool, the worst thing about Fraps is that I have to manually enable it whenever I want to record something. That’s fine if I know something cool might happen in advance, or when I know I’m going to do something which I might need footage for later, but I honestly couldn’t tell you how many times I’ve done something epic and wished it has been recorded. So many times I’ve missed out on capturing some real Kodak moments, and all because FRAPS wasn’t recording. The “workaround” for this, if you can call it that, is to have Fraps running all the time — but when gaming sessions go for hours on end, I have neither the hard drive space nor the low-FPS tolerance for that to be a viable solution.

shadowplay settings

Enter Nvidia’s ShadowPlay.

In Shadow Mode, ShadowPlay automatically records everything in the background. It records up to the last ten minutes of gameplay in the background, which you can then save to disk if you want by pressing the appropriate key combo. Do something epic, and want to have a permanent record of it? No need to gripe about not having Fraps turned on and recording to your friends over TeamSpeak, because ShadowPlay already recorded it for you. All you have to do is save the recording.

ShadowPlay is also great because it doesn’t produce massive files when recording footage. It uses the GPU to transcode your recordings on the fly to H.264 (which is why you’ll need a GTX 600 or 700 series graphics card), resulting in reasonably-sized files, and best of all, there’s no performance hit that I’ve noticed thus far. (For comparative purposes, 1GB of hard drive space gives me roughly three minutes of in-game footage with ShadowPlay at 1080p/60fps, compared to under a minute with Fraps at 720p/60fps.) There are alternative software capture tools that can perform similar compression on your recordings, but those use CPU power instead of a dedicated H.264 encoder built into the graphics card. And since my CPU is a few years old now, I don’t really have those CPU cycles to spare when I’m gaming.

ShadowPlay has a manual recording option too á la Fraps, in case you want to go down that path. But having something sit in the background silently recording my every move is great, and means I don’t have to think about what I’m going to be doing next and whether I want to have that on file for later. It’s like having an instant rewind for anything.

There’s always room for improvement though, and ShadowPlay is no exception. It needs the ability to record voice input, for starters. If I’m communicating hilarious things over TeamSpeak but all the recording captures is my teammates’ responses, then that’s not very useful. And I have to do some more thorough testing, but I’ve had a few recordings with a number of graphical glitches too. Then again, Nvidia have labelled it a beta for a reason, so I’m sure it’ll get there.

But for now, ShadowPlay is pretty great. Reasonably-sized files, little to no performance hit when recording, and the best part is, it means I don’t have to worry about turning on Fraps before doing something cool. What’s not to love?

ShadowPlay makes recoding game footage an afterthought, which is what it should be — because you’re supposed to be playing games, not thinking about whether you want to record what you’re doing in games.

About the video2: OK, so, there was this one game of DOTA 2 I was playing, right. We had an Earthshaker on our team who wanted to play him like a carry — constantly going 1v1 against other heroes. Dude thought he was invincible, even after he died three times in the space of two and a half minutes. After he died he’d usually ping-spam the map, resulting in our Death Prophet getting worked up and shout at him over in-game voice. It was hilarious, right up until the point where Earthshaker revealed he had a mic after all, but apparently only used it to abuse other teammates over voice. We lost the game, of course, but it was really strange. Almost like the dude was drunk or something.

  1. Since I game at 2560×1440, the native resolution of my display, half size turns out to be 720p, which works out well enough for YouTube purposes. 1080p would be great, but recording at full size and then down-sizing is too much work. ↩
  2. I had to upload the video to Vimeo because YouTube blocked the audio because of the Lady Gaga going on in the background. But the audio is kind of the best part. And yeah, sorry about having the not-very ad-free Spotify going on in the background. (The new Lady Gaga is just OK, IMHO). ↩

Winning (and losing)

Dota Dire Ancient Gone

If there’s a universal truth, it’s that people don’t like losing. Ask anyone, and they’ll tell you that losing sucks; anyone that tells you otherwise is either lying or a sadist.

The question is: do I take winning too seriously? There was one time, years ago, where a friend and I were playing Left 4 Dead. We were in a co-op match with two other folks, and I was shouting obscenities into our team’s text chat in an attempt to get the other players on our team to do something useful. After the match, the friend I was playing with pointed out “that guy” that was trying to get the team to win. I pointed out that “that guy” was actually me, and things were pretty awkward from that point on.

I’ve played a number of DotA 2 games now. As of writing, dotabuff says 249 real matches, with perhaps an extra 10-15 versus bots on top of that. At the moment, my win-loss ratio is sitting just under the 50-50 ratio, at 124 wins to 125 losses. Anecdotal evidence (i.e. the dotabuff profiles of a number of friends who have played hundreds of more games than I have) leads me to believe the matchmaking in DotA conspires to keep you around a 50-50 WL ratio, but with a good enough team, you can beat the odds.

Despite what you may believe, the number one influencer on your win-loss ratio isn’t yourself. At least, it’s not about yourself as much as it is about other players. For example: if another player on your team, in a different lane, decides to die repeatedly to one of your opponents in the early game, then that opposing hero now has a level and gold advantage. And even if you’re playing to the best of your ability, there’s very little you can do from preventing that opposing hero from dominating the rest of the match. From there, your fate is all but sealed: the opposing hero which received early kills dominates teamfights, and hence wipes the floor with your team. Eventually, through no fault of your own, you lose. Good game, sir.

But I’ve played enough games of DotA 2 now to realise that it’s a little more complicated than that. I’ve seen my share of impressive comebacks and last-gasp pushes that result in a win to know that the balance in DotA is incredibly delicate. What one player does or doesn’t do can tip the scales in your favour, or lose you the match. Didn’t deny the tower when you had the chance? You lose because the enemy all gained gold. Didn’t carry a TP scroll when pushing? You lose because a Nature’s Prophet decided to teleport into your base and demolish your ancient with his army of trees. Spent too much time jungling instead of pushing with your team? You lose because your team just lost that 4v5 teamfight, the enemy pushed, and you lost a tower and barracks.

Don’t get me wrong, good team work is of the utmost importance in DotA 2. It’s why I gently push others to be the best they can be if they’re having a bad game, because good teamwork means you can bring a game back from 9-0, their advantage. 30 minutes in, and it’s 16-32, still their advantage. We’re behind in kills the entire time, but when we finally take their ancient, the scoreboard reads 44-54, still in their favour. You’ll notice I went 2-17 in that match. I contributed almost nothing to that game, and yet we won. So how does that work, exactly?

Teamwork.

Continue Reading →