@censurely wrote:
Here is a better analogy (I think) since it relates directly to disclaimers (which is what those minimum requirements essentially are).
The label on the side of my cup of coffee says "contents hot, may burn you". Are the contents hot by my definition? Maybe not. In fact... most of the time the contents don't seem hot to me. Lets say I've bought coffee many times and it was "tepid" by my definition 100 out of 100 times. I know other people have gotten coffee they consider to be hot... but what matters to me is my own experience and the experience of the people I want to listen to. I, therefore, used inductive reasoning to assume it would never be hot in the future for me. That label still exists though... which means that if I open that cup of coffee in an irresponsible manner and burn myself the company did its due dilligence. Period. The fact that i was burned was not that companies fault. My experience, and my inductive conclusions based on that experience, is entirely irrelevant. You've yet to explain why this sceario (which I attempted to explain through the gambling analogy) is fundamentally different. Your inductive reasoning used to selectively choose when you feel that the word requirement really means requirement is entirely irrelevent.
That's not to say I don't have a case if I end up with 3rd degree burns over 1/3 of my body (in that case a specific cup of coffe was made unreasonably hot and/or a policy is in place that made that coffee unreasonbly hot) but in a fundamental way the company did it's due diligence and, more importantly, my anecdotal perceptions are entirely irrelevent.
To bring us full circle... here I am looking at the back of a PC game and its list of requirements. I know X requirement is flexible (at least based on my inherently limited anecdotal experience). That doesn't actually change that it's a requirement. My inductive reasoning doesn't change the words on the box or what they actually mean. This company is communicating, clearly to me, that I shouldn't buy this game unless I meet this minimum. My person experience is irrelevent. They are telling me to hold on to my money until I meet those minimums. Do they want my money?! Of course.. but they would rather their customers have a good chance of being realtively happy with their product. I have actually always assumed that they inflate those minimums to play it safe... in my book that makes them responsible advocates on behalf of the consumer. Does that assumption change the substance of that disclaimer in any way?! No. If my CPU is 1mhz below those disclaimers I am taking my chances. I get that you, on a personal level, don't seem to think that is reasonable... I just disagree.
I don't disagree with anything in your post. What I am saying though is that it might benefit the company to do more than it's "due diligence" as there is no cost involved to do so, and a considerable benefit. In your coffee analogy the company knows that it is likely the case that the coffee won't be so hot it will burn somebody, but there is still the miniscule possibility, so to protect itself from lawsuits it labels the coffee as hot. Now, my concern isn't that the company is not trying to send a message about minimum requirements. I do think that it is in this case. My concern is that if the company could've made the message clearer and more explicit If on the box it said that the game will not run without a quad-core, just like games in the past said that they will not run unless the GPU had DX9 or DX 10 then I think EA/Bioware would have fewer people trying to argue that they should support the game. Furthermore, if it does come out that the game is able to run on a dual-core platform and it was a simple code injection away, then that creates an atmosphere of laziness to the consumer (such is the case now with Ubisoft and Far Cry 4), regardless of whether that is a legitimate judgement or not. Companies don't care about whether or not complaints are legitimate, but rather whether or not they exist in the first place, and how damaging they can be. I am arguing that it would've been in EA's/Bioware's interest, knowing very well that core-count never really was a hard-requirement to startup the game and also knowing very well that many consumers wouldn't mind running the game at low setting and framerates, to make it clear through their information that the game is not only performing poorly on dual-cores but it is also not performing at all on dual cores. Now I understand there was risk involved on the consumer's end, and I don't think the consumer is entirely blameless, but the producer has power to reduce such conflicts, and it makes sense - especially since the cost is minimal - to use such power. Some of the confusion, for example, was caused by a Bioware QA saying he was running the game quite well on a 2-threaded CPU and that people with 2-threaded CPU's should be fine. That turned out to be false, he was running two 2-threaded Xeons, not one. Information like that confuses people and causes a distrustful environment, regardless of whether the mistakes were legitimate.
MOD EDIT: To clear up some potential misinformation, here are the exact quotes referenced in this post.
http://forum.bioware.com/topic/515302-dragon-age-inquisition-pc-screenshots-system-requirements-and-...
http://forum.bioware.com/topic/515302-dragon-age-inquisition-pc-screenshots-system-requirements-and-...
- Fred_vdp