Micro-optimizations to allow more dynamic objects
When profiling my game, normcore's Realtime.Update is consistently the most expensive part of my update loop. Even in a best case scenario, when idling in my game, when most objects are not moving, and we're not spawning any synced objects.
The most expensive method when idling is RealtimeModel.OnWillWrite. Within that, the most expensive OnWillWrite is RealtimeTransformModel, and within that RealtimeTransformRigidbody.OnLocalModelWillWrite is most expensive. A quick look at a deep profile sample shows some micro-optimisations which could shave a signficant percentage of the CPU cost of updating RealtimeTransforms.
From the call counts in this screenshot, you can see there are: ...
The most expensive method when idling is RealtimeModel.OnWillWrite. Within that, the most expensive OnWillWrite is RealtimeTransformModel, and within that RealtimeTransformRigidbody.OnLocalModelWillWrite is most expensive. A quick look at a deep profile sample shows some micro-optimisations which could shave a signficant percentage of the CPU cost of updating RealtimeTransforms.
From the call counts in this screenshot, you can see there are: ...
Auto-Requesting RealtimeTransforms (Rigidbody) on connect
I do not believe this is a base feature currently, but having Normcore automatically take ownership of a RealtimeTransform with a rigidbody attached when you are the first joiner would make some additional logic a lot more simple and save new developers the headache of wondering why their objects are floating in midair on first connection. (the image may or may not have been faked for dramatic effect)
Network Profiler
Something like this could be super sweet to have while not being extremely complicated. Unity allows creation of custom profiler modules, so perhaps even one with simple stats like outbound / inbound data as well as what sent it out / received it could be extremely useful in tracking down bandwidth hogs and squash them.
