I'm no Wine dev, so take this with a grain of salt.

tl;dr it seems like Dragon's Dogma 2 (an upcoming Capcom game) will include Enigma DRM. The section from the commit to Valve Wine's bleeding_edge branch specifically noted to fix Monster Hunter Rise ( https://github.com/ValveSoftware/wine/commit/711601ab05b37eac03465794c8342e171fa395c6 [External Link] ) was updated to include the AppID for Dragon's Dogma 2, meaning the workaround to fix Monster Hunter Rise (which, I assume, is a fix for a breakage caused by the newly-added Enigma DRM) is also required for Dragon's Dogma 2 ( https://github.com/ValveSoftware/wine/commit/41290c089b299aa2b2fb90ae61585f156c38517f [External Link] ).

Valve's Wine fork ( https://github.com/ValveSoftware/wine [External Link] ) is split into several branches: The major Proton versions (8.0, 7.0, etc), the Experimental Branches for each of these (experimental_8.0, etc). There is also a "bleeding_edge" branch, which you can enable for Proton Experimental by searching for it in your Steam Library, going to Properties -> Betas, and selecting the bleeding_edge branch.

As the article has been updated to note that Monster Hunter Rise has been fixed in Proton Hotfix, a few hours ago at the time of writing, the Bleeding Edge branch got a commit to fix Monster Hunter Rise. The fix consists of checking if a game's AppID matches one in a list, and if it does, setting the "WINESTEAMNOEXEC" environment variable to "1" (presumably). Currently it does it for the following games:
- Mafia II (Classic) (50130)
- Call of Duty: Black Ops II (202990)
- Call of Duty: Black Ops II - Zombies (212910, not appearing on store page or SteamDB, but this AppID shows up in search engines)
- Madballs in Babo:Invasion (25700)
- Monster Hunter Rise (1446780)

These games could conceivably contain problematic DRM that requires a workaround (no idea about Madballs :smile:), so this could be a DRM-related workround. At the very least, since it fixes Monster Hunter Rise, and it is presumed that the new DRM caused the breakage, in this case it shouldn't be too much of a stretch to conclude that this is a fix for Capcom's Enigma DRM implementation in Monster Hunter Rise.

We also know that Capcom have tried to include this DRM in games in the past (Resident Evil Revelations) and that they want to include it in more games in the future.

Valve's Wine bleeding_edge branch got another commit to enable this fix for AppID 2054970 ( https://github.com/ValveSoftware/wine/commit/41290c089b299aa2b2fb90ae61585f156c38517f [External Link] ), which is Dragon's Dogma 2 ( https://store.steampowered.com/app/2054970/Dragons_Dogma_2 [External Link] ).

I suppose this is not necessarily surprising as Capcom have stated they want to include this in more games, but this could be food for thought for anyone interested in this game.

As I said, I'm not a Wine dev. I am only inferring this based on: Monster Hunter Rise got an update that broke Wine compatibility -> This update added a new DRM -> Valve appear to have fixed this in their Wine fork by adding the Monster Hunter Rise AppID to a section that could conceivably be related to other games with DRM-related issues -> Dragon's Dogma 2 was later also added to this part of the code.

Anyone who is a lot smarter than me, please feel free to correct me if I am wrong. A little knowledge is a dangerous thing as they say. :smile:

EDIT: I want to emphasise that this is purely informational, I am not stating an opinion on whether or not the game should or should not include this DRM. However, the store page for Dragon's Dogma 2 at time of writing does not disclose that it will contain Enigma DRM, and still states that it is using Denuvo. The Monster Hunter Rise store page also does not disclose that it is using the Enigma DRM. The information of what DRM Dragon's Dogma 2 may or may not include may be of value to some people, though, and Capcom have yet to disclose this. The recent commits to Valve Wine were just an observation I thought interesting and informative to share.

View this comment - View article - View full comments

It looks interesting, but I feel like the absurd hype will only make me enjoy it less. Once the hype dies down I'll check it out. :smile:

View this comment - View article - View full comments

While this is a fun tech demo, WMan22 makes a fantastic point and we should not rush to dismiss this as a total novelty:

Quoting: WMan22I love the idea of this being embedded into a computer in an Immersive Sim type game.

If anyone has played "Doki Doki Literature Club! Plus", they do exactly this. The original version of the game uses renPy and expects you to inspect the game files by browsing local files. However DDLC Plus uses Unity, which has a much different file structure (even if the original DDLC mocked a lot of the files for meta purposes), and also this remake targets consoles which you cannot browse local files on (likewise for the Steam Deck in Game Mode).

To get around this, the developers created a mock OS-like interface (that is also partially woven into the story), very similar to GodotOS. Having something like GodotOS could be a very cool gameplay element. This GodotOS piece could inspire some creativity!

View this comment - View article - View full comments

Quoting: Altefierso why take it down?

As far as I understand, they were redistributing assets. Engine re-implementation projects explicitly do not include any data files for this reason, and you have to supply those yourself, usually with an existing copy of the game (OpenMW, GZDoom, etc). I suspect if it weren't for this, Valve wouldn't have issued a DMCA.

I decided to check the Wayback Machine and found a link to the repository (Wayback Machine archive from September 2nd 2023 [External Link] ), it cannot really be browsed but it does archive the Readme, which suggests the game can just be downloaded and played. They may have re-created all of the assets, I cannot verify, but I would imagine if a DMCA was verified over redistributing assets, that they were in fact redistributing assets directly from Team Fortress 2.

I'm not familiar with the Source engines in any way, but I would guess many of the assets wouldn't be backwards compatible and couldn't be drop-in replacements. But that doesn't mean they weren't including at least some directly from the game.

View this comment - View article - View full comments

Looking forward to this one when I can finally stop replaying Yakuza 0 :grin:

View this comment - View article - View full comments

Linux was a great decision, but this is another handheld that missed the trackpads and handheld ergonomics that Valve have perfected on the Steam Deck. This looks like it would give me the same cramps a Switch would, and would be uncomfortable for those long Desktop Mode sessions that are so effortless on my Steam Deck.

View this comment - View article - View full comments

Quoting: FesiugAh.. I see. What I seem to remember, then, is dxvk_async being removed from Proton-GE? Is that still the case?

I believe so, but this has nothing to do with GE-Proton. This downloads the DXVK DLLs and native shared library files, like the kind you would download directly from the DXVK repository. This is not Proton.

The previous dxvk_async is incompatible with DXVK v2.1 and above, so I believe the patches were removed from GE-Proton since they cannot be used by default (unless you manually download DXVK). And this newer dxvk_async which is compatible with DXVK v2.1 and above, technically called dxvk_gplasync, is not included in GE-Proton as far as I know, as per the dxvk_gplasync maintainers note on the ProtonUp-Qt GitHub issue I linked [External Link] (as of October 10th 2023):

> Getting this patch to GE-proton is possibility, but i am in GE discord server and people don't seem to care about this.

I skimmed the changelog for GE-Proton releases since then, and I didn't see mention of re-adding DXVK Async. It may be included, but last I heard, dxvk_gplasync is not in GE-Proton.

And just to reiterate, all of these projects are technically separate from Proton. DXVK is a standalone project that is often used with Wine builds and thus also Proton, but can be used natively (DXVK Native, used by Valve in place of ToGL for Portal and Portal 2 with the '-gamepadui' launch option). If you want to use dxvk_gplasync with a given Wine build that doesn't include it you can install it manually into the prefix *or* into the default_pfx for Proton builds. Lutris and Heroic also allow you to manually select DXVK (and vkd3d-proton) versions.

And also, in case you're looking and see older builds, it's called GE-Proton now.

View this comment - View article - View full comments

Quoting: PyreticIs Northstar for Titanfall? What's the point of it?

Northstar Proton is a fork of GE-Proton specifically and only for use TitanFall 2. ProtonUp-Qt doesn't maintain it or any Proton version, it just allows you to download them.

As for the point, it seems minimal, just including dxvk_gplasync and LatencyFleX (Vulkan layer still needs manual installation afaik), both of which still need enabled with environment variables of course. Refer to the Northstar Proton GitHub Project Page [External Link] for more information.

Note: Northstar Proton was not added in this release, the URL was just updated as the repository was moved. The initial inclusion was requested in DavidoTek/ProtonUp-Qt#115 [External Link].

View this comment - View article - View full comments

Quoting: Fesiugdxvk_async? when was that readded? was it? what's up?

Nothing was re-added, nothing was removed to begin with. ProtonUp-Qt always allowed you to download dxvk_async for Lutris, however it now uses the updated fork that is compatible with DXVK 2.1 and above. When DXVK 2.1 introduced Graphics Pipeline (or "GPL") it broke compatibility with the old dxvk_async.

There is a separate dxvk_async fork maintained by someone else that is compatible with newer DXVK versions. ProtonUp-Qt previously used the older version, which is no longer maintained and was superceded by a new dxvk_async fork.

This is specific to DXVK and is not included with Proton, however ProtonUp-Qt allows you to install this DXVK version for use with Lutris and Heroic, which allow you to manually select DXVK version overrides (Lutris temporarily overwrites the D3D DLLs in the Proton version files to accomplish this iirc, since it cannot modify the prefix as it will get overwritten by the DLLs included in Proton).

This isn't included in any Proton version, this is specifically to allow you to download an up-to-date dxvk_async project for use with Lutris and Heroic.

See DavidoTek/ProtonUp-Qt#243 [External Link] for background.

View this comment - View article - View full comments

Quoting: no_information_hereStrangely, I seem to have over 220 hours in it. How did that happen?

We stared into the fire for hours and days. But that can't last forever!

View this comment - View article - View full comments