Thanks! The current version isn’t perfect unfortunately
I still don’t know how to solve a couple of issues. There are two known problems right now:
I understand you. It's hard to perfect something. I have several scripts and programs for VAM in development myselfThanks! The current version isn’t perfect unfortunately
1. Restarting the scene from the menu doesn’t reactivate the collisions.
2. If you switch the prefab too quickly using the slider on a CUA atom, some hair particles may get destroyed.
Basically these are the kinds of problems that can currently only be fixed by restarting the game completely. If you find any other issues please let me know. Clear steps to reproduce them are really important and would help a lot.
I’m not sure automatically generating box or capsule colliders from arbitrary scene geometry would be practical. Are you asking for support for colliders that you would place manually? Also, what kind of scene are you using? My test scene has around 250k colliders vertices, and the performance is still very good. I have this - https://hub.virtamate.com/resources...-to-30-faster-physics-up-to-60-more-fps.43427Could you provide support for box colliders for the plugin? Using mesh colliders for the entire scene does have some performance overhead.
The log confirms that the collider is found, but its mesh was exported without Read/Write enabled option in unity. CUACollision needs CPU access to the mesh vertices and triangles to build its GPU BVH. A mesh selector would help with optimization, but it cannot make a non-readable mesh usable. The asset author needs to enable Read/Write Enabled on the collider mesh and rebuild the assetbundle.
When creating environments, I don't use mesh colliders for simple furniture, but for furniture with a high vertex count, such as a carved cabinet, box collisions are obviously more suitable. Of course,I will manually place the box collider. it just needs to be supported within the plugin.
Well, I managed to get something working. we can place virtual colliders inside a cua. But it’s still pretty rough at the moment. I’ve also fixed the old bug where collisions stopped working after reloading the scene. I’ll release the update once I’m sure everything is stable.When creating environments, I don't use mesh colliders for simple furniture, but for furniture with a high vertex count, such as a carved cabinet, box collisions are obviously more suitable. Of course,I will manually place the box collider. it just needs to be supported within the plugin.
That's absolutely fantastic, bro! Looking forward to your updates!Well, I managed to get something working. we can place virtual colliders inside a cua. But it’s still pretty rough at the moment. I’ve also fixed the old bug where collisions stopped working after reloading the scene. I’ll release the update once I’m sure everything is stable.
As for automatic colliders they’re simply not practical for a large scene. They might work for a small simple prop, but even then automatically generating a simplified collider is too difficult and often inaccurate. There’s no guarantee it will properly match the mesh topology
View attachment 615469
Thanks, I'll try your suggestions! And if hair breaks on simple square collider then that's probably just VAM things and your plugin is perfectly fine. I remember my other looks didn't have those problems when I was using box colliders with Foost plugin, so it's most likely specific hair settings!
