Page 1 of 1

-DROP_GLOBAL_SHIFT not working?

Posted: Tue Nov 29, 2016 9:19 am
by Haax
Hello
If i run the line below in a cmd window, I get a .ply in the same coordinates as the original .dxf. Should'nt the exported .ply be in low/moved coordinates then?
If I remove the -DROP_GLOBAL_SHIFT flag I get the exact same result, does not seem like the -DROP_GLOBAL_SHIFT flag do anything at all.

-M_EXPORT_FMT PLY -PLY_EXPORT_FMT BINARY_LE -O -GLOBAL_SHIFT -442000 -6199000 0 myfile.dxf -DROP_GLOBAL_SHIFT -NO_TIMESTAMP -SAVE_MESHES

Regards
/Haax

Re: -DROP_GLOBAL_SHIFT not working?

Posted: Tue Nov 29, 2016 9:28 am
by daniel
Ha! I think I know what's going on. Let me check something and I'll get back to you.

Re: -DROP_GLOBAL_SHIFT not working?

Posted: Tue Nov 29, 2016 10:46 am
by daniel
No, it was not what I thought... It works on my side.

Can you maybe share the DXF file with me? (cloudcompare [at] danielgm.net)

Re: -DROP_GLOBAL_SHIFT not working?

Posted: Tue Nov 29, 2016 11:01 am
by Haax
Thank's for your quick help
You've got an e-mail now

And by the way, thank's for the hard work on a really great program.

/Haax

Re: -DROP_GLOBAL_SHIFT not working?

Posted: Tue Nov 29, 2016 12:21 pm
by daniel
Ok the culprit was the DXF loader (which was wrongly locking the vertices) and another internal test that was too restrictive when handling locked vertices...

I'll try to update the online version soon. I'll keep you updated.

Re: -DROP_GLOBAL_SHIFT not working?

Posted: Tue Nov 29, 2016 1:17 pm
by daniel
Ok the online 2.8 beta has just been updated. Thanks for the feedback.

Re: -DROP_GLOBAL_SHIFT not working?

Posted: Tue Nov 29, 2016 1:30 pm
by Haax
Wow, quick work, will try it right away and see if it works.

Re: -DROP_GLOBAL_SHIFT not working?

Posted: Tue Nov 29, 2016 1:49 pm
by Haax
Thank's Daniel

Worked as expected.

One strange thing though, i could not just use the dxf-name any longer. Had to put the whole path in.

Regards
/Haax

Re: -DROP_GLOBAL_SHIFT not working?

Posted: Tue Nov 29, 2016 1:57 pm
by daniel
Yes, I think that there has been a change in the default path (it was necessary for the Mac version I believe).