Quoting: spiffyk

Quoting: GuestBut where are our ****ing performance optimizations for specific games?

You mean where are the workarounds introduced to make up for a game abusing the API? To hell with that.

Actually, that's quite state of the art. Game developers and driver developers working around special use cases where the available API implementation just sucks.

With each driver release, even on Windows, NVidia introduced optimizations for certain games. That should not be necessary. Seems it is .. at least currently.

View this comment - View article - View full comments

Stop teasing start releasing :D ... nah, I've a so huge backlog of games that I hope they take a year or so to release.

View this comment - View article - View full comments

Quoting: pete910

Quoting: CreakKnowing that the Linux kernel maintainers don't allow two drivers enabled for the same hardware at the same time (from what I understood), there's going to be a battle between RADV and AMD if they open source their Vulkan drivers...

They would more than likely merge the two.

I highly doubt that. We may see the AMDGPU-PRO driver making use of radv in future instead of their own implementation below AMDs AL in their driver. Same thing which goes on now with the DC/DAL patchset. It's more work involved there for the AMD devs, and AMD has been .. slightly pissed off not being able to do what ever they want for their hardware in the kernel, so we may still end up with two implementations in the end ;-).

View this comment - View article - View full comments

Dawn of War 3. Very likely.

View this comment - View article - View full comments

Very nice. I didn't even know Valve had something like Steam Audio. Cross Platform Audio is one thing, but that one seems pretty much different. Audio based on physical parameters, materials and geometry ... that has a lot of potential (for saving time during development).

View this comment - View article - View full comments

I've played this game quite some, and I disagree with a lot of design decisions. As somebody being very crafting and PvE bound in such games (I do love crafting), you'd think it's a game I'd enjoy.

I don't. It's still very early to judge, but with the path they're going I'm really not seeing it getting a good reception amongst the wider player base. Probably not their goal either, but it will certainly be a very nieche product which will fail to aquire a large playerbase, which certainly is death for every MMO.

View this comment - View article - View full comments

Valve should have done this already. A year ago. Why didn't they? I know quite a few games which wiuld have profited by this.

View this comment - View article - View full comments

Hmh, puzzle adventure. Could be for me :-).

View this comment - View article - View full comments

I am really having a time issue. I cant even play through 25 percent of the great games feral, obsidian, inxile and others release. I cant keep up their release speed with my gaming speed..

Odd, thinking a few years back considering what we had back then. Basically nothing except publishers and porters going bankrupt until Valve pulled the switch with steam.

View this comment - View article - View full comments

Quoting: BTRE

Quoting: WorMzyDon't downgrade your openssl package, you'll break everything that now depends on the new soname (including pacman! Well done!).

Not true in this instance. openssl is at its latest version on my system (1.1.0.e-1) and I only downgraded openssl-1.0 to 1.0.2.k-2. No breakage to either pacman or anything else insofar I can tell. This is after rebooting and explicitly checking if I could still install, sync and whatever else with pacman after downgrading. And things like Mad Max and Civ 6 work. You may be right in general about downgrading packages but this is a simple workaround if you're too impatient to wait until they fix this.

So you say it broke between 1.0.2.k-2 and 1.0.2.k-3?

That would be the versioned symbol patch breaking things... which shouldn't be.

https://git.archlinux.org/svntogit/packages.git/tree/trunk/openssl-1.0-versioned-symbols.patch?h=packages/openssl-1.0 [External Link]

View this comment - View article - View full comments