Plugins CuaGpuColliders

[Foost]

Foost submitted a new resource:

CuaGpuColliders - Adds GPU colliders to CUA objects, allowing them to interact with clothes and hair

A simple plugin that enabled CUA atoms to collider with VAM clothing and hair.

To use the plugin, just add CuaGpuColliders.clist to a CUA atom.

When attached to a CUA atom, it automatically creates GPU colliders for any sphere and capsule colliders it can find in the asset.
It will do nothing if the asset has only box or mesh colliders, those are not supported by GPU colliders.

The plugin has nothing to configure, but you can check its custom UI for an overview...

Read more about this resource...

 

[SortaLewd]

any chance for a session plugin to automatically add this to cuas? Great plugin btw

 

[JC318]

Any chance this could also work for colliding with floors?

 

[Foost]

Any chance this could also work for colliding with floors?

VAM's GPU colliders work only with sphere and capsule colliders. Unfortunately floors will most likely use box colliders, or even worse, probably just one big mesh collider for the whole asset.

At some point I'd like to create another addon that would let you place GPU colliders freely, including a grid of capsules roughly approximating a box. But you'd have to place those manually.

 

[Foost]

any chance for a session plugin to automatically add this to cuas? Great plugin btw

I am personally not a fan of those "add to everything" plugins. Especially since this addon won't work with way too many CUAs which just slap one mesh collider onto everything. But maybe one day...

 

[TRSD]

I noticed it's not compatible with Stopper's CUA Controllers. I'm guessing it has something to do with how Stopper handles the CUA, as there's a noticable asset reload when initializing it.
This is the error message your plugin throws:

!> CustomUnityAsset: Expected the CUA object to have one active child with the loaded asset, but it has 2 childern in total and at least two active.

I don't know how much work it'd be to fix. Since honestly, Stopper's plugin is still experimental. So might not be worth the time fixing it for now.

 

[Foost]

I noticed it's not compatible with Stopper's CUA Controllers. I'm guessing it has something to do with how Stopper handles the CUA, as there's a noticable asset reload when initializing it.
This is the error message your plugin throws:

I don't know how much work it'd be to fix. Since honestly, Stopper's plugin is still experimental. So might not be worth the time fixing it for now.

Thanks for the report. I'll at least have a look if I find some time. This error message means that there are multiple objects loaded in the CUA hierarchy when I get the notification about asset change, so my plugin has no idea which one to use for the GPU colliders. This happens even with the normal VAM's CUA loader when switching assets from one assetbundle. I implemented a workaround for that, so it might be not so hard to extend it for this case, who knows. I wanted to play some more with his plugins anyway