KSP using the same model for two parts??

[NermNermNerm]

Yesterday I finally got my first ever part in a state that I was reasonably happy with and incorporated it into my mod!  Yay!  So I made a second one!  And that went well too...

But now I notice something I can't explain:  my first part is now using the model from the second.

Now, you can imagine there are a variety of ways I could have boneheaded that.  But I've checked it every which way, and it's just not so.  My .cfg's are pointing at different .mu's, and git assures me I haven't inadvertently overwritten my first .mu.

Idunno - is there some kind of identifier baked in to the .file exported by Unity?  I am using the same unity project for both parts.

I also notice that when I look at the part-info page, the preview pic of the parts both seem to shimmy...  Like it's actually drawing both models, one then the other.

[NermNermNerm]

Jacked with it until it worked.

I think my mistake was in copying some other parts that did 'mesh = blah' rather than 'MODEL { model = blah }'.  My guess is that 'mesh = blah' doesn't do anything, really, and if KSP doesn't see a MODEL object, it looks for a .mu file in the same folder as the .cfg file and uses the first one it finds.

The shimmering I reported  is because I fail at smoothing, and one of my cylinders is actually still an n-gon, and as the image is rotated in the preview window, the model gets one pixel wider a few times a second.

[Electrocutor]

mesh= does work, but is legacy and mutually exclusive with MODEL{}.