I was able to get this working by looking through output_log, thanks for the suggestions. This was a result of my using KSP MOD Admin to install the mod. It chose not to maintain the folder structure in the zip file, ignoring the top-level NehemiahInc folder and instead installing all of the sub folders directly into Gamedata. When KSP tried loading the experiments, it was attempting to clone a model with a absolute path of /NehemiahInc/... which of course, failed. I can only assume it did so to support it's conflict resolution; If you have multiple part.cfg files, for instance, how else could you tell if they conflicted other that by the path, which would need to assume that they would all have roughly the same depth. (Well, I guess you could look inside the .cfgs for various keys. would be easier if there was versioning info in there. I guess that's what CKAN is doing with metadata. Now I'm way off on a tangent) Regardless, I was able to override this behavior in KSP MOD Admin by overriding the automatic destination of the NehemiahInc folder (right click, set destination, Gamedata). Maybe it's time to switch to CKAN, there seems to be a fair amount of momentum in that direction. Thanks again, I look forward to running these experiments.