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

eobet

Members
  • Posts

    286
  • Joined

  • Last visited

Everything posted by eobet

  1. The creator of that database has said that he does not have time to maintain it anymore. You are a commercial entity using that database, and apparently it is open source as well. Why don't you put some effort back into the community and update it yourselves?
  2. Unless I misclicked it, it shouldn't have been. I tried the wet edge effect but doesn't look 100% the same as in that screenshot above... but again, today the strokes are normal and no amount of clicking in the toolbar can make me replicate what I saw that made me post this thread.
  3. No settings, it's a built-in basic brush. It worked the day before yesterday, then yesterday it was like that all day, and today it's back to normal. Not really stable. 🙁
  4. Why has this happened? Why are there outlines around where the brush crosses an old stroke? Also, if I start drawing inside a stroke, I can no longer draw outside of it.
  5. I think this thick line with a butt cap behaves as if it had a square cap when it doesn't:
  6. Is this still true in 2021? (I was also surprised by the default Publisher behavior, and for my internet search, this thread was the top result.) EDIT: The answer is no, linked documents now reduce the file size of the publisher file, which is very nice! 👍
  7. I can't see if I posted in this thread yet or not, but again I was surprised that Affinity doesn't support DXF when I tried today. Zero chance that anyone where I work will even consider Affinity without this as well (but granted, there are other showstoppers in Affinity too).
  8. I also have the flickering issue. 1440p 144hz monitor using the latest Nvidia drivers. Apparently, Unreal Engine is also affected (several people in their Discord have acknowledged it). I hope Nvidia are aware of this, but there has been two driver releases with this problem in now already.
  9. Thank you from 2021! 😀 Is there an easy way to scale the effect?
  10. After I enable the "force pixel alignment" and "move by whole pixels" buttons in the toolbar, I expect all my copy, paste and move operations, regardless of shortcuts or tool combinations used, to be pixel aligned. And it looks like it is... until you press Ctrl-E to merge... then all of the sudden, things get super blurry. I hope this gets fixed soon!
  11. That's great. One person is like, ooh, artboards are so flexible and can do pretty much anything, and the second person is like, no, they're very different. Talk about a UI that leaves confusing impressions on people! 😂 I'm half joking, but Affinity could do well to make the Ux more consistent and clear in this area, I think.
  12. 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.
  13. 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.
  14. +1 (It's also interesting to note that no matter how much you press ctrl+a in the layer panel and choose "collapse selection", you can never get everything to collapse... so the only workaround is a lot of manual clicking.)
  15. 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?
  16. I imported a PDF. In the layers panel, I now get a top category called Artboard, with contents (including the background) in it. I imported a SVG. In the layers panel, I now get a top category called Layer (with a background in it). 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... 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. 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?
  17. 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.
  18. Affnity 1.9.0.932: Illustrator CC 2021: 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.
  19. 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...)
  20. Agree with this entire thread. Most of my posts on this forum is either about bugs, or really basic things that I'm very surprised are still missing.
  21. 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... 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!!!
  22. Surprised to see that DXF failed to import in Affinity when I tried it jus tnow, and even more surprised to see that this thread is 5 years old...
  23. Had to do an internet search to find it, but no, that was not checked. However, the issue went away again... but we'll see for how long. (I'm still reinstalling Photoshop in the background, though.)
×
×
  • 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.