Hi there,
I'm working 3D model of coral colonies, and I use point clouds in ply format as well as meshes in obj.
I was working on projects with several obj files opened in on CloudCompare v2.12 (Windows 64bit, 128GB RAM)
Then I switch to another computer (Windows 64bit, 64GB RAM) which have v.2.13.2 installed, and I can't open any obj file (no matter the size of the file). Cloud compare doesn't send any error or warning message, just don't open the file and then crash
OBJ files are opened well in other software such as Meshlab.
Do you have an idea of the problem origin ? And how to fix it ?
Thank you in advance,
Théo
Opening OBJ file
-
- Posts: 2
- Joined: Tue Apr 22, 2025 2:42 pm
Re: Opening OBJ file
I may have a begining of an explainatation :
Cloud compare doesn't display this message "[ccGLWindow] Succesfully initialized PBO for faster depth picking" at its starting on the computer where i can't open OBJ files, while it is diplayed on other computer where i can open OBJ files
I have currently no idea of what coud be the meaning of this, but maybe it is link to the issue
Cloud compare doesn't display this message "[ccGLWindow] Succesfully initialized PBO for faster depth picking" at its starting on the computer where i can't open OBJ files, while it is diplayed on other computer where i can open OBJ files
I have currently no idea of what coud be the meaning of this, but maybe it is link to the issue
Re: Opening OBJ file
In this case, can you uncheck the option 'Try to load clouds on GPU for faster display' (in the 'Display > Display settings' dialog) to see if it helps?
Daniel, CloudCompare admin
-
- Posts: 1
- Joined: Fri May 09, 2025 6:19 pm
Re: Opening OBJ file
Hi,
I’ve seen similar issues when switching between different versions of CloudCompare. Sometimes it’s related to how certain plugins or file handlers behave across versions. A few things to try:
– Make sure you’re not opening the OBJ from a network drive — try moving it to a local disk.
– Check if the OBJ file has any non-standard elements (like MTL references or embedded textures) that might trip up the new version.
– Try re-saving the file from Meshlab or Blender with minimal metadata.
If none of that works, it might be worth downgrading to v2.12 on the second machine to see if compatibility is the root cause.
I’ve seen similar issues when switching between different versions of CloudCompare. Sometimes it’s related to how certain plugins or file handlers behave across versions. A few things to try:
– Make sure you’re not opening the OBJ from a network drive — try moving it to a local disk.
– Check if the OBJ file has any non-standard elements (like MTL references or embedded textures) that might trip up the new version.
– Try re-saving the file from Meshlab or Blender with minimal metadata.
If none of that works, it might be worth downgrading to v2.12 on the second machine to see if compatibility is the root cause.
Hi there! I'm Zu. It's a pleasure to meet you.