Opened 8 years ago
Last modified 7 years ago
#3615 new defect
Serializationtest support for random map scripts
Reported by: | elexis | Owned by: | |
---|---|---|---|
Priority: | Should Have | Milestone: | Backlog |
Component: | Core engine | Keywords: | |
Cc: | Patch: |
Description (last modified by )
Currently it is not possible to do serializationtests on random-map-scripts.
However most matches are played on RMS, so most out-of-sync errors become known on such maps.
Also most of the time we can't reproduce the OOS error otherwise, so we have to create the equivalent RMS map in atlas to do a serializationtestmatch with the provided replay file, which is a painful process.
We can generate the map once and then reuse that consecutively.
Attachments (1)
Change History (3)
comment:1 by , 8 years ago
by , 8 years ago
Attachment: | serialization.patch added |
---|
comment:2 by , 7 years ago
Description: | modified (diff) |
---|---|
Priority: | Nice to Have → Should Have |
(About every OOS on rejoin is revealed in multiplayer lobby matches and those take place in the vast majority on random-map-matches. Having to create the equivalent scenario map consumes a lot of time, so this is an important bottleneck of OOS debugging.)
Attached patch attempts this. It seems like the "map generation" part works correctly but there is an unknown OOS in the obstruction manager and I think also an OOS in a range manager (will create an upcoming ticket for that one).
It also stops the serializationtest from recreating the map every turn which was wasteful.