Some userdata variables are still uint32_t

Question

Some userdata variables are still uint32_t

Closed this issue 2 months ago · 2 comments

Some mUserData variables, such as the one in CompoundShapeSettings, are still uint32_t, instead of uint64_t. Should these be expanded to be 64-bit variables so they are suitable for storing custom pointers?

Answer 1 · 2024-03-27T19:08:05.000Z

This is on purpose to keep compound shapes small (we have compounds with 1000s of shapes).

Answer 2 · 2024-03-27T19:50:22.000Z

OK, makes sense. During contact callbacks, etc., is the SubShapeID one of these such sub-shapes, or does the 'parent' compound shape body ID consist of this? (I admit I have not gotten to the point of testing this yet)

Essentially I want to be sure that if I am handling a contact, or a ray/shape cast, etc, I can find out the mUserPointer of the parent compound shape (the 64-bit mUserData).