It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
...and well, everytime they said something stupid.

http://www.gamerheadlines.com/2014/11/ubisoft-dev-on-acu-issues-game-testing/

It's impossible they can't try their games before shipping them.

Now they are blaming PS4 firmware 2.0, so that's is the problem causing "some small bugs". Ok. But why there are so many bugs on PC and One too? :D
Post edited November 21, 2014 by ThePunishedSnake
seaturtles mate
Yes, we do have retail units, but you can’t test anything on them, because they can only run signed code. Which means that the only time when we can actually run a game we worked on on a retail console is when we get the actual discs with it in the studio, couple weeks before the release.
Did he just say that the DRM in the retail versions cause problems? And not being able to test it on an actual console seems like a bad idea. What do they do? Send their resources to Sony; Then Sony makes a custom disc and ships it back to them, then they can look for issues while they don't have any debugging assistance? That's comparable to an architect looking at a building with binoculars from a mile away trying to tell you why the foundation is unstable...
"Zut alors! Unity is a catastrophe! We have to apologize!"
- "Yes, but how?"
"By blaming someone else!"
- "Brilliant! ... Who?"
"Ummmmmh...uh...got me!"
- "PIRATES!"
"Naaaah, there are no pirates on the PS4..."
- "Merde!"
"Oooh, I know, let's blame PS4! That starts with a 'p' too, so it's virtually the same!"
- "Right on it!"
Post edited November 23, 2014 by Randalator
^ yeah they cant blame AMD this time
Can someone explain why is it that new games (released near the firmware update) are affected but older games don't? How does that work?
Post edited November 21, 2014 by Cyraxpt
avatar
Cyraxpt: Can someone explain why is it that new games (released near the firmware update) are affected but older games don't? How does that work?
I'd speculate that older games weren't as tailored to specific aspects of the firmware as the more recent ones. Same principle that makes end-of-generation games look so much better than games from the starting line-up...

Yes, we do have retail units, but you can’t test anything on them, because they can only run signed code. Which means that the only time when we can actually run a game we worked on on a retail console is when we get the actual discs with it in the studio, couple weeks before the release.
avatar
rtcvb32: Did he just say that the DRM in the retail versions cause problems? And not being able to test it on an actual console seems like a bad idea. What do they do? Send their resources to Sony; Then Sony makes a custom disc and ships it back to them, then they can look for issues while they don't have any debugging assistance? That's comparable to an architect looking at a building with binoculars from a mile away trying to tell you why the foundation is unstable...
Yeah he did. :D

I love reading forums for really disastrous releases and I have not read about a single bug on its steam discussion that can't be explained by three things.

1: A really bad port. The missing skins are exactly what happens when for example you install a skin texture in Skyrim incorrectly. The skeleton and textures aren't properly "talking" to each others.
VERY demanding for getting even decent graphics on PC. The performance issue on PC is also most probably connected to the DRM.

2: Really shitty Uplay connections, server code, net code or something similar. Basically the game needs to call home all the time and it gets a lot of late or missed calls. Lag, stutter and so on.

3: DRM. A really restricting DRM. That's not just a 5% performance hit that companies have been known to claim DRM only give. This is really a extension of the previous point.

It's been really fun reading threads where gamers say it works much better "offline".
avatar
rtcvb32: Did he just say that the DRM in the retail versions cause problems? And not being able to test it on an actual console seems like a bad idea. What do they do? Send their resources to Sony; Then Sony makes a custom disc and ships it back to them, then they can look for issues while they don't have any debugging assistance? That's comparable to an architect looking at a building with binoculars from a mile away trying to tell you why the foundation is unstable...
avatar
Tarm: Yeah he did. :D
No he did not.
Signed code just means just that, it's been signed to verify it as being safe and executable code.

Obviously some of what he said is about covering their own asses, but the thing with the firmware at least is plausible.
But I seriously doubt that 99% of the issues weren't around on the devkits.
And if the PC version has the same issues, well...
ubisoft games having draconian DRM bollcoks that damn near castrate the game they are trying to protect
and then try to pass the blame off to anything else other then their own ineptitude and paranoia

tell me what else is new ?
avatar
Randalator: I'd speculate that older games weren't as tailored to specific aspects of the firmware as the more recent ones. Same principle that makes end-of-generation games look so much better than games from the starting line-up...
So in this case, they were aiming for some features/code that was available on fw 2.0 but it was not what they expected because Sony screwed up?
Uhm, it would be interesting to grab one console with the old firmware and one game that doesn't need day one patch but has some problems because of the new fw to see if what they're saying is true or not.

Not that it matters, Ubisoft released that garbage in 3 different plataforms and the fw from one console doesn't excuse the problems of the other 2...
avatar
Tarm: Yeah he did. :D
avatar
Smannesman: No he did not.
Signed code just means just that, it's been signed to verify it as being safe and executable code.

Obviously some of what he said is about covering their own asses, but the thing with the firmware at least is plausible.
But I seriously doubt that 99% of the issues weren't around on the devkits.
And if the PC version has the same issues, well...
That's a pity. Would have been seriously funny. :)
Never change, Ubisoft.
avatar
Randalator: I'd speculate that older games weren't as tailored to specific aspects of the firmware as the more recent ones. Same principle that makes end-of-generation games look so much better than games from the starting line-up...
avatar
Cyraxpt: So in this case, they were aiming for some features/code that was available on fw 2.0 but it was not what they expected because Sony screwed up?
Nope, other way round.

Because they had more time to work with the old firmware and got to understand it better, they wrote code which used specific aspects or kinks of it. FW 2.0 changed those and things went kabloeey...
avatar
ThePunishedSnake: ...and well, everytime they said something stupid.

http://www.gamerheadlines.com/2014/11/ubisoft-dev-on-acu-issues-game-testing/

It's impossible they can't try their games before shipping them.

Now they are blaming PS4 firmware 2.0, so that's is the problem causing "some small bugs". Ok. But why there are so many bugs on PC and One too? :D
I also put blame on the fact that Ubisoft Montreal, the guys that made AC Unity, were also busy making Far Cry 4 and Watch Dogs. All 3 released on the same year and all released on multiple systems. And not only that Montreal is also making Rainbow Six Siege for next year. They are juggling 4 games in development. No wonder AC Unity was an assfucked buggy mess.