Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Basic Co-op 1.2.lua causes issues with M2 level "If I Had a Rocket Launcher..." in multiplayer. #508

Open
Deltau13 opened this issue Aug 15, 2024 · 4 comments

Comments

@Deltau13
Copy link

The level begins as normal, but players become desynced and eventually disconnected. Enemies killed and switches activated would not appear as interacted with from the other player's perspective. We tried:

  • Loading into IIHARL using all save stations throughout the level, incase there was a specific point of the level the desync was happening (there was not)
  • Loading previous level save and entering into IIHARL normally (STFU played just fine)
  • Playing on P2P and Dedicated Server, both desynced
  • When player who was not the host attempted to save, the following message appeared on their screen
    photo_2024-08-14_22-52-26
  • Having one player rush to the level exit caused the other player to become disconnected, they would remain on the level on their end

The rest of the game up to this point works as intended, as well as the levels following. We eventually discovered we could make it past IIHARL by deactivating Basic Co-op 1.2.lua for just this level, which proceeded to play normally.

@treellama
Copy link
Member

Was this Aleph One 1.9? Can you try with 1.8?

@Deltau13
Copy link
Author

Deltau13 commented Aug 15, 2024

Was this Aleph One 1.9? Can you try with 1.8?

We're both running on steam version through windows 10. Will try it on 1.8 to see if that fixes anything.

@Deltau13
Copy link
Author

Hate to be the bearer of bad news, but we tested in 1.8 and were unable to recreate the issue, it works fine. Only 1.9 is causing issues on that level.

@Kolfering
Copy link
Member

The disk space error message was fixed in 1.10 which was not related to the OOS bug.
For the OOS, I'am having a hard time reproducing it on master / 1.10 but I know it's not fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants