I'm probably doing something wrong... I've remapped Michaels body suit with UV mapper... and that works perfectly... I then replace the old bodysuit geometry with the new from mapper... and that works perfectly... So now I want to share some of my new files, and I have to share the remapped bodysuit obj. file... so I use Objaction Mover right? The seed file would be the original geometry and using mover I create a new .pcf file... and that works perfectly... I can even decode it just fine... but then I had some one test it... and they get a "Range Check Error" The same thing happens when the second party uses Mover to make a pcf on his side... he can open it, but I get the same error. Any help? Thanks, Doug

I came, I rendered, I'm still broke.

If you didn't rework the geometry, you can probably use UVMapper to export a UVS file. That is an encoded file similar to a Mover PCF, and the original is needed to decode.

Have you altered your original body suit .obj at any point? Has your tester altered his/hers? Also, if all you did was change the mapping or materials or grouping, and haven't changed the shape of the actual geometry, you may want to try a UVMapper .uvs file instead of a .pcf. Smaller file size for one thing.

Hey, nice answer wyrwulf ;)

Thanks JKeller and wyrwulf! UVMapper it is! But any idea why Mover wouldnt work? I hadnt altered the file in any way except just to remap it. Doug

I came, I rendered, I'm still broke.

It sounds like a Mike problem that Maz should be told about.

I've just spotted this thread. Nobody told me about the problem!!!!! It's probably caused because the computer doing the decoding is set up to use a comma (,) as its decimal separator rather than a full stop or period (.) I don't know why this should be, it just seems to be one of life's little oddities.

We think it was zip causing the problem... as if it was crunching it just too much... without any compression applied, it worked fine. Doug

I came, I rendered, I'm still broke.