-
Posts
21 -
Joined
-
Last visited
Everything posted by Molumen
-
Print document crashes Designer and Publisher 1.9.0
Molumen replied to erchdk's topic in V1 Bugs found on Windows
Same here, Designer 1.9.0.932 crashes 5 out of 6 times when I open the printing dialog (CTRL+P). My document has 9 artboards. Printing can be achieved though, as the printing dialog will eventually appear without crashing the app, just restarting Designer and opening the same file several times is kinda annoying, so I'm eager to see that bug squashed. @Mark Ingram thank you for the good news, looking forward to testing the beta!- 10 replies
-
- affinity publisher
- crash
-
(and 3 more)
Tagged with:
-
Expand Stroke bug (not accurate)
Molumen replied to debraspicher's topic in V1 Bugs found on Windows
Seems to be fixed in 1.8.0.585. I just checked the Expand Stroke, and it's VERY accurate now! -
Affinity Designer 1.7.3.481 Bug is reproducible (printed this document on 2 different printers with same results) The document was created from scratch (basically it's a new document) Sample document is attached. Photo of the result is attached too. Operating system is Windows 10 (with all latest updates at the time of writing this) What happens: - I created a new document, it's a 2-page template for a small bi-fold wallet - All Strokes are 2pt thick, all Dashed Strokes are 1.5pt thick - When I print the document from Affinity Designer, all but 2 objects are printed with a very thin line, including dashed strokes. The printers that I used to print this are: - Oki SP 111 - HP Color LaserJet Enterprise flow M880z Both printers ended up with the same results Looks like the information about stroke thickness gets lost when Affinity Designer sends info to the printer. Mini bifold card holder.afdesign
-
Expand Stroke bug (not accurate)
Molumen replied to debraspicher's topic in V1 Bugs found on Windows
Designer is indeed a great software, but it is still not suitable for pixel-perfect work -
Expand Stroke bug (not accurate)
Molumen replied to debraspicher's topic in V1 Bugs found on Windows
If you look closely, you'll notice that there is a clearly visible distortion appearing on circular objects when you expand their strokes. It may seem OK from afar, but if you use those icons in an app on a small screen with high pixel density, it'll look veeeeeery bad... -
Expand Stroke bug (not accurate)
Molumen replied to debraspicher's topic in V1 Bugs found on Windows
Designer 1.7.1 I created a file that clearly shows the amount of inaccuracy after expanding strokes. I took white icons and grouped them on a black background. I duplicated the group on top of the first one, painted it black, and expanded strokes. The white color of the original, non-expanded icons that is visible, shows the difference between expanded and non-expanded. Each icon is about 40x40 pixels. The original afdesign file is attached to this post. icons.afdesign -
Expand Stroke bug (not accurate)
Molumen replied to debraspicher's topic in V1 Bugs found on Windows
This bug has been reported in Designer 1.6 as far as November 3rd, 2017. Since then, nothing has changed. In this post I even compared different vector drawing software with Affinity Designer (Adobe Illustrator, Corel Draw, and the opensource Inkscape). All perform way better than Designer at expanding strokes... :( -
Designer: Expand stroke is completely broken
Molumen replied to footof's topic in V1 Bugs found on macOS
2019 here, version 1.7 released, bug is still present. https://forum.affinity.serif.com/index.php?/topic/49241-designer-16-expand-stroke-tool-overly-aggressive-with-rounded-corners/&page=2- 124 replies
-
- bug
- expand stroke
-
(and 2 more)
Tagged with:
-
This sneak preview is a nice Christmas present from the developers. Looking forward to testing and buying Affinity Publisher!
-
There is a bug in 1.6.0.85 that doesn't appear in 1.5.3.69: Expanding a stroke, results in slight distortions of the resulting object. I've made two screenshots of both superimposed objects, the red one being the stroke, and the green one being the resulting expanded object. It looks like a regression, since to my knowledge, early betas of 1.5.xx had similar problems.