1) Yes but exactly that option is not working for me in the beta, even with "clip thumbnails to image bounds" the thumbnail will stay square... it works fine in the app store version, as you could see in the screen recording

2) I tried again on A4 canvas with only 3 layers, it still doesn't work

3) I understand... but maybe thickness can still be reduced a bit more

4) The outline looks very weird in my eyes, I actually thought it was a graphical bug, rather than an visibility improvement... Especially thin strokes (sketches) are hard to see details like that. I think it should be completely removed again.

Checkerboard was better in that case, since on checkerboard you can see light and dark strokes... However, in Procreate it works too without checkerboard and without outline, so idk... but the outline definitely is very very odd

4) nvm it’s much better with the thinner outline!

Active area was increased a bit weeks ago in the App Store version.

It seems increasing sidebar width is not the good idea, maybe it should be redesigned from scratch...
I will publish version with increased width in new beta so you can test it. But then i will probably go back to original width .

Any update of when it will go back to previous width?

We removed "Square Thumbnails" option from Preferences to make UI more consistent.

1) I saw that, but what I meant is, that it’s generally always square thumbnail now. Before it was possible to have the thumbnail in the same ratio as the image. Now it only changes within the square ratio, when it should be changing the overall ratio. If that’s on purpose, then I don’t think it’s the best UI decision, I think it should be up to the user if they want a square thumbnail or image ratio, so definitely the previous way, where everything could be adjusted individually was better. (Like in the current AppStore version)

Layer Flashing options works fine, i have just tested that.

2) It doesn’t do anything for me, it also doesn’t work in the AppStore version, I just noticed.

X is too thick - we will fix it

3) I saw it was adjusted a bit, but I still think it’s too thick and opaque. It should be very subtle, like before, otherwise it’s too distracting.

4) Also the strokes of the thumbnails (like the lines of what is drawn on the layer), look a bit weird now, almost as if they are very strongly sharpened with a white outline around it. It doesn’t look like a true representation of what’s on the layer, the colors look slighty different too. Especially if you compare it with the current AppStore version, it looks wrong.

I attached a screen recording showing all of what I just mentioned, compared with the beta (dark blue accent color) and the AppStore version(light blue accent color). Generally I’d suggest everything to stay as it was, except for removing the checkerboard background. The other changes made to the thumbnails right now, are not an improvement to the UI, imo it looks less professional, with less options than before. Hope it can be fixed.

Thanks!

1) Just tested the new beta and it’s already so much better with the opacity slider! So I don’t think line thickness will be needed now.

But the opacity slider should really go from 0% to 100%, meaning that at 0% percent the lines aren’t visible at all. Right now they are more like between 30% -100%, so at 0% they are still visible, which seems weird. It should work like when adjusting layer opacity.

And the horizon line doesn’t get affected by the opacity slider, but it should too.

Also there’s still a lack of consistency between canvas sizes of the lines, so basically, they still appear “thicker” on lower resolutions and “thinner” on bigger ones. Which would be okay now, if the other things I just mentioned will be fixed.

2) the grid is still unevenly spaced in 1 point

3) artifacts and overlapping lines at horizon are still present

4) As just one more small note, I want to suggest removing the “density 3” option from the one and two point perspective, as it doesn’t do anything in those.

Thank you!

We decreased a bit time to trigger Autosave. Now, in the latest beta, you have to stop painting for at least 2-3 seconds.

The problem with faster autosave is that we always have to update preview and thumbnail images inside the document, which takes a lot of time when document is large.

Maybe the thumbnail/preview images could only be updated when actually switching to the document browser, or when clicking on/opening the “open documents” view?

So that while you’re just on the canvas and painting, it doesn’t need to do those thumbnail updates every time, and can just save continually. So it would only take longer when actually going to document browser.

I think it was fixed in the latest beta.

It’s still the same in the latest beta. I included a screen recording, showing the small difference between keyboard shortcut and Apple Pencil, and the big difference when using 3 finger swipe.

We will fix it asap.

I just noticed that when the toggle is on to show it in the corner, the brush previews are still at slightly different positions between Apple Pencil and keyboard shortcut. And at a very different position when changing with the 3 finger swipe gesture

We are now working on faster autosave!

I have just tested one large document, and we went down from 10s to 1.5s when autosaving after painting one layer. It will be available in new beta.

That's awesome looking forward for the update!

But I also noticed that sometimes even if it says "autosaving", but then the app crashes soon after,  or I manually close and reopen the app, it didn't actually autosave it for quite some time. (Sometimes lost work up to an hour like this, sometimes just a few min, even though autosave is set to just 1min)

One way i go around this, is by periodically going to the document browser after it autosaved and then back to the canvas, or by saving it manually before closing it and just in between. Usually it only then, actually saved it to the current version when reopening the app manually or after a crash, or sometimes even after just switching between apps.

Not sure why that is,  but I notice it mostly on bigger files.