11-27-2006, 09:16 PM
I've been looking into the multiple collision mesh issue again. I had just posted again to the Niftools forum when I remembered RW's post earlier in this very thread. I had seen it a while back, but I didn't know enough about all of this to connect the dots. But now...
HOW TO EXPORT MULTIPLE COLLISION MESHES FROM MAX (ON PURPOSE)
Versions: Max 8, NifTools Max plugin 0.2.9.
- Make your model with all its components, then your simplified collision meshes (CMs) for those components.
- Combine (via Attach) all of your CMs that you wish to share the same Havok properties; this is probably not necessary, but simplifies things.
- Make sure that you have set the Havok properties for all of your CMs with the NifProps tool.
- At this point, you have a set of non-CM meshes and a set of CM meshes. Use the Max group function to make one group of the non-CM meshes and one group for each of the CM meshes. At the end, you should have N+1 groups, where N is the number of CMs.
- Then export the model, ensuring that the "Remove extra bones" option is not checked.
Notes:
- I've only done this for statics,
- the bhkListShape block still must be inserted for each CM to fix the arrow-penetration problem.
Hope this helps,
Steve
HOW TO EXPORT MULTIPLE COLLISION MESHES FROM MAX (ON PURPOSE)
Versions: Max 8, NifTools Max plugin 0.2.9.
- Make your model with all its components, then your simplified collision meshes (CMs) for those components.
- Combine (via Attach) all of your CMs that you wish to share the same Havok properties; this is probably not necessary, but simplifies things.
- Make sure that you have set the Havok properties for all of your CMs with the NifProps tool.
- At this point, you have a set of non-CM meshes and a set of CM meshes. Use the Max group function to make one group of the non-CM meshes and one group for each of the CM meshes. At the end, you should have N+1 groups, where N is the number of CMs.
- Then export the model, ensuring that the "Remove extra bones" option is not checked.
Notes:
- I've only done this for statics,
- the bhkListShape block still must be inserted for each CM to fix the arrow-penetration problem.
Hope this helps,
Steve