lithiumfox
lithiumfox
About
- Username
- lithiumfox
- Joined
- Visits
- 3
- Last Active
Comments
-
Ah, there we go.
Some further information from experiences of what we tried for the above post:
- It does not seem to matter based on console/version of the game. We have friends reporting this on Xbox, Playstation, and PC.
- An example is the custom game that Foxfire posted above. We had 2 users in the game joining off of me, but two users were unable to join. (One Xbox, 2 PC at the time)
- Once the xbox user left, the remaining 2 were able to join, the xbox player could join after some brute force attempts of just trying, restarting the game, and trying again. We tried various methods, from direct joins, invites, steam invites, it kinda varied on what would work person to person.
A similar issue, same as Foxfire described, appeared on Sunday as well, with one user able to join off an invite, one able to off of a join request, and a final person requiring a Steam Invite after restarting their game multiple times.
A really weird issue is that if you join a loby while another user is in the process of joining, you can actually see their join requests while on the main menu or even, sometimes, in your own lobby. Then it will error out and give you an "Unkonwn Error has Occurred" message.
As Foxfire stated, going into the survivor lobby does seem to raise the success level of joining, but it does not fix it. (Something I personally experienced).
For reference, I did have logs of these games, but as they do not allow me to open them, I cannot tell you which one is helpful. They are in reference to Monday (pre-patch), Thursday, and Sunday, of when all the issues were occurring.
DeadByDaylight.log DeadByDaylight-backup-2022.09.14-01.06.08.log DeadByDaylight-backup-2022.09.14-02.26.36.log DeadByDaylight-backup-2022.09.16-01.13.43.log DeadByDaylight-backup-2022.09.16-01.19.00.log DeadByDaylight-backup-2022.09.16-03.57.31.log DeadByDaylight-backup-2022.09.18-17.32.26.logAnother issue we also had was that sometimes a user would join and see everyone else, but one of the people could end up not seeing that user in the lobby. Sometimes the "host", in this case reference to the original person who opened the lobby, wouldn't see them as we experienced on Sunday, and sometimes another user might not see another person. This became an issue in Custom Games where one user did not see people either return from their matches (It would state "In a match") as a Killer if we were rotating to another killer. The game would then state you cannot start with 2 killers for that person, even if everyone saw that the lobby was showing only one killer. The player who was not able to see the updated lobby state would then have to leave and rejoin, which could lead to the Unknown Error upon rejoining again. We got a bit lucky when we had that happen.
I hope the above logs can provide some further insight.
If the game managed to start in this state, everyone would load in and the game would play normally, but the issues would come with pre-game checks if updated lobby status wasn't being correctly seen by the client.