6 ms·
It's funny that Microsoft feels XBox Live Indie Games was such a mistake and seems to think that indies did so much harm to them, given that indies generally fe
by kevingadd 13y ago
It's funny that Microsoft feels XBox Live Indie Games was such a mistake and seems to think that indies did so much harm to them, given that indies generally feel like Microsoft has been intentionally harming them from the start.
They basically left that system to rot without supervision, and then it did. Where's the surprise in that? It's like they decided to greenlight it only so they could sabotage it and use it as proof that they don't have any reason to work with indies. It's incredibly stupid given that some of the best indie XBox Live Arcade exclusives (or former exclusives) were all built using XNA - Bastion, Fez, Dust - but they screwed those devs as hard as they could too, despite the fact that those games were partially funded by deals with Microsoft!
- gamblor956 13y agoOf those 3, only Fez was "screwed" by Microsoft, and that was Fish's own fault--he released a buggy game without adequate QA...and a buggier patch with even worse QA...and wouldn't (but could afford to) pay for the follow-up patch that would supposedly have fixed the bugs he didn't fix twice before. But yeah, it is an incredibly short-sighted decision for Microsoft to eliminate the Indie program. Some of the best new games/studios rose up through that--using C#, DirectX, and other parts of the MS toolchain--but it looks like the next generation of indies will be learning the PS4/OpenGL toolchain instead.
- DanHulton 13y agoIt's absolutely insane to me that devs have to pay to get their patches allowed onto the XBox in the first place. Even Apple doesn't charge you for a bugfix patch. You should never have to choose between wrecking yourself financially or reputationally like that. I really hope the new XBox Bro tanks super hard because of nonsense like this.
- AUmrysh 13y agoApparently they do this because they do their own QA/testing. It's pretty sad that they are charging users $50/year and then charging developers $10,000+ for patches. Isn't the subscription supposed to pay for the infrastructure? I can understand MS wanting to protect their baby, but the walls on the garden are so high they keep light out. Valve wasn't having any of that pay per update deal and that's why TF2 on the 360 hasn't had anywhere near the number of updates as on PC. MS has done a lot to hurt not just indie developers, but first party (Bungie) developers as well. Remember that ordeal with MS forcing them to release Halo 3 before it was ready and then the whole team threatened to quit? It's sad that they've taken a digital distribution system like Xbox Live and turned it into a cash cow on both ends. They're stifling not only innovation, but regular development processes, with their blind profiteering.
- usea 13y agoNot only that, but the fact that such a buggy patch (Fez) came out which deleted save files etc, it wasn't exactly clear what value $10k patch QA was getting you.
- gamblor956 13y agoFirst patch is free--only the 2nd patch and beyond cost the developer.
- jonny_eh 13y agoSo they don't QA the first patch, but they'll QA the second patch? I don't follow your logic.
- gamblor956 13y agoThey QA both, but only the first patch is gratis.
- winter_blue 13y agoWhat the heck? Why do you developers have to pay to submit patches? This makes no sense to me. Devs don't pay Apple or Google to update their Android or iOS apps. What kind of unearthly nonsense is this?
- usea 13y agoMicrosoft has/had a somewhat captive audience, so they can do a lot of milking. The justification from Microsoft is two-fold: 1) Having to pay for patches gives publishers an incentive to release less-buggy games the first time. When consoles first started enabling developers to release patches, it was fashionable for gamers and reviewers to complain about patches. Many people subscribed to the idea that patching was lazy and games shouldn't have bugs at all. These days people are more likely accept patching as a good thing, so this patch cost is really more damaging than helpful. 2) Microsoft does extensive QA on your patch (just like they do initial releases) to make sure it doesn't do anything egregious, and this process costs money. Gamers don't always care who screwed up, they will blame the console-maker. So Microsoft benefits from ensuring patches don't brick your console, etc. However, it's not exactly clear how worthwhile this process is considering the buggy patches that have come out. Surely it doesn't cost them anywhere near 10 grand to pay for the testing process. Although the top-end games are still getting more and more expensive to produce, the quality of game that the average developer is able to make on her own has risen dramatically. You no longer have to have very specialized skills to create a great game that will sell a million copies. Publishers and console-makers don't hold the power they used to. There are so many available open channels for developers to release their games to large audiences with no interference. MS is refocusing away from the gamers who rely on them less and less, to a more broad audience. Other similar behaviors Microsoft gets/got away with: charging gamers for the ability to play online, charging a 'licensing fee' for any game released on the system (other console manufacturers do this as well), showing advertisements while navigating the console's menus.
- sdfaf 13y ago>>but it looks like the next generation of indies will be learning the PS4/OpenGL toolchain instead. Thank God! I really do not want to spend any time learning Microsoft specific frameworks/APIs. I'm already familiar OpenGL and I rather spend my time working on the game itself rather then having to learn new APIs.
- drharris 13y agoYes, we should never learn new things.
- sdfaf 13y agoYou are really missing the point. Read this: http://www.joelonsoftware.com/articles/fog0000000339.html http://www.joelonsoftware.com/articles/fog0000000339.html Is a technique that Microsoft loves doing. From the article: >> The competition has no choice but to spend all their time porting and keeping up, time that they can't spend writing new features. Look closely at the software landscape. The companies that do well are the ones who rely least on big companies and don't have to spend all their cycles catching up and reimplementing and fixing bugs that crop up only on Windows XP. The companies who stumble are the ones who spend too much time reading tea leaves to figure out the future direction of Microsoft. People get worried about .NET and decide to rewrite their whole architecture for .NET because they think they have to. Microsoft is shooting at you, and it's just cover fire so that they can move forward and you can't, because this is how the game is played, Bubby. <<
- pjmlp 13y agoYeah, right, like if everyone else wasn't doing the same.
- angersock 13y agoYou might enjoy Direct3D...imagine if people designed an API, documented it really well, and weren't crufty as fuck. I've done a lot of time with OpenGL, but I won't pretend for a second that there aren't better things out there.
- pjmlp 13y agoOpenGL? So far I have only seen references to libGCM.
- eropple 13y agoThere may eventually be a GL stack, but from what I've heard, all "real" games are going to use libGCM.
- seivan 13y agoNot true, Braid guy (Sorry, forgot his name) felt Microsoft tried to fuck him over intentionally. Some people spoke openly about the shitty treatment and Microsoft fucked them over as well.
- usea 13y agoJonathan Blow [1] [1] http://en.wikipedia.org/wiki/Jonathan_Blow http://en.wikipedia.org/wiki/Jonathan_Blow
- rictic 13y agoAlso the Super Meat Boy devs were promised specific promotional considerations, were told that they wouldn't have a chance of success without them, put themselves through incredible agony to meet the corresponding deadline only to find that the promised promotional placement never came. A bit of this is covered in Indie Game the Movie, more on various blogs and postmortems afterwards.
- kevingadd 13y agoFez got hit the hardest, but the negligence applied to the XBLIG program as a whole (and XNA as a technology) actively hampered development of every serious game built with it. Developers locked into using XNA for their title were developing games for the XBox 360 without the benefit of many essential XBox 360 dev tools and features, like full on-device profiling, SIMD, etc. In practice this meant if you had a game that ran great and worked well on PC, but had severe performance issues on the console, your only choice was to try and do very tedious printf debugging by deploying hundreds of modified executables to the console and trying them one-by-one. In comparison, native devs had access to PIX for XBox 360 which reportedly offered near-VTUNE levels of insight into CPU and GPU performance. Constraints are fine, of course, but most of XNA's problems were not active constraints but instead negligence - promises were constantly made and then broken, whether it was promising to fix serious issues or promising to pay devs on time for game purchases.
- kabdib 13y ago> _They basically left that system to rot without supervision_ A few things were probably going on: 1. Microsoft is all about control and process. A lot of this is justified with "security" (so devs don't add holes to the system) or "content control" (so Little Timmy isn't allowed to see giant pink ... stuff, in games) or "we've always done it this way" (which is /safe/). 2. Promotions at MS are gated by how much you're perceived to be involved in things, not necessarily by how much value you are adding. So going to lots of meetings and being visible (e.g., adding process, or being a gatekeeper) is rewarded much more than making something go smoothly. Being invisible at review time is Not A Good Thing. Therefore: lots of accretion. 3. Reviews again: "I made that thing we did last year continue to go well" is weaker than "I did whizzy features X, Y and Z". (Hell, I've done this myself). You can't appear to be sitting on your butt. The end result is that MS becomes difficult to work with, appears to lose focus, and cycles new, somewhat flaky technology at developers at unsustainable rates. The "new shiny" of two years ago becomes a wasteland because nobody ever got a good review based on the efforts of 18 months ago.
- rodgerd 13y agoThe odd thing about 1 is that Microsoft's empire is essentially based on the opposite premise. The foundation of their success was selling an open-for-developers OS on open hardware.