Quoting: Smilex

Quoting: ShmerlThey are using their own engine?

Yes. Jonathan Blow as explained in detail why they did, in one of his many videos. I can't remember what the reason was exactly, and I can't remember which video. I'm pretty sure he advocates that small teams always roll with their own engine.

That's good, I like when developers make their own engines. But it sounds like they don't use Vulkan yet.

View this comment - View article - View full comments

They are using their own engine?

View this comment - View article - View full comments

Quoting: IncandescentThe RadeonSi driver is for GCN 1.0 and 1.1 cards (7000 series and certain R9 cards) until the AMDGPU (non-Pro version) driver is made fully compatible with them. Your RX 460 is GCN 1.3, which uses the open-source AMDGPU driver by default, and is fully compatible with Gallium-Nine.

That sounded somewhat confusing. Radeonsi works with all recent AMD cards including RX 460. I.e. you get combination amdgpu + radeonsi. Si while stands for "Southern Islands" isn't limited to the early GCN architecture. They just didn't change the name, because it's the same OpenGL implementation for later GCN too.

View this comment - View article - View full comments

Quoting: Purple Library GuyI didn't realize even experimental Wine was even very near the point of actually allowing any DX11 or Vulkan games to run. Is it just me or has Wine been moving very fast lately?

Not any, and I wouldn't call it fast, but it has been moving. They for sure were working on things gradually, and laid a lot of DX11 ground work already, but lot's of DX11 games are still unplayable. I'd say it will be still a while, until it will reach the situation of DX9, when most games already work, unless Wine developers will focus on DX11 specifically as a major feature they want to implement in the fixed period of time. So far they didn't do it.

View this comment - View article - View full comments

For the reference. I put the timeline of TW3 Linux port misadventures here on the wiki.

View this comment - View article - View full comments

Quoting: nattydread

Quoting: ajgpI would be happy enough if Witcher 3 could be made to work in Wine, I have given up expecting it to be ported now but having played W1 (on windows and again in wine) and W2(Native) I really want to know how the whole thing ends.

Why not just pick up a cheap ps4 and play it on that?
That's what I did, I couldn't wait and quite honestly it is the best game I have ever played.

Many reasons. For instance, boycotting DRM and not paying anything to Sony which proliferates it and as well sabotages adoption of open graphics APIs like Vulkan. Paying them money helps them doing the nasty stuff. Also don't forget things like this [External Link].

I'm also waiting for the Witcher 3 to become playable in Wine. But PS4? No, thanks.

View this comment - View article - View full comments

In the trends page the color legend looks broken - only the outline is colored, while inside color is gray for me.

Also, it would be nice if you could make the graph lines slightly thicker. Or may be it's just antialiasing on them is somewhat rough?



On a side note, good to see AMD usage rising.

View this comment - View article - View full comments

Quoting: CreakI won't extend more on that, so please write an application in TCP/IP, write another one with HTTP. Compare the network performances between them, and compare the code size as well, and then (and only then) I'll be interested to talk a bit more about it with you.

Easier to make doesn't make it a good design. HTTP is not well suited for many use cases, and looks like a kludge when used for duplex communication especially. I agree of course that designing and making new protocols is not a trivial task, I don't however see it as reinventing the wheel. HTTP wasn't meant to replace TCP/IP, but often used that way.

It's the case of "when you have a hammer (HTTP), everything looks like a nail".

View this comment - View article - View full comments

Quoting: Sgt.Romeo9The point is, having SPIR-V be able to work with GLSL and HLSL on equal ground is probably what drove Microsoft to open-source this DirectX shader compiler. Just my opinion.

I can understand Vulkan developers being interested in it. But why MS if they staunchly refused to participate in the Vulkan working group? Or they now are changing their mind?

View this comment - View article - View full comments

Quoting: TealDamn, that's some good news.

I bet it's mostly to make HLSL compete with SPIR-V a bit better, but if competition leads to open sourcing things, that's to great benefit of everyone!

I think it actually helps Vulkan and SPIR-V. See https://github.com/KhronosGroup/glslang/issues/362 [External Link]

View this comment - View article - View full comments