#3
by Personwithhat2
Not to mention that their system is flat out buggy, bad RMI's, bad option groups, etc. etc.
Lots of issues that I've had to fix in the engine source code.....and I'm STILL working on it!
In fact, you can't reliabiliy implement networking becuase their core timer system is inaccurate. As in, client/server diverge near instantly.
1) Floating point errors, catastrophic cancellation, rounding, inconsistent sleep rates (e.g. 0.065 vs 0.0073 seconds, obviously they're diverging. Every frame. Pretty fast.....)
2) Physics thread has a giant 'TODO' on fixed timesteps/thread-syncing. That hasn't been touched in ages .-.
And so on.
Currently overhauling the engine to improve the timer system, in final merging/pull request stage. Should have it out as soon as possible, was hoping 3 months ago but RL kicked in. So, dunno, a month?
Doesn't help that nobody has a decent work flow with github, or a work flow period. Then again, seeing how most people 'debug networking' code (e.g. open each window by hand and drag them around) vs my method -> Press 'debug' and boom 3 windows instantly in proper positions...... xd