Support for Seamless Coop (and other modengine2 based mods)

[BorboBorgo]

Hi folks! Thanks to Garyttierney's help and bugfixes I've been able to get me3 working on Linux save for one thing - I can't get the Seamless Co-op .dll to load alongside the loaded mod folders, so I wanted to double-check how adding natives using the --native command line option works.

Currently, I'm using a folder setup like this:

With a shell script that runs this command:

./me3 --windows-binaries-dir "$thisdir" launch -g nightreign --native "natives/SeamlessCoop/nrsc.dll" --package "mods"

I noticed me3 does acknowledge the native path I've given it:
config: AttachConfig { game: Nightreign, natives: [Native { path: ModFile("/mnt/MiniSpeedyLoad/SteamLibrary/steamapps/common/ELDEN RING NIGHTREIGN/Game/Mods/natives/SeamlessCoop/nrsc.dll")

But unless I'm doing something wrong with Seamless Co-op it doesn't actually seem to load it, as I go straight to the normal menu with no acknowledgement of SC and using my normal save file.

I have also tried --native "natives/SeamlessCoop" and --native "natives" with the same result. Any idea what I'm doing wrong or could this be a problem with SC specifically?

[BorboBorgo]

Here's the log of what comes up as Nightreign loads:

attach{self=Game { child: Child { stdin: None, stdout: None, stderr: None, .. } } dll_path="/mnt/MiniSpeedyLoad/SteamLibrary/steamapps/common/ELDEN RING NIGHTREIGN/Game/Mods/me3_mod_host.dll" request=AttachRequest { monitor_name: "65caf9f8-5177-46a1-90ea-82cf76bb378f", config: AttachConfig { game: Nightreign, natives: [Native { path: ModFile("/mnt/MiniSpeedyLoad/SteamLibrary/steamapps/common/ELDEN RING NIGHTREIGN/Game/Mods/natives"), optional: false, enabled: true, load_before: [], load_after: [], initializer: None, finalizer: None }], packages: [Package { id: "mods", source: ModFile("/mnt/MiniSpeedyLoad/SteamLibrary/steamapps/common/ELDEN RING NIGHTREIGN/Game/Mods/mods"), load_after: [], load_before: [] }] } }}: me3_launcher::game: AttachError(
"LoadLibraryExW {\n source: Os {\n code: 126,\n kind: Uncategorized,\n message: "Module not found.",\n },\n}",
)
Fossilize INFO: Overriding serialization path: "/mnt/MiniSpeedyLoad/SteamLibrary/steamapps/shadercache/2622380/fozpipelinesv6/steamapprun_pipeline_cache".
Fossilize WARN: Pipeline library handle 0x000079b978233280 is not registered.
It has either not been recorded, or it failed to be recorded earlier (which is expected if application uses an extension that is not recognized by Fossilize).
Fossilize WARN: Pipeline library handle 0x000079b978ca4210 is not registered.
It has either not been recorded, or it failed to be recorded earlier (which is expected if application uses an extension that is not recognized by Fossilize).
Fossilize WARN: Pipeline library handle 0x000079b9714f7a10 is not registered.
It has either not been recorded, or it failed to be recorded earlier (which is expected if application uses an extension that is not recognized by Fossilize).

[garyttierney]

Yeah, this is a problem with SC (or more specifically how me3 loads SC). There's 2 ways SC expects to be loaded:

• By its own launcher, which makes SC run before any other code in the game
• By modengine2, which will call modengine_ext_init on the SC DLL to tell it that it's time to load

me3 isn't looking for that modengine_ext_init right now so SC just sits around waiting to be loaded. I have a fix WIP for this, but nothing pushed that can be tested right now. I'll ping here when it's available and I'm going to update the title to reflect this is about compatibility with mods that relied on modengine2.

There is a mechanism with natives in me3 that can be used to call functions in the mod, but modengine_ext_init unfortunately has some values that are expected to be set by the mod it calls. So this probably won't work and I expect it'll just crash the game, however, you can try adding an "initializer" in the native:

[[native]]
path = "nrsc.dll"
initializer = { function = "modengine_ext_init" }

(I don't recall if that's the exact syntax, but you can verify if it's being sent in the same AttachConfig you shared above.

[BorboBorgo]

Yeah, this is a problem with SC (or more specifically how me3 loads SC). There's 2 ways SC expects to be loaded:

* By its own launcher, which makes SC run before any other code in the game

* By modengine2, which will call `modengine_ext_init` on the SC DLL to tell it that it's time to load

me3 isn't looking for that modengine_ext_init right now so SC just sits around waiting to be loaded. I have a fix WIP for this, but nothing pushed that can be tested right now. I'll ping here when it's available and I'm going to update the title to reflect this is about compatibility with mods that relied on modengine2.

There is a mechanism with natives in me3 that can be used to call functions in the mod, but modengine_ext_init unfortunately has some values that are expected to be set by the mod it calls. So this probably won't work and I expect it'll just crash the game, however, you can try adding an "initializer" in the native:

[[native]]
path = "nrsc.dll"
initializer = { function = "modengine_ext_init" }

(I don't recall if that's the exact syntax, but you can verify if it's being sent in the same AttachConfig you shared above.

Aaaah alright, I thought there might have been something SC specific going on there - am I right in thinking I would load your suggestion with --native [Path to that .toml file]?

[garyttierney]

That'd be with --profile path/to/toml.file (or just --profile <filename> if the TOML file is inside the profile directory).

[BorboBorgo]

That'd be with --profile path/to/toml.file (or just --profile <filename> if the TOML file is inside the profile directory).

Great, thanks man!

Yeah, just to confirm it does seem to be a Seamless Co-op issue, I ran me3 with ./me3 --windows-binaries-dir "$thisdir" launch -g nightreign --package "mods" --native "natives/nightreign_alt_saves.dll" --native "natives/DisableChromaticAberration.dll" and both .dlls worked fine!

[garyttierney]

There's another change available on that branch with support for the modengine_ext_init shim. I haven't tested it with NR, but it seems okay on ELDEN RING + Seamless Coop.

[BorboBorgo]

There's another change available on that branch with support for the modengine_ext_init shim. I haven't tested it with NR, but it seems okay on ELDEN RING + Seamless Coop.

Aaah sadly it didn't work with Nightreign Seamless Co-op on my end!