Just install version 4.0.4 from the App Store

Just downloaded it and testing. So far it seems to perform much much better 

iPad Pro 12.9" (2018) iPadOS 14.5
Updated after staying for quite a while on 3.X.
Now the same files I’ve used to work on (300 - 500 MB A3 Canvas with many many layers) take a longer time to open, the app closes when going to a different app for a sec or when screen is locked and then unlocked, can’t have more than 2 documents open at the same time (10+ before update), occasional crashes… Not good.

Is this performance drop something you’re aware of and planning to fix, or is just how the things are going to be moving forward? I’d really like to get same level of smooth performance as before…

Smart objects yay!

+1 to this

Quote from: Dorothyfan1 on August 27, 2021, 07:45:04 AM

Thiis Procreate 5.2 release must be a massive one because it was announced 5 MONTHS ago. And we still haven’t heard when it’s coming out. Talk about hyping a point release update.

They always do it like that

Quote

There are a lot of bugs in Procreate. Some of them is several years already. Procreate’s developers answer to users that they are aware of them, but bugs are still not fixed. Comparing to that, ASP developers are very responsive.

That’s one of the main reasons I ditched procreate and moved to ASP

Indeed. But it is even worse that they are trying to sell some bugs as features… smh
ASP devs are really one of the best teams on iPadOS

+1 for templates

Quote from: lastaccess on July 14, 2021, 06:09:06 PM

You can check it yourself. Procreate allows 18 layers on 4000x6000 300 dpi canvas. I made 50 layers in ASP on that resolution. After 42 layers app became slow, because memory is out and swap is used massively, but you still can use the app if needed. Of course it’s better to keep less layers while ipad free ram is pretty low.

P.S.

Borodante is just an artist as every other artist.

I still think having the ability to calculate the number of layers a canvas can take WITHOUT excessive memory swapping would be a useful feature. And this even if ASP offers more legroom in terms of layer support. I’d still have to use Procreate to estimate the layer limit based on canvas and DPI size before using ASP simply because I can’t do such a calulation in ASP.

In fact, that’s one of the reasons I use ASP… I don’t see how you’d need to do that cumbersome process of calculating how much layers the app will let you have when in ASP you don’t have (such a restrictive) limit (as in Procreate). My iPad pro 2018 handles 150+ layers on an A3 300 dpi document just fine (in Procreate that’d be around 24? I believe…). I might see performance drop if I really push it, but I don’t care that much cause if it’s still responsive enough, I can still work and the app (usually) won’t crash.

On a second note, I don’t think a layer estimator would work very well on ASP because in my experience the app handles layers differently. If layers are almost empty (eg.: just the head of a character on one layer, less than 5% of the document size), it doesn’t seem to count as a full layer (like in Procreate).