| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 0001723 | OpenClonk | Engine - Network | public | 2016-04-19 21:39 | 2017-12-28 20:47 | ||||||||
| Reporter | K-Pone | ||||||||||||
| Assigned To | |||||||||||||
| Priority | normal | Severity | major | Reproducibility | sometimes | ||||||||
| Status | acknowledged | Resolution | open | ||||||||||
| Product Version | |||||||||||||
| Target Version | git master | Fixed in Version | |||||||||||
| Summary | 0001723: Network Sync Loss in replays | ||||||||||||
| Description | In some replays from network games a Sync Loss will occur after some time and causing the game to end before the replay ends. You can continue the replay and it will play fine, but the console gets spammed with sync loss messages and right after the replay ends you end up with a huge message box with all the sync loss messages, which are quite a lot after some time. | ||||||||||||
| Tags | No tags attached. | ||||||||||||
| Attached Files |
| ||||||||||||
 Relationships |
|
 Relationships |
| Notes |
|
|
Isilkor (developer) 2017-03-26 12:49 |
We should store the revision used to record a replay inside the file and check/emit a warning if they're different from the current engine. |
|
Caesar (developer) 2017-09-03 04:49 |
This happens for me. On records that were made with the exact same build and repository… |
| Notes |
| Issue History |
|||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-04-19 21:39 | K-Pone | New Issue | |
| 2016-04-19 21:39 | K-Pone | File Added: 742-MeltingCastle.ocs | |
| 2017-03-26 12:49 | Isilkor | Status | new => acknowledged |
| 2017-03-26 12:49 | Isilkor | Note Added: 0005636 | |
| 2017-08-05 13:58 | Maikel | Target Version | => 8.0 |
| 2017-09-03 04:49 | Caesar | Note Added: 0005772 | |
| 2017-12-28 20:47 | Luchs | Target Version | 8.0 => git master |
| Issue History |
