I’m not here to have a convo on whos right with a reply war so i’m just gonna say you win, have a great day.
All good at least you got it working. Also my version works fine. As I said tested.
Couldn’t get it working, as I don’t feel the need to parent the entire car-script or use multiple which i deem unnecessary, though I hope a bug report is done about it at some point as I can’t make one myself.
The Solution was that it was a bug and that’s all I really got.
What are you talking about … you had the script in the wrong place to call parent like that. That was your error.
What’s the chance you have the following properties of the parts in the car set as so:
Because CanQuery must be checked in order for it to accept clicks
Though obviously you can click it beforehand, don’t know if something else may be disabling everything
CanQuery is always on regardless, it wouldn’t have been clickable when it was visible if not.
Found out that the problem was CanCollide, which when the model goes invisible and has CanCollide off the ClickDetector will stop functioning, is this expected behavior?
I would’ve expected to it to work, though I guess not… maybe I’m rusty
You may have just found a bug, this isn’t supposed to be happening.
Though if you wouldn’t mind posting about it, I genuinely cannot access #bug-reports and I’m unsure how to access it.
One thing to note it happens inside Studio and In-game which is notable for a bug-report.
I just want to point out this may also just be from the fact the clickdetector is a child of the model and not a part.
Conventionally, you should have a clickdetector childed to a part.
Expected behavior is model should be 100% clickable by every part if ClickDetector is present.
This may have been an error on roblox’s part due to forgetting to use canquery and not cancollide when it released originally in 2021.
Bug Report was replied to, this might be fixed soon.
1 Like
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.