Gear maker Posted September 2, 2017 Share Posted September 2, 2017 I have a rectangle with a stroke aligned to the inside of a rectangle. I wanted another rectangle that went from the edge of the stroke to the edge of the stroke. Seeing as snapping doesn't detect the inside of the stroke I zoomed in. But as I changed the zoom the width of the stroke kept changing as seen below. Of course there are ways to get around this problem. But it does show that there is a problem. Using beta 8 on a mac running Sierra. predick and A_B_C 2 iMac (27-inch, Late 2009) with macOS Sierra Link to comment Share on other sites More sharing options...
Staff Chris B Posted September 4, 2017 Staff Share Posted September 4, 2017 Hey Gear maker, Ah yes I see what you mean. I think we may have something similar logged to this but I'll see what I can dig out and pass this over to the dev team. Thank you predick 1 How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials Link to comment Share on other sites More sharing options...
michaelmee Posted September 13, 2017 Share Posted September 13, 2017 Hi there 1.6 Beta 9, macOS Sierra, 2012 15" MBP Not sure if this issue is related or deserves it's own thread. Brush strokes are inconsistent at different zoom sizes. I can't predict what the export will look like. I mentioned this issue on the forum a couple of years back. I'm sad to see there's no progress is A_B_C 1 Link to comment Share on other sites More sharing options...
Staff Chris B Posted September 14, 2017 Staff Share Posted September 14, 2017 Hey michaelmee, This might be the same or similar issue so I'll leave it in here. It's all zoom related. I'm sorry nobody ever replied to your post from a couple years ago from Affinity. I'll get this looked at. The export at different zoom levels always looks the same but like you said, you're not sure which one you're going to get. The issue seems to be when there are a bunch of nodes at the end of a stroke or where you change direction and the stroke goes over itself. Deleting some of those nodes fixes this but I wouldn't expect you should have to do that. Leave it with me. A_B_C 1 How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials Link to comment Share on other sites More sharing options...
thi.mic Posted November 8, 2017 Share Posted November 8, 2017 Hello, I have the same issue and I´m using the latest Version: 1.6.0.89. I have a Windows 10 pc. Can sombody tell me how to fix it? Link to comment Share on other sites More sharing options...
Staff Chris B Posted November 9, 2017 Staff Share Posted November 9, 2017 14 hours ago, thi.mic said: Hello, I have the same issue and I´m using the latest Version: 1.6.0.89. I have a Windows 10 pc. Can sombody tell me how to fix it? I noticed nothing had changed since 1.6 was released so I bumped the bug report but I'll do it again to remind dev users are still struggling with this. As I said above, the only known workaround at the moment is to remove some of the end nodes that crossover but this is obviously time consuming. Sorry How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials Link to comment Share on other sites More sharing options...
michaelmee Posted November 21, 2017 Share Posted November 21, 2017 The way I see it, 'removing some of the end nodes' is not a viable workaround. How will the user know if enough nodes have been removed? The preview looks different at different zoom levels and may render/export differently than the preview. So the only way to really know is to remove a few nodes, then export, then remove a couple of nodes and export again ... All the while trying to maintain the integrity of the artwork. ...Then who knows what may happen when exporting at a different size, for example? This is profoundly unreliable and should have been dealt with long ago... It makes me perceive the software as generally unreliable – one of a few reasons I'm finding it difficult to make the move from Illustrator. Link to comment Share on other sites More sharing options...
Staff Chris B Posted November 22, 2017 Staff Share Posted November 22, 2017 Hey michaelmee, I said this is a workaround and that does not suggest it is a solution. I also acknowledged that this would also be time consuming and to some degree, ineffective, but until development decide to fix this, all I can offer is the workaround but I appreciate it isn't ideal. I will bump the bug report for you and remind dev this is still a serious issue that needs some attention. How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials Link to comment Share on other sites More sharing options...
michaelmee Posted November 22, 2017 Share Posted November 22, 2017 Thank you Chris. I appreciate the response. Link to comment Share on other sites More sharing options...
Recommended Posts