Jump to content


  • Content count

  • Joined

  • Last visited

About CartoonMike

  • Rank
    Advanced Member

Profile Information

  • Gender
  • Location
    Walnut Creek, CA USA

Recent Profile Visitors

1,056 profile views
  1. CartoonMike

    Can't Import Brushes

    Well this was interesting. I tried to open a file in AD 1.7.2 and got an "unable to open because of permissions" error (sorry about not quoting it exactly, I'm a bit busy today and doing a detailed bug report is just one thing that i can't fit on my plate this week. Anyway, due to the dearth of actual assistance about the importing brush issue and now this unable to open a file that i was able to open in the beta -- I decided to do a bit of searching. There were problems/issues with others opening files and getting the permission error message. Seems that those with this issue all had App Store versions and in one case the user had many fonts active. When the number of fonts went down, the user was able to open files again. Hmm, I thought, and it seems that those who bought the app from the Affinity Store didn't have the issue. Seems with Apple Appstore apps the @#&%@ sandbox "feature" would cause permission-type errors when too many fonts were active. Now what if... that stupid "feature" was the cause of my problems ? I thought of it... I bought Publisher from the Affinity Store, the betas were downloaded from Affinity and maybe didn't have the sandboxing feature of their Apple store cousins. The more I thought about it, the more it made sense. I mean, I am able to open all the files and import brushes that Designer couldn't in Publisher. The beta RC candidate could import any brush file and Designer File. I went into Suitcase and deactivated a slew of fonts. Opened up Designer and I imported the brush with no issue. I opened the Designer file with not a single error message. I add that I am using the Container folder that I renamed with the ".old" extension now and am having no issue. So it seems that the time I spent uploading a 3gig zip file was for naught. Really. TBH, this whole week of troubleshooting and not being able to do the work in Designer has me very, very, leery of using any Apple App store apps. Because Pages, Numbers and other Apple apps gave me no issues; but Affinity Designer and Photo had issues while Designer (bought from the Affinity Store, remember) had absolutely no issues with opening files or importing brushes at all. And I feel a bit out of sorts about this, as I seem to recall that Affinity's line is that there's no way to transfer a license from the Apple Store to the Affinity Store (although there has been some companies who were able to do so. There's some kind of file inside the app that acts as a receipt of sorts. But I don't remember the specifics). So my best option to have an optimal experience (that is, not wasting a week dealing with an issue that I could've solved in minutes all because of the stinkin' sandbox that Apple foists on developers) with Affinity products is to just go and re-purchase them via the Affinity Store? Anyway, I'm a week behind on work and I gotta get cracking.
  2. Damn, you have a great eye Alfred! That's what was eventually chosen, as having the bottom half being the only "off-center" bit of text made the entire word look more broken than having both halves rotated.
  3. I claim early-morning-before-coffee excuse. Thanks for the correction and I've edited the post to have the correct name.
  4. What I did was to make 2 copies of the text, group them. Then I made a jagged line and duplicated that and then made one copy a rectangle with the bottom edge being the jagged lined and the other had the jagged line as the top side. Both of these had NO fill and NO stroke. Then from the layer palette I dragged one set of the title text into the "upper" shape and the other into the lower shape. Since the Jagged line intersected the text and AD treats shapes like a mask when you move things into it -- all I had to do was to rotate the Jagged shape (NOT the text) to get the results you see. A little bit of adding layer FX for the shading and it's done. I like what you did, GaryP, was it similar to how I did it? I like the method I used, because the title went through a few changes and the text remains editable. If this was unclear, give me a few days to do a "proper" tutorial. BTW, the font is "Friend or Foe" from the Blambot.com website. I like BlamBot as it has dozens of excellent fonts that's free to use by indie comic artists and others. Friend or Foe is a paid font, though. It's quite reminiscent of early 70's title lettering in Marvel Comics of that era.
  5. Here's one page of a short (15pg) story I've been working on.l Originally used the Publisher Beta to begin with and now using the released Version. I'm following the lettering techniques for Illustator from the ComicCraft tutorial I saw on Lynda.com. And i works, even better using Publisher with the Designer persona used when needed. The art was hand drawn on paper, real old-school. Will be finishing it up (pencils, inks and colors) in Clip Studio (would like to use Designer, but I like CS for pixel drawing/inking and painting a bit better). this is a WIP, so as I wrap things up, I'll update this thread as i can. One nice thing is that having a link to the file, rather than embedding, allows me to letter rough penciled pages and see If I need to move things around in the roughs to make the panel "read" better as a visual composition. Yeah, it's a comic thing. This is something that most comics don't do, as it's so production-oriented. Y'know, if novelists can do a second draft, why can't comics. And Publisher allows me that flexibility and freedom. Thanks Serif and Affinity!
  6. CartoonMike


    It's always a treat to see a new Eejit! Thanks!
  7. CartoonMike

    Can't Import Brushes

    Okay, uploading the zip now. It's named "CartoonMIkeBrushIssue_190922" And to make it clear, even when the affinity designer container folder was empty (using the .old appending to the original folder name) I couldn't import any brush file. NONE were ABR brushes. All the brushes were "afbrushes" and while Photo and Publisher could import them, Designer (with the new container folder) could not.
  8. CartoonMike

    Can't Import Brushes

    I truly think this is a bug in the app itself. I deleted it from my apps folder and renamed the container folder to "old' as per the instructions in the reply. Reinstalled Designer from the app store. Tried to import brushes and got the unexpected format message. interesting thing: the icon for the afbrush file changed to that of Affinity Photo. Okay, I thought, what if I change the "owner" of the file to Designer. I did so and the icon changed to that of a generic document. And still cannot import brushes. I find it hard to believe that the problem is on my end. Prior beta RC have worked just fine, like the Publisher RC. But the released version had some thing or another flipped and it didn't work well at all, which was fixed in a point release in short order. So I keep coming back to the fact that in the 1.7.2 RC1 Designer beta I was able to import brushes with no problem. But the released 1.7.2 won't import the very same brush file. So I guess, due to the time difference between California and Affinity, I'll have to wait another day for a response. So until then, I'll just wait patiently.
  9. CartoonMike

    Can't Import Brushes

    Hi Sean, I followed your instructions and after starting Designer with a new "com.seriflabs.affinitydesigner" folder, still can't import brush files. I tried multiple brush files from RetroSupply (Vector Sketch), Artifex (the updated Fineline and the Tattoo set [which was pruchased from the serif site and freshly downloaded], and the Frankentoon's vector Marker set) and each one gave me the same "Unexpected Brush format" error. Interesting thing the RC for Designer 1.7.2 had no issue with importing the Fineliner brush set, but 1.7.1 had the format error message and 1.7.0 imported brushes okay. I didn't report the 1.7.1 issue because (in my mind) the beta for 1.7.2 resolved it. However the app store release of 1.7.2 had the inability to import brushes as did its predecessor. I have a zip file containing a few sample afbrushes files and my container folder for Designer. It's about 3gig (lots of patterns and textures), and that's a bit big to send to a Dropbox, I feel.So would it be okay to drop it in the Dropbox as is or should I just root around and delete the textures?
  10. Updated to 1.7.2, most recent version of Mac OS X Mojave. No matter what the vendor (I tried RetroSupply and others) and using the exact same files that Imported just fine in 1.7.1 I get this: (no screen cap, as it's easier just to transcribe) --- Unexpected Brush Format: Failed to load file '/Users/*******/Downloads/Fineliner Brushes and Textures/Brushes/Fineliner Brushes.afbrushes'. --- I tried restarting AD with the shift key held down, but that did nothing. It seems to me that if AD cannot import brushes from files that it could in a previous version, it's something wacky in the update or something on my side got corrupted. Any clues, tips, hints or suggestions on how to resolve this on my end, if that's possible even. Thanks
  11. CartoonMike

    Affinity Publisher (1.7) Launch Announcement

    [slow clap] Well played, sir. Well played. I actually spelt Localisation that way, but the frackin' spellcheck "corrected" me. As far as spelt goes, I didn't feel right to my grammar. And since she's such a nice lady, I went with what felt right. [shrug]
  12. CartoonMike

    Affinity Publisher (1.7) Launch Announcement

    Saw the affinity live video and was promptly floored. I was feeling this during the beta, but now with the released version of Publisher it's not a feeling any longer -- this is the DTP app I've been waiting for years to use to letter an entire comic book/ graphic novel. I can use the Designer persona for creating word balloons and the Photo persona for adjusting the scanned artwork. So thanks to all the Devs and Testers that made this app what it is today! Oh and... I'm in the US and I really think that "Colour" should remain spelled that way in ALL Affinity Apps, localization be damned! For me the "British English" spelling (although it's used in many other places) just adds to the ... ah... flavour ( ) of Affinity apps.
  13. Don't know if this will be helpful, but what language is your Mac set up for? Mine is english and I'm assuming (from his previous posts, correct me if I'm wrong) Bruce's is English also. I'm also using an Apple Magic Keyboard with extended keypad. Again, just trying to find some thing that could be causing this issue. Are you using any key/type utilities like TextExpander? I had mine set up to automatically close parentheses and brackets and that caused issues when I was trying to increase brush size using the open bracket key. So maybe your shift and modifier keys are being remapped or something ...
  14. Have basically the same setup as Bruce, not having that issue. Shift and command (for not contiguous item selection from a list, like Layers) work as they always has on Affinity and Mac OS in general. Also using a Wacom intuos pro tablet.
  15. The fact that the files are Embedded and not linked, forces me to repeat the Place command for each page. for a 32 page comic, that's a bit of effort that is caused by the arbitrary elimination of Linking to files. Linking allows the source file to be changed (or replaced if the exact same file name is used) and that change is propagated to the doc that is linked to the file. In essence, just embedding the file is costing me anywhere between 2-3 hours of work per 32pg comic. I didn't know the replace image was a trick, so I didn't mention it. To be fair, All affinity apps have had so many changes, my head is spinning and I don't know how to work around this embbeding thing. So this is me throwing up my hands and I'm just going to work through this and maybe by July, I'll have figured out how to use AD/APub for comics or just revert to using Comic Life (which is a good app), which can export a ePub, PDF and raster formats (JPG, PNG and/or TIFF).