Opened 10 years ago

Closed 7 years ago

#2863 closed defect (needsinfo)

OOS related to changedEntityTemplateInfo, on rejoin

Reported by: z Owned by:
Priority: Must Have Milestone:
Component: Core engine Keywords:
Cc: Patch:

Description

Game goes oos when somebody rejoins.. strange, cuz leper fixed old rejoin oos bug, and afterwards we had an excessive rejoin test session, where no oos occured.

Attachments (4)

oos_dump.txt.tar.gz (233.6 KB ) - added by z 10 years ago.
commands4.txt (172.2 KB ) - added by z 10 years ago.
oos_dump.zip (245.2 KB ) - added by Timothy Hamlett 10 years ago.
oos_dump.log from Angelo and Z.
oos_dumps.diff (139.5 KB ) - added by Itms 9 years ago.

Download all attachments as: .zip

Change History (8)

by z, 10 years ago

Attachment: oos_dump.txt.tar.gz added

by z, 10 years ago

Attachment: commands4.txt added

by Timothy Hamlett, 10 years ago

Attachment: oos_dump.zip added

oos_dump.log from Angelo and Z.

comment:1 by Itms, 9 years ago

Milestone: BacklogAlpha 18
Priority: Should HaveMust Have
Summary: Rejoin oosOOS related to changedEntityTemplateInfo, on rejoin

The problem seems to come from the changedEntityTemplateInfo data. I generated a diff.

Also, both games in #2844 seem to have encountered the same problem, so I am going to close it as a duplicate and gather information here. Don't hesitate to take a look at the other ticket and valuable information there.

I'm setting the priority to Release Blocker, but determining if the problem is still here is important too.

by Itms, 9 years ago

Attachment: oos_dumps.diff added

comment:2 by historic_bruno, 9 years ago

Milestone: Alpha 18Backlog

Backlogging since according to mimo, it shouldn't affect gameplay, but it might still be a bug that needs investigating.

comment:3 by Itms, 9 years ago

#3375 might be the cause.

comment:4 by elexis, 7 years ago

Milestone: Backlog
Resolution: needsinfo
Status: newclosed

In #3133 and #2844 there are also OOS reported with changedEntityTemplateInfo being affected. Sounds like it's been fixed meanwhile as we didn't get any further reports.

As Itms mentioned probably a dupe of #3375.

Note: See TracTickets for help on using tickets.