So forget CBOAT's post and any paranoid speculation but this is what really concerns me. It's 2 weeks out from launch and and simple OS patches are bricking consolesOk so pre-release builds ban you from playing SP. Ok, got it, thanks Albert.
But having to always be online was part of the DRM policy, so having to patch it to play offline HAS to be something to do with DRM. Why manufacture a console without DRM and then have to patch it so it doesn't behave as if it HAD DRM. It doesn't make sense at all. Playing offline should be no problem at all if what Penello said is perfectly honest.
You really thought they shipped the software with all the drm stuff? No. They had plenty of time to take that stuff out. They require a day one update so that they can have the extra development time to work on a shippable OS.
Just hold one second ... just one second:
Then why do you need the patch in the first place. Wasn't the reason for the patch to remove DRM. Isn't that what MS told us? If it's not to remove DRM and only to update the OS, were they going to let us continue to believe it was to remove DRM as first stated? Mmmmm ...
I have less of a problem with that if its just an OS fix, and more of an issue with the fact that if they knew this in June, why didn't they plan for a better solution than just "DL THE PATCH DAY 1"?
I'm thinking discs shipped to retailers, etc, etc.
I'm a little confused here. I thought the reason it was required to play games offline was because you literally cannot use the system at all without the update putting the launch OS in its final form in place. Naturally, if the system did have a proper OS in place, it would not play games, offline or otherwise. So that could also be the case?
I am close to giving up trying to follow this confusing madness.
I don't know any more. I too am incredibly confused.I'm a little confused here. I thought the reason it was required to play games offline was because you literally cannot use the system at all without the update putting the launch OS in its final form in place. Naturally, if the system did have a proper OS in place, it would not play games, offline or otherwise. So that could also be the case?
I am close to giving up trying to follow this confusing madness.
No, they said a day one update doesn't have to do with DRM and it was always planned.
It's because they started manufacturing these things in late-August or early September. Why would they force themselves to have "final" OS software back in August when they can just deliver an update in November? Sony's doing the same thing.
I'm a little confused here. I thought the reason it was required to play games offline was because you literally cannot use the system at all without the update putting the launch OS in its final form in place. Naturally, if the system did have a proper OS in place, it would not play games, offline or otherwise. So that could also be the case?
I am close to giving up trying to follow this confusing madness.
Because they are manufacturing boxes months in advance of essential OS functions being completed. It's not that difficult to comprehend, really. You're not downloading a "patch" on Day 1. You're downloading a completed OS.
So answer me, why can't he play offline?
Because the OS is fucked/not final/not workable/etc
So answer me, why can't he play offline?
Because he did not have a final consumer OS. What he downloaded was most likely a beta/developer OS with a limited functional window. Ans that most likely expired after he lost XBL access.But then, how was he able to play offline yesterday and not today? The only explanation was that he never played yesterday and assumed it to be the case, which doesn't make sense either.
From the looks of it, itsfuckingnothing.gif.
But then, how was he able to play offline yesterday and not today? The only explanation was that he never played yesterday and assumed it to be the case, which doesn't make sense either.
Makes sense. They needed to a finish a version the OS before consoles started being manufactured, but that was months ago. There must have been lots of works still to do, and they wanted every last second of time to work on the OS. The day one patch gives them tons of extra time. As Penello said they are still working on it now, only two weeks before release.From Kotaku 6/19/13
UPDATE: Microsoft clarifies that the planned day-one Xbox One update, which Whitten told me, will "complete some of the software that won’t be there," is actually not a result of today's DRM policy change. Rather, it was always planned and will simply be required for playing off-line, among other things. Not a patch, they say. But, yes, your new Xbox console would have to connect online once in order to do the things Microsoft described today. And then you can keep it offline and play games without re-connecting to the Internet forever.P
http://kotaku.com/xbox-one-drm-reversal-cuts-features-requires-one-time-514419715
Because the OS is fucked/not final/not workable/etc
Or maybe yesterday's version of the OS worked and it expired. Or he downloaded an update that fucked it.
But then, how was he able to play offline yesterday and not today? The only explanation was that he never played yesterday and assumed it to be the case, which doesn't make sense either.
This is going round in circles. How was he playing the games online AND offline yesterday if the OS was fucked (as you put it). Did it eventually crash? Is that what you are getting at?
This is going round in circles. How was he playing the games online AND offline yesterday if the OS was fucked (as you put it). Did it eventually crash? Is that what you are getting at?
His build expired and he is blocked from Live so he can not download the current build.
Because he did not have a final consumer OS. What he downloaded was most likely a beta/developer OS with a limited functional window. Ans that most likely expired after he lost XBL access.
Or maybe yesterday's version of the OS worked and it expired. Or he downloaded an update that fucked it.
Thank you. Exactly right.
His build expired and he is blocked from Live so he can not download the current build.
FYI it's 11pm on a Sunday, so people aren't exactly quick to respond to work email. I wanted to check in before I shut-down for the evening. This is what I believe is going on:
We still have two more weeks before launch - the console is in a pre-release state. We are doing regular updates - I personally took one a few minutes before he posted. His build is now old. This is why we were saying we didn't want people on early - it's not done yet.
This behavior is only because we are in pre-release. When we launch, console will work exactly as you expect today on 360.
For sure this has nothing to do with requiring a connection. There is no "DRM removal" in the Day One update because none of the consoles were ever built with that stuff in it.
This also has nothing to do with COD. The Day One update just brings the SW up to date with the latest versions vs. what's on the box. But there is no 24 check in, that's for sure.
This is pointless. Not everything has to be filtered through the lens of the warz.
His build expired and he is blocked from Live so he can not download the current build.
FYI it's 11pm on a Sunday, so people aren't exactly quick to respond to work email. I wanted to check in before I shut-down for the evening. This is what I believe is going on:
We still have two more weeks before launch - the console is in a pre-release state. We are doing regular updates - I personally took one a few minutes before he posted. His build is now old. This is why we were saying we didn't want people on early - it's not done yet.
This behavior is only because we are in pre-release. When we launch, console will work exactly as you expect today on 360.
For sure this has nothing to do with requiring a connection. There is no "DRM removal" in the Day One update because none of the consoles were ever built with that stuff in it.
This also has nothing to do with COD. The Day One update just brings the SW up to date with the latest versions vs. what's on the box. But there is no 24 check in, that's for sure.
His build expired and he is blocked from Live so he can not download the current build.
The build had not expired yet? Maybe each build works for a limited time before expiring. The final build will not have that limit of course.
Damn he was so unlucky to get a patch that expired on the very day he got his X1.
His build expired and he is blocked from Live so he can not download the current build.
The build had not expired yet? Maybe each build works for a limited time before expiring. The final build will not have that limit of course.
So what you're telling me is that any beta tester or reviewer, or developer, or MS employee that has a console in their house; if they dont download the latest update right away it bricks their console?
This is seriously fucked up If he can't download the latest build.
His build expired and he is blocked from Live so he can not download the current build.
The build had not expired yet? Maybe each build works for a limited time before expiring. The final build will not have that limit of course.
Because he did not have a final consumer OS. What he downloaded was most likely a beta/developer OS with a limited functional window. Ans that most likely expired after he lost XBL access.
So basically we are mad that Microsoft did not bake in the DRM reversal/play offline patch into the system from an earlier date?
Still trying to figure out the controversy here.
I think the scariest part about all this is why has Microsoft built into their system a way to deny us from playing single player games offline from the disk? This suggests that they can just turn our games off at any point, even physical offline games. The question is not why would Microsoft ever turn our games off but rather why did they give themselves the ability to do it at all?
Other than as an academic exercise, why on earth would you care or even think they should divulge every pre-release detail?So what you're telling me is that any beta tester or reviewer, or developer, or MS employee that has a console in their house; if they dont download the latest update right away it bricks their console?
So what you're telling me is that any beta tester or reviewer, or developer, or MS employee that has a console in their house; if they dont download the latest update right away it bricks their console?
If the build expiring forces you to get back online to download an update to continue playing your offline games, how is this different than the proposed 24 hour check in? Will builds never do this after launch?
Build expired? LOL
FYI it's 11pm on a Sunday, so people aren't exactly quick to respond to work email. I wanted to check in before I shut-down for the evening. This is what I believe is going on:
We still have two more weeks before launch - the console is in a pre-release state. We are doing regular updates - I personally took one a few minutes before he posted. His build is now old. This is why we were saying we didn't want people on early - it's not done yet.
This behavior is only because we are in pre-release. When we launch, console will work exactly as you expect today on 360.
For sure this has nothing to do with requiring a connection. There is no "DRM removal" in the Day One update because none of the consoles were ever built with that stuff in it.
This also has nothing to do with COD. The Day One update just brings the SW up to date with the latest versions vs. what's on the box. But there is no 24 check in, that's for sure.
If the build expiring forces you to get back online to download an update to continue playing your offline games, how is this different than the proposed 24 hour check in? Will builds never do this after launch?
WHY DAY ONE UPDATE THEN????