I'm OK with that. Epic's fault obviously that they don't care to make their engine use Vulkan properly, but it's also a lesson to any developers that assuming things will just easily work if they didn't investigate it from the beginning is quite wrong.

As a backer, I already have a game from GOG, so whether it's native or runs through Wine+vkd3d-proton is of little concern in practice, especially when native UE4 is so buggy in comparison. I'd take a well performing game over the fact that it's native but broken UE4.

View this comment - View article - View full comments

See also the big design post about it here: https://github.com/KhronosGroup/Vulkan-Docs/blob/main/proposals/VK_EXT_shader_object.adoc

View this comment - View article - View full comments

What's good is Nintendo's interest to advance Vulkan instead of pushing their NIH. I guess they decided there is no point in continuing reinventing the wheel and put their effort behind Vulkan fully now.

Too bad Sony didn't decide to do it yet.

View this comment - View article - View full comments

I'd call it predictive upscaling. It still tries to render at higher resolution that actual scene is. Generating pixels for the missing parts using previous frames helps make it look better, but as above, it's not going to be perfectly equal to rendering at that resolution to begin with.

View this comment - View article - View full comments

Quoting: Guestthe latest dlss and fsr implementations are not upscaling. When we talk about upscaling, we usually mean taking a pixel and making more pixels out of it. Dlss takes several pixels from different frames and makes a picture of higher resolution. Since all of those pixels are rendered with tiny offset, each pixel has unique information about the portion of frame it shows. This method works so well that for static scenes it can achieve nearly ground truth quality even on the lowest input resolutions. In dynamic scenes a lot of old pixels are discarded because they are too different from the current frame and can't help in picture reconstruction, and there you can see that places with a lot of movement get low res, but in those moments it is rarely that important.

Well, it's still upscaling, just more complex one than simply using a static frame. I think by mere theory of it, no matter how you upscale, you can't guarantee that resulting quality will be equal to the original. Algorithms try to be smart with approximations or predictions, but it's still not equal to original rendering at that resolution.

So while it might look good enough in some sense, avoiding it will by definition be likely better. So my point is, that if you can avoid it, then you get guaranteed level of quality. Otherwise it becomes something moot.

The whole push into these upscaling methods began when GPUs stopped coping with rendering at resolutions some wanted to them to render at fast (like 4K and such). So my take on it is to simply avoid those resolutions and use those which GPU can handle without upscaling properly.

View this comment - View article - View full comments

I generally try to avoid upscaling. But it's interesting to see how it improves.

View this comment - View article - View full comments

Nice. I've been using Wayland for quite a while already, and recently tried OBS screen recording - it was a breeze. Stuff like Discord and co. I suppose simply don't care to provide support for modern desktop use case. Stark contrast with projects like OBS. So these kind of solutions should indeed help until those lagging behind decide to provide support.

View this comment - View article - View full comments

Nice to see Wayland patches finally starting to land. It's not usable yet, but it's getting there. Once they merge all the major parts, it would be interesting to re-test.

View this comment - View article - View full comments

So what is their refresh cadence? Turning it into incumbent consoles 5+ year cycle sounds like a bad idea.

View this comment - View article - View full comments

Looks interesting.

About whether the game is FOSS - I'd also draw the line on the code vs art assets.

To give an example - if the engine is FOSS, you can in theory take the engine and build it for some new architecture, reuse game assets and run it there (like ScummVM does).

If it's Unity - you can't do it unless you have access to actual code.

But it's still good that the game code here besides Unity is open.

View this comment - View article - View full comments