Zandronum Chat on our Discord Server Get the latest version: 3.2
Source Code
My View | View Issues | Change Log | Roadmap | All Projects Issue Support Ranking | Rules | My Account
  

View Revisions: Issue #2671 [ All Revisions ] [ Back to Issue ]
Summary 0002671: TIDs only sent to client as short - huge issues when combined with UniqueTID()
Revision 2016-06-04 17:36 by Ru5tK1ng
Description UniqueTID() can return any TID in the range [1, 0x7FFFFFFF].

Only TIDs in the range [1, 32767] will be sent properly to the client, since the TID is sent as a signed short.

This causes quite a few issues with using UniqueTID() and newly-spawned actors as a way to send position data to the client (presumably you could also send angle/pitch data this way, but I haven't messed with that), namely that the client only gets a correct TID about 1/65536 of the time.

Right now, almost no Zandronum mods use UniqueTID(), but as mods get developed for Zandronum 3.0, this could very easily become an issue.
Revision 2016-03-20 16:14 by cobalt
Description UniqueTID() can return any TID in the range [1, 0x7FFFFFFF].

Only TIDs in the range [1, 32767] will be sent properly to the client, since the TID is sent as a signed short.

This causes quite a few issues with using UniqueTID() and newly-spawned actors as a way to send position data to the client (presumably you could also send angle/pitch data this way, but I haven't messed with that), namely that the client only gets a correct TID about 1/65536 of the time.

Right now, almost no Zandronum mods use UniqueTID(), but as mods get developed for Zandronum 3.0, this could very easily become an issue.
Revision 2016-03-07 04:51 by throwaway
Description UniqueTID() can return any TID in the range [1, 0x7FFFFFFF].

Only TIDs in the range [1, 32767] will be sent properly to the client, since the TID is sent as a signed short.

This causes quite a few issues with using UniqueTID() and newly-spawned actors as a way to send position data to the client (presumably you could also send angle/pitch data this way, but I haven't messed with that), namely that the client only gets a correct TID about 1/65536 of the time.

Right now, almost no Zandronum mods use UniqueTID(), but as mods get developed for Zandronum 3.0, this could very easily become an issue.




Questions or other issues? Contact Us.

Links

Copyright © 2000 - 2025 MantisBT Team
Powered by Mantis Bugtracker