Games

31818 readers

1320 users here now

Welcome to the largest gaming community on Lemmy! Discussion for all kinds of games. Video games, tabletop games, card games etc.

Weekly Threads:

What Are You Playing?

The Weekly Discussion Topic

Rules:

Submissions have to be related to games
No bigotry or harassment, be civil
No excessive self-promotion
Stay on-topic; no memes, funny videos, giveaways, reposts, or low-effort posts
Mark Spoilers and NSFW
No linking to piracy

More information about the community rules can be found here.

founded 1 year ago

MODERATORS

[email protected]

Lies of P will be released on Mac as part of the game's official launch on September 19 (www.aroged.com)

submitted 1 year ago by [email protected] to c/[email protected]

29 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 1 year ago* (last edited 1 year ago)

Think about it like this: if you we're to sit down and port a Windows game to Linux manually, what would you have to do?

You would need to translate the Windows API calls to something Linux understand. That's what WINE does.
If the game runs a Microsoft proprietary rendering engine, you would need add Vulkan support. That's what DXVK/VKD3D do.
You would need to convert any FMVs that use proprietary codecs to open formats. That's what Proton's transcoding feature does.
You will need to provide a shader cache to the user. That's what fossilize does.

So Proton is doing all of these things that you have to do when you port the game anyway. Why spend the money and resources to do something that Proton does for free? If Proton is in any way insufficient to run your game well, it's open source. You can submit merge requests to Proton yourself if you really care about Linux performance.

It's not about Proton versus Native. It's Vulkan versus DirectX. Games that optimize for Vulkan have zero overhead on Linux, and that's what devs should strive for.