» Wed May 16, 2012 12:54 am
In response to the thread, you couldnt take it up as an issue the same as what EA are facing there. Purely because theres no promise been made by bethesda, they havent gone back on anything.
However.
Overall, bethesda knew of this issue, it has been present in FO3 and FONV, they knew this... and should have completely tested for this, after it has plagued their engine for the past two releases. Now if they supposedly tested this in depth, then two things have happened:
They never encountered this bug, meaning they didnt test it enough
Or , they did encounter this bug, realise they couldnt fix it before release, so kept quiet about it.
Now the point you could argue is that they knew about this issue before selling the game, and therefore should not have sold you the game OR given you a written warning along with the game that this issue was there.
Failure to do so is clarified as knowingly selling a product of inferior quality, and comes under an attempt to decieve in a transaction.
Now, ontop of this... you can also request a full refund from Bethesda directly, stating the issue, and they should be obliged to give you that full refund. The product is faulty, as far as law goes, it does not do what it says on the tin, so to speak. However you have to go down the route of getting a refund , and being declined one, before you can take any action against them. As by law the issues here fall under product quality and malfunction, not false advertising.