The reason why I suspect the bug to be affecting HingeConstraint is because it is how the train bogie/wheels/truck is attached to the body. In my games, they are attached to a “base” part, which is welded to the rest of the body. Upon observations, this base part and the body are both gone from the game. It’s either deleting or getting glitched so fast into a region that causes it to delete as the doors attached to the body via PrismaticConstraint are not deleted. Instead, they remain but fall into the void as they are now attached to nothing.
Very interesting finding, thanks for the update! Couple questions:
For the post you made on July 14th, in which experience did you observe the issue?
For the post you made on July 15th, did you experience this while running in studio, or while in an experience? If you were in an experience, which was it?
In the meantime, I’m going to disable my feature on every experience you listed in this thread. Please continue to report your findings, this will be very useful for us.
Ah, quick question: if you are disabling a feature in those games but I am publishing another game to it that I have not mentioned (it is a game where development updates are first made before being published to the main game), will it revert the disabled feature? I may have forgotten to account for that. I’ll link the games below:
Good question. We can only disable features for specific place IDs (the long number near the end of each game url), so if those experiences have different place IDs, the feature will not be disabled for them.
I think we can just consider the 10 experiences that you previously listed in this thread with these place IDs: 6214255393, 7027922660, 9133022367, 12395337537, 5177561496, 6927810595, 82031223, 4119848102, 6458393580, 10063918929, and 6510504476. Please continue reporting crashes on those experiences.
It currently seems that my feature may not be the culprit since you’re still seeing issues for experiences that I disabled the feature.
Also, would it be possible to DM me an rbxl file for either PTA Subway: Callaghan-Madison Lines or PTA Subway: Fifth Av Lines?
Sorry to hear the file is too big, would it be possible to send an rbxl with just a working train and some section of track?
Seems like my feature is likely not the culprit, since you are continuing to see the issue after I disabled the feature. If we have a working example that we can run locally, we’ll be able to step through the debugger to see exactly what’s going on.
An update: the bug seems to affect BallSocketConstraint as well? We’re currently figuring out ways to fix/avoid the bug, but nothing seems to be working. We also tried changing the CustomPhysicalProperties as directed and it still seems to be happening.
Unfortunately, it might still be occurring, though I’m not sure about the circumstances this time as this is not in one of our games.
The only information I know is that the train’s body was already gone by the time it was seen and that the wheels are connected by BallSocketConstraint (and this bug also affected that if I remember correctly as a previous test was done with them replacing the HingeConstraint).
See the screenshot attached below:
