• Hi Guest!

    Please be aware that we have released another critical security patch for VaM. We strongly recommend updating to version 1.22.0.10 using the VaM_Updater found in your installation folder.

    Details about the security patch can be found here.
CollisionManager

Plugins + Scripts CollisionManager

Download [0 MB]
Overview Updates (3) Reviews (6) History Discussion Dependency Usage (4)
CheesyFX

CheesyFX

Invaluable member
Featured Contributor
Messages
1,106
Reactions
4,062
Points
173
CheesyFX submitted a new resource:

CollisionManager - Choose atoms which should not collide with the containing atom

I wrote this for @BigBoobCoomBlast69 , but it can be useful for everyone who wants to build structures with native VAM shapes. Now you can overlap them without disabling their collision with other atoms.

Add this to any atom and disable the collision with this atom and a set of other atoms you choose.
Click to expand...

Read more about this resource...
 
Hi! This plugin is just what I was looking for in order to do one of my scene mechanics, however, I have encountered issues.
1) I used ISPhere and ISCapsule plugins on the Person atom and set the plugin to ignore collisions with said person. Story wise this is to block player touch access to certain zones. When I added the plugin into the scene, everything worked as intended. However, when I loaded the scene again, weird collision issues started to happen with the butt, as you will see in the attached video. You can see there that re-enabling soft butt physics fixes it for soft-physics on state, but without them enabled still an issue.
2) this one is pretty serious as it breaks the scene editing: the atoms to which the plugin is attached can not be selected in the trigger menu. They just don't appear. Removing the plugin from them, saving the scene and then loading a scene without them fixes the issue. You can see this in the second part of the video.

Can these be fixed somehow? The plugin is a no doubt a powerful tool!
 
Hey! Glad you find it useful. The first issue appears when you disable collision with the person while soft physics is off. If you set it to on later the soft colliders will collide with the object. This is due to them being disabled in the first place, so the plugin does not cach them. I'll release a fixed version.

I can't reproduce the second error though, nor should this plugin do anything to the storables an atom has.
 
CheesyFX said:
Hey! Glad you find it useful. The first issue appears when you disable collision with the person while soft physics is off. If you set it to on later the soft colliders will collide with the object. This is due to them being disabled in the first place, so the plugin does not cach them. I'll release a fixed version.

I can't reproduce the second error though, nor should this plugin do anything to the storables an atom has.
Click to expand...
Cheers for the update! I can send you the scene it happens in if you are willing to test it there. What worries me is that I can only see them after I remove the plugin.
 
VAMFantasy said:
Cheers for the update! I can send you the scene it happens in if you are willing to test it there. What worries me is that I can only see them after I remove the plugin.
Click to expand...
Would be better if you'd tell me the exact steps to reproduce, starting from a default scene.
 
CheesyFX said:
Would be better if you'd tell me the exact steps to reproduce, starting from a default scene.
Click to expand...
1. Create Empty Scene
2. Add ISSphere atom
3. Add Collision Manager to ISSphere
4. Confirm that it is visible in any trigger menu (for example it's own CollisionTrigger tab)
5. Save the scene
6. Load the scene again
7. Confirm in any trigger menu that it is visible (for example it's own CollisionTrigger tab)

For me in empty scene at step #7 it is already not visible, no settings in the plugin, just having it in the atom
 
Hi! Your plugin doesn't work with CUAs. Only with natice VAM assets or shapes. After applying the plugin to asset and selecting atoms to ignore it works fine.... until you load the scene again. I've tested different CUAs and issue persists.
Steps to reproduce:
1) create CollisionTrigger atom and add the plugin to it
2) add any CUA atom that can collide
3) set the CT atom to ignore collisions with CUA
4) now the trigger should not activate when colliding with CUA
5) save scene
6) restart VAM
7) load scene. The CT atom will now collide with the CUA despite the rule we have set.
 
VAMFantasy said:
Hi! Your plugin doesn't work with CUAs. Only with natice VAM assets or shapes. After applying the plugin to asset and selecting atoms to ignore it works fine.... until you load the scene again. I've tested different CUAs and issue persists.
Steps to reproduce:
1) create CollisionTrigger atom and add the plugin to it
2) add any CUA atom that can collide
3) set the CT atom to ignore collisions with CUA
4) now the trigger should not activate when colliding with CUA
5) save scene
6) restart VAM
7) load scene. The CT atom will now collide with the CUA despite the rule we have set.
Click to expand...
Thanks for the report. Depending on the load order and the complexity of the asset, the asset and its colliders may not exist yet when the plugin initializes. I'd need to wait until the asset is ready, but this can lead to other problems.
Plus, if you do it the way you described, I'd also need to keep track of the atom type to see if some waiting is required.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom