Datablocks

#1 AFX leverages most core aspects of Torque, including the way it handles datablock and object ids. However, we do typically find the default setting of 10 for DataBlockObjectIdBitSize to be too small so we ship AFX with DataBlockObjectIdBitSize=13 which makes room for over 8000 datablocks. We've also run with higher values without running into any problems.

It is true that datablocks and objects share the space of a 32-bit integer for their id representation, so it is also true that increasing the value for DataBlockObjectIdBitSize also reduces the total number of possible object ids. However, there is an awful lot of headroom for regular object ids. With DataBlockObjectIdBitSize=13, the first object id is 8258. That leaves a lot of object ids before you overflow.

(Note that setting DataBlockObjectIdBitSize=13 does not mask off 13 bits of the object id. It merely specifies the number of bits required to send a datablock id over a network connection.)

#2 Thanks for the reply. So I am assuming that setting it to 13 allows for roughly 8191 datablocks and 4,294,959,104 object ids since it is 32 bit?

By the way AFX looks amazing and I plan on purchasing soon!

#3

Quote:
So I am assuming that setting it to 13 allows for roughly 8191 datablocks and 4,294,959,104 object ids since it is 32 bit?

Yes, that's generally correct, although there is a small range of ids (64 I think) that are earmarked for message-objects.

#4 Thanks for the quick help. Everything makes more sense now.