STGM

I've never experienced this bug with any of the V1 Affinity apps on any platform. On a side note, would having both V1 and V2 apps on the same system cause any conflicts?

I believe that this bug is only linked to Affinity Designer on mobile devices. So far I haven't noticed it on Desktop/Windows. Has anyone experienced crashes with a high zoom level on Win/MacOS?

Zoom level appears to be what's causing the issue. Thank you so much for the clarification! Any hope that this bug could be fixed with the next update?

Yes, this happens with a fresh file every time I create one. And I'm guessing that it has something to do with a document that includes multiple artboards because it doesn't happen with a file that has no artboards. At least, not as far as I've tested it. When I try to replicate the issue on the sample files that come with the app, it doesn't happen. But again, I just opened a couple ones to try it and never really edited anything myself. Worst of all, there doesn't even need to be any objects in the document. When I create an empty document with 5 artboards, as soon as I hit any of the Split View modes, the app crashes. I tried it with just two artboards too. Same thing. Below, I've attached two demos: Demo 1: Document with 5 artboards, each 32x32px (size is irrelevant, but nonetheless). No paths/curves in the whole document. Demo 2: Screen recording of me creating this exact same document and then trying to use the Split View modes. DEMO-2_screen-recording.mov DEMO-1_empty-doc.afdesign

Thanks for the explanation! I see what you mean now. I just had it all backwards in my head.

Problem #1 Problem #2 Problem #3: Color picker is still sampling incorrectly I reported this issue a while back and I'm so disappointed that it hasn't been fixed in version 2. If anyone wants to follow along, then try this... Create two shapes and add different fills to both. Now select one shape and sample the color from the other with the eyedropper tool. Both shapes will seem to have the same fill. Or do they? Select one of the shapes again. Then go to Select > Select Same > Fill color. What happened this time? Both shapes very likely won't be selected for some reason. And while in Affinity Designer 1 both shapes would have different color values, in Affinity Designer 2 the color values appear to be identical (at least during my review). So what causes this problem? Could there be something wrong with Select Same? Not sure. But if you created two shapes with the same color to begin with -- and then you tried Select Same afterwards -- both shapes would probably be selected. So to sum it up... Select Same works when: You pick a color and then create any number of shapes with that same fill. Select Same does not work when: You create any number of shapes and then apply the same fill to all of them by sampling with the eyedropper tool.

Problem #1 Problem #3 Problem #2: Adding new swatches The palette dropdown menu seems to switch back to the Recent Colors list every time a swatch is added to a custom Document palette. Nonetheless, the palette set dropdown still displays your custom palette. As soon as a new swatch is added to the list something weird happens. The dropdown menu displays the correct palette set created just seconds ago. But the palette box appears to switch to the Recent Colors list because suddenly I can see a bunch of them in the area. This always makes me think that I've added multiple fills to my custom palette. It's confusing. Try to replicate this yourself while following these steps: Start a new document. Create an empty Document palette. Create 5 rectangles. Remove their stroke color. Select each rectangle individually and apply a different fill. All 5 shapes should have unique fills. Select one of the rectangles and save the swatch to the empty palette created moments ago. This is where instead of the currently selected fill, suddenly all recent colors you picked appear in the box. Just as if they were all added to the set.

Currently on the iPad version of Affinity Designer 2 the Grid Settings button seems to behave differently compared to the Snapping Options button. When the former is inset/pressed down, all enabled modes are turned off and vice versa. This doesn't seem normal to me. Is this behavior intentional by design or a bug?

Problem #2 Problem #3 Problem #1: Split View Mode This is by far the worst bug that I discovered during my workflow because it puts a complete halt to my entire process and forces me to export every artboard to its individual file. The problem occurs when I create a document with multiple artboards. In my case, I was designing an icon set with artboards @ 32x32 px. When my progress reached artboard #5, I had to use the Split View Mode in the Navigator studio to review the outline of the shapes. Unfortunately, Affinity Designer crashes every time I try to select one of the modes for the split screen, just as reported by another user in the forum. I tried using the Split View Mode with fewer artboards in the document but the outcome still didn't change. Attached to this thread is a sample file that you can download and test to see if you get the same result as me. And for anyone else who wants to replicate the issue from scratch, try doing it this way: Create a document with at least 5 artboards. Leave them as they are. Don't change their coordinates. Each artboard should have at least 2 vector layers. Every layer should contain multiple of objects (say, up to 10). There should be at least 1 default shape (rectangle, ellipse, et.); 1 curve made with the pen tool; and 1 stroke (open curve). Crash-Test.afdesign

As far as I'm aware, this option is only available for a select few of the shapes under the Shape Tool. What if my object is any closed path (curve) created with the pen tool, or even a rectangle that had been converted to a curve? Personally, I think that the Boolean operations in Affinity need major improvement. Here's another example: As you can see, once you expand a very simple path like a circle, you get two added nodes in the middle of the segment there. That circle was expanded individually from the shape below it; nothing there to mess with the geometry. Then I take it one step further. In the example on the far right I used a Boolean operation to unify both expanded objects and I got even more nodes (some are nested just under existing nodes). Now, someone might say that both shapes in my example follow the exact same outline, and that those added nodes are just the result of the program trying to squeeze two paths that occupy identical mathematical coordinates into one. Well, it doesn't need to be two overlapping paths either. Same thing happens regardless of how close to one another the paths are, or how identical in form they are. Also, the left side of the final combined shape looks as it should (no added nodes). The right side is a Frankenstein! How come one side of the compound path turns out great and the other doesn't? That's just bad!!!

Hello, everyone! When I round two adjacent nodes of a rectangle with the Corner Tool all the way up and then either 1) expand the stroke, or 2) bake the object's appearance, I get two overlapping nodes where the imaginary anchor points forming the arc would meet to a full stop (I think). I hope I just made it sound clear 🙄 Pic below This may become a problem when I have to sumbit my work for approval. But what's even worse is that sometimes the shape would subtract what appears to be the end cap of the curve from its own geometry (see pic below). And when you have several artboards full of hundreds of paths each, then that becomes a horror story. It could take me a whole eternity just to clean it up. I've played around with all stroke properties, like meter ratio, end cap type, etc. Nothing really solves the problem. And another thing. Why is Affinity Designer adding extra nodes where there shouldn't be? If you look at the second shape from the left in the screenshot, you'll notice the added node between the top and right one. What the... ?! So far I've never experienced this with any other vector software, including Illustrator, Inkscape and Vectornator. Before publishing my post I actually checked with both programs to see if I get the same problem. And just to be fair, I also copied and exported the shape directly from Affinity Designer before applying the same actions in Illustrator, Vectornator and Inkscape. No problem there whatsoever. Not even extra nodes being added to simple shapes like the one from my example! I'm also attaching a demo document for you guys. It's the same one from the screenshot above. This thing is driving me nuts. Any ideas? double-overlapping-nodes.afdesign

Hi Nathan! That's good to know! I can't wait for the fix. In the mean time, is there a convenient workaround? I rarely work with global colors when I'm exploring styles early on in my process. I use the copy [value] menu option from the color panel on the iPad and then just paste that color in the attributes of another object. It seems to work. That way everything is recognized by the select same > fill/stroke color function and I can easily grab all similar objects if I decide to re-color them later. How is everyone else is doing it? Just curious. Thanks a bunch!

I'm experiencing the same problem on my iPad. It's been this way since I downloaded Designer the first time a while back. Has anayone been able to find a solution yet?? I've already been through several iOS and Designer updates since I first noticed this bug. I uninstalled and re-installed Deisnger. I rebooted my iPad a bunch of times. Nothing worked. All my files in the Files app still appear with the generic Deisgner logo and no thumb preview. I read elsewhere on the forum that it's likely an Apple caching issue or whatnot. Be that as it may, why is Affinity Designer the only app that has this issue on my ipad?? Not even the free apps that I'm using have ever had this bug so far. Also, I think that several iOS updates and my fresh install of Affinity Designer would have sorted this out by now, wouldn't they? Alas, that's not the case.

Hello, everyone! I've had enough of trying to find a solution to a problem that started occurring ever since the "select same" function was added. Today I decided to call it quits and give this forum a shot. If anyone knows why this annoying thing is happening, I'd love to know the reason. Perhaps I'm doing something wrong? THE PROBLEM More often than not, the eyedropper tool isn't able to sample and apply the right color to whatever shape is currently selected. The sampled color may look the same to the naked eye but it's actually ever so slightly different from the original fill. A closer inspection at the colors referring to the color panel shows a minor difference in values. Unfortunately that's all it takes to render the "select same [fill/stroke color]" function completely useless. In fact, if you tried to invoke the "select same" function by referencing one of the newly colored objects, chances are that the original one won't be selected because it doesn't share the same color data. This also works the other way around, where you would reference the original object and then the newly colored paths would be completely ignored from the selection. I have no idea why it is happening. I've tried to troubleshoot this issue both with the dedicated eyedropper tool and the little color picker tool available right in the color panel. Same results happen almost always. I should also mention that the issue is present on both desktop and iPad versions of Affinity. My devices and apps are all up to date. EXAMPLE DOCUMENT SETUP My current project is an icon set that contains 10 icons. The document consists of 10 artboards with 2 layers in each artboard; one for the outline and another layer for flat colors. Again, that's 10 artboards + 2 layers each and a minimal number of shapes. However, anyone can try this with a very basic setup. I just replicated the scenario on a 1920x1080px document with no artboards inside. I created 5 rectangles and applied different fills to them. Then I recolored all of them using the aforementioned method with the color picker. Finally, I selected a random object and attempted to add all objects that shared the same color to the selection with select same > fill. Result - the object that the color was sampled from is omitted from the "select same" function, while all others obviously share the same color data between each other and are therefore recognized by "select same > fill". I look forward to hearing opinions. Thank you!