Player unable to stand on part

Help and Feedback Scripting Support
#1

Can’t seem to find anything about this online, but it seems like there’s some really weird physics going on between the player and the part I’m trying to stand on.
Is there any general reasons why this could be happening I have no idea what could be the cause.

The floor part is placed by the player in a furniture placement system I had created, the part with cancollide on is a meshpart I had imported from blender, but that doesn’t seem to matter as normal parts also fling the player.

1 Like
#2

Quite a vague issue, I have a few questions to help narrow it down:

  1. Are you using a custom character system?
  2. Just to clarify, the part in the video is a meshpart imported from blender?
1 Like
#3

  1. I’m not using a custom character system, however, I am using a default dummy starter character, testing it again using the players own avatar has the same results.

  2. As I’ve mentioned before, yes the meshpart is imported from blender. however, testing it with a normal part gives the same results.

Adding onto this, when I move the part to workspace via studio and not through the furniture placement system in game, it works fine and I can stand on it.

#4

It may be helpful to check the actual geometry of the meshpart by enabling this option in studio
image
Send a screenshot of the geometry and I’ll take a look.
Or just share the meshpart.

If that doesn’t work, please answer these questions related to your furniture system:

  1. Is the part placed only on the client-side or on the server-side?
  2. What method do you use to position the part? (sharing the code that positions the part would be helpful)
  3. Does your furniture system have anything related to velocity?
#5

Geometry looks completely fine to me.

  1. The part is being placed on the client-side
  2. On player click, the part is cloned then anchored to its place, the positioning is done through raycasting whenever the player moves their mouse.
#6

This may be the issue, try having the part placed on the server rather than the client.

#7

In order to do this I would have to completely overhaul the system and it’s interaction with other scripts.

I’d prefer not to and I don’t see how this could be the problem.

#8

If you check the collisions on the server, it would completely ignore this part as it doesnt replicate.

#9

Client-only objects can have weird physics behavior since there’s a disagreement with the server and client (well at least in my experience).

If that’s not an option, then try using a regular part? If that’s not an option either or does not fix the issue then unfortunately I’m out of ideas.

Goodluck!

Edit:
In normal circumstances, objects made on the client should be perfectly fine, I’m not sure about meshparts. My knowledge about physics replication may be outdated, but I’m pretty sure there’s a solution to this.