In studio make a part, group it as a model, insert a ProximityPrompt into the model beside the part.
Play the game, the prompt doesn’t work. If you move the prompt to the part, it immediately works.
Expected behavior
It is documented that proximity prompts should work under Models.
We have pivots now, this should be able to work. That it doesn’t work is very confusing and unexpected. There is further no documentation about this.
I noticed that this only works if you assign a part as the PrimaryPart.
Well, yeah… theres no object for the prompt to connect to unless as @Dyllon3761 said, you set a PrimaryPart on the model. I mean, it’s either an actual bug or the documentation just needs to be fixed.
See above. It’s good that primary part works at least, but this shouldn’t need a primary part.
Aren’t ProximityPrompts BillboardGuis? Do they render when parented to a Model with no PrimaryPart?
Thanks for the report! Just to confirm, we have a ticket filed in our internal database for this issue.
Thanks for bringing this up. I looked into it, and using a Model for the parent of a ProximityPrompt does require PrimaryPart to be set. I see that this info is missing from the documentation - we will update that.
The decision to not use Pivot at the moment is a performance consideration. In some cases, that needs to traverse through all child parts of the model in order to calculate a bounding box and find a center.
We may decide to relax this requirement in the future, but at the moment this is working as intended - you will need to set PrimaryPart to make it work. Thanks!
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.