public static class SnapshotInspectorTakes a snapshot apart, without applying any of it.
No guide page documents this yet — the page shows what the code says about itself.
Remarks
The half of a packet inspector that has to live next to the encoder, because it is the only thing that knows the record layout. What is done with the answer — a console dump, a tick timeline, an editor panel — is somebody else's problem and deliberately not this type's.
It reads the same bytes the client does and applies none of them. That is what makes it usable on a recorded capture, on a snapshot the client rejected, and on a peer's traffic while it is running. It needs the registry to name the component types, and it degrades to reporting sizes without names rather than failing when a type is not in it.
A difference cannot be decoded to a value without the capture it was measured from, which the inspector does not have. It reports the shape — which object, which component, which baseline, how many bits — and that is the question a bandwidth investigation is asking anyway.
Methods (1)
public static SnapshotContents Inspect(ReplicationRegistry registry, ReadOnlySpan<byte> snapshot)Reads a snapshot.
Used by (3)
- LocalMatchMultiplayer
- DiagnosticsTestsVixen.Net.Tests
- SnapshotInspectorTargetVixen.Net.Fuzz