Error reading .e57

[BeHo]

I can not open some e57-files created from cyclon register 360 or autodesk recap in V 2.11.3.
Same files work fine in V 2.10.2 . Any Suggestions ?

[daniel]

What's the error? Can you share a sample file with me? (admin [at] cloudcompare.org)

[BeHo]

Hallo Daniel, thank you for your fast response.
I send you a screenshot from the error message.
The file with this behaviour is over 700 Mb (500 as zip).
I think this won´t work by email.
The original e57-file comes from leica cyclone register 360 (BLK edition).
I can import this file in autodesk recap pro. I can open it in CC 2.10.2.
I have exported the pointcloud from recap to another e57-file, without doing any manipulation in the pointcloud.
From this file i get the same error in CC 2.11.3.
After saving the file in CC 2.10.2 under new name, i can open it in CC 2.11.3.
I have cut out a piece of the pointcloud in recap and exported it to an e57-file. This part i can also open in CC 2.11.3.
The error seems only to come up with original file.
If you show me a way to send you the file , i have no problem sharing it.

error_message.PNG (89.55 KiB) Viewed 4219 times

[daniel]

Do you have a Google Drive account maybe (or similar solution)?

Otherwise services like Wetransfer will work as well (it's free up to 2Gb).

[daniel]

Thanks for the file.

When trying to load the file with 2.12, I get a "checksum" error. This means that the content of the file is not what it's supposed to be.

And when I tried to remove the checksum check, I ended on another error (a corrupted packet, as what could be expected).

I'll now have to understand if it comes from the new version of the E57 library, or if it comes from the file.

[daniel]

Digging a little bit more, I have the same 'checksum' error with the 2.10.2 version (on Windows).

[Hagaeus Bygghantverk]

I have this exact same problem with an E57 from Cyclone. Is there any hope for a solution?

[daniel]

See https://github.com/CloudCompare/CloudCo ... -944261289, that might help.

[Hagaeus Bygghantverk]

It seems to be an issue in the stable release. In the Alpha I can open it.