You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
The text was updated successfully, but these errors were encountered:
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.
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.
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:
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.
The text was updated successfully, but these errors were encountered: