Hello, I‘ve been using Nomad on the the 2024 ipad since last September. The Performance was better then on my privious iPad from 2021. Both devices have the same ram and memory. Since 2-3 months, while voxel remeshing, the new iPad with the m4 chip performs worse then the older iPad with the M1 chip. I still have the old iPad and compared the two with the same settings and models.
I went to apple, they checked my iPad and said: the hardware is fine, maybe the app doesn’t work so good with the new m4 chip and needs software adjustment.
Could it be, that there was an update around April this year that does not work on the new iPad chip so good when remeshing?
Best regards
Gero
No.
Same version of the app?
Maybe show a screen with actual number…
You can display the log window with the number (debug menu → logs)
Thanks for answering Stephomi, both apps are version 2.2.
I send you two pictures of the log menu, one while remeshing at about 1333 (that works) and the second right before crashing at a resolution about 1600.
The older iPad can easily go over 2000.
After a crash the log menu resets.
1 Like
Wait… you were talking about performance difference between m chips and now it’s about crashing.
The crash is a know issue that will happen starting around >~1200 resolution, it can happen anywhere.
Yes, but with the older m 1 chip voxel remesh with a resolution of around 2000 is no problem. Until around April I was able to voxel remesh with up to 3000 on the m4 chip. The m1 still performes as it used to, no changes. The crashes on the m4 chip happen now with only half the resolution then 3 months ago, that definitely has changed.
I just said that “it can happen anywhere”. It’s random, underministic.
Also performance is for speed comparison, here it’s a bug.
I know, it’s over the recommended limit. Since I use the app daily and I am very happy I would like to keep using it the way I did the last 3 years. Voxel remesh crashes have really gotten worse. Is there any chance I could install the app version before April (maybe 1.97)? I would be eager to do so. That way I would know if the new version is the problem.
Jeez, I just told you 2 times there is a bug, just wait the next like update like everyone else.
There are bugs on every release since 3 years…
No you cannot go back and even if there was an option for it, I would disable it.
Alright, thank you