Quoting: vulturewhile Gameworks suffers from being closed and that is why it only works good on NVidia, this one is tied to GCN and features not exposed in APIs.

not true, most technologies in the GPUOpen were technologies they had before, and work on both AMD and nvidia, they just open-sourced them now. their new technologies should also work with nvidia.
also async compute is a Vulkan/DX12 feature, not AMD or nvidia specific, though nvidia's implementation of async is currently not as good as AMD's, but that's up to nvidia to fix in their newer hardware, since Async compute is one of the things that gives DX12 and Vulkan their biggest performance advantage over older API's

View this comment - View article - View full comments

Quoting: amonobeax[byou can't turn off it's features anymore[/b].

not just that, the features like hairworks use of tessellation can't be reduced by developers, it's forced to 64x, which is the highest the DirectX specification currently allows, and WAY to much for gaming, cause they know it seriously hinders AMD.
there's a reason AMD implemented an option to limit tesselation in programs to their windows drivers, cause nvidia tries to force it to rediculous ammounts, but AMD can't enable the option by default on hairworks games, cause then they get accused of "cheating in performance benchmarks", so it remains a manual setting

View this comment - View article - View full comments

Quoting: amonobeaxHey guys I know this is a little bit off topic, but aren't you concerned with the choices NVIDIA has been taking lately? ( Long read but worth it: https://www.reddit.com/comments/367qav/ [External Link] )

you're a bit late to the party, nvidia has been doing shady business practices since forever, it starts with physx on CPU being purposely hindered by deliberately ignoring CPU-extensions like SSE and SSE2 (available in CPU's since 2000 or something) that could speed up performance drastically. then the retarded ammounts of tesselation on flat surfaces in crysis2. also, for the people that might prefer a video form instead of text:
https://www.youtube.com/watch?v=ZcF36_qMd8M [External Link]

View this comment - View article - View full comments

Quoting: NelBecause it's a french studio and we have AZERTY keyboards [External Link] here in France. Standard KB+M controls are ZQSD and not WASD.

So now you're getting a taste of your own medicine, when WE always have to rebind every fucking single game to ZQSD again and again (for more than 30 years I play on PC). And I don't talk about those game devs who think how futile is to let people remap keys.
I think I need to relax a bit. ^_^

lol it was the french people's choise back in the day to choose a non standard keyboard. i'm from belgium (flemish part) so we have azerty as well, but i'm always buying keyboards from the netherlands to have a qwerty layout. so i don't have to deal with these annoying issues

View this comment - View article - View full comments

Quoting: MGOidSome people (or almost everybody) believe that the bad performance of Catalyst drivers are entirely AMD's fault, but I have seen some people that are studying OpenGL and they say that AMD does have good OpenGL drivers, IF your code actually meets the OpenGL specification to the letter. The code generated this way works good in the proprietary Nvidia driver too, but if your implementations is faulty, you have a better chance they can work (bad, but work) with the Nvidia driver, since it is more tolerant with bad code. So there you have your Linux port with half the Windows one performance.

So Feral cannot "fix" the AMD driver, but they can make their ports perform better outside the Nvidia drivers. Remember that the biggest vendor of GPUs are not Nvidia or AMD, is Intel, because today people buy more laptops than desktops. If you make your driver work with the opensource Intel driver, you will expand your market. If you only limit yourself to Nvidia, you are cutting sales by half in Linux, and it's already a small market.

that's verry much possible, might also explain why the unigine benchmark shows much better performance on amd compared to the tested games, since it's a benchmark it has to follow the specifications to the letter to form unbiased performance statistics.

View this comment - View article - View full comments

personally, i hate playing games in my native language, i prefer english.

View this comment - View article - View full comments

are these problems only apparent when using a Linux machine as host, which linux distro did you use? do those glitches also appear when the host PC is Windows?

View this comment - View article - View full comments

looking at the conversation on twitter, it doesn't look like he even bothered to test it on Linux before releasing it he doesn't even have anything with Linux installed... -_-

EDIT: i'm wrong, they have been testing with Linux, but apparently they didn't have the same issues.

View this comment - View article - View full comments

Quoting: chopdokI think putting majority of blame on porters is kinda unjustified. OpenGL is simply lacking in performance and capability department when it comes to game development

i really don't see how people still use this as an arguement, it's all down to the drivers
some of the best performing games i've seen in my life have been openGL games, just look at Rage from id-software. which runs at 1080p60fps on Intel HD graphics, yes intel HD4000 graphics, also my mothers laptop is 7 years old and has a budget AMD card yet it still runs a beautifull game like Amnesia: The Dark Descent fine on it's native 1600x900 resolution. no directX game with those graphics come even close to that performance. openGL has always allowed for better optimization by the developers than directX (where games often require driver patches to improve performance), while it is harder to develop games with, it is not worse than directX performance wise

View this comment - View article - View full comments

too bad it gives an error on my PC:
libpng warning: Interlace handling should be turned on when using png_read_image

Fatal signal 11 (Segmentation Violation)

View this comment - View article - View full comments