You can see the original character and the ragdoll existing at the same time. :Destroy() is called the same frame a ragdoll is created, but the character model visually stays there for a frame or two.
The game is FilteringEnabled - someone did mention that these sort of problems might be FE related, opposed to non-FE games.
I’m trying to find a way to fix this graphical bug.
Maybe you could just turn the character invisible for a quick fix.
Are you locally destroying it?
If not then it could be server latency.
Locally
Mind showing us some code? It could make a difference.
I had issues with character graphics not updating until I stopped using humanoids in shard seekers.
It’s too complex and modular to show an accurate example, sorry
sloomingbla was having a similar issue where objects wouldn’t disappear. In his case it was parts not being hidden after their transparency property was set to 1 and it was because ROBLOX had so much rendering to update that it got congested – your game could be having issues where too much rendering/unloading is going on which is causing it to take longer than normal for the renderer to make the character disappear visually.
It could always be different here, but usually when someone says that, they’re not trying hard enough to make a bare-bones repro. 99.99% of bugs can either be solved in the process of making a bare-bones repro or you can find a ROBLOX bug with definitive repro steps, making it a lot easier for the ROBLOX engineers to track down and patch. Try playing on a template map with only a couple of parts and keep an eye on the Shift+F2 panel (namely the Draw (total), Delta, and Scheduler Render properties) and look for any abnormal values.
I’d rather leave it that way then. hue hue hue.
