Search Issue Tracker
Won't Fix
Votes
2
Found in
4.3.4f1
Issue ID
594682
Regression
No
RPC execution order is wrong sometimes
To reproduce:
1. Open attached project
2. Open TestScene
3. Build and run the testscene
4. Click "ServerWrong"
5. In the editor, enter play mode and select the "Client"
6. Three logs are printed - notice how SecondRPC gets called before the FirstRPC
It seems to be caused by having the FirstRPC call the SecondRPC
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] FPS does not match the targeted FPS when it is set with Application.targetFrameRate
- RenderPipelineManager.activeRenderPipelineTypeChanged does not detect changes when changing the Render Pipeline Asset outside of Play Mode
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
zeroZshadow
Jun 17, 2014 01:23
As i cant see the attachement im not sure if this is the same bug as i has.
When calling an RPC using RPCMode.AllBuffered. The RPC will first call the function locally and on return add it to the buffer. This behaviour should be reversed. Adding to the buffer first, then call.
Otherwise having multiple rpc calls within eachother will be buffered in the reverse order.