bwackv

@deeds any idea if they're addressing this?

Hello, I didn't see anything about the selection tool in designer on the v2 features. Has it been improved at all? Was hoping for an object selection tool like in photoshop. (Does Photo v2 have it?). I really only use Designer, though. Second question - how does Designer v2 run on a 2017 macbook pro? my fans go insane with v1 right now.

@stokerg following up with this old post because I still need to make a decision. What did the dev team say? Oh ok thanks, so the solution is to... work with less layers (the file isn't that large at <200mb)? My 2013 macbook can handle these files - so it seems a bit odd maybe something wrong with how affinity ipad handles large amounts of layers? Would love some suggestions for what I should do so I can continue working with affinity!

@stokerg Is it time for me to buy a new iPad (happy to do that, I have a discount currently)? Just trying to get a sense here of what to do quickly as I have some work backing up....

@stokerg Oh ok thanks, so the solution is to... work with less layers (the file isn't that large at <200mb)? My 2013 macbook can handle these files - so it seems a bit odd maybe something wrong with how affinity ipad handles large amounts of layers? Would love some suggestions for what I should do so I can continue working with affinity!

Hey am I doing something incorrectly in my posts? Just wondering why I'm not receiving any replies to this?

Hello, I posted this before but after one response I followed up multiple times with no responses... whenever I'm working with large files using affinity designer on iPad (iPad pro 12.9" 4th generation) it crashes and I lose my most recent sections work - very frustrating. I've closed out a bunch of files on the affinity designer home screen, hard reset my ipad. I'm attaching the crash report and the file. At this point my work flow is ruined so I can't use affinity would really appreciate some clarity. This happens with other large files, not just this one. This is just the most recent. Designer iPad-2022-01-21-101541.ips infinite_main51_1.afdesign

Hey following up on this again? Can anyone offer advice on how to stop the crashes ? I posted the crash report.

@stokerg following up - who do I contact for resolution? I can’t use the app in its current state

@stokerg Update: after hard reset and closing a bunch of home apps, it crashes again-I was making vector shapes/using the vector pencil. Attaching crash report. Designer iPad-2022-01-21-101541.ips

@stokerg wow thanks for taking the time. I just force restarted. Also I had no idea about the Home Screen thing - I’ve never closed a file. There should be. Psa about this. Thank you!

Attaching one of my files. (it’s bad enough that I might have to go back to photoshop (which I dread because affinity is precious to me)). Just randomly crashes while I’m working. Happens to me on any large file I’m using. 2020 iPad Pro12” updated. I switch a lot between vector/raster and obviously these are large files with large dimensions but… yeah. I’ve just lost so much work I can’t tell you how frustrating this is. At this point there should be a warning. Feel like I’ve been robbed, to be working creatively and then just lose so much work… Also, palm recognition seems to be half-working: I keep getting random straight lines? infinite_main57-1.afdesign

Wow thanks for taking the time to solve this for me. I didn’t try the final cut export, only the other two. Should’ve! Good to know about the hsl error layers. I’m amazed you started going through layer by layer - there are so many and it’s so disorganized I never intended to animate the project, so I also feel for the person who has to manage my mess! Cheers.

@Callum also, I can export to png just fine. just cannot export to PSD. You were able to export to PSD? I had a friend try it with this file and he also said he cannot export it to PSD.

Hi Callum, thanks for your reply. Good idea on trying another file. I can export other files to PSD (just tested). I created a new file and copy and pasted in the content, and I am still receiving the same error.