My weld constraints keep disabling whenever I go in-game
1 Like
Does this issue happen even if you test in a new blank baseplate? If yes, then you might have a plugin installed that’s causing this issue to happen, otherwise a script inside of your game is messing with the constraints
It might also be the case that you’re experiencing some kind of instability if you’re creating the welds yourself during play-testing (after clicking Run, Play, or Play Here) although this is theoretical
its at random when all of my welds just disables. I’ve figured out how to fix it (replacing the welds) but I’m just confused as to why it happens at all. It has happened to me multiple times in the past.
3 Likes
this keeps happening to me, randomly my welds decide to get disabled (while in studio, editing), and when i publish the game they get published as disabled and everything falls apart, i dont have much plugins and im using literally 0 of them, this keeps happening on only 1 of my games for the past year, there is very few scripts that all ahve nothing to do with welds and are all coded by me.
3 Likes
I’ve been having the same issue, I had everything working and then I tested it later and it stopped working. For some reason the welds got disabled in studio, which I wouldn’t do, And then I enabled them and it worked in studio but not in play testing. Then I just read your comment and I deleted the welds and literally made the exact same new ones and it worked play testing. So weird
update: another game of mine (has nothing to with the other, also i now have even less plugins + my studio settings are the default) started doing this, welds randomly disable them while in studio, i believe this is a major engine bug and should be fixed immediately
Hi there. I wish to assist you more, but I need to see some pictures/videos to further help? It would help alot.
Thanks!
Having the same issue. Whenever I close studio and reopen it one of my weld constraints becomes disabled and I have to check “Enabled” again.
Edit: Deleting it and replacing it with a new one fixed the issue. Not sure why