The maximum frame-rate seems to be limited to 5/6th of the refresh rate - this means, when using a 60Hz monitor, the game simply cannot go beyond 50 frames per second.We even tried it with a Core i7 system paired with Titan X running at 720p on the lowest settings, but 50fps was still the limit - and the same thing applies to AMD GPUs too."
"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.There's the sense that this game needed more focus, a lot more testing, and - in Nvidia's case - better drivers.But Microsoft has to bear responsibility too: several of the issues encountered here are a direct result of UWP's lack of features and quality, to the point where even downloading and installing the game is a trial Game sounds like a total disaster on PC.if this is what we have to look forward to with DX12 then I'll stick with DX11. At least it worked for me.Īgain I wasn't trying to troll. That's why I said what I said about complaining on Nvidia boards about Nvidia issues with games. Even went to the PR team and Raja Koduri with my performance issues on Twitter, official AMD boards, AMD Twitch livestreams, etc. Sorry, but I think that they have done much better in the past and certainly need to do better in the future.Īnd if you pay any attention to my posts I complained to AMD about their performance in other titles also.
The guy in the Digital Foundry video even stated that Nvidia put out a driver for this title.
I still think they need to rethink their drivers code in relation to DX12. I can't think of a DX12 title where Nvidia drivers are better at DX12 in relation to DX11. To me that's kinda broken when the DX12 calling card is performance boosts. Tomb Raider as far as I can remember gets zero boost on Nvidia's hardware under DX12. Maybe it's the 5 year old motherboard and processor choice? /sarcasm. As does Quantum Break except for scenes where the lighting is more prevalent. Gears runs perfect on the equipment in my signature. And you are perpetuating that as evidenced in this thread so far. PC gamers need to put pressure on Nvidia, but they also need to stop giving AMD a pass everytime they have a problem. The current state of QB is a top post on both /r/games and /r/pcgaming right now as well as multiple PC gaming websites around the web. If it's an async issue, then there's nothing more we can do about it since it's dominated headlines for the last 6 months. So what exactly should we complain about.? "Nvidia needs to work harder on Gaming Evolved games"? You could apply the same logic to AMD and GameWorks games, nobody is petitioning AMD over those. But I think AMD deserved the same treatment over Gears of War, which makes QB's issues less notable. I don't see any reason users should be complaining to Nvidia about "optimizing their DX12 drivers", except QB obviously. Both of those games are pretty messed up overall. Rise of the Tomb Raider runs great on Nvidia. But dammit go complain to Nvidia at least.Ĭlick to expand.We have two AMD sponsored games that run great on AMD. I think you're misconstruing my outspokenness as trolling. Feel free to show me a different mode of thinking and I will take that into consideration. I encourage their customers to complain on their boards for a positive change instead of looking starstruck at Pascal as the savior. But Nvidia definitely needs to optimize their DX12 drivers for general gaming across the board. Obviously going by their performance in other DX12 games this hasn't changed.Ĭan Remedy optimize the game more for Nvidia users? Sure! There are always bugs even in finished games from 20 years ago. Their performance has been nonexistent since Ashes was in PreAlpha. I say driver in this case since Nvidia has been sucking it up on ALL DX12 games year to date.
Want to know what fixed the game? A patch. It was still pausing and jerking like a Parkinson's patient after the driver.