I’ve noticed a bug where a ProximityPrompt stays visible in the world even after it’s destroyed. When this happens, it can’t be interacted with or triggered, but it just sits there stuck at the world origin (0, 0, 0). It usually happens after the object that had the ProximityPrompt is removed, and it looks like the prompt’s UI doesn’t clean up properly, leaving a sort of “ghost” prompt on the screen. This only started happening after I turned on StreamingEnabled, it never happened before.
3 Likes
Thanks for the report. I’m not able to reproduce this at the moment. When a ProximityPrompt is stuck at the origin, this is usually an indication that its parent isn’t valid. For example, the prompt could be parented to a Folder, or a Model with no PrimaryPart set. I wonder if the objects streaming out cause the hierarchy to be in a state like this. If possible, it would be helpful to have a minimal repro file. Or if you get this to happen in Studio, search for the ProximityPrompt in the explorer view and see if it’s there with an invalid parent.