RE: LDraw part 118091p looks fine in Part Designer but imports into Studio with extra geo
2026-08-17, 5:33
2026-08-17, 5:33
Hi,
This is a general answer, I didn’t check that exact part and its components.
When you import a file in PartDesigner, it’ll first look for subfiles/subparts in the same folder (or a subfolder named ‘s’ when the files need to be in such a subfolder).
Then, when you export toward Studio, PD checks that the files that are needed are already known to Studio. If not, they are inlined in the exported .dat. Otherwise, it assumes they are the same files and it’s Studio’s stock files that will be used.
So, if you downloaded and extracted the Zip from the tracker, PD loaded the ‘local’ files… but if some of these files/subparts are already in Studio and they are older and different there, then you get surprises once in Studio.
One solution is to rename the local files and edit the main/calling file(s) accordingly to force PD to use these in the export.
This is a general answer, I didn’t check that exact part and its components.
When you import a file in PartDesigner, it’ll first look for subfiles/subparts in the same folder (or a subfolder named ‘s’ when the files need to be in such a subfolder).
Then, when you export toward Studio, PD checks that the files that are needed are already known to Studio. If not, they are inlined in the exported .dat. Otherwise, it assumes they are the same files and it’s Studio’s stock files that will be used.
So, if you downloaded and extracted the Zip from the tracker, PD loaded the ‘local’ files… but if some of these files/subparts are already in Studio and they are older and different there, then you get surprises once in Studio.
One solution is to rename the local files and edit the main/calling file(s) accordingly to force PD to use these in the export.