"with the blMilWomLo.obj of V2 you get an "Range check Error" I remember with one pcf, one of Arduino's actually, the name of the .obj had changed (may have just been the case of the letters). Changing it to match (on a copy of course) fixed the problem. I'm not sure if that would generate the range check error or something else though. In another case, the geometry hadn't changed but a comment line at the beginning of the .obj had changed. Putting in the proper comment fixed it. Of course the 3rd case is if the geometry actually did change in which case, you're SOL without the correct version.

"Democracy is a pathetic belief in the collective wisdom of individual ignorance." - H. L. Mencken