-
Notifications
You must be signed in to change notification settings - Fork 0
Fix multisync #1505
Comments
|
Per uploaded file Should remove the asserts before committing to 2.3 |
|
Per changed status from |
|
Per set resolution to |
|
Per commented (In [9579]) Fix offscreen updates, they were only setting droid pos.x and pos.y for most orders, and those are |
|
Buginator commented Whoops, didn't see this ticket before. When I get some more time, I will dig deeper into this patch, and see why it is so unstable for me. |
|
Per changed status from |
|
Per changed resolution from |
|
Per changed status from |
|
Per changed owner from `` to |
|
Per commented I tested it quite a bit, and it worked fine for me. I did not up the network version, so if you forgot to use the patch on both sides, it would cause this problem. |
|
Buginator commented I did svn up on both, and was testing my other stuff with reverse merging that patch before. If I didn't reverse it, then it would cause all kinds of strange bugs on either windows or linux. As I said, I will check into it some more as soon as I get more time. |
|
Per uploaded file New version. Untested in MP yet. |
|
Per changed status from |
|
Per changed resolution from `` to |
keyword_sync_check_networkresolution_fixedtype_bug| by PerOffscreen updates did not seem to work anymore. I traced this back to offscreen updates only setting pos.x and pos.y on a droid for most orders, and those are promptly overwritten next frame by sMove.fx and sMove.fy which are not updated. So I rewrote the code a bit to only use the floating point values. I also made it issue move command for onscreen changes when in guard order. Not sure why we do not do this for all orders, but at least guard should also be safe. DORDER_NONE is rarely used anymore.
Issue migrated from trac:1505 at 2022-04-15 20:59:55 -0700
The text was updated successfully, but these errors were encountered: