userIan Hendersoncancel
branchrust_reboot/main/network_profilercancel

14 Commits over 0 Days - ∞cph!

16 Days Ago
Final profiler window tweaks: supports larger packet rundowns
16 Days Ago
Capture all missed outgoing packets in client and server
16 Days Ago
Ensure 'server' is set right on our inbound packets
16 Days Ago
missed files (again)
16 Days Ago
Record the rest of the inbound packets I missed: group enter, group change, group destroy, world data, voice data, entity flags, entity position
16 Days Ago
Better effect outgoing packets
16 Days Ago
missing file
16 Days Ago
main -> network_profiler
20 Days Ago
- Added RPC name under the info section of RPC packets - Added global filters for server/client realms - Added packet type breakdown of the top packets - Clean restyle of the net graph
20 Days Ago
Add a network graph
20 Days Ago
First draft of a network profiler. Featuring: - Simple packet stats - Advanced stats (entity name, packet size, timestamp etc) - Filtering via timestamp, name, type, direction, realms - Per entity bandwidth usage, showing how much % of the bandwidth is taken up by what packets
20 Days Ago
compile error
20 Days Ago
Store: - RPC inbound/outbound - SyncVar inbound/outbound - PackedSyncVar inbound/outbound - Effect inbound/outbound Missed some metrics here and there, but critically I've managed to grab the id its going to for each one
20 Days Ago
Setup data structures to store more detailed packet information, this will be stored and handled locally rather than being sent off for analytics. Data will be stored in a big ass circular buffer that we can then sort through to do the analytics. These include: - Basic data we stored before (byte size, type, etc) - Associated entity with the packet - Optional full packet data - Timestamp