vincentlepes

Thank you both, I was unable to find that thread when I was searching but am glad it is documented. I felt I had seen this issue before v2. Seems like an easy thing to fix, since it appears to always be an unexpected Y offset when things are recalculated as new artboards are created, but I know sometimes there's more to it . Some developer forums have an area where users can vote on bug fixes and feature requests, do we have something like that here?

When working in Photo or Designer, on a pixel layer, using the command select all works on a new document but stops working as soon as I introduce an irregularly placed artboard. The same behavior with the invert pixel selection. I will attach a video and file to show the problem in action. It appears to happen as soon as the artboards are no longer aligned with each other but I am not positive, I just know it appears after creating new artboards that shift around in location. As it stands now, the only workaround I have found is to make a mask, invert the layer directly, and then make a new pixel selection to get an inverse pixel selection. Similarly, I can workaround the select all by using a rectangular marquee with snapping. However, these workarounds are cumbersome. While preparing a video to demonstrate this, I believe I have discovered that it all falls apart when an artboard is placed vertically higher than the initial document/artboard, suggesting that when the Y values shift to accommodate the new position is when the bug appears. There could be other factors, that's just what I observed. selection issue.mov Affinity Designer/Photo 2.2.0 MacBook Pro 2019 15" MacOS 13.3.1, 2.3GHz 8-Core Intel i9 Radeon Pro Vega 20 4GB 32GB 2400MHz DDR4 selection issue.mov selection issue.afdesign

There are appears to be a bug with the miter join setting. The results change unpredictably when moving nodes, and the results change even when simply zooming in and out without changing a thing. Video and file attached. I'd like to be able to draw my outlines with the vector pencil tool using miter join to get clean lines with sharp corners, but my results differ greatly from what I saw in online tutorials doing the same thing. The corner often flies way off the curve, and the miter setting value doesn't make a lot of sense to me. Let me know if this is user error. I have also confirmed this happens on a fresh, new file. Select pencil tool, draw a tight zig-zag/squiggle shape, turn up miter join until corners appear. Corners don't match the arc of the curve, and change at various zoom levels. I will add that file as well. I've noticed this happens on sharper corners that have a curve coming into them, and it can be replicated using the pen tool. It just happens constantly with the pencil tool because it creates a lot of fluid curves. Even when I tweak and simplify the curves, the corner changes at different zoom levels. Affinity Designer 2.2.0 MacBook Pro 2019 15" MacOS 13.3.1, 2.3GHz 8-Core Intel i9 Radeon Pro Vega 20 4GB 32GB 2400MHz DDR4 Screen Recording 2023-09-21 at 1.23.02 PM.mov Screen Recording 2023-09-21 at 1.47.25 PM.mov 2023-09-21 Characters.afdesign New squiggle.afdesign

I changed the group blending mode to "normal", and the result became consistent. I'm leaving this here in case someone can explain to me why this changed anything at all. From the help document: "Any layer or object can have a blend mode assigned. The default blend mode is 'Normal'—no special compositing is applied. For a group, the default is 'Passthrough'. When set, the group itself has no special blend properties of its own, and passes on the blend mode of its parent layer." If the default is "normal", and the group has no parent, why is "passthrough" creating an unexpected result? If it isn't inheriting "normal" from the document default, what is happening here? Thanks in advance for any insight!

Hi all, I may be missing something here, but I have a pixel layer with a mask nested within a group. I want to move the mask to the group so I can add additional layers within that will obey the mask. However, when I move the mask from the nested layer to the group layer, I get a completely different result even though I believe the results should be the same since the only layer in the group is the pixel layer that has the mask. Can anyone see what I'm missing here, or is this perhaps a bug or inconsistency in the software? Attaching a video to demonstrate--look at the difference along the edge of his hair as I move the mask between layer and group. AP-Mask-Layer-Group.mov

@Dan C The upload finally finished, it's called 3.psb

Will do, thanks!

Just to be safe, I will upload the old version again. I think I might have uploaded it in reference to a color issue I had on the same document in another forum post. I can share it with you, just not publicly as it was purchased.

I believe I did upload the files to the Dropbox link, let me know if I am remembering wrong and I will upload again. I sent you a previous revision from around the time of the video with a filename "Book Design (OLD VERSION).afdesign". The "old" version is because I had made changes since, that version is from Google Drive version history so it may not be 100% match but it does demonstrate the behavior. I also uploaded the latest, same filename without the parenthetical. I'm happy to send again, if needed, just let me know! Thanks!

I believe this is truth

The original PSD in Photoshop is set to RGB/8 (according to the mode setting), sRGB-IEC61966-2.1 (according to the color settings panel) and "Linear Color Space" (according to the convert colors dialog). If there is a better place to check, please let me know, I've been getting rusty on Photoshop as I've been making the switch over the past couple years. I thought it was in the info window, but they have changed the UI recently and if it was there before, it isn't anymore.

Also if I change the setting away and back, and then save, with the toggle still on "Convert", it converts as expected. It is only by opening the dialog, making no changes, and pressing "OK" that nothing happens. It would seem what is in error is what color space Designer reports the document is in before making changes, perhaps? AD-Color-4-Reselect.mov

It would seem that if I select "Assign" in the Designer Document Setup > Color tab, when I submit, the document updates correctly. When I choose "Convert", it updates the color space and converts all the colors to what they looked like in the incorrect color space. If I leave it alone and choose ok, it still shows the incorrect color space and does not update. See what I mean: AD-Color-1-Save.mov AD-Color-2-Assign.mov AD-Color-3-Convert.mov

1: works as expected 2: Problem still exists 3: Problem still exists I messed around and the problem persisted, but I think the document setup color settings tab is the source of the issue, I will follow up with more details.

@- S - great catch! The document setup dialog showed 2.1, so I thought they were the same. Photo sees it differently. I went back into the dialog, and discovered if I toggle between "Assign" and "Convert", the document updates to the correct color space. Very weird, but now I can create in the correct gamut again, so that's a win! I will try the other troubleshooting exercises as soon as I have a chance and report back. I have fixed it for my needs, but there still may be a bug at play with that dialog or perhaps the file. Thanks all!