Shmoo Posted January 22, 2017 Share Posted January 22, 2017 Any idea about this? It's a curve with an inside stroke but for some reason the background color is shown on the outside by a very thin line. You'd think this is such a micro thin line you can barely see it on vector display but when you export this to bitmap (png) this line becomes even more visible. It's a simple rectangle with stroke inside 2px. Converted to a curve. None of the other properties have this problem, only the inside stroke. Quote Hardware Mac mini (late-2014), 2.6GHz, 16GB RAM, Intel Iris 5100 Graphics iPad Air 16GB WhiteSoftware I love, and you should get :wink:Affinity Desinger - Affinity Photo - Sketch - Coda - CodeKit - iA Writer - Dropbox - 1Password Link to comment Share on other sites More sharing options...
R C-R Posted January 22, 2017 Share Posted January 22, 2017 I see this too (with the fill color showing as a very thin line, rather than the background color, if there is one). I also see some odd blocky artifacts in the stroke if I zoom in to extreme magnification levels. Quote All 3 1.10.8, & all 3 V2.4.1 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7 Affinity Photo 1.10.8; Affinity Designer 1.108; & all 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7 Link to comment Share on other sites More sharing options...
gdenby Posted January 22, 2017 Share Posted January 22, 2017 I've noticed something similar in various files. I suspect it is a rendering artifact. When I zoom in repeatedly, the thin line is slightly pixelated, then smooths out. But no matter what level of magnification, it doesn't get any thicker on screen. Doesn't make any difference if the shape has been converted to curves, or not. Quote iMac 27" Retina, c. 2015: OS X 10.11.5: 3.3 GHz I c-5: 32 Gb, AMD Radeon R9 M290 2048 Mb iPad 12.9" Retina, iOS 10, 512 Gb, Apple pencil Huion WH1409 tablet Link to comment Share on other sites More sharing options...
pixelrain Posted January 22, 2017 Share Posted January 22, 2017 Did a test, the only blue contour i see in 1.5.2.54 is if i have the object selected. I might have seen this happen if you have stroke set to anything other than "None" with no stroke set "0 px". Quote System specs: Win 8.1 Pro 64bit | AMD PhenomII X6 1055T @ 3.0Ghz | 16GB DDR3 @ 1600Mhz | WD10EZEX | GTX 960 4GB | Wacom CTL-672 Link to comment Share on other sites More sharing options...
Shmoo Posted January 23, 2017 Author Share Posted January 23, 2017 No it's not a selection stroke thingy. It's the color of the fill behind the stroke for sure. Thing is, I've never seen this happen before. I work with Designer from the very first version but this is the first time I notice it. Maybe it has something to do with me upgrading from El Capitan to OS Sierra. I read someplace it maybe could have something to do with how computers rearrange floating points. Let's say if you set a fixed number to be 10.000 the computer generaties it as 9.999 in real life. It's a bummer really, because I'd like to use this vector artwork in Sketch and when exporting it from Sketch to bitmap format it really makes this line visible and ugly. Quote Hardware Mac mini (late-2014), 2.6GHz, 16GB RAM, Intel Iris 5100 Graphics iPad Air 16GB WhiteSoftware I love, and you should get :wink:Affinity Desinger - Affinity Photo - Sketch - Coda - CodeKit - iA Writer - Dropbox - 1Password Link to comment Share on other sites More sharing options...
R C-R Posted January 23, 2017 Share Posted January 23, 2017 For me it is also the color of the fill of the object sort of bleeding out around the stroke. I am still using El Capitan so it does not seem to have anything to do with upgrading to Sierra. Quote All 3 1.10.8, & all 3 V2.4.1 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7 Affinity Photo 1.10.8; Affinity Designer 1.108; & all 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7 Link to comment Share on other sites More sharing options...
pixelrain Posted January 23, 2017 Share Posted January 23, 2017 I'd first assume it's a bug within the app than in the OS. Maybe try an older version to check ? Quote System specs: Win 8.1 Pro 64bit | AMD PhenomII X6 1055T @ 3.0Ghz | 16GB DDR3 @ 1600Mhz | WD10EZEX | GTX 960 4GB | Wacom CTL-672 Link to comment Share on other sites More sharing options...
JimmyJack Posted January 23, 2017 Share Posted January 23, 2017 This has been around since day 1...... unfortunately. It's on the list. But, it was put on the list so long ago I believe it's worth squeaking the wheel :ph34r: . Quote Link to comment Share on other sites More sharing options...
Staff MEB Posted January 23, 2017 Staff Share Posted January 23, 2017 Hi Shmoo, This is a side effect of the rasterization routine. You may also encounter this when the boundaries of two object overlap over a contrasting background. Please check this post from Matt for additional details. Quote A Guide to Learning Affinity Software | Affinity Quick Reference Link to comment Share on other sites More sharing options...
JimmyJack Posted January 23, 2017 Share Posted January 23, 2017 Yes I should have been more clear. Not a bug. But on the list "to be looked at", and possibly improved. Quote Link to comment Share on other sites More sharing options...
WeekendProducer Posted February 15, 2017 Share Posted February 15, 2017 This drives me crazy. Windows version has the same problem so it's the way the App (doesn't) works (well). I need that stroke inside and having a background outline visible around the stroke is a serious flaw. It's a BG (fill) color as if you change the fill color the thin line around the stroke also changes it's color. ASAP fix needed. 1) https://www.dropbox.com/s/lm4roklhr6nezee/Affinity%20Designer%20stroke%20inside%20fill%20outline%20visible.PNG?dl=0 2) And another completely different example with no strokes at all. So completely different PROBLEM. This is just an object path visible as a thin white line no matter of the fill color (I changed the fill color it's always visible as thin white line) but ONLY when and where there is a child path within and crossing over the edge of the parent path (see layers panel). https://www.dropbox.com/s/tzm0958i0epq2gi/20170215%20Affinity%20Designer%20object%20borders%20visible.PNG?dl=0 P.S. direct link included for both examples as the adding image as the dropbox link is not working... Quote Link to comment Share on other sites More sharing options...
WeekendProducer Posted March 8, 2017 Share Posted March 8, 2017 I produce digital content for web, so a per pixel precision is a must. I won't go into all the nonsense of moving and creating objects ending with subzero values (size and position) no matter the "force pixel alignment" and other tools checked, in addition to all above, after exporting (creating slice from some object within artboard placed on some colored background) I got those subpixel thin hairlines visible!!! On the end product?!?! Visible on 1:1 So I just end up with sending to my client this BS (attached) as a solution - unfortunately I noticed the exporting error too late. Check the thin blue right and bottom border that should not be there. Slice size exactly matching the object size. Why should we not consider this as a bug that needs ASAP fix please? Quote Link to comment Share on other sites More sharing options...
Staff MEB Posted March 9, 2017 Staff Share Posted March 9, 2017 Hi WeekendProducer, Welcome to Affinity Forums :) I'm sorry you are experiencing a few issues with the app. Regarding you first post, the first point is a known issue we already have logged. For the second point please go to Affinity Designer Preferences, Performance section and check Use precise clipping. The issue from the post immediately above this one seems a bug. Can you please attach the original afdesign file so we can take a look at this? You can PM me the link if you don't want to post it publicly. Thanks. Quote A Guide to Learning Affinity Software | Affinity Quick Reference Link to comment Share on other sites More sharing options...
Valan Posted February 28, 2021 Share Posted February 28, 2021 This is annoying, and I was looking for a fix. Looks like the Fill and Stoke are anti-aliasing precisely and separately. This leaves a mathematical 'gap'. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.