ozCollisionCreator v2.1

October 21, 2010

.
After receiving feedback showing an interest in this script, I decided it was about time for me to clean it up and get it out here for public release.

The functions are still the same, with a slight change to the interface, and 1 main addition.

Basic functions / actions of this script:

Creates collision box
Renames the collision box (to 1 of the 4 collision types)
Assigns a collision shader
Assigns Game Engine properties if applicable
(NOTE: this has been commented out in the script, and depends on what game engine you are using.)

In the top section,
Option 1 “Create Collision”:

creates 1 collision based on ALL objects selected in the scene.

Option 2 “Create Multi-Collision”:

creates a collision box for EVERY object selected in the scene. (i.e. 5 objects selected = 5 collision boxes) To make management of assets easier, each collision box is parented / linked to their respective object.

The 2nd section “Selected Object is Collision”:
This section is used if you already have a collision object created and you want to assign collision properties to the selected mesh.

3rd section “Add Modifier to Collision”:
This adds 1 of 2 modifiers, if further editing and modeling of the collision box is needed or desired for a more accurate fit to the game asset.

4th section “Toggle Collision Display”:
Toggles the collision boxes within the max scene. I found this helpful, because after I have a collision box created, I don’t care to see it. Just boxmode, freeze it and forget about it.

And finally, the new stuff;
5th section “Collision Shader Options”:
Here the user has the option to choose their DirectX shader to use (or not use) for creating the collisions. By default, the OZ collision shader is used, and comes packaged in the script. If your pipeline uses another shader for collisions (assuming it does), no problem. Select the last radio button and “Browse for new (.fx) shader”. The script will remember the shader you browsed for and that option will be used next time the script is run. So that means you don’t have to keep the script window open and you won’t have to browse for it every time you reopen max.

DOWNLOAD

ozCollisionCreator.mzp (version 2.1)

Installation:
Installation is easy; after downloading the ozCollisionCreator.mzp from link provided below, (with 3DsMax running) just drag and drop the .MZP file onto your viewport.

// Posted in Maxscript
Tags: 3DsMax, collision, DirectX Shader, DOWNLOAD, GameDev, MXS, OZ Tools

http://www.omnized.com ΦZ

testing comments and Gravatar images…
http://www.OmniZed.com ΦZ

more testing…hooking up Disqus for comments
http://www.OmniZed.com/cybergrub2/ Jason Barnidge

Great tutorial via @3dmotive:twitter»Create Mesh Collision for #UDK in #3dsMax http://goo.gl/1bBZO
Why not use the CollisionCreator to speed things up?
Convention standards & requirements for UDK pipeline integration are fairly easy to implement into ozCollisionCreator.
If you have any questions, requests or problems implementing this setup, I’m happy to address them here.
http://www.OmniZed.com/cybergrub2/ Jason Barnidge

Great tutorial via @3dmotive:twitter»Create Mesh Collision for #UDK in #3dsMax http://goo.gl/1bBZO
Why not use the CollisionCreator to speed things up?
Convention standards & requirements for UDK pipeline integration are fairly easy to implement into ozCollisionCreator.
If you have any questions, requests or problems implementing this setup, I’m happy to address them here.