Jump to content
You must now use your email address to sign in [click for more info] ×

eobet

Members
  • Posts

    279
  • Joined

  • Last visited

Posts posted by eobet

  1. On 5/21/2020 at 10:23 AM, Maciek Blaźniak said:

    Hi,

    It's 2020 and there is still no no built-in spatter effect in affinity. Here's how I deal with it with help of live displacement map filter from APhoto. Just open the attached file (spatter_1.0.afdesign) in Designer or Photo and move the only layer to your project. Works quite well live, when active all the time while creating the illustration. However, it may not work for people who do not have an Affinity Photo license (I didn't check it).

    spatter.thumb.jpg.60e1e4dbdfea88ea9737c1400ba6f4fd.jpg

    Thank you from 2021! 😀

    Is there an easy way to scale the effect?

  2. 16 hours ago, walt.farrell said:

    Why shouldn't it be?

    With that attidue, why have Artboards at all, if Layers work the same? Right now, you're just complicated it for the user, and allowing them to make mistakes they might not even find because they don't expect them to ever be allowed to happen.

    What's the use cases for all the things you mentioned?

    Artboards fill a specific use case that has to do with exporting to other formats. I don't think any of what you mention has anything to do with that and can't be exported.

  3. I tried to move the stroke panel from the top to the middle by the appearance panel... but I think I missed and the layers panel got involved.

    Dragging around trying to get back to where I was, after a while made the whole app crash.

    The entire experience also felt rather unintuitive and inconsistent in where the panels actually ended up when you released it prior to crashing.

    I found no other threads about this and of course I don't have exact repro steps, so I'm creating this thread as a data point and hopefully others will chime in with their experiences as well.

  4. On 6/16/2021 at 3:21 PM, Alfred said:

    Since a Layer of the above type isn’t an object as such, it stands to reason that it can’t be converted to an artboard.

    But the artboard in the PDF isn't "an object as such" either. I think Affinity blurs the line here in a rather inconsistent way.

    Oh, and I just discovered that I can set an opacity on an artboard!! Why would I ever want to do that and why is that even supported?

    1. I imported a PDF.
    2. In the layers panel, I now get a top category called Artboard, with contents (including the background) in it.
    3. I imported a SVG.
    4. In the layers panel, I now get a top category called Layer (with a background in it).
    5. If I copy the top category from the SVG and paste it side by side compared to the top category in the PDF, I now have one top category of the type Layer and one of the type Artboard. Both can be moved freely on that grey document(?) background...
    6. If I select the background object in the Layers panel and use "convert to Object to Artboard" in the layers panel, the top category is still a Layer, but that object itself becomes an Artboard.
    7. Visually, in that grey document(?) background area, they now look the same... but in the layers panel, the top category still says Layer

    This is a bit confusing.

    • Why did the object itself become an artboard, instead of transforming the entire layer into one?
    • Why am I not allowed to click on the top layer category and convert that into an artboard, since that's how imported PDFs behave?
    • Why is a layer allowed to be at the same level as an artboard, and behave basically the same?
    • How is it that an object inside a layer can be an artboard? What's the workflow or use case for that behavior?
  5. We just received a contract PDF we wish to update, however, upon import with font replacement in Affinity, all white space is removed.

    Tested on three different computers, Mac and PC, using Designer and Publisher, all exhibit similar problems (one PC "appears" as if OK, but on closer inspection is not).

    Contract contains sensitive information, and since it's an import issue, can't be altered.

    Mailed Affinity about this and am awaiting secure way of delivering the file to a developer for testing.

  6. Affnity 1.9.0.932:

    image.png.31a4e27bf585dbac2fc875358811e49a.pngimage.png.5d045194c2221835efa21cb043969c50.pngimage.png.de66a06a1b8c2a269590a6f24f14b653.png 

    Illustrator CC 2021:

    image.png.56b6aa40772c036aa3ccace7674a6905.pngimage.png.fc50fefe402426cc4f81bd8d5043fa30.pngimage.png.2c3c0138e0278ff915d1f2233b06ed19.png

     

    Client file so can't show more than this, but it's very simple shapes.

    Btw, the reason I need to pass this through Illustrator is because expanding curves in Affinity is still messed up, and Illustrator does it accurately. However, this is the first time I've seen Affinity fail at even this level. Guess I'll try using PDF next.

  7. Got a new laptop and attempted Affinity only for a while... had to re-install CC within a day, I think. ☹️

    It's sadly impossible to switch completely to Affinity at the moment. To many bugs and too many basic things missing.

    Muscle memory and shortcuts didn't even have time to become an issue for me! 😂

    (See my post history for the specifics, and am just about to post a new thing as well, when I find the appropriate thread...)

  8. It this the new "Expand Strokes Still Sucks" thread? :)

    (Or is it this one... or this one...?)

    Either way, here's my result in 1.9...

    image.png.572473dab1267047055d66605c4bf55b.png

     

    However, pasting it into a new document makes the bug go away, and these are files for a client so I can't share the entire thing.

     

     

    EDIT: Wow, changed the stroke from round to mitre and the result is actually THE SAME... it expands exactly the same as if it has a round join!!!

  9. Can anyone see anything from this picture? I'm painting on a pixel layer, using the default brush, no selection, no mask (on that layer), yet there's clearly something blocking the brush in some areas...

    image.png.44ff4db5c16aee61de13c0b65dfa4219.png

    I can't share the file because I bought it from a stock photo site, and I'm just using the mouse for now because I wanted to do a quick job.

    (There's zero chance to convince any coworkers to try Affinity when things like this happens 2 min into working in a file. I have a new machine but I guess I'm installing Photoshop on this one too... sigh!)

  10. Question: What does this icon mean?

    image.png.805ed97772c9547dbb1dc57a75ef92c9.pngimage.png.c931f4e5f45fc9339c3d3a53d63715fd.png

     

    In affinity, that is unlocked (even though it's a chain... so "unlinked", I guess), which seems crazy.

    Only after you click on it, do you see that they actually add *another* few lines to tie it together.

     

    I mean, the natural thing to do would be to do something like this:

    image.png.1190f7d9992424df5fbd912d9250e734.png

     

    This issue feels similar to this thread:

    And also, this almost invisible icon:

     

     

     

    Why does it seem as if Affinity didn't really think their smaller icons through?

     

  11. On 3/10/2019 at 10:32 PM, firstdefence said:

    Make sure you have Precise clipping enabled in Preferences: Performance.

    Wow, I was just about to post this as a bug... lucky I found this thread!

    clipping.gif.f421e8a1d40a1325a9d605a0707168f2.gif

    What a silly thing to disable by default... although, I've noticed that the app does become quite sluggish quite quickly. Illustrator is always slow, but never bogs down. Designer is fast on small documents, but quickly becomes sluggish.

×
×
  • Create New...

Important Information

Terms of Use | 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.