Originally posted by bridgman
View Post
Announcement
Collapse
No announcement yet.
The Highly-Anticipated XCOM 2 Game For Linux Will Be NVIDIA-Only
Collapse
X
-
This is bull! XCOM 1 is running better on my machine with Mesa drivers than with fglrx (it's running barely playable though - about 20-25fps, I got R7 250X), and here with the same engine they say they won't make it run on Radeons?
Like a couple of people said - nvidia should get the boot for breaking the specs.
- Likes 1
Comment
-
Everybody seems to be blaming the Catalyst drivers, but as somebody pointed out the MESA drivers are at the same feature parity as OSX drivers, and faster to boot. This is where I'm confused, especially since Macs use AMD gpus now so... wtf Feral? Couldn't they have targeted the much less buggy MESA drivers instead of trying it once or twice on Catalyst and going "nope, doesn't work"?
- Likes 1
Comment
-
Originally posted by bug77 View Post
Yeah, ok. You guys are doing everything just fine, but it must be a world-class conspiracy confining you to under 20% market share.
It's not a conspiracy, it's a combination of NVidia's (questionable, but brilliant) marketing and admittedly slower DX11 drivers on AMD's side. Most of these "AMD-only problems" didn't exist when ATI/AMD had a similar market share to NVidia, but once AMD's market share slipped under the 35% market share or so, barely anybody bothered testing on it more than cursory, since they didn't deem it worthy. THAT'S when NVidia's laxness in the standard finally showed through, forcing bugs to show up in standards-complient drivers like AMD or Intel, further forcing them down in market share since people thought they were buggy on the latest triple-A games.
Now it's just a vicious circle of people only testing on NVidia leading to bugs in AMD leading to less people buying AMD leading to people only testing on NVidia and so on and so forth.
- Likes 3
Comment
-
Originally posted by Daktyl198 View Post
Michael, I petition to give this guy the title "Official NVidia Fanboy"
Also, the problem isn't people testing only on Nvidia. There's no such problem on Windows. The problem here is that AMD has neglected Linux drivers for so long, they probably have 10% market share of the 1% desktop systems (systems that run Linux) and that is so low, people can't justify the costs of testing and eventually supporting AMD anymore.
- Likes 1
Comment
-
Originally posted by Daktyl198 View Post
Michael, I petition to give this guy the title "Official NVidia Fanboy"
bug77 : I get your point and your "it just works" stance, and I respect it. Just do one thing, please : look how it works on consoles... Pick up a game and play? Nope. If each vendor has his own variant of OpenGL, buying a game for PC would also require checking you have a compatible GPU (as is the basis of this thread).
Edit : ad windows : yes, there Catalyst is a lot more complete, and AFAIK AMD has copied nvidia's hacks so it just works(tm)...
Comment
-
Originally posted by Serafean View PostI understand this is said in jest, right?
bug77 : I get your point and your "it just works" stance, and I respect it. Just do one thing, please : look how it works on consoles... Pick up a game and play? Nope. If each vendor has his own variant of OpenGL, buying a game for PC would also require checking you have a compatible GPU (as is the basis of this thread).
Edit : ad windows : yes, there Catalyst is a lot more complete, and AFAIK AMD has copied nvidia's hacks so it just works(tm)...
- Likes 1
Comment
-
Originally posted by bug77 View Post
Since you can't play properly until you have both "OpenGL features" and game profiles, the order in which they are added is pretty much irrelevant.
In all the development I've ever been involved in the initial target is always delivering functionality, tuning then comes later in the development cycle.
- Likes 1
Comment
-
Originally posted by Daktyl198 View Post
Of course. Being funny doesn't come across well on forums, I'm afraid :/
Originally posted by Herem View PostI don't understand your logic that the order is irrelevant. How could anyone possibly tune something which hadn't been implemented yet?
In all the development I've ever been involved in the initial target is always delivering functionality, tuning then comes later in the development cycle.
Comment
Comment