n0f8r
February 22, 2025, 2:39am
1
Why does Creality Scan software keep crashing on attempting to create the mesh?
The error message is very generic, and pops up almost instantly on some scans when I try to create the mesh. It’s not happening on all scans, only some. I’ve only used the software for a few hours so I haven’t noticed any pattern yet. But when a scan refuses to mesh, it always refuses to mesh. I can quit and restart, and try to create the mesh - but that project will always crash immediately with the same error.
Could it be connected to the size of the point cloud? are there memory settings anywhere I can increase?
I was using the maximum 0.02mm resolution on the Optimisation settings before meshing, when I reduced the resolution to 0.05mm meshing worked.
Note my PC is a Unit - 128gb memory, RTX 4090, and 16 core Ryzen 5950 - so it’s certainly not resource constrained.
The same thing is happening to me today
n0f8r:
Why does Creality Scan software keep crashing on attempting to create the mesh?
The error message is very generic, and pops up almost instantly on some scans when I try to create the mesh. It’s not happening on all scans, only some. I’ve only used the software for a few hours so I haven’t noticed any pattern yet. But when a scan refuses to mesh, it always refuses to mesh. I can quit and restart, and try to create the mesh - but that project will always crash immediately with the same error.
Could it be connected to the size of the point cloud? are there memory settings anywhere I can increase?
If you scan an object as large as a DSLR camera, the resolution of 0.05 is the operating limit, and the smoother should be 0.1.
Gfnord
April 8, 2025, 8:09pm
4
Same error here.
Is there a limit of cloudpoint number the software can handle to create the mesh?
Here are the last lines of the logfile
[2025-04-08 13:38:55.144735][INFO ][46704][::0] send process msg id : OB_SCAN_MESSAGE_ID_PROJECT_IMPORT_SUCCESS
[2025-04-08 13:38:55.144735][INFO ][46704][::0] b p msg s
[2025-04-08 13:38:55.144735][INFO ][46704][::0] a p msg s
[2025-04-08 13:38:55.144735][INFO ][38612][::0] obscan_session_get_session_const_data
[2025-04-08 13:38:55.144735][INFO ][38612][::0] get session const data finished !
[2025-04-08 13:39:50.144790][INFO ][45260][::0] obscan_session_meshlization
[2025-04-08 13:39:50.144790][INFO ][40624][::0] mesh progress 0.000000
[2025-04-08 13:39:50.144790][INFO ][40624][::0] start combination meshlization !
[2025-04-08 13:39:50.144790][INFO ][40624][::0] voxel size: 0.050000
[2025-04-08 13:39:50.144790][INFO ][40624][::0] fill_hole true
[2025-04-08 13:39:50.144790][INFO ][40624][::0] is_closed false
[2025-04-08 13:39:50.144790][INFO ][40624][::0] smooth_level 0
[2025-04-08 13:39:50.144790][INFO ][40624][::0] final_triangle_num 2000000
[2025-04-08 13:39:50.144790][INFO ][40624][::0] mesh progress 0.010000
Gfnord
April 8, 2025, 9:25pm
5
From where did you take that? How can you be sure the max resolution for a not large object as a DSLR camera is 0.05 and smoother 0.1?
I’m fancing the same problem here, looks if I capture too much details the software crashes even with lots of resources (CPU/RAM/Disk) available.