hydrophilic attack
Member
But is there any group of people where XB1 owners are the obvious majority?
People that own Surface iPads.
But is there any group of people where XB1 owners are the obvious majority?
People that own Surface iPads.
Maybe, maybe not. But for a company that is concerned with those loyal to their ecosystem to change policy it helps that change is demanded by those loyalist.
Look at all the policy changes that MS has enacted over the last year, plus as Chubs joking pointed out, the OS updates. MS is listening to their consumer base, and trying to shape their product the the wants of that base.
The point is that if those who own XB1s don't become the vocal majority the incentive for MS to change policy isn't there.
But is there any group of people where XB1 owners are the obvious majority?
I don't agree with the parity clause, but BruiserBear does have a point. The people who are "upset" don't even own a X1. I don't see any X1 owner really voicing that they dislike the for clause.
Apparently, they've persuaded about 300 indies to hold off on publishing the PS4 version of their game, so they probably see that as a win for their side.
Besides, as MS supporters are fond of pointing out, they don't actually need anyone else's money; they just feel like they should have it on principle. And maximizing returns while minimizing effort is just smart business.
In this post, you seem to be arguing that because Microsoft's policy wasn't 100% successful, it can't be considered anticompetitive. Actually, right at the end, you made a subtle shift to it not being "anti-consumer," but yeah, it's anti-consumer too; they're hurting their own development partners, they're hurting their competition, they're hurting their competitor's customers, and thanks to the backfire they're hurting their own customers too.
The policy is in place solely to unfairly hamstring their competition. That's anti-competetive, regardless of the actual effectiveness of the policy.
I have absolutely no problem with people who disagree with the parity clause. I don't personally object to it, but I have no problem with anyone else not liking it. I've made that quite clear.
BUT, you can't browse this thread and not see a lot of people who are really just being opportunists, and jumping on the opportunity to attack Microsoft and tell us how they don't want indie devs to feed their families. That is the sub narrative of this thread, regardless of people wanting to admit it. I have yet to a see an XB1 owner in this thread saying "man, I'm so mad this policy is keeping all these great games off the XB1".
I've already made it clear what I consider to be anticompetitive. You're looking for a specific definition you can defeat through pedantry, but again, semantic acrobatics don't impress me. Wrong is wrong.
And I don't disagree with the legal definition of anticompetitive. I just don't try to pretend it's comprehensive, either in a legal sense, or in a "common use" sense. What I do disagree with it the implication that because their behavior isn't explicitly illegal, it's perfectly acceptable and/or not worthy of debate.
Why do you think it's wrong? I think it's wrong because Microsoft are pressuring their suppliers in to shorting Microsoft's competition, thereby eliminating said competition's legitimate advantage. To me, that's anticompetitive, and therefore, wrong.
It helps if you quote actual people when spreading your own 'narrative'.
So just to catch up, the past two pages have basically been,
"You can only complain about a terrible clause if you own the specific system", which is terrible. You know it's basically like saying "If you're not gay you can't complain about laws that negatively affect the gay community"
and
"If you're a good indie the Microsoft will bargain with you against the clause", so wanting to have your cake and eat it too. Cause if you're good and popular, sure release it here too (for whatever Microsoft bargain for), if you're not, then either screw yourself out of sales from other places if you want to be on our system at all.
I wouldn't say MS are cherry picking or even that they have "persuaded" 300 devs to make xbox one versions and delay others.
I've spoken to a couple of devs who are working on PC/xbone one versions of games because they haven't got, couldn't get or simply can't afford a wii u/ps4 dev kit and MS sent them dev kits first, so they started making those versions.
I know Crazy Viking Studios 'Volgarr the Viking' devs have said they would love to make other versions and are hoping that the xbox one version can help them fund dev kits if and when they can get them.
Which is fine. No one's saying indies can't appear on Xbox One first. The stupid thing would be if Sony or Nintendo didn't allow Volgarr the Viking on their platforms just because it appeared on Xbox One first. Which is what Microsoft is doing here with their parity clause.
Aren't there plenty of demonstrated cases already where they in fact have released games that have launched on other platforms first?
Aren't there plenty of demonstrated cases already where they in fact have released games that have launched on other platforms first?
No? The only one that comes to mind is Outlast.
Yeah there are only a few.
Outlast, Contrast, Stick it to the Man, and Warframe.
Didn't Strike Suit Zero see a PC release before Xbox One? DiveKick is supposed to release on Xbox One, and it's already on PS3, Vita and PC.1001 Spikes should also be seeing release on Xbox One, already on WiiU and PC. I've seen people mention threes! or whatever its called which I'm pretty sure is an app on iTunes.
These are just games I can think of in about 30 seconds time and I don't even follow Indie titles much.
Uh oh. Has the word ipad become synonymous with tablet where people use the word ipad to describe every company's tablet? Like band-aid, "coke", etc?
There was a loophole though right? Something about signed before the whole ID@Xbox thing was officially announced or something. Those games might have just fallen under that loophole.
I don't think the policy applies to PC releases. It seems kind of clear that this policy is really only against the PS4 (and maybe to a lesser degree the Wii U?)
There was a loophole though right? Something about signed before the whole ID@Xbox thing was officially announced or something. Those games might have just fallen under that loophole.
I don't think the policy applies to PC releases. It seems kind of clear that this policy is really only against the PS4 (and maybe to a lesser degree the Wii U?)
So... console parity clause - care to elaborate how you got round that?
Hah, this had to be the first question, didn't it?
So, I'll preface the answer by saying that we have been asking Microsoft for years to allow developers to self publish. We had been talking about self publishing Contrast since at least early 2012, to anyone at MS who would listen. When self publishing was announced for MS, it took us by surprise - we had no idea it was coming, which is a bit of a bugger because we had just signed a publishing deal for the 360. So, when they announced it, we were already committed to four platforms on launch, and for an 8 person team, that's pretty crazy already.
However, we still asked for dev kits from the middle of last year. Unfortunately, it took some time (as you guys know) for the ID program to get up and running, and we didn't get kits until after release. I think that's pretty reasonable - Microsoft was creating a new program, and priority probably should have gone to other devs who were not launching on other platforms, who wanted kits. But, obviously it meant that we couldn't have launched on Xbox One even if we tried.
I think that's the gist of why we "got around" the parity clause. But Microsoft's reasoning is their own. They are pretty flexible in unique situations, which I think is a good thing.
The work around was if you had a deal with another company before this policy came out this didnt apply to your game.Aren't there plenty of demonstrated cases already where they in fact have released games that have launched on other platforms first?
I will say this though, as horrible as this Parity garbage is, bravo Microsoft for grabbing Iron Galaxy to make Killer Instinct Season 2. From the looks of it, they fixed most of the issues I had with season 1. If Phil really wanted to engender trust and make Xbone owners feel like they are 1st class, focus more on projects like Killer Instinct and forget about parity. Microsoft has too much potential with the Xbone for it to be squandered on nonsense.
Basically this: http://www.gamesindustry.biz/articles/2014-08-14-microsofts-chequebook-warfare-is-bound-to-failThank You!! Here is my take, the Xbox One will not be the most powerful system this gen. Wise up and recognize Microsoft! Stop trying to obfuscate and using underhanded methods/tactics in everything you do. Make your box distinct enough that people want it for the irresistible content they cannot get anywhere else. Do this not through enforced parity and moneyhats, do it through creativity and originality.
Umm yeah? That's how many devs have joined the program which enforces launch parity, right?SERIOUSLY? WTF
Maybe earlier in the thread? By the time I got here, people were talking about ID having about 300 members as though it were true. Is it not?Is there a source for that number?
Seems somewhat unbelievable.
How many members does ID have? As I said, I think I saw 285 and 300 mentioned in the thread. Is that not accurate?Going to assume you think that that is the amount of devs in the ID@Xbox program and that ALL of them are holding back games? You are vastly wrong on both the number of devs in ID, and wrong to assume that every one of them had plans to launch on PS4 first. So please, stop making stuff up with posts like that.
Your analogies are a bit flawed.Well, imagine this tactic in other contexts:
Movie theatres: Would it be wrong for one movie theatre to refuse to show a 6 month old movie from a studio that released it in a rival theatres in the same city first? Especially if the movie didn't perform well? Would it be anti-competitive for a movie theatre to have a policy that they only show the latest releases? I don't think so, and I think you could understand why.
Clothing stores: could we blame a store that didn't want to feature a jacket that was from last season? I think we'd feel fine with them refusing it and we wouldn't call it "anti-competitive" for not having release date parity on a once-hot fashion item that has since lost its appeal.
Umm yeah? That's how many devs have joined the program which enforces launch parity, right?
As of August there were over 500 developers signed to id@xbox with dev kits.
http://news.xbox.com/2014/08/gamescom-id-xbox-games-coming-to-xbox-one
But some could be people like chubagins where they have a dev kit, yet won't release their game because of the launch parity clause.
That's where you're wrong. They need to listen to people who don't have xbones so that they can sell those people xbones. If you consistently ignore the concerns of potential consumers, they will ignore your product and go with the obviously better competing product.
Places like /r/xboxone, which is a pretty amusing place.
Right, there could've been other factors which made agreeing to launch parity a comparatively easy decision for the dev in question, but by joining, they agreed to it, unless they're one of the privileged few who were granted an exception to the clause.
Where are the "in Phil we trust" group now?
Phil was a part of the group that put the Xbone and its initial policies together - why there ever was an assumption that he would usher in a complete reversal of Microsoft's shittiness, I'll never know.
I will say this though, as horrible as this Parity garbage is, bravo Microsoft for grabbing Iron Galaxy to make Killer Instinct Season 2. From the looks of it, they fixed most of the issues I had with season 1. If Phil really wanted to engender trust and make Xbone owners feel like they are 1st class, focus more on projects like Killer Instinct and forget about parity. Microsoft has too much potential with the Xbone for it to be squandered on nonsense.
I would go further, Phil has been at Microsoft since the 80s, you can imagine what philosophies he follows being in that bubble for so long.
Sure you can. In fact, you'd have little reason not to, at that point.Well you can't really agree to parity when you haven't got a kit for the competition.
Umm yeah? That's how many devs have joined the program which enforces launch parity, right?
Maybe earlier in the thread? By the time I got here, people were talking about ID having about 300 members as though it were true. Is it not?
How many members does ID have? As I said, I think I saw 285 and 300 mentioned in the thread. Is that not accurate?
And no, not all of them will have agreed to delay their PS4 game. MS like to imply they make exceptions in special cases, but the only exceptions I personally know of were developers who heard about the ID program's parity clause before it was officially announced, and scrambled to sign an exclusivity deal with Sony before it was. Perhaps they've made other exceptions for Mojang-class devs and/or devs who've managed to get some public outcry going, but I don't personally know of any, and I imagine such exceptions are few and far between.
Then you'll have fanboys who never planned to release on PlayStation because reasons, but I can't imagine that makes up a large fraction of their members.
So no, not all of them will have agreed to delay a PS4 game, but it seems likely the vast majority of them have done so. Hence, "about 300." Even if 10% managed to get an exception, that's still 270 who didn't, which I'd still consider "about 300."
That said, it sounds like you have a more accurate number you can share? Where did you get it?
Your analogies are a bit flawed.
Movies:
AMC: Hey, we heard you've been giving Regal movies with surround sound, and we're only getting stereo. How does that make us look?
Warner Bros: Well, they have surround speakers, and you guys only have stereo.
AMC: Okay? So just deliver stereo movies to them too, or we'll never show any of your movies.
Clothes:
Kohl's: WTF? You're already delivering to Gordman's?? Where are the clothes you promised us?
DKNY: Err, Gordman's are already open. Your store doesn't even have a door cut yet. How are we supposed to deliver your stuff now?
Kohl's: You can't, obviously, but you need to delay their shipment until we're ready to open, or we'll never carry any of your clothes.
That stuff is anticompetitive. Also, your examples are stuff that has more of a "shelf date" than what we're talking about. With movies and clothes, there was nothing preventing me from going to the competition and getting the new thing last year when it was new. Video games are different in that most people are locked in to whatever platform they happened to buy. When Castle Crashers came to PlayStation, it was new to me, because I don't own an XBox; I had no opportunity to play it before now. For most gamers, these games don't lose value simply because someone else already played it.
Ah, right on. Sorry for the confusion. It sounded like you were saying, "Situations such as these aren't really bad," and I was saying, "Yes, but those examples are almost entirely unlike what we're actually dealing with here."Erm.. you manipulated my examples into totally different situations.
Those weren't really meant to be analogies. I'm saying the practice of demanding release date parity for various types of products isn't an evil in and of itself which we should frown upon in the abstract. Those examples were specifically offered as an acceptable contrast to Microsoft's parity clause.
The thing is, no, your examples weren't anticompetitive, but they also didn't describe the behavior MS engage in. The anti-competition comes in to play when you take actions to hamstring your competitors. I agree that not taking actions to harm your competitors isn't anticompetitive behavior, but I maintain that doing so is.I agree with you about Microsoft and it looks like we aren't going to see eye to eye about the definition of the word "anti-competitive." I can live with that.