-
-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add "Create boundary cube collision sibling" option for mesh #5868
Comments
The Advanced Import Settings dialog already allows you to create primitive collision shapes for various meshes in a 3D scene. See also #3155. While a new option to do this in existing scenes makes sense, I feel it's not flexible enough as you may want to have a capsule, cylinder or sphere shape instead. The difficulty here is providing this kind of flexibility without making the dropdown too complex. |
I fail to see how adding a new option, or three, makes the dropdown too complex. If it grows, it can be made into a submenu instead |
i like this idea because many times when i setup scenes i have to do a bunch of work setting up colliders for simple objects. it would be nice to have a much simpler one click solution |
It is still very tedious to add collision upon import since you must manually edit a box collider (or any other primitive) to fit every single mesh being imported. This would be easier (or not at all necessary) if the bounding box was assumed instead when a box collider is desired. Some other major papercuts in the collision import workflow right now:
|
Describe the project you are working on
A 3D space game with many large and small collidable meshes.
Describe the problem or limitation you are having in your project
Describe the feature / enhancement and how it helps to overcome the problem or limitation
Having an option in the mesh drop down to create a boundary box collision sibling would very easily allow the developer to quickly create safe and performant colliders around their objects.
Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams
I imagine the code would find the most distant points and create a cube that encapsulate those points.
If this enhancement will not be used often, can it be worked around with a few lines of script?
I propose that for a heavy number of use cases, a simple box collider would be more beneficial for mesh objects, especially static ones. I think that this feature will be used very often.
Is there a reason why this should be core and not an add-on in the asset library?
The reason I feel this should be in the core is that it deals with the fundamentals of 3D interaction via colliders. I propose that many developers are using the collider generators as a means to speed up the development of simple game fundamentals and this tool would give them a free performance and safety boost.
The text was updated successfully, but these errors were encountered: