StudioJason

Welcome to the Liars Club everyone. Canva is a DIY replacement tool. You’ve just added your entire User Base to the replacement pool. All this time, big talk about professionals, standards, quality, NEVER a subscription model and more, turns out after all to be nothing more than any other Sellout. ‘Even when forced to purchase V2… and we all did, it was the product believed in “by professionals, for professionals” without being greedy like Adobe having subscription. And here we are. Canva has nothing your current Users need… as everything Canva can do, WE your Users (you know, the ones that kept you in business) already can do with current Affinity products. ‘All of the touting and Marketing, and support in MINDSET more than anything… of denying the Adobe Subscription greed train, is finally revealed. The only thing mildly good hearing this news, is you didn’t layoff your current Dev Staff… but that’s only because Canva HAS NONE to keep it functioning. ‘Guaranteed… as soon as the Subscription comes, and it WILL (we all know it), even your/they will be obsolete… so kudos. Makes perfect sense now as to why fixing or updating your iPad V2 hasn’t happened in several months to a year even though reported numerous times. All I know is, I purchased BOTH V1 and V2 of all three Affinity apps for iPad… not even the Universal License as some (which YOU recommended)… and expect to be able to use them in perpetuity as you claimed in writing. Else the term Class Action happens, which is typical where PROFESSIONALS are concerned. Enjoy your money Sellouts.

Unless you are on iPad Pro version of Publisher, and the App continually crashes while doing basic Editing, and the Devs haven’t updated in almost a year to fix it. But good Tutorial overall.

Update 1/15/24: Another Sporadic Crash- this time using Affinity Photo. ‘Applying FX to Text, such as Outline, Shadow… in particular was simply adjusting the settings for applying a Shadow to Text (using both Slider and Number Input), trying to get the best aesthetic Color and amount of shadow… then the App completely crashed.

Is interesting indeed, though I discovered this a long while ago and used a different formula for success based on this. Saved as new ‘Accurate B/W’ Preset…and works flawlessly.

Update: 1/12/24 After posting the above response, I went and first saved files within Publisher to another folder and then Deleted the App completely. Reinstalled Publisher, and then underwent the process of re-saving files to be used in Publisher from their location. Began working on the Document previously mentioned- there are no Linked Files, all are Embedded just as they were prior. Worked at simple Editing Text within Text Frames, as well as separate Artistic Text headlines for a period of approximately 15-20 minutes… and the App completely crashed. Update 1/12/24- After the first Crash, opened Publisher to work on Document. Within 5 minutes of editing… the App crashed. ‘The only thing other than what I have already elaborated on to offer is this new Log that was saved, the previous “reason: locally requested” is my actual closing of the App…. last input being simply opening the App again, with nothing about the actual Crash itself. [2024-01-12T15:26:50.287-0500] Initialising IPC for Affinity Publisher 2.3.1.2217 [2024-01-12T15:26:50.636-0500] [Client] Starting IPC connection management [2024-01-12T15:26:50.636-0500] [Client] Attempting to start local server... [2024-01-12T15:26:50.637-0500] [Server] Started [2024-01-12T15:26:50.656-0500] [Client] Local server has started; attempting to connect to it... [2024-01-12T15:26:50.658-0500] [Server] Got new client 2 ("Affinity Publisher 2.3.1.2217") [2024-01-12T15:26:50.658-0500] [Client] Connected to server [2024-01-12T15:27:14.056-0500] [Client] Stopping IPC connection management [2024-01-12T15:27:14.057-0500] [Server] Lost client 2 [2024-01-12T15:27:14.057-0500] [Client] Disconnected from server [2024-01-12T15:27:14.062-0500] [Server] Stopped (reason: LocallyRequested) [2024-01-12T15:27:43.198-0500] [Client] Starting IPC connection management [2024-01-12T15:27:43.198-0500] [Client] Attempting to start local server... [2024-01-12T15:27:43.200-0500] [Server] Started [2024-01-12T15:27:43.389-0500] [Client] Local server has started; attempting to connect to it... [2024-01-12T15:27:43.498-0500] [Server] Got new client 3 ("Affinity Publisher 2.3.1.2217") [2024-01-12T15:27:43.499-0500] [Client] Connected to server [2024-01-12T15:27:49.681-0500] [Client] Stopping IPC connection management [2024-01-12T15:27:49.682-0500] [Server] Lost client 3 [2024-01-12T15:27:49.682-0500] [Client] Disconnected from server [2024-01-12T15:27:49.683-0500] [Server] Stopped (reason: LocallyRequested) [2024-01-12T15:40:02.946-0500] [Client] Starting IPC connection management [2024-01-12T15:40:02.948-0500] [Client] Attempting to start local server... [2024-01-12T15:40:02.950-0500] [Server] Started [2024-01-12T15:40:03.107-0500] [Client] Local server has started; attempting to connect to it... [2024-01-12T15:40:03.538-0500] [Server] Got new client 4 ("Affinity Publisher 2.3.1.2217") [2024-01-12T15:40:03.551-0500] [Client] Connected to server

Seeing as the one of the biggest culprits in crashing is Publisher, which is mostly about Text it is rather surprising it is an issue at all. Also, take note of what Devendra has added to this post with examples. ‘It is sporadic and too difficult to determine what the cause or triggers for this can be. Have given examples multiple times, especially regarding Text functionality even since the Chinese Characters replacing simple font names was an issue… which although fixed STILL replaces Font names in the list with other Font types. ‘It is NOT having to do with RAM as there is plenty (just as described by Devendra)… nor with files that are used or created. ‘Not to mention what is described in her/his post in regards to AP or AD brushing on a layer (randomly after I had already painted for some while) switching layers using the color slider and pipette typing values in a panel switching tools opening a document It is simply too sporadic even with those, which was never the case in V1… nor initially in V2, only having cropped up since the iOS 17 Update ‘Plus given the fact that I can only use Publisher itself incrementally before it crashes, have virtually not been able to use… or finish projects, resulting in lost revenue opportunities (much less having to wait for support). ‘Given that these latest recommendations you have given are the only options available… then of course I’ll have to try them. But it seems ultimately with any extended time use of the App itself, more than anything… which even then is just as sporadic, as sometimes it can be over 30 minutes of use or incredibly only 5 minutes! ‘I’m just amazed at how much Dev attention and implementations are given to the Desktop version… but lack thereof is given to your own iPad versions. It is becoming highly disappointing.

Very nice. Just remember for those using… the Map Borderlines (boxed areas) also certain dimensions… as a border type of overall visual scaling of distances as well. Meaning, each black and white box individually represent an increment of size/distance (I.e. inches/meters, miles/kilometers, etc). Unless you’re just wanting the overall effect.

Nope. Is all Embedded (and image files are not large PNGs). But thanks. Mine is apparently different… and have to await someone’s leave/vacation to be over apparently, for assistance.🤯

My Publisher files have absolutely no SVG files in it… and constantly crashes since iOS Update 17. ‘Can’t even perform simple Text Editing… and consistently crashes. ‘Hard Resets do not fix. The app is virtually useless for an entire month now (as described in my own crashing post).

So the issue still persists, and is more prevalent and rampant now. Publisher continuously crashes upon doing simple Editing of Text within Text Frames. Am able to make 3-6 edits of text within a 40 page Document… and then it crashes. Repeatedly. Cannot even work on the Document basically. Submitted a screenshot of my available Free/Used Gigs (above, which is the same)… which should be well over plenty needed. The Document has several images, but no more than seen in any other examples similar… and even the Text is limited. Was asked earlier about workflows… which I’ve now given several examples and descriptions of, but it isn’t anything more drastic than basic functions that should be capable of performing… especially since they were prior. (Other than what I’ve given, unsure what else I can offer but would if I could). ‘Has been about a month now, and have heard no response… which is highly disconcerting.

I’m using and have been using V2 since release. Thanks.

Then it’s been a bug as mentioned, since the iteration of Version 1 of the apps…again as mentioned, with no updated fix ever. And as previously stated, has already been brought up in several posts (one even dated 2019) with prominent users who frequently offer help on this forum, to do the only thing possible…make copies, delete and reinstall. My post isn’t looking for assistance, because there is none. It’s in the Feedback section…and for a reason. A User giving feedback, so hopefully Devs will correct a big oversight. Appreciate your attempts, but you are not on the Affinity Dev Team, which this Feedback is for.

No. Never has. Is always greyed out. You either have to remember the settings or delete,and reinstall as posted. In fact, to alter the settings…and use the Brush..you have to Save first…which completely changes the Brush altogether…and no Reset, again as already mentioned. Maybe it is different for the Desktop….but I’m on an iPad Pro and doesn’t work. And if it is the old argument between cost/features between the two….then it is more than absurd and ridiculous. ‘Should simply be a part of Brush Creation. Period.

Have read previous posts about this, and know all about duplicating a brush, saving copies and such beforehand when deciding to alter a Brushes settings…to simply test it out or try new settings. ‘But the fact that there is no actual working ‘Reset’ - to auto return all settings to their initial default settings, when the Brush was originally created, is a major oversight (especially since it’s been discussed several years prior, with no updates to make it possible). A major Developer of an app, with the popular ability for diverse and dynamic Brush creation, has a simple additional feature in their Brush Settings, to set a Default Point for Settings. Whereby a Default Point is set upon the last settings made before saving…BUT ALSO saves that Default Point, so that is at anytime anyone wants to experiment with a Brush but changes their mind…can return to the original settings. Any altered settings can still be saved….so you can utilize your newly applied one to a Brush, but can STILL revert back to the original. And if you wanted to save your newly changed brush…you THEN would save a copy of it, going through what you have currently set up as having to do…which makes more sense. NOT having to Delete and Reinstall every single every time. (The Brush Creator is protected simply as well with Authoring the Brush). ‘The fact there is no SIMPLE way for this to be done is highly inefficient and rather absurd. Especially in a modern tech Graphic Design market where there are numerous possibilities, yet are restricted with such a simple solution, having to resort to tedious workarounds. ‘Would be nice to have a simple Reset on Brushes…that actually works or does what should be intended.

This is a good one, for even more than just distressed textures. Great tutorial as always.