Jump to content

CartoonMike

Members
  • Content Count

    453
  • Joined

1 Follower

About CartoonMike

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male
  • Location
    Walnut Creek, CA USA

Recent Profile Visitors

3,040 profile views
  1. Here's the revised art. Will work a bit on the text over the weekend, as what's there is more-or-less a placeholder. Really simplified the wing. Bad habit of mine is to do excessive noodling when I need to be simple and bold. I like it the way it is now.
  2. @GarryP -- thanks for the suggestions. I agree with all of them now that I can "see" it via your perceptions. Going to work on the modifications and may have the revised Raven up soonish.
  3. Had an idea for a T-shirt design. I guess it could also be used for a cloisonné (sp?) pin or button. I my wife suggested the use of the Raven (due to it's role in folklore and myth) as the main focal point. What I discovered is that I can drag from the browser window to the Affinity Designer window graphics to use as reference. Sure is easier than downloading them and then placing them. Also shout-out to Pure Ref (pureref.com) for an amazing "digital corkboard" where I can put pix on for reference and have that window float above all other windows. Cool little app. Mac and Windows versions, btw.
  4. Thanks, looks like I'll have no other choice but the online option. Thanks Affinity Jedi, may the force be strong with you.
  5. For the past 2 Mac OS X major updates (14 & 15) Affinity Help searches yield a lot of hits, but NOT one for the affinity app that I'm using. I posted on a pre-existing topic on Sunday, and tonight, Tues, have yet to get any reply. Yes, I know that Apple's help app got blamed because it didn't update or get refreshed according to some undisclosed rubric. Um.... if that's the case why on my Mac only Affinity products have this issue? Even old apps that I've updated and new ones that I recently installed have a full working search ability in their Help and it sure looks and behaves exactly like Apples Help ... and there was a line ("killall helpd; rm -rf ~/Library/Caches/com.apple.help*; rm -rf ~/Library/Preferences/com.apple.help*") on another thread that I copied and pasted into the Terminal app to force a help app database refresh, or something like that, and the response I got from terminal was: Michaels-iMac:~ cartoonmike$ killall helpd; rm -rf ~/Library/Caches/com.apple.help*; rm -rf ~/Library/Preferences/com.apple.help* No matching processes belonging to you were found Michaels-iMac:~ cartoonmike$ I'm an Administrative User, on Mac OS X 15 Catalina, and I did something to start using the BASH of preference (Z-something-something). I did that, so maybe the "killall..." line also needed to be updated. Or something. I dunno, I am comfy using Terminal, but not an expert -- Just like driving a car doesn't make me a mechanic... Like I said in the other topic thread, all I want is to be able to search help instead of hunting and pecking for what I'm looking for as if this help is nothing more than a digital dead tree manual with no index. I feel this shouldn't be such a hard thing or such a big deal. Thanks, I should also mention that it would be nice if the help for the app I'm currently using reads like it's the help for the app instead of for all affinity products. Meaning, if I'm trying to get info on Bleeds in Affinity Designer, then I shouldn't be reading description that fits Affinity Publisher better. (i.e. options on the dialog box matches aPub better than aDesigner). Aside from the Help search snafu, I am so very happy with all 3 of my affinity apps! I'm only antsy because of the Stay In Home quarantine and my comprised immune system, I'm trying to do a self-printed & published mini-comic during these ... um... novel times we're living in. It's a bit of a challenge trying to find specific things about bleeds and margins that seem to be there in the help but damned if I can find them. However, I couldn't see me trying this without the Affinity apps. Thanks again for reading this, stay healthy and wash your hands!
  6. Tried to do the Terminal thing. Somewhat comfortable with it, but (of course!) I got this error: I copied and pasted, so if there's any typos, they were in the original post or it just wasn't crystal clear exactly what to copy or if anything needed to be added (like what the "*" wildcard could be [if anything but what it is], for example...) Part of me finds it interesting that for things like Help, it's always Apple's (or somebody else's). But the help function is hosed only on Affinity apps. Works fine on other apps. Or at least the apps that I use and needed to search help for that app. And that's been the case for at least 2 major OS X updates (14 and 15 for example.). I would like to do a help search and have it work. That's all. It's "only" computer science. Shouldn't be worthy of sacrificing small animals in the dark of the moon to the elder gods. Or is it...(cue ominous music...)
  7. 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.
  8. 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.
  9. I claim early-morning-before-coffee excuse. Thanks for the correction and I've edited the post to have the correct name.
  10. 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.
  11. 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!
  12. It's always a treat to see a new Eejit! Thanks!
  13. 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.
  14. 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.
  15. 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?
×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.