Crash when trimming dense meshes with symmetry on. It happens quite frequently.
Not sure if it’s really the density though as the last crash was on a mesh with 590k and two layers.
I am on an IPad Pro M2
How much ram remaining?
Trim Boolean mode? What’s the detail value in the tool setting?
If it’s reliable you send me the file that triggers the crash.
No it’s not the RAM, plenty available. Seems it only happens when symmetry is enabled. Yes Boolean mode. I am not absolutely sure but I think the bigger the cutter portion the higher the chance of it crashing. So if I just cut a little corner its fine.I can send a file but the problem is it doesn’t happen eveytime.
I just need to replicate once, so it can be helpful.
And with the approximate way the cutting is done (lasso), if that’s relevant.
Also, what’s the shape/hole value in the trim menu, in case those are not at 100%.
Also, are on beta 1.98 or 1.97? Just so that I check the same version.
Ok let me try getting something useful for you
Here a file that crashes every time I try to try to split, regardless of symmetry or not.
However, only if I split a portion like in the image.
Damn, now I accidentally overwrote my project with this part. Is it possible to retrieve it?
Not possible.
If autosave is on, you can check in data/projects/ if there is an autosave.
I’m trying in 1.97, the store version but split works fine.
I see you have less RAM, it might be the issue, I’ll check what’s the memory spike.
I don’t understand what you mean, you are in the “open” sub menu so a save option doesn’t make sense.
If you want to browse the projects first, click the big thumbnail and select the correct project, a drop-down will appear.
Ok it’s indeed a RAM thing.
If I limit to 7GB ram available it crashes, but only if I put 300% in the detail split menu (it uses a bit more ram, enough to get past the threshold).
That’s why I asked about the detail value (plzzz answer my question).
But I know that you are using 300% since I now have the file, so it checks out.
Boolean is using lot of memory, maybe it could be improved but it’s not a bug. (I’m using a library so I don’t control everything for Boolean).
I see, forgive me my ignorance today. I now know what you meant with detail value. I only checked my memory which said 200MB.
Edit: for trim/split I have a workaround that should improve both performance and memory usage
I digged a little bit and there seems to be a weird performance issue with the underlying boolean library in some cases.
For example if you put yourself a 1M box and do the boolean it works much faster.
Or if you rotate the mesh a bit, the performance changes a lot, weird.
Internally, trim/split spawns a mesh and perform a boolean operation, but it seems the triangulation in the clip object causes performance issues.
I’ll report these issues, it’s fishy.
1 Like
Thanks!
Wait, now I see what happened…
I saved the file for you using "include only selected " when I realized I should use export instead of save. Then I kept working on my file and saved it not noticing that the “include only selected” was still checked.
Please make it uncheck automatically after saving. It’s so easy to miss this, resulting in overwriting the project file.
It’s a bug actually, the checkbox was supposed to be unchecked the moment the “save as” menu is closed.
Yeah it cost me 3 days of work 