You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, CBitStream instances are created and destructed a lot within the scope of the netcode. In the scope of unpacking incoming messages, a single CBitStream object should be kept around and merely reset for each packet to unpack while also being instructed as to where its next unpacking target resides.
Further, when messages are sent at any time, a new CBitStream is constructed which entails not only memory allocation for the CBitStream itself but also the heap entry for its working data. These especially should be reused in the same way as they would be for incoming messages.
The text was updated successfully, but these errors were encountered:
Currently, CBitStream instances are created and destructed a lot within the scope of the netcode. In the scope of unpacking incoming messages, a single CBitStream object should be kept around and merely reset for each packet to unpack while also being instructed as to where its next unpacking target resides.
Further, when messages are sent at any time, a new CBitStream is constructed which entails not only memory allocation for the CBitStream itself but also the heap entry for its working data. These especially should be reused in the same way as they would be for incoming messages.
The text was updated successfully, but these errors were encountered: