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.
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.
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?
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.
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.
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.
Some people spoke openly about the shitty treatment and Microsoft fucked them over as well.
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.
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.
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.
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.
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.
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...
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.
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. <<
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.