UUM-147343
Fixed in 6000.6.0f1Mentioned in 14 release notes.
First fixed in 6000.6.0f1 (Aug 31, 2026); relisted in 11 later releases.
| Version | Section | Risk | Impact | Note |
|---|---|---|---|---|
| 6000.7.0b8 | Fixes Netcode for Entities | Fix | Fixed a predicted ghost divergence caused by running at very high framerates with very low SimulationTickRate, which meant that the client to not even fully predict one tick ahead of the latest snapshot arrival, causing the snapshot to be applied on a partial tick, which in turn resulted in the prediction-history backup failing to write, so it would constantly be stale. | |
| 6000.7.0b7 | Fixes Netcode for Entities | Fix | Fixed a predicted ghost divergence caused by running at very high framerates with very low SimulationTickRate, which meant that the client to not even fully predict one tick ahead of the latest snapshot arrival, causing the snapshot to be applied on a partial tick, which in turn resulted in the prediction-history backup failing to write, so it would constantly be stale. | |
| 6000.7.0b6 | Fixes Netcode for Entities | Fix | Fixed a predicted ghost divergence caused by running at very high framerates with very low SimulationTickRate, which meant that the client to not even fully predict one tick ahead of the latest snapshot arrival, causing the snapshot to be applied on a partial tick, which in turn resulted in the prediction-history backup failing to write, so it would constantly be stale. | |
| 6000.7.0b5 | Fixes Netcode for Entities | Fix | Fixed a predicted ghost divergence caused by running at very high framerates with very low SimulationTickRate, which meant that the client to not even fully predict one tick ahead of the latest snapshot arrival, causing the snapshot to be applied on a partial tick, which in turn resulted in the prediction-history backup failing to write, so it would constantly be stale. | |
| 6000.7.0b4 | Fixes Netcode for Entities | Fix | Fixed a predicted ghost divergence caused by running at very high framerates with very low SimulationTickRate, which meant that the client to not even fully predict one tick ahead of the latest snapshot arrival, causing the snapshot to be applied on a partial tick, which in turn resulted in the prediction-history backup failing to write, so it would constantly be stale. | |
| 6000.7.0b3 | Fixes Netcode for Entities | Fix | Fixed a predicted ghost divergence caused by running at very high framerates with very low SimulationTickRate, which meant that the client to not even fully predict one tick ahead of the latest snapshot arrival, causing the snapshot to be applied on a partial tick, which in turn resulted in the prediction-history backup failing to write, so it would constantly be stale. | |
| 6000.7.0b2 | Fixes Netcode for Entities | Fix | Fixed a predicted ghost divergence caused by running at very high framerates with very low SimulationTickRate, which meant that the client to not even fully predict one tick ahead of the latest snapshot arrival, causing the snapshot to be applied on a partial tick, which in turn resulted in the prediction-history backup failing to write, so it would constantly be stale. | |
| 6000.7.0b1 | Fixes Netcode for Entities | Fix | Fixed a predicted ghost divergence caused by running at very high framerates with very low SimulationTickRate, which meant that the client to not even fully predict one tick ahead of the latest snapshot arrival, causing the snapshot to be applied on a partial tick, which in turn resulted in the prediction-history backup failing to write, so it would constantly be stale. | |
| 6000.7.0a6 | Fixes Netcode for Entities | Fix | Fixed a predicted ghost divergence caused by running at very high framerates with very low SimulationTickRate, which meant that the client to not even fully predict one tick ahead of the latest snapshot arrival, causing the snapshot to be applied on a partial tick, which in turn resulted in the prediction-history backup failing to write, so it would constantly be stale. | |
| 6000.5.11f1 | Fixes Netcode for Entities | Fix | Fixed a predicted ghost divergence caused by running at very high framerates with very low SimulationTickRate, which meant that the client to not even fully predict one tick ahead of the latest snapshot arrival, causing the snapshot to be applied on a partial tick, which in turn resulted in the prediction-history backup failing to write, so it would constantly be stale. | |
| 6000.6.0f1 | Fixes Netcode for Entities | Fix | Fixed a predicted ghost divergence caused by running at very high framerates with very low SimulationTickRate, which meant that the client to not even fully predict one tick ahead of the latest snapshot arrival, causing the snapshot to be applied on a partial tick, which in turn resulted in the prediction-history backup failing to write, so it would constantly be stale. | |
| 6000.6.0f1 | Fixes Netcode for Entities | Fix | Fixed a predicted ghost divergence caused by running at very high framerates with very low SimulationTickRate, which meant that the client to not even fully predict one tick ahead of the latest snapshot arrival, causing the snapshot to be applied on a partial tick, which in turn resulted in the prediction-history backup failing to write, so it would constantly be stale. | |
| 6000.6.0b10 | Known Issues Netcode for Entities | Caution | Known issue | Fixed a predicted ghost divergence caused by running at very high framerates with very low SimulationTickRate, which meant that the client to not even fully predict one tick ahead of the latest snapshot arrival, causing the snapshot to be applied on a partial tick, which in turn resulted in the prediction-history backup failing to write, so it would constantly be stale. (UUM-147343) Fixed in 6000.6.0f1. |
| 6000.6.0b9 | Known Issues Netcode for Entities | Caution | Known issue | Fixed a predicted ghost divergence caused by running at very high framerates with very low SimulationTickRate, which meant that the client to not even fully predict one tick ahead of the latest snapshot arrival, causing the snapshot to be applied on a partial tick, which in turn resulted in the prediction-history backup failing to write, so it would constantly be stale. (UUM-147343) Fixed in 6000.6.0f1. |