Yeah, I know you don't read the cfg, but you use the UrlConfig objects from the game, and the path defined on them is derived from the name of the config. The code that loads models tries to find the location of the config so it can locate the models. It looks at the path defined on the UrlConfig object, and expects there to be a "/part/" element in that path, when instead the game actually uses "/<nameofconfig>/". Because the code is expecting "/part/", it fails to manipulate the path correctly, causing it to look in the wrong location for the model files. In the case I presented to you (with ExLaunchpads's hexcans), the part config was named "Huge.cfg", unlike the code expects, and the model was named "model.mu", which is the standard, as well as what the mod looks for by default. At least, that's what I got from reading the code.