-
Competitor rules
Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
Nvidia GameWorks HBAO+ Behind Visual Corruption In Gears Of War Ultimate Edition
- Thread starter Boomstick777
- Start date
I believe no one should buy anything to do with Microsoft store, especially for a game that was out years ago on the eggs box 360.
If someone wants that game then fair do to them, All we can do is give our opinions on forums and hope people listen.
If someone wants that game then fair do to them, All we can do is give our opinions on forums and hope people listen.
Both Nvidia and MS can share the blame on this one.
GameWorks is a lazy and woefully unoptimised way to implement graphical effects and Nvidia are happy to kill performance for their own customers as long as it kills performance on AMD even more.
MS and Nvidia collaborating together is poor for gaming and this game shows what we can expect from them.
Do the right thing people and never purchase from MS.
GameWorks is a lazy and woefully unoptimised way to implement graphical effects and Nvidia are happy to kill performance for their own customers as long as it kills performance on AMD even more.
MS and Nvidia collaborating together is poor for gaming and this game shows what we can expect from them.
Do the right thing people and never purchase from MS.
Exactly, suddenly it's NV's fault despite Tomb Raider on the Windows Store also being riddled with issues the normal version does not.
Never mind that in Rise of the Tomb Raider, and Fallout 4 HBAO+ runs better on AMD cards than NVIDIA cards.
It must be NV after all, it's not even remotely possible that it's MS, their developer and the horrific mess than the UWP system is and how it destroys games by removing features that have been there for decades.
Did I miss something, when did MS take over PhysX ownership?
Nv only make the GW's api-and run hw PhysX exclusively while making everyone else run slow mo sw PhysX-since the very start.
That's pretty basic info people are ignoring.
The only part that's MS's fault in regards to PhysX is locking out config files in this title.
The ongoing Gw's **** stain continues, the stench gets more pungent every new release.
No self respecting journo/tech site is going to compare performance anyway when both can't be run on an even comparison.
Nv only make the GW's api-and run hw PhysX exclusively while making everyone else run slow mo sw PhysX-since the very start.
That's pretty basic info people are ignoring.
The only part that's MS's fault in regards to PhysX is locking out config files in this title.
The ongoing Gw's **** stain continues, the stench gets more pungent every new release.
No self respecting journo/tech site is going to compare performance anyway when both can't be run on an even comparison.
Last edited:
They also cant do any proper testing. They can only rely on the in-game benchmark. If there even is one. Anything that uses the UWP system cannot get access to the executables, or use anything with API hooks, which includes overlays for benchmarking, or even SLI or Xfire profiles.
MS have done an amazing job with their Windows Store and forcing UWP compliance on developers that want to use the store.
For Ashes of the Singularity PCPer actually had to work with the developers for them to build FCAT directly into the game engine so any proper performance and Frame testing could be done; and even then it doesn't always work properly.
Did I miss something, when did MS take over PhysX ownership?
Nv only make the GW's api-and run hw PhysX exclusively while making everyone else run slow mo sw PhysX-since the very start.
That's pretty basic info people are ignoring.
The only part that's MS's fault in regards to PhysX is locking out config files in this title.
The ongoing Gw's **** stain continues, the stench gets more pungent every new release.
No self respecting journo/tech site is going to compare performance anyway when both can't be run on an even comparison.
Nice rant.
The thread is about visual corruption caused by HBAO+. The same HBAO+ that actually works better on AMD hardware in recent titles, giving weight to the argument that it's developer incompetence rather than a nefarious NV plot.
Rant?
If you think that's a rant get yourself down your local and listen to some proper rants.
Did you miss the op slating GW's problems every release?
Miss the usual suspects adminishing responsibility?
The Nv GW's **** stain continues.
If you think that's a rant get yourself down your local and listen to some proper rants.
Did you miss the op slating GW's problems every release?
Miss the usual suspects adminishing responsibility?
The Nv GW's **** stain continues.
Shhhhhh in a forum so biased towards Nvidia, do not mention such things, or the GTX970 scandal. Or that upcoming DP1.3 NV cards going to have VESA adaptive sync on hardware level, but no drivers will exist to make it work....
Last edited:
Well reasoned debate is out the window then. HBAO+ was fine for other games but because it isn't running well in GoW, lets talk about the 970 or other matters unrelated to this thread. Usual fanboy nonsense being spouted I see.
What I don't understand is that people here argue that they're well informed and somehow do not know anything about how the MS UWP system for their store works. How restrictive it is, and how it's removing features from games we've had for decades; even the HBAO+ and PhysX always on issues are directly related to it.
Just look at the Windows Store version of Tomb Raider vs buying it anywhere else and it's riddled with issues; but some how despite it also using HBAO+ it's not NV's issue there; and was somehow never NV's amazing work that made HBAO+ run better on AMD hardware in that game.
It's down to the developer to properly implement and optimise any features they add, and MS simply do not care for a good experience when it comes to PC Games.
Permabanned
- Joined
- 12 Sep 2013
- Posts
- 9,221
- Location
- Knowhere
Microsoft should care though, There effectively alienating a segment of a market they're going to struggle claiming due to there practises. In a years time they'll turn around and claim the reason there dropping support for PC with a lot of games is because the markets dying. Not because they suck but because the markets too small.
Caporegime
- Joined
- 9 Nov 2009
- Posts
- 25,607
- Location
- Planet Earth
****Cough! Batman****
****Cough!****
Wait so the game still being a broken buggy mess is NV's fault still? Despite Rocksteady saying they can't fix the game at all because it was inherently too broken from the start, even if you ran it with or without any NV tech?
Was it also NV's fault the console versions looked better on launch than the PC one, with the PC missing Ambient Occlusion, Depth of Field, shader effects like rain textures, and more?
Last edited: