Hi,
MAX_PACKET_SIZE defines the MTU for the connection, but it does not control the per-frame bandwidth limit. I don’t believe we generally recommend changing this value.
The bandwidth limit is set by the ConfiguredInternetSpeed, ConfiguredLanSpeed, MaxClientRate, and MaxInternetClientRate config values. These are by default 100,000, but they can be raised further if needed. These values represent bytes per second, so the per-frame bandwidth limit is also dependent on the framerate (you can see where this is calculated towards the end of UNetConnection::Tick).
In Networking Insights, it’s worth noting that each column represents a single packet, not a single frame. If you hover over each column, you can see the timestamp and engine frame number the packet was sent/received on.
As for seeing how the packet is arranged, I don’t believe there is any way to get more info than what is shown in the packet contents panel, where you can see the number of bits that were sent/received as part of the MoverNetworkPredictionLiasonComponent’s replication (ActorChannel->MoverNetworkPredictionLiasonComponent->Properties->ReplicationProxy_Simulated/Autonomous).
Finally, for more info on managing Mover’s bandwidth, I’m going to loop in someone more familiar with the system.
Thanks,
Alex