:O

TBH I would of said that the GOL community is anything but toxic :dizzy:

I'm not the most frequent in here nor read every article/post so may miss a lot of it but still, would never consider GOL/users being toxic! .

I admit I pick on liam on occasion :P

View this comment - View article - View full comments

FYI:

They have patched a fix it for us Linux users :D Well going on what the problem was they built it correctly :P

View this comment - View article - View full comments

After running the benchmark I have cheats enabled box showing all thew time now . This is when loading a previous save game.

Anyone else get that?

View this comment - View article - View full comments

Well, there's an update for it but still broke on my end :(

View this comment - View article - View full comments

Same here, vulkan's a no go for me on the 1080

View this comment - View article - View full comments

Not just me then.

Edit:

This shows in console when run

Player data archive not found at `/mnt/games/steamapps/common/Ballistic/BallisticOverkill_Data/data.unity3d`, using local filesystem[pete@com1 Ballistic]

View this comment - View article - View full comments

Quoting: iskaputtCan this be bought on steam and then played without the steam client? Nothing 32-bits to ever touch my system.

lol.
Rules out 99% of the games on steam then including Ballistic overkill

View this comment - View article - View full comments

Quoting: STiAT

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 ;-).

We are referring to Vulkan and Radv not the kernel driver

View this comment - View article - View full comments

Or AMD would hand it to dave to integrate into RADv which I feel they would do.

View this comment - View article - View full comments

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.

View this comment - View article - View full comments