News for hackers. Stuff that matters.
Re:Indie developers cannot self-publish on Xbox One by kevingadd on Wednesday May 22, 2013 @12:28PM (#5751933)
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!

Re:Indie developers cannot self-publish on Xbox One by kabdib on Wednesday May 22, 2013 @02:41PM (#5752891)
> _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.

Re:Indie developers cannot self-publish on Xbox One by rodgerd on Wednesday May 22, 2013 @09:57PM (#5754918)
The 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.
Re:Indie developers cannot self-publish on Xbox One by gamblor956 on Wednesday May 22, 2013 @12:39PM (#5752005)
Of 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.

Re:Indie developers cannot self-publish on Xbox One by DanHulton on Wednesday May 22, 2013 @12:51PM (#5752088)
It'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.

Re:Indie developers cannot self-publish on Xbox One by AUmrysh on Wednesday May 22, 2013 @01:05PM (#5752210)
Apparently 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.

Re:Indie developers cannot self-publish on Xbox One by usea on Wednesday May 22, 2013 @01:53PM (#5752554)
Not 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.
Re:Indie developers cannot self-publish on Xbox One by winter_blue on Wednesday May 22, 2013 @11:19PM (#5755153)
What 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?

Re:Indie developers cannot self-publish on Xbox One by usea on Thursday May 23, 2013 @04:08AM (#5755783)
Microsoft 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.

Re:Indie developers cannot self-publish on Xbox One by gamblor956 on Wednesday May 22, 2013 @02:01PM (#5752624)
First patch is free--only the 2nd patch and beyond cost the developer.
Re:Indie developers cannot self-publish on Xbox One by jonny_eh on Wednesday May 22, 2013 @07:13PM (#5754382)
So they don't QA the first patch, but they'll QA the second patch? I don't follow your logic.
Re:Indie developers cannot self-publish on Xbox One by gamblor956 on Wednesday May 22, 2013 @09:57PM (#5754915)
They QA both, but only the first patch is gratis.
Re:Indie developers cannot self-publish on Xbox One by georgemcbay on Wednesday May 22, 2013 @02:21PM (#5752771)
"Apparently they do this because they do their own QA/testing."

They do supposedly do their own TRC/QA pass on all patches, but the system is highly flawed. As Exhibit A I present Call of Duty: Black Ops 2. Quite an enjoyable multiplayer game, IMO, but despite already having a handful of updates in the half-a-year or so since release, the online is still terribly buggy. I've never seen an Xbox game with such poor networking and matchmaking (unlike every other 360 game I've played with friends, the party is always being split into different lobbies, lobbies get into weird states where you're supposedly able to join them but you can't until the party leader leaves and recreates them, etc, etc, total amateur hour shit).

From a QA perspective that game is an absolute mess, so either Microsoft's QA is worthless shit or they are willing to look the other way for games with high enough profile.

Re:Indie developers cannot self-publish on Xbox One by pandaman on Thursday May 23, 2013 @03:04AM (#5755668)
Submission process is not a game QA, TRC is not checking if the game is fun or if you get correct ads on your players in Madden. TRC is checking for uniform behavior (like loading UI, save game UI, correct naming of parts of the console and actions, handling pulled out controller, disk errors etc) and security issues (correct libraries, proper protocols for online etc).

Another thing - big titles break TRC routinely. Failing CoD for a TRC is like giving a speeding ticket to Obama's motorcade. That game sells 10M and brings ~100M in licensing fees every year.

Re:Indie developers cannot self-publish on Xbox One by m_mueller on Wednesday May 22, 2013 @05:31PM (#5753876)
What makes this situation even worse is that Microsoft was once such a high quality game publisher. Remember the days of Age2?
Re:Indie developers cannot self-publish on Xbox One by seivan on Wednesday May 22, 2013 @01:44PM (#5752479)
Not 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.

Re:Indie developers cannot self-publish on Xbox One by rictic on Wednesday May 22, 2013 @11:10PM (#5755113)
Also 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.
Re:Indie developers cannot self-publish on Xbox One by usea on Wednesday May 22, 2013 @01:55PM (#5752570)
Re:Indie developers cannot self-publish on Xbox One by kevingadd on Wednesday May 22, 2013 @06:53PM (#5754304)
Fez 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.

Re:Indie developers cannot self-publish on Xbox One by sdfaf on Wednesday May 22, 2013 @12:54PM (#5752114)
>>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.

Re:Indie developers cannot self-publish on Xbox One by Impossible on Wednesday May 22, 2013 @04:36PM (#5753520)
PS4 does not use OpenGL as it's graphics API, and doesn't even support PSGL (the higher level, OpenGL ES 1.1 like library that PS3 supported.) This is a rumor that's going to persist for the lifetime of the system.

That said most indies are moving to using Unity 3D, so as long as Unity support for PS4 is good and licensing costs aren't too high, the low level graphics API of PS4 won't matter.

Re:Indie developers cannot self-publish on Xbox One by pjmlp on Thursday May 23, 2013 @02:09AM (#5755574)
Open source geeks like to spread the myth that Microsoft consoles are the only ones not supporting OpenGL.

Given that the games industry is very hostile to open source and very few geeks have access to console development kits, it is no wonder the myth persists.

Re:Indie developers cannot self-publish on Xbox One by angersock on Wednesday May 22, 2013 @02:48PM (#5752949)
You 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.

Re:Indie developers cannot self-publish on Xbox One by qompiler on Thursday May 23, 2013 @07:59AM (#5756314)
If you truly understand the OpenGL programmable pipeline you understand graphics programming in general and should have to spend little time picking up a new API. Just like how you should be able to learn a new programming language with ease if you have enough experience.

From Eurogamer.net:

Low-level access and the "wrapper" graphics API

In terms of rendering, there was some interesting news.

Norden pointed out one of the principal weaknesses of DirectX 11 and OpenGL - they need to service a vast array of different hardware. The advantage of PlayStation 4 is that it's a fixed hardware platform, meaning that the specifics of the tech can be addressed directly. (It's worth pointing out at this point that the next-gen Xbox has hardware-specific extensions on top of the standard DX11 API.)

"We can significantly enhance performance by bypassing a lot of the artificial DirectX limitations and bottlenecks that are imposed so DirectX can work across a wide range of hardware," he revealed.

The development environment is designed to be flexible enough to get code up and running quickly, but offering the option for the more adventurous developers to get more out of the platform. To that end, PlayStation 4 has two rendering APIs.

"One of them is the absolute low-level API, you're talking directly to the hardware. It's used to draw the static RAM buffers and feed them directly to the GPU," Norden shared. "It's much, much lower level than you're used to with DirectX or OpenGL but it's not quite at the driver level. It's very similar if you've programmed PS3 or PS Vita, very similar to those graphics libraries."

But on top of that Sony is also providing what it terms a "wrapper API" that more closely resembles the standard PC rendering APIs.

"The key is that it doesn't sacrifice the efficiency of the low-level API. It's actually a wrapper on top of the low-level API that does a lot of the mundane tasks that you don't want to have to do over and over."

The cool thing about the wrapper API is that while its task is to simplify development, Sony actually provides the source code for it so if there's anything that developers don't get on with, they can adapt it themselves to better suit their project.

http://www.eurogamer.net/articles/digitalfoundry-inside-play...

Re:Indie developers cannot self-publish on Xbox One by sdfaf on Friday May 24, 2013 @05:06PM (#5765178)
>>If you truly understand the OpenGL programmable pipeline you understand graphics programming in general and should have to spend little time picking up a new API. Just like how you should be able to learn a new programming language with ease if you have enough experience.

This is very true. However, I rather not spend anytime on this if I don't have to. What you are underestimating though are the quirkiness of the new API that could waste you hours and hours. i.e. Some graphics rendering may not look quite right because some unexpected limitations, etc. etc. Finding work-arounds for all those tiny quirks can be time consuming Time that you'd rather spend on the product itself.

Re:Indie developers cannot self-publish on Xbox One by drharris on Wednesday May 22, 2013 @12:56PM (#5752144)
Yes, we should never learn new things.
Re:Indie developers cannot self-publish on Xbox One by sdfaf on Wednesday May 22, 2013 @01:01PM (#5752190)
You are really missing the point. Read this:

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. <<

Re:Indie developers cannot self-publish on Xbox One by pjmlp on Thursday May 23, 2013 @02:06AM (#5755571)
Yeah, right, like if everyone else wasn't doing the same.
Re:Indie developers cannot self-publish on Xbox One by pjmlp on Wednesday May 22, 2013 @01:18PM (#5752313)
OpenGL?

So far I have only seen references to libGCM.

Re:Indie developers cannot self-publish on Xbox One by eropple on Wednesday May 22, 2013 @01:56PM (#5752581)
There may eventually be a GL stack, but from what I've heard, all "real" games are going to use libGCM.