Model not being removed when falling below FallenPartsDestroyHeight

Bug Reports Engine Bugs
,
1

If a model falls into the void, under certain conditions, it does not get parented to nil. I’m attaching a file that shows this. This is an issue with the RootPriority - if the RootPriority of the Distributor part is set to 127, it properly destroys

If I had to guess, the parts named “Wheel” are internally setting the RootPriority to take precedence which somehow affects the chain when attempting to destroy the base model

I had it setup where changing the RootPriority would make it properly remove but it doesn’t seem to be the case with the file here

BugReportFile.rbxl (50.0 KB)

Expected behavior

I expect for models to be parented to nil when all parts are removed

2

I see what happens here. The parts are all removed but a single folder is left inside the model making it non-empty.

A non-empty model will be removed/parented to nil.

We’ll investigate.

3 Likes
3

This is still an issue. Is there any update for this?

1 Like
4

Also encountering this issue. Very undesirable. Is there any updates on this?

Seems to exclusively happen when folders with instances are present inside models. Does not seem to be an issue when those folders are models though.

Edit: I see what’s happening, the instances outside of the nested folder are destroying first, and since there’s still children inside the nested folders it doesn’t destroy the whole model. Then, when the instances inside the folders destroy, they don’t seem to check if their ancestor is empty which doesn’t destroy the model.

1 Like