Pixels Deconstructing Down Multiple Layers

[Mroachfo96]

I seriously need help! 
I’ve done my editing on the iPad version for years, and I’ve never experienced this before. While editing, it has started destroying whole blocks of pixels down to the last layer, sometimes, even deleting the last layer too. When I try to go back in the history, IT DESTROYS MORE. It gets worse the more I go back, but I can’t stop it in the current point in its history. I sat for 4 hours and had been thrown back at least two-hours in progress.

Does this happen to anyone else? I need help to fix this ASAP. Do I have to switch some setting?

[Paul Mudditt]

8 hours ago, Mroachfo96 said:

I seriously need help! 
I’ve done my editing on the iPad version for years, and I’ve never experienced this before. While editing, it has started destroying whole blocks of pixels down to the last layer, sometimes, even deleting the last layer too. When I try to go back in the history, IT DESTROYS MORE. It gets worse the more I go back, but I can’t stop it in the current point in its history. I sat for 4 hours and had been thrown back at least two-hours in progress.

Does this happen to anyone else? I need help to fix this ASAP. Do I have to switch some setting?

Which iPad are you using, I have had to upgrade from my original 9.7” iPad Pro (2GB RAM) to the latest 11” iPad Pro (8 GB RAM) and the performance of Affinity is back to where it used to be with V1.7. I think it is inevitable as users clamor for more features, our hardware starts to creak.

However always worth closing all open apps and doing a Forced Restart (press home plus power button continuously until you see the Apple logo or on devices without a home button, press volume up then volume down then press and hold power button until you see the Apple logo.)

[Mroachfo96]

25 minutes ago, Paul Mudditt said:

Which iPad are you using, I have had to upgrade from my original 9.7” iPad Pro (2GB RAM) to the latest 11” iPad Pro (8 GB RAM) and the performance of Affinity is back to where it used to be with V1.7. I think it is inevitable as users clamor for more features, our hardware starts to creak.

However always worth closing all open apps and doing a Forced Restart (press home plus power button continuously until you see the Apple logo or on devices without a home button, press volume up then volume down the press and hold power button until you see the Apple logo.)

I have an iPad Pro 10.5 inch 2017 model I believe. I guess I’ll just have to upgrade my iPad so I can still carry the same work load. 
 

I’ve removed and reinstalled it the program before on my iPad, so it may just be time.

Thank you! 

[Mroachfo96]

12 hours ago, Paul Mudditt said:

Which iPad are you using, I have had to upgrade from my original 9.7” iPad Pro (2GB RAM) to the latest 11” iPad Pro (8 GB RAM) and the performance of Affinity is back to where it used to be with V1.7. I think it is inevitable as users clamor for more features, our hardware starts to creak.

However always worth closing all open apps and doing a Forced Restart (press home plus power button continuously until you see the Apple logo or on devices without a home button, press volume up then volume down then press and hold power button until you see the Apple logo.)

To give you a better look at it, this is what it does at random. It may be time to upgrade, but I want to know if it is at all possible to fix.

[Paul Mudditt]

1 hour ago, Mroachfo96 said:

To give you a better look at it, this is what it does at random. It may be time to upgrade, but I want to know if it is at all possible to fix.

If you save as to an iCloud folder as an .afphoto file then upload it here myself and others can see if the problem exists on newer devices before you break the bank on a new iPad.

[DM1]

2 hours ago, Mroachfo96 said:

but I want to know if it is at all possible to fix.

If it is due to lack of ram, (not yet convinced this is the case), one option would be to modify the workflow. Use 'Save a Copy' - save with history, at various points in the workflow, to back up the adjustments already applied. Then rasterise all the layers, ready to begin next stage of workflow. This would remove all the groups and sub folders. You can then reload earlier versions if unhappy with end result.

As Paul suggested, attach a problematic .afphoto version here. I can see if my 10.5 pro has issues with same file.

[ericosmosNEW]

Hey, this is the same issue that I reported back in August 2021. See here: 👇

It seems to mainly affect versions on iPad Pro 

It had been logged with the developers. No news since …