Correct.
Although you only need to set collision on the base mesh, not all the texture layer's geometry. You can do this by tracking down the base mesh name. Its something like trn_baselayer or something. Im not at my PC so cant remember. However, have a look whats its called in a 3D app (or dump the entitynames to the debuglog in b3d). It will certainly speed up your collision!
PS: if you want different footstep sounds ie, snow grass etc then use an AI color recognition from a tiny downward render capture, rather than testing collisions on all that extra geometry ;)
X when loaded seems to ignore the vertex alpha values even though they are in the file. This isnt just in blitz3d, it even happens in MS's own X viewer too and i have no idea why. However, search my forum there is some code in there to re-parse the X file once loaded and set the alpha values on the loaded mesh correctly.
Although you only need to set collision on the base mesh, not all the texture layer's geometry. You can do this by tracking down the base mesh name. Its something like trn_baselayer or something. Im not at my PC so cant remember. However, have a look whats its called in a 3D app (or dump the entitynames to the debuglog in b3d). It will certainly speed up your collision!
PS: if you want different footstep sounds ie, snow grass etc then use an AI color recognition from a tiny downward render capture, rather than testing collisions on all that extra geometry ;)
X when loaded seems to ignore the vertex alpha values even though they are in the file. This isnt just in blitz3d, it even happens in MS's own X viewer too and i have no idea why. However, search my forum there is some code in there to re-parse the X file once loaded and set the alpha values on the loaded mesh correctly.