Error opening bin files in 2.6.2

If you are allergic to bug trackers, you can post here any remarks, issues and potential bugs you encounter
Post Reply
aknight0
Posts: 5
Joined: Mon Apr 14, 2014 5:59 pm

Error opening bin files in 2.6.2

Post by aknight0 »

I have several very large bin files (> 5GB) that I've been working with in CC. I recently updated to 2.6.2, and found that I could no longer open my files. Either cloud compare would crash, or it would return an error saying that the file may be corrupted. I downgraded to 2.6.1, and the files open just fine. Any ideas why this would happen?
daniel
Site Admin
Posts: 7707
Joined: Wed Oct 13, 2010 7:34 am
Location: Grenoble, France
Contact:

Re: Error opening bin files in 2.6.2

Post by daniel »

Indeed it was a bug with Qt if I recall properly. This has been fixed in the 2.6.3 beta version. Can you try it?
Daniel, CloudCompare admin
aknight0
Posts: 5
Joined: Mon Apr 14, 2014 5:59 pm

Re: Error opening bin files in 2.6.2

Post by aknight0 »

That fixed it. Thanks for the quick reply!
adririquelme
Posts: 13
Joined: Wed Mar 02, 2016 2:55 pm

Re: Error opening bin files in 2.6.2

Post by adririquelme »

Dear all,

Since last update to 2.7.0 I am getting errors when opening large .bin files (close to 10GB)

[14:08:17] [BIN] Version 4.3 (coords: float / scalar: float)
[14:09:28] File seems to be corrupted
[14:09:28] An error occurred while loading '2016_Villajoyosa_Analisis': see console

This was not happening in previous version.
daniel
Site Admin
Posts: 7707
Joined: Wed Oct 13, 2010 7:34 am
Location: Grenoble, France
Contact:

Re: Error opening bin files in 2.6.2

Post by daniel »

Or maybe the issue is that the file format has changed and the readers are not handling the old files correctly...

What was stored in this file? Only point clouds?
Daniel, CloudCompare admin
adririquelme
Posts: 13
Joined: Wed Mar 02, 2016 2:55 pm

Re: Error opening bin files in 2.6.2

Post by adririquelme »

Yes, only point clouds.

When using 2.6.2 I can load the .bin, but when 2.7 I found this error
Post Reply