Model sometimes breaks.

TobiasBruh

@When I’m working a model for a long amount of time, if I save and exit then renter, the mesh will entirely break, ruining all my layers.
ive also had issues with the symmetry tool, where some parts aren’t symmetrical despite keeping the tool on the entire time, and upon talking to other people, this has been an issue unresolved for years. Paid 10$ for this app man.

JavierEdo

Hi TobiasBruh so sorry about that.

There was a mixup with sculpt layers introduced with the recent geometry format changes that was causing this issue, disabled layers were being inverted on scene load.

This issue has been fixed and a new version has been submitted and is awaiting Apple's approval, it should be out in the next day or so.

Regarding symmetry, due to precision loss in consecutive operations, symmetry can go out of whack, which is why all (mobile/desktop) apps tend to have a way to make a mesh symmetrical again if this happens.

In forger there are two ways of doing this:

Using "Reapply Symmetry"
Using "Make Symmetrical..."

Both approaches are shown in the Symmetry videotutorial 😉

2:56 Reapply Symmetry
3:16 Make Symmetrical

TobiasBruh

Thank you! Good to hear.

JavierEdo

TobiasBruh quick update, although the app was submitted earlier Today, there seems to be an ongoing issue with app submissions on Apple's end, so it may take a day or two more to process until they fix it.

Once "App Store Connect App Processing" changes to green, it will start the countdown to approval, until then it's waiting in the previous step.

https://developer.apple.com/system-status/

this is unfortunately on Apple's side of the fence so we can only wait. Developers have been notifying about it for hours until Apple started looking at the issue: https://developer.apple.com/forums/thread/671373

In the meantime please note that since the issue happens with disabled layers, you can work around it by enabling layers before saving and when re-opening the scene disable them, it's annoying but should do the trick for now 😉

JavierEdo

I failed to mention that this fix went out on Friday with v1.7.14.