Quoting: williamjcmWell, since the leak happened, I'm sure competition watchdogs will keep a very close eye on Microsoft for the years to come.

Except, where can we find competent competition watchdogs? Current application of competition law seems to be getting more and more toothless.

View this comment - View article - View full comments

What exactly is the difference between compositor latency settings in the current System Settings?

View this comment - View article - View full comments

I enjoyed CP2077 game itself. It has some flaws, but overall the story is pretty good. Looking forward to the expansion.

View this comment - View article - View full comments

Quoting: PublicNuisanceI originally was hyped for Cyberpunk. What I wanted was a darker single player story based experience. What they seem to put out was an open world Saints Row/GTA type game with bugs galore. Will this update give me what I wanted ?

That sounds like Deus Ex. I wish they made a sequel to Mankind Divided. I just finished it recently, and it's a very well written cyberpunk story.

View this comment - View article - View full comments

Quoting: poiuzAMD disagrees with you, in Feb 2015:
https://gamingbolt.com/the-big-interview-amds-robert-hallock-on-mantle-directx-12-ps4xbox-one-free-sync-and-more [External Link]

I don't see any disagreement. AMD wanted their API to be used by MS - so what. They wanted it to be used by everyone else too.

And they are MS partner for consoles. Obviously if MS started pushing their NIH AMD won't be trying to stop them. It was MS idea, not AMD's.

View this comment - View article - View full comments

Quoting: poiuz

Quoting: ShmerlThat's exactly the point. Obviously AMD wanted to have one common API, not multiple NIHs. So why did MS and Apple have to rush making theirs? They could work with AMD and then Khronos on the common one.

If that was the case, they wouldn't have provided Microsoft with everyrhing on Mantle, but they did.

They provided everyone with everything. Their whole API was opened for anyone who wanted. The goal was to encourage collaboration, which indeed happened when enough people got together to make Vulkan from it. But not MS and Apple. They just exploited it to make their own NIHs becasue they could. It tells you everything there is to tell about their approach.

View this comment - View article - View full comments

Quoting: poiuzMantle is omitted since it's the starting point for all APIs.

That's exactly the point. Obviously AMD wanted to have one common API, not multiple NIHs. So why did MS and Apple have to rush making theirs? They could work with AMD and then Khronos on the common one.

View this comment - View article - View full comments

Quoting: poiuzAre you serious? My timeline?

Timeline starts with Mantle which presented such ideas before Apple and MS rushed to make NIH knock offs of them. And AMD from the beginning expressed the interest to make it a common API. That's why Mantle later was turned into Vulkan. Basically, collaboration on it could have started from the beginning, if Apple and MS weren't arrogant lock-in proponents who benefit from work of others either way.

See also: https://twitter.com/renderpipeline/status/581086347450007553 [External Link]

View this comment - View article - View full comments

Quoting: poiuzDirect3D 12, Announcement: March 24, 2014
Metal, Initial release iOS: June 2, 2014
Vulkan, Announcement: March 13, 2015
Metal, Initial release macOS: June 8, 2015
Direct3D 12, Initial release: July 29, 2015
Vulkan, Initial release: February 16, 2016

Your timeline is misleading. Both MS and Apple can be blamed for not supporting Vulkan. They did it very deliberately knowing it's being developed, since they did it out of obvious lock-in intent.

View this comment - View article - View full comments

Quoting: poiuzYes, your right. Gamers care about games. Apple tries to get games on macOS

Saying they care about gamers or try to get games on macOS when they make existing games unplayable is complete nonsense. No point to even argue further about it.

Ubuntu realized it in time when they wanted to drop 32-bit support and reversed that dumb idea, which is a lot better than how Apple treats gamers by completely disregarding them.

That's why I seriously don't get anyone expecting macOS to be usable for gaming, when Apple just gives them middle finger in that sense.

It's simple. Apple cares about Apple and tells users what they should do or not do. Apple doesn't care about gamers and isn't interested in their needs.

View this comment - View article - View full comments