Originally posted by smitty3268
View Post
Announcement
Collapse
No announcement yet.
F1 2015: Don't Go Racing Yet With AMDGPU-Pro Or RadeonSI Gallium3D
Collapse
X
-
Originally posted by shiba87 View PostShould be both. Broken driver is a very big problem here
You do know that AMD-pro and fgrlx have certified OpenGL implementation.
If the game works slow on certified driver than that is driver/hw problem.
If the game does not work on certified driver its the games problem.
Comment
-
Originally posted by theriddick View PostI got a strong vibe from Feral after talking to them that they are not really interested in getting things working for AMD hardware because all their drivers are beta or whatever and they are going to ignore them because of that (this is what they said).
Not a very good stance to take, too many developers pretending AMD hardware doesn't exist is bad for Linux...
I think you are spreading FUD here. Feral is the biggest supporter of AMD OSS drivers among the companies that are porting games to Linux.
Last year they bought lots of AMD hardware to do tests, they actually make bug reports to OSS drivers and implement patchs in the game to improve performance with the radeon driver.
Look what they did with the last Tomb Raider patch. Actually, that was their first game with official OSS driver support. How many other AAA porters do that.
Last year, there was a problem with the splitscreen mode in Grid Autosport. Not only they acknowledged it, but submit bug reports to Mesa and got that mode fixed by the time Ubuntu 16.04 got out with mesa 12.
So this F1 game is not working now, but that doesn't mean it will not work forever.
- Likes 1
Comment
-
Originally posted by pixo View PostIf you mean Nvidias glitchy driver that allows broken OpenGL to run on them than yes.
You do know that AMD-pro and fgrlx have certified OpenGL implementation.
If the game works slow on certified driver than that is driver/hw problem.
If the game does not work on certified driver its the games problem.
if the drivers works, the game will work too, and if both, Feral and AMD cooperate, will be better and faster. Blaming everyone, doesn't fix anything
Comment
-
Originally posted by M@GOid View PostLook what they did with the last Tomb Raider patch. Actually, that was their first game with official OSS driver support. How many other AAA porters do that.
Feral is the only one who can't get their shit together.
I decided to let money do the talking and simply stopped buying Feral games altogether.
- Likes 1
Comment
-
Originally posted by Awesomeness View Post
Aspyr and Valve. I played several games on Linux, including two Borderlands games (Aspyr) and the Portal games (Valve). No problems with Mesa-based drivers (aside from the usual performance drop).
Feral is the only one who can't get their shit together.
I decided to let money do the talking and simply stopped buying Feral games altogether.
Previous Feral ports do not work with radeonsi because the drivers functionality wasn't there. As the drivers get more feature rich, the games start working.
And because this F1 game not working now, all previous Feral efforts in OSS drivers mean nothing to you?
Comment
-
Originally posted by M@GOid View PostIt was Aspyr/Valve or was AMD effort, that make those games work?
I was talking about Mesa in general which also means Intel, btw.
Originally posted by M@GOid View PostPrevious Feral ports do not work with radeonsi because the drivers functionality wasn't there.
Originally posted by M@GOid View PostAs the drivers get more feature rich, the games start working.
Originally posted by M@GOid View PostAnd because this F1 game not working now, all previous Feral efforts in OSS drivers mean nothing to you?- 9 reported bugs: https://bugs.freedesktop.org/buglist...ormat=advanced
- 18 bug reports with some form of activity (incl. a single comment): https://bugs.freedesktop.org/buglist...ormat=advanced
Wow…
- Likes 2
Comment
-
For everyone saying Feral's targetting Nvidia's driver and exploiting its looser conformance to the spec, it might not be the case this time:
https://lists.freedesktop.org/archiv...ay/118607.html
Turns out that at least the menu rendering issue with radeonsi is due to Mesa generating an error that was against the GL spec (or at least the current version of the spec).
Comment
Comment