Info
Studio Version: Version 0.652.0.6520764 (64bit)
⚠️ Note, when testing! ⚠️
This issue may be Hardware dependent, or depending on some Settings that control Performance within Roblox.- This issue may not occur on a Roblox Studio self-hosted server that is on an AMD CPU. This issue may occur on Intel. I don’t really know which hardware it doesn’t occur on. Mine was on a unadvanced Intel device.
-
This issue is most likely to occur on a Roblox Server however.
- So, best is to publish a game on Roblox and test it there, instead of debugging it in Roblox Studio.
A private message is associated with this bug report
Description
If two objects are not moving and in pure “IDLE”, but have their Collision Group’s collidable value changed, they don’t update unless other physics interact with the affected objects.
Re-production Steps
For instance, two boxes on top of each other in two different collision groups.
Box A and Box B, with the Collision Groups TestA and TestB, assigned corresponding to the letters.
- Box B is larger than Box A.
- Box A is placed ontop of Box B.
- With that setup, start the game.
- Box A will fall ontop of Box B, like intended.
- Run F8 in Studio to run as server.
- Use the Collision Group Editor to make TestA and TestB no longer collideable.
- Observe how Box A is STILL ontop of Box B.
- Create any Part and let it fall ontop of Box A or Box B.
- Observe how Box A now recognised that it shouldn’t collide with Box B anymore, and then proceeded to fall.
Expected Result
When a Collision Group has their properties altered, it should immediately apply. I expected that Box A will no longer collide with B, when being told to no longer collide.
Actual Result
TestA and TestB was set to no longer collide with eachother. Yet Box A did not fall unless Box A or B received interaction through physics.