Changes between Version 14 and Version 15 of Debugging

Timestamp:

Dec 20, 2015, 11:23:06 PM (8 years ago)

Author:

elexis

Comment:

Add debugging advice and link to patch

Debugging

@@ -102 +102 @@
 Even OOS dumps with many differences can be useful. Differences between local entities (previews, waypoint flags) can be disregarded, as they don't affect the serialized game state. If you notice one component is especially affected or a component of a recently added feature, then it's often possible (and desirable) to construct a much simpler test case. An OOS in an hour long multiplayer game is complicated, but an OOS or serialization failure on a blank map with a handful of entities is much simpler.
 
+On linux you can safely start two instances of 0 A.D., host with one and rejoin with the other. This way you can test whether a certain behavior triggers an out-of-sync error.
+If you do that, you can use [attachment:t3339_command_line_option_ooslog_unique_v1.2.patch:ticket:3339 this patch] to prevent the oos_dump.txt from being overwritten, allowing you to compare the newly produced oos-dumps.
+
 === OOS caused by the AI ===
 An out of sync error is caused by the AI if the following conditions are both true: