• Hey, guest user. Hope you're enjoying NeoGAF! Have you considered registering for an account? Come join us and add your take to the daily discourse.

Quantum Break PC is a mess (non-native render, badly optimized, overpriced, etc)

GHG

Gold Member
We need to repro issues, research them, analysue and then we can say whats up. Please have some patience.

You can reproduce most of the issues by simply playing the game. One of them is staring you right in the face the moment you start the game up and get to the main menu.

The first step to fixing something is admitting you have a problem. That would be nice and I think you'd get a lot more empathy from the community that way.
 

Poster#1

Member
You can reproduce most of the issues by simply playing the game. One of them is staring you right in the face the moment you start the game up and get to the main menu.

The first step to fixing something is admitting you have a problem. That would be nice and I think you'd get a lot more empathy from the community that way.

Do you have the game? You seem concerned.
 

cyen

Member
well... im embarassed to say this (please be gentle with me) but i spent 70 euro bucks on this game.

Im finishing the second act, and it´s a great game gameplay and story wise but i can´t make my mind if i should continue playing it or stop until the problems are fixed, im playing at 1440p and the performance is awfull, specially when comparing it to The Division that in my opinion runs ten times better for the visuals im getting from the game.

The IQ is horrendus, after playing Division, Witcher, Tomb Raider, etc i can´t get used to it, everything is blured, pardon me, super blurred, i can only see texture details if im facing directly to the texture (even forcing 16x AF). Why can´t the pc owners have the option to render the game natively? Rainbow Six also had reconstruction but it gave us the option to turn that blurry shit off on PC.

Even worse is the framepacing, it makes the game almost nauseating and borderline unplayable for me.

I did not expect something like this from Remedy, until now it´s my biggest let down of the year, i really hope they can fix this.
 

JaseC

gave away the keys to the kingdom.
What the heck are they doing at Microsoft?
This is the third game launching at their store (after Gears Ultimate and KI) with serious problems, while denying features and holding back patches for days (as seen with Rise of the Tomb Raider) on the basis of security and QA.
What a way to introduce their new platform.

Certification processes are a necessary evil on the PC, too. I mean, Steam has almost half a million apps in its database and exactly 0% of them have malicious--oh.
 

Saintruski

Unconfirmed Member
Certification processes are a necessary evil on the PC, too. I mean, Steam has almost half a million apps in its database and exactly 0% of them have malicious--oh.

It's funny on the rare occasion my scanners will detect some of my steam games as Trojans....false positives of course but when Microsoft made that announcement it made me chuckle.
 

Saty

Member
The weirdest thing about this whole UWP affair is: why the rush?

It's clear that UWP isn't ready for prime-time so why did MS insist on launching the games now instead of waiting a few more months and then launching Gears, KI, QB, Forza for PC on the same day? There's a weird clash here because it's great to have simultaneous launch for XB1 and PC games and it would be better for sales of the PC version to launch with the marketing cycle of the console version. But on the other hand, launching the games when the UWP is under-featured and with all these issues will cripple the sales of the PC game and no one will want to get near for quite some time.

I think it would have been a better choice for Microsoft to announce the games coming to W10 at E3 and say something like 'oh, and those 4 games are launching on W10 July 1st' and get the benefit of the hype of multiple titles launching together, hopefully with most of the features PC came to expect.
 
I don't why you bother yourself. If it's a bad port then fuck it, it's their loss.

I don't get this sentiment.

People are anticipating this game on PC, and if they somehow can fix it, people will gladly buy it. Of course not at this state. These people are their potential customers.

Looking forward to what imaginary issues you'll find. ;)

image.php
 

Starfield

Member
At this point early buyers of the PC version should get the new Tomb Raider for free as compensation so they can play something while QB is getting fixed.

Anyone agree?
 

Trup1aya

Member
The weirdest thing about this whole UWP affair is: why the rush?

It's clear that UWP isn't ready for prime-time so why did MS insist on launching the games now instead of waiting a few more months and then launching Gears, KI, QB, Forza for PC on the same day? There's a weird clash here because it's great to have simultaneous launch for XB1 and PC games and it would be better for sales of the PC version to launch with the marketing cycle of the console version. But on the other hand, launching the games when the UWP is under-featured and with all these issues will cripple the sales of the PC game and no one will want to get near for quite some time.

I think it would have been a better choice for Microsoft to announce the games coming to W10 at E3 and say something like 'oh, and those 4 games are launching on W10 July 1st' and get the benefit of the hype of multiple titles launching together, hopefully with most of the features PC came to expect.

Yeah, this is my question too... Except for KI, it's a good port despite UWP limitations... It just has a non UWP related bug.
 
The weirdest thing about this whole UWP affair is: why the rush?

It's clear that UWP isn't ready for prime-time so why did MS insist on launching the games now instead of waiting a few more months and then launching Gears, KI, QB, Forza for PC on the same day? There's a weird clash here because it's great to have simultaneous launch for XB1 and PC games and it would be better for sales of the PC version to launch with the marketing cycle of the console version. But on the other hand, launching the games when the UWP is under-featured and with all these issues will cripple the sales of the PC game and no one will want to get near for quite some time.

I think it would have been a better choice for Microsoft to announce the games coming to W10 at E3 and say something like 'oh, and those 4 games are launching on W10 July 1st' and get the benefit of the hype of multiple titles launching together, hopefully with most of the features PC came to expect.

I think it's this.

Staggered releases hurt sales and so do bad ports. They chose the latter option, is all.
 

wapplew

Member
The weirdest thing about this whole UWP affair is: why the rush?

It's clear that UWP isn't ready for prime-time so why did MS insist on launching the games now instead of waiting a few more months and then launching Gears, KI, QB, Forza for PC on the same day? There's a weird clash here because it's great to have simultaneous launch for XB1 and PC games and it would be better for sales of the PC version to launch with the marketing cycle of the console version. But on the other hand, launching the games when the UWP is under-featured and with all these issues will cripple the sales of the PC game and no one will want to get near for quite some time.

I think it would have been a better choice for Microsoft to announce the games coming to W10 at E3 and say something like 'oh, and those 4 games are launching on W10 July 1st' and get the benefit of the hype of multiple titles launching together, hopefully with most of the features PC came to expect.

Microsoft always rush unpolished product and ask customer buy them base on thier potential.
All the Windows, surface, mobile, Kin, Kinect...
But their are good at fixing thing and slowly turn them into a good product. Most of them get killed before that happen thou.
 

Kysen

Member
The weirdest thing about this whole UWP affair is: why the rush?

It's in line with MSs' other efforts around software releases. Release it buggy/lacking features and patch it up later.

Other examples:
Edge browser
Win 10
SP4/SB (firmware)
newest Win Phones (OS/firmware)
 
Knowing it was another UWP release I figured some common PC features would be restricted, but holy fuck the stuff in the OP looks terrible. That's what, 3 for 3 on trash MS UWP releases so far? Time to start pretending they don't exist so I don't get my hopes up.

Then again, maybe MS is trying some reverse psychology. Been seeing a lot of posts about how there's no need for an XBO if all the good stuff is coming to PC, so perhaps they're throwing us some sacrificial lambs to convince us to break down and get one to avoid this half-assed shit.
/s
 

ISee

Member
I don't why you bother yourself. If it's a bad port then fuck it, it's their loss.

That's what I'm doing tbh, right after I lol at posts telling me to be thankful for getting a port in the first place independent of the quality. But I get why people who don't own the game are a bit angry. I was looking forward to this too.
 
The weirdest thing about this whole UWP affair is: why the rush?

It's clear that UWP isn't ready for prime-time so why did MS insist on launching the games now instead of waiting a few more months and then launching Gears, KI, QB, Forza for PC on the same day? There's a weird clash here because it's great to have simultaneous launch for XB1 and PC games and it would be better for sales of the PC version to launch with the marketing cycle of the console version. But on the other hand, launching the games when the UWP is under-featured and with all these issues will cripple the sales of the PC game and no one will want to get near for quite some time.

I think it would have been a better choice for Microsoft to announce the games coming to W10 at E3 and say something like 'oh, and those 4 games are launching on W10 July 1st' and get the benefit of the hype of multiple titles launching together, hopefully with most of the features PC came to expect.
9032a-2011-06-27_organizational_charts-ms.png


The development and maintenance of MS Store is not under Xbox division, and I'd wager the communication is not that good between Xbox and Windows team.
 

LordRaptor

Member
Are they serious? Please tell me they are joking.

This is not the Remedy I remember.

Good Guy Remedy sacrificing QB to get the message out to stay the hell away from UWA

I think it would have been a better choice for Microsoft to announce the games coming to W10 at E3 and say something like 'oh, and those 4 games are launching on W10 July 1st' and get the benefit of the hype of multiple titles launching together, hopefully with most of the features PC came to expect.

Given the Win10 Store has no functionality for things like "coming soon" landing pages, preorders or preloading, MS don't actually benefit at all from anything other than announcing a game is available on literally the day it becomes available.
 

Doffen

Member
9032a-2011-06-27_organizational_charts-ms.png


The development and maintenance of MS Store is not under Xbox division, and I'd wager the communication is not that good between Xbox and Windows team.

That's an old structure of Microsoft, I'm quite certain Satya changed it when he took over.
Anyone working at Microsoft are welcome to correct me.
 

Rymuth

Member
I find really strange that comment from a Remedy representative, it´s clear to everyone that played the game that it has major issues.
It's the same thing when people reported issues with Master Chief Collection, Black Crush and the rejection of the Always-online polices.

When there's a problem, MS and their developers always blame the consumer.
 
That's an old structure of Microsoft, I'm quite certain Satya changed it when he took over.
Anyone working at Microsoft are welcome to correct me.
The new structure wasn't helping much, there is no way that Microsoft doesn't know the state MS Store is in, yet Phil Spencer could only give safe, vague PR promise of "fixing" UWA.

Quantum Break simply showed they weren't trying very hard on delivering a competent PC port.
 

LordRaptor

Member
When there's a problem, MS and their developers always blame the consumer.

As I've said before, UWA does exactly what it was engineered to do, which is allow mobile developers an easy way to convert their existing Win32 builds to work on a Windows Phone and let people distribute their WinPhone apps on the Win10 Storefront.

Using UWA as AAA DRM and the Win10 Storefront as a surrogate GFWL 2.0 when neither were clearly ever intended for that purpose is squarely on the shoulders of Phil Spencer and the Xbox division.
 

GHG

Gold Member
I think this also needs to be added to the OP:

Quantum Break has arrived on the PC and to suggest that the results are disappointing would be a massive understatement. PC gamers are left out in the cold with another high profile release failing to deliver expected levels of performance, features and customisation. As things stand, it simply isn't possible to achieve a smooth frame-rate on any PC hardware configuration and thanks to the profound limitations imposed on gamers by the Universal Windows Platform, there's no way to fix it.

We really enjoyed Quantum Break on Xbox One and the promise of using additional horsepower to smooth out the game's issues and play at 60fps was a huge lure in us fronting up the cash to buy the PC game, but the bottom line is that the PC version is a profound disappointment. The few improvements on offer cannot offset the major performance and image quality issues present in this port. What really stings is that some of these issues could be addressed by the community right now if not for the limitations of the Universal Windows Platform. We've expressed concerns over Microsoft's multi-platform initiative in the past and this situation is a perfect example of why. Until these limitations are removed from UWP, it's really hard to recommend purchasing any game that runs on it.

http://www.eurogamer.net/articles/digitalfoundry-2016-what-went-wrong-with-quantum-break-pc
 

SomTervo

Member
You can reproduce most of the issues by simply playing the game. One of them is staring you right in the face the moment you start the game up and get to the main menu.

The first step to fixing something is admitting you have a problem. That would be nice and I think you'd get a lot more empathy from the community that way.

It doesn't matter how much it's "staring you in the face", though. There is a process for this. They will have a database and quality/procedural checks at every step whenever there's an issue. Every issue, no matter how minor/major, will have to go through several steps and several people before it can get added to the fix log. They can't just fire out a loose hand-written list of the issues they notice. It has to be dealt with methodically, and that takes time.

(Not that I'm excusing a shameful port :p just defending their undoubtedly airtight troubleshooting process)
 

GHG

Gold Member
It doesn't matter how much it's "staring you in the face", though. There is a process for this. They will have a database and quality/procedural checks at every step whenever there's an issue. Every issue, no matter how minor/major, will have to go through several steps and several people before it can get added to the fix log. They can't just fire out a loose hand-written list of the issues they notice. It has to be dealt with methodically, and that takes time.

(Not that I'm excusing a shameful port :p just defending their undoubtedly airtight troubleshooting process)

Of course there is a process, I don't doubt that. What is in question is how they have responded to the community since the game has been released. I mean how can they state they are checking if the problems are "real" or not? Simply apologising and saying they are taking the feedback seriously and will fix as much as possible ASAP would be a much better response.

Then there is the speed which they can get stuff out which is another issue, but that isn't their fault, we all know that.
 
9032a-2011-06-27_organizational_charts-ms.png


The development and maintenance of MS Store is not under Xbox division, and I'd wager the communication is not that good between Xbox and Windows team.

Think about it. If that picture was still true, then we wouldn't see Quantum Break on PC, much less on the Windows Store. The Xbox and Windows divisions both report to the same boss.
 

LordRaptor

Member
I think this also needs to be added to the OP:

The biggest shockers to me there and from the thread about it are:
bonus points to UWP for overwriting our Xbox One completed game save with fresh PC data instead, eliminating our existing progress completely.

and

you cannot play on XO and PC at the same time even with two licensees.

What the fuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuck......?

They can't just fire out a loose hand-written list of the issues they notice. It has to be dealt with methodically, and that takes time.

Sure, it's just annoying that due to UWA when there is an RC fixed build ready for deployment, its not going to be deployed because it has to go back and forth with MS cert first, to make sure it passes all of the important issues like displaying a message telling you not to turn off your console while data is saving
 

Zojirushi

Member
It doesn't matter how much it's "staring you in the face", though. There is a process for this. They will have a database and quality/procedural checks at every step whenever there's an issue. Every issue, no matter how minor/major, will have to go through several steps and several people before it can get added to the fix log. They can't just fire out a loose hand-written list of the issues they notice. It has to be dealt with methodically, and that takes time.

(Not that I'm excusing a shameful port :p just defending their undoubtedly airtight troubleshooting process)

I think they have to phrase it like this because if they just said, yeah we know, they would outright admit to knowingly having released a broken game and they probably can't do that under any circumstances.

They're just in a bad spot right now, it kinda doesn't matter what they say at this point as long as they start releasing patches asap.

We can just hope they're aware of the important stuff because if they come out with yo guys, there's an exit button so everything's cool now right? this won't end well.
 

SomTervo

Member
Of course there is a process, I don't doubt that. What is in question is how they have responded to the community since the game has been released. I mean how can they state they are checking if the problems are "real" or not? Simply apologising and saying they are taking the feedback seriously and will fix as much as possible ASAP would be a much better response.

Then there is the speed which they can get stuff out which is another issue, but that isn't their fault, we all know that.

Yeah, the 'which ones are real' thing is bullshit. Although again, to play devil's advocate, we don't know what sort of random shit people are reporting. Perhaps they are getting a lot of troll-ey reports as well as the legitimate issues which are independently verified.

I think they have to phrase it like this because if they just said, yeah we know, they would outright admit to knowingly having released a broken game and they probably can't do that under any circumstances.

They're just in a bad spot right now, it kinda doesn't matter what they say at this point as long as they start releasing patches asap.

We can just hope they're aware of the important stuff because if they come out with yo guys, there's an exit button so everything's cool now right? this won't end well.

Agreed. Their hands seem pretty much bound with MS hanging right over their head.

Sure, it's just annoying that due to UWA when there is an RC fixed build ready for deployment, its not going to be deployed because it has to go back and forth with MS cert first, to make sure it passes all of the important issues like displaying a message telling you not to turn off your console while data is saving

Naturally. Game I'm working on right now is going through the throes of that right this minute :/
 
The development and maintenance of MS Store is not under Xbox division, and I'd wager the communication is not that good between Xbox and Windows team.
Xbox is part of the Windows org, and a unified store (giving things like preload) has been announced & is on the way. Can't remember if a date has been given.
 
It doesn't matter how much it's "staring you in the face", though. There is a process for this. They will have a database and quality/procedural checks at every step whenever there's an issue. Every issue, no matter how minor/major, will have to go through several steps and several people before it can get added to the fix log. They can't just fire out a loose hand-written list of the issues they notice. It has to be dealt with methodically, and that takes time.

(Not that I'm excusing a shameful port :p just defending their undoubtedly airtight troubleshooting process)
So airtight that everyone involved got so oxygen deprived that they let this dumpster fire of a port loose on the world.
 

SomTervo

Member
So airtight that everyone involved got so oxygen deprived that they let this dumpster fire of a port loose on the world.

QA processes have nothing to do with being given a clearly very small window in which to create a PC port of an XBO game

Regardless, no one did anything about Windows Store after the Rise of the Tomb Raider debacle.

RotTR had nothing on this game. I'm still playing RotTR as a UWP and it's not too bad at all. It's not ideal, obviously, but it's fine on the whole. I'm not surprised there wasn't a huge stink around it. This is a higher profile release and a significantly more broken port.
 

Poster#1

Member
They should fixed it.
I hope they will, it's 2016 and we still getting thing like this in PC -___-

btw: http://www.neogaf.com/forum/showthread.php?p=200463512

They will fix it but it will take couple a month for it to be in acceptable state. I learned my lesson with shitty PC releases to wait till it fixed. If I still had interest then.

That's what I'm doing tbh, right after I lol at posts telling me to be thankful for getting a port in the first place independent of the quality. But I get why people who don't own the game are a bit angry. I was looking forward to this too.

no one should be thankful for a terrible port. It's not like you are getting it for free. You are paying for it.
 

GHG

Gold Member
Yeah, the 'which ones are real' thing is bullshit. Although again, to play devil's advocate, we don't know what sort of random shit people are reporting. Perhaps they are getting a lot of troll-ey reports as well as the legitimate issues which are independently verified.



Agreed. Their hands seem pretty much bound with MS hanging right over their head.



Naturally. Game I'm working on right now is going through the throes of that right this minute :/

As a company, in situations like this you need to play mr nice guy and always assume "the customer is always right". Even if in the back of your head you think they might be wrong for whatever reason you need to at the very least acknowledge them and then say you will revert ASAP with a response/fix.

The moment I start telling my customers they are wrong (or even start telling them that I doubt the issues they are having are real or not) if they have a problem with the services provide is the moment I will go out of business. There is a right way and a wrong way to tell your customers that they are wrong :) .

And even if they are wrong, it is imperative that you go back to them with some kind of solution, not simply say "get fucked, you're wrong".

It's disastrous PR. They should have left this one to Phil Spencer.
 
Top Bottom