I like your stance on Natural Selection.
I think it's somehow understandable when a developer
removes support for platform that's barely used anymore.
At least when the effort of support is totally out of
proportion with the player count.
I think in this case with a player count of barely 200, this is fair.

We've seen similar actions by developers without the user base depleting.
And this is not okay.

Your comment about Steam/Valve and a new (partial) refund policy, when a platform
is removed, is kind of problematic, when it is not paired with some quality control.
If a developer has to pay refunds for a game they remove, they simply won't remove it,
but probably don't support it anymore.
That's not much better, as it is in the Forage case.

View this comment - View article - View full comments

Quoting: ShmerlAccording to this, it's for support of Nvidia's ray tracing ASICs: http://www.cgchannel.com/2019/10/nvidia-backs-blender-development/ [External Link]

The backend enables hardware-accelerated ray tracing on Nvidia’s RTX graphics cards, with Blender’s benchmark scenes rendering 30-100% faster on a GeForce RTX 2080 Ti than using Nvidia’s older CUDA API.

Still lock-in though, until such extensions become portable. For Nvidia, it's trying to lock the 3D creators market.

Btw, how good is the OpenCL support on Nvidia's side?

For many years they didn't support newer revisions and didn't optimize what they offered.

Ofc, it's hard to interpret that in any other way than them wanting to hurt OpenCL and thus further push CUDA. At the same time bringing up business slides how usage shows how customers prefer CUDA over OpenCL.

With the many resources they have, bringing up OpenCL support on par would've been no issues at all.

I really despise the business practices of Nvidia and how they manage to make the Linux folks even praise their actions.

View this comment - View article - View full comments

Quoting: ArehandoroPoint & Click, Pixel Art, Gritty atmosphere... They've got me.

This is from the same guys.

https://www.gamingonlinux.com/articles/the-inanimate-mr-coatrack-a-free-comedy-adventure-worth-taking-a-look-at.14514

And completely free, btw.

View this comment - View article - View full comments

After having soooo much fun with Ion Fury, I'm really looking forward to this one.

View this comment - View article - View full comments

Quoting: nox

Quoting: sub

Quoting: Liam Dawe

Quoting: sub

Quoting: Liam Dawe

Quoting: NeoTheFoxGreat job on that sliding preview, it really works well for side-by-side. You are very good at this Liam.

Can't take all credit. I implemented it using https://github.com/koenoe/cocoen [External Link], no point reinventing the wheel :)

Nice feature, Liam.

Do you notice a slight misalignment between the two pictures?
I wonder if this is due to the source material slightly shifted,
the post-processing or the implementation of the new feature?

I don't see any misalignment? Can you point it out?

Here it's just a pixel or so.
If I quickly move the slider, so that it's like swapping the images,
it clearly looks like the post-processed image is slightly shifted downwards.

Wait, this is strange. :)

When I freshly open the page, it looks fine.
Once I go to another comment page this misalignment occurs and stays until I freshly open the article,
say in another tab.

Firefox on Fedora.

Yet, it's really not a big thing.

Can you reproduce that?

I'm getting this consistently. Seems like the post-processed image is ~2 pixels further down, but it's barely noticeable.

It looks like a minor scaling issue.
It's not a plain shift.

The effect gets more noticeable the farther down and right I focus (in particular in the bigger comparison it's very noticeable). Yet, in the upper left corner it always looks perfect also in cases where the issue is present in other parts.

I don't have a consistent way at hand to reproduce the issue and cases where it doesn't happen.
Most of the time it's bugged, but then sometimes it looks like it was intended.

View this comment - View article - View full comments

Quoting: Liam Dawe

Quoting: sub

Quoting: Liam Dawe

Quoting: NeoTheFoxGreat job on that sliding preview, it really works well for side-by-side. You are very good at this Liam.

Can't take all credit. I implemented it using https://github.com/koenoe/cocoen [External Link], no point reinventing the wheel :)

Nice feature, Liam.

Do you notice a slight misalignment between the two pictures?
I wonder if this is due to the source material slightly shifted,
the post-processing or the implementation of the new feature?

I don't see any misalignment? Can you point it out?

Here it's just a pixel or so.
If I quickly move the slider, so that it's like swapping the images,
it clearly looks like the post-processed image is slightly shifted downwards.

Wait, this is strange. :)

When I freshly open the page, it looks fine.
Once I go to another comment page this misalignment occurs and stays until I freshly open the article,
say in another tab.

Firefox on Fedora.

Yet, it's really not a big thing.

Can you reproduce that?

View this comment - View article - View full comments

Quoting: Liam Dawe

Quoting: NeoTheFoxGreat job on that sliding preview, it really works well for side-by-side. You are very good at this Liam.

Can't take all credit. I implemented it using https://github.com/koenoe/cocoen [External Link], no point reinventing the wheel :)

Nice feature, Liam.

Do you notice a slight misalignment between the two pictures?
I wonder if this is due to the source material slightly shifted,
the post-processing or the implementation of the new feature?

View this comment - View article - View full comments

Quoting: EhvisI wonder if it's just me, but I really don't like the artificial sharpening. Never have on any medium and for any game that offers the option I turn it off. It just feels harsh and unnatural.

Well, I'm quite amazed how good it looks in the example without adding excessive noise.
Would use it.

View this comment - View article - View full comments

Quoting: YoRHa-2B

Quoting: 1xokWould you mind to elaborate a bit about AMD's Vulkan driver state on Windows?
What's so bad about it?

It's fairly buggy even compared to the open-source AMDVLK driver, which would indicate issues in the proprietary shader compiler.

It wouldn't be so bad if things were at least consistently broken, but they aren't. One driver update might randomly fix an issue, the next update might fix something else but break the very same thing they fixed in the earlier update. It's a rollercoaster, and honestly I just can't be arsed to report bugs against it.

AMD's Windows driver has been a broken mess ever since Navi launched anyway, with D3D9 being completely broken in some cases and other major issues, but that's a different story.

Thanks.

That doesn't sound promising, indeed.
I have a very old card. Radeon HD 7950.
The Windows driver never gave me headaches.
Even when that card was new.

All games I tried with Vulkan run great on that old beast (paired with a Phenom II X4).
DOOM and Wolf 2. FullHD. Perfectly smooth. :)

In the not too far future I will update the full rig.
The idea was to go for Navi judging from my AMD experience so far... Hmmmm.

Specifically for Navi, would you suggest using AMDVLK or RADV?

View this comment - View article - View full comments

Thanks for the input, Philip.

Quoting: YoRHa-2B

Quoting: 1xokWhat are the advantages of DX12 over Vulkan for developers? I can only think of the Xbox support.

Well, for starters, D3D12 works on all Windows 10 systems and has excellent driver support from all vendors.

Windows drivers shipping with Windows Update sometimes don't come with Vulkan support -> games straigt-up don't work. Driver quality is also way worse (AMD is pretty bad, Intel seems to be especially bad, only Nvidia is acceptable these days - and that also was a whole different story ~2 years ago).

Would you mind to elaborate a bit about AMD's Vulkan driver state on Windows?
What's so bad about it?

That's really sad to hear as AMD was actually initiating all the low-level API thing with Metal.

Edit: Plus, I thought making a good Vulkan driver is by far *much* easier than a good OpenGL one.

View this comment - View article - View full comments