Importing a new mesh into a MeshPart now creates a new part. This is unexpected and unwanted. As a vehicle developer, to make a new vehicle I clone an existing vehicle, place it at the origin, and load new MeshParts into the vehicle, as the vehicles all have the same number of parts with the same properties. Now that importing creates a new part, I have to take the extra step to copy the asset ID back into the existing part, which annoys me.
Not only this, but if I select “no” to “the mesh contains location data do you want to move the part to the location?” the position of the new part is all sorts of strange.
Repro:
insert a MeshPart into workspace
load a file into the MeshPart
select “no” to the location prompt
inspect the new part and unusual position
Outcome: new MeshPart is created with the mesh specified at a different CFrame than the original MeshPart, and in Workspace
Expected outcome: when the new MeshPart is loaded it inherits all the properties of the part previously (except those related to CFrame [if the user chose to reposition the mesh] and size).
Having this same issue, it completely haults me from organizing before importing. Usually I do the following:
Create a MeshPart in the workspace.
Group it
Rename the model to what the whole structure is going to consist of (Lets say a Door for instance) and then name the MeshPart(s) to what the model is going to entail(Ex: Door handle, Lock, Frame…)
Import the models.
Now I can no longer do this and instead have to import each mesh first THEN name it, change the material of it, group it, etc. Like the OP states, it doesn’t use the MeshPart you’re loading your meshes to since it creates an entirely new MeshPart in the workspace when you upload a mesh instead of using the existing one.
In addition to all of this, here is the result of what happens when you click “No.” after being asked to use location data.
