PlayerLocationCommand Improvements

Open DominicMaas opened this issue 6 years ago • 2 comments

Limit how often the PlayerLocationCommand is sent, or look into how the command is being handled on the server / other clients. Are there any bottlenecks that could be fixed? (I may introduce a timing library so we can see if there are any areas of the mod that need improvements).
Fix ICameraUpdateCurrentPosition.PostFix (ICameraHandler.cs). It's causing a whole lot of exceptions (on the host, have not tested the client).

Related to #153

Dec 22 '19 21:12 DominicMaas

The actual sending and receiving of PlayerLocationCommand might not be causing the issue, but instead the size of the log file due to how often the command is sent.

Dec 22 '19 21:12 DominicMaas

Tag: P is not defined is caused when the client moves NullRefException is caused when the host moves

Dec 22 '19 21:12 DominicMaas

PlayerLocationCommand has been replaced by the new player pointer implementation

Apr 09 '23 01:04 kaenganxt