Future Multitroid 1.6 discussion.

[Miepee]

Multitroid will very likely use PG64 at one point. This issue serves as a discussion post for it.

---

Continuing the discussion from AM2R-Community-Developers/AM2RLauncher#56

Whether unpatched or patched for 64-bit using the directions above, it seems like the server opens a window and then immediately crashes

1.4 was exported as "VM" (it has GM bytecode, that the runner interprets and executes at runtime), while later versions were exported as "YYC" (yoyocompiler, code is compiled natively in the runner)
What GPU do you have? YYG had some bug related to threading that made it crash on mesa. mesa has a hardcoded check for the file's sha. you can try renaming it as runner if you haven't yet, alternatvely, you can try to use the environment variables that are listed in the server's release description.

[Lojemiru]

For the sake of continuity, you should probably be conducting testing with the unofficial updates since they're the current primary branch for the community: https://github.com/DodoBirby/AM2R-Multitroid-Unofficial-Patch/releases/tag/1.6.2

Should also be guaranteed to be a VM build.

[Miepee]

unofficial updates were slightly harder for me to use, because they were already modified with utmt and have already had some decompiler fixes. they would for that reason need some modifications in the pg64 script, which i didnt wanna deal with.
the official multitroids were thus much closer to 1.5.5 in that regard.

[peeley]

What GPU do you have? YYG had some bug related to threading that made it crash on mesa. mesa has a hardcoded check for the file's sha. you can try renaming it as runner if you haven't yet

Ouch, yeah I have an AMD GPU. I was able to get the 1.4 server (both 32- and 64-bit) up and running after running it with R600_DEBUG=mono, though.

I got the Multitroid 1.4 mod installed, and was able to connect to the server. I was able to connect with the mod un-patched and in 32-bit mode, even when the server was running in 64-bit - I thought this was surprising at first, but I guess it doesn't really matter what architecture the client/server is on if they're only communicating over the network.

I can take a crack at the unofficial Multitroid patches next, but that might be a bit more challenging as it seems that the server is only available via AppImage.

[Miepee]

I got the Multitroid 1.4 mod installed, and was able to connect to the server.

Sorry, I don't quite get this part, could you clarify it a bit please? From what I understand, you tried the following scenarios, which all worked (please correct me if i'm wrong):

• server 64bit unpatched, client 32bit unpatched
• server 32bit unpatched, client 32bit unpatched

[peeley]

Sorry, I don't quite get this part, could you clarify it a bit please?

Ah, my bad. I'll use "patched" in this context to mean that I've run the following on the respective AM2R_Server or runner files,

patchelf AM2R_Server \
    --replace-needed "libcrypto.so.1.0.0" "libcurl.so" \
    --replace-needed "libssl.so.1.0.0" "libcurl.so" \
    --clear-symbol-version X509_free

Here's all the different scenarios I've tested, and seem to work:

• 1.4 32-bit patched server, 1.4 32-bit patched client
• 1.4 64-bit patched server, 1.4 32-bit patched client
• 1.4 64-bit patched server, 1.4 64-bit patched client
• 1.4 32-bit patched server, 1.4 64-bit patched client

[Miepee]

interesting and in all combinations the client was able to successfully connect to the server?
I couldnt get patched stuff to work due to dependency issues (i assume), but whenever i tried 64bit unpatched server + 64bit unpatched client, i always gett timeouts 🤔

[peeley]

Sorry for the late reply, been busy with work and other projects.

@Miepee Regarding something you brought up in the previous thread:

out of curiosity, I also tried running your patchelf command on it, but then i just got hit with:

./runner: /usr/lib/libcurl.so: version `OPENSSL_1.0.0' not found (required by ./runner)
./runner: /usr/lib/libcurl.so: version `OPENSSL_1.0.1' not found (required by ./runner)
./runner: /usr/lib/libcurl.so: version `OPENSSL_1.0.0' not found (required by ./runner)

I don't think I have missing dependencies (got both (lib32-)openssl-1.1 and openssl-1.0 from the AUR), especially since it works without patchelf. But y'all are probably able to judge it better.

I think this may be caused by how the AUR packages libcurl. From what I can gather in the PKGBUILD (src), versioned symbols are enabled on the default curl package. On my distribution (NixOS), curl is configured with symbol versions disabled. I'm not sure of how feasible it might be to test out different curl versions on your system, but I think if you patched the .runner-unwrapped binary to use libcurl-gnutls (or one of the other builds that has --disable-versioned-symbols) it may behave differently.

Concerning the multiplayer stuff - yep, I was able to connect the client to the server for all those combinations. I'll double-check all of them since the patching process has been pretty manual and error-prone so far, and I'll also inspect the network traffic with tcpdump/WireShark to see if I can find anything that might explain the timeouts.