5argon
-
Posts
41 -
Joined
-
Last visited
Posts posted by 5argon
-
-
If I create a symbol on this artboard, and then delete it in the Symbol tab, the child will lose all it's orange line (correct) but on pressing Ctrl + Z, the child reverted to dashed orange line. (wrong)
-
Ah, right sorry. This is on Windows. I just recently built a new PC so it's out of habit to submit a bug here..
-
Here's a better one. I deleted everything in the file and it still crash on clicking Slices tab. What's special about this file is that it had been created from copy pasting of an another file at first, then modify its content to diverge from original.
What I did is to New a file, then copy paste the only artboard in the SetIcon file, then I am able to export.
-
The attached file crash 100% when clicking on the Slices tab when about to export in Export Persona.
-
When clicking the + button, the scrollbar snaps to the highlighted entry, which may not be this entry. By common sense it should instead snaps to the new variant that was added as a result of this + press regardless of currently highlighted entry. See clip, I have to scroll back up if I didn't select the entry before pressing +
-
Hi, I have a follow up on this. I want to ask is it really a design that one must align an object to a whole pixel to ensure correct export?
I think the correct requirement should be depending on object's size rather than it's coordinate. For example these are 4 empty artboards, all the same 1024x1024 integer size. Common sense would be : if I slice-export all these artboards I would get all 1024x1024 images. (For this instance it is a setup for icon design) However, because their artboard position (on "world" space, outside the artboard) aren't perfect integer, the resulting slices are either 1024 or 1025.
-
Hi, thank you. One other work around is to use 99% hardness, if someone stumbled on this thread and want to have some hot fix for hard brush that you do want some consistent aliasing.
7 minutes ago, Sean P said:My intuition says that on the size like 9, 11, 13, and 15, even though there is that protruding pixel, when dragging horizontally/vertically that pixel should "smear" itself linearly instead of repeating in intervals. Is this a bug also? Or the brush works like a repeatedly firing gun instead of like the actual "brush"?
Top : Actual result of size 11 pixel brush
Bottom : Expected result of size 11 pixel brush
-
Here, back to aliased brush. There is definitely some bad size on the whole number. And also I sometimes notice that even when in the one brush scaling, I could get a different result on the same number sometimes.
-
Here, even with pixel brush, when scaling around (or even type in the number) I can get 2 version of 10.0 px and 16.0 px brush, where there is a repeating pixel problem and the one that looked fine.
-
4 hours ago, Sean P said:
Hi 5argon,
Your brush sizes are non whole pixels, so you will get this aliasing behaviour, as the brush doesn't sit completely on a pixel boundary so is divided over 2 pixels. I would suggest you try looking into the Pixel Brush if you want completely hard edges.Hi. I get what you meant. What I want is actually non hard edge, a consistently aliased brush regardless of size. And all other software I used do not suffer from this problem no matter the size is whole pixel or not. For example, this clip is from Clip Studio Paint. It gives consistent aliasing edge and no sharp edge mixed in no matter what the size. And also, there is no size that produce the "upper repeating dotted pixel" like Affinity Photo. And when painting, I randomly get "bad brush" when scaling around the size. Brush size scaling is done arbitrarily by the painter and we should not have to concern whether the size is whole pixel or not.
-
New clip, sometimes you can see it is going to be wrong from the preview when adjusting brush size too.
-
In Clip Studio Paint there is one feature that's very good for painter. When you hold down E instead of just pressing it, releasing the key will return you to the previous brush. It's a huge productivity boost and better than eraser at the back of the stylus. Could we get something similar?
-
*This is in fact Affinity Photo for macOS, mods please move it to that forum. But I am not sure it could be reproduced on pixel persona of Designer as well.
In this clip I show that the Basic brush with 100% opacity / flow / hardness, can produce unexpected aliasing depeding on brush size.
To suppliment the clip, for example, at this size there are parts with unaliased result similar to when using the Pixel Tool. Except that it happen randomly along the other edges that were correctly aliased.
At this size, it produce spacing artifacts in interval.
These are sizes that produce expected, consistent aliasing result.
Device : Wacom Intuos Pro M
Affinity Photo 1.7.2
-
Look at this 3 slices here, when I press Create Slice button one of them got 80 instead of 79 width. All of them has a slight variation, but essentially a copy and paste and no variation goes out of their common outer silhouette bound.
-
2 hours ago, GabrielM said:
Hi @5argon,
This is not a bug.
Adjustments/masks inside "empty" groups are applied to anything below the group. When the group is populated with an object, the adjustment/mask only applies to objects within the group.
Thanks,
Gabe.
Is that so? Then it is still a bug because the mask square is rotated 45 degree to diamond position, but it is clipping as if it hadn't rotated in the clip.
-
When adding layer effect to one symbol, other symbols follows as expected. However pressing merge and it now applies to only that one symbol, a bunch of unlinks appeared, the orange line became dashed, and undoing cannot restore back the linked state.
Related question, how can I intentionally unlink some "attribute" that it is showing here? What are available attributes that I could unlink manually? How to relink them? Any documentation of this "dashed line" symbol? -
After removing the layers inside a group with mask one by one, on the last layer removed, the mask will punch through other layers. Sometimes undoing back will also produce weird mask but generally it make the mask work again. Also happen on the beta version.
-
-
19 minutes ago, GabrielM said:
Hmm.... very odd. I could not replicate this even on a 2014 Macbook air. Can you attach a screenshot of your Desigenr preferecnes > Performance window?
It's on bottom left in the video. Plus I turn off Metal in the vid and it didnt make any difference.
-
-
When detaching mask, the graphic is expected to restore to unmasked state immediately. If I detach by dragging to above this is no problem. But if below, the masked residues remains on the screen until I click/drag/zoom around multiple times for it to update to unmasked state. The same happen if using undo to revert from detached mask that was dragged to below.
-
An expected result is that clicking Create Slice on PFXIcon should correctly frame the active area, similar in size to the frame of transform handle in Designer Persona in the first image. (plus take account of stroke, so all stroke pixel won't be clipped)
But seems like it misunderstand something and create much bigger area. (probably related to group scaling and that its content are symbols) -
See the video clip or try it in the file. The squares were duplicated and arranged in grids. But sometimes it is not able to snap to it's previous instances. (Column 2, 4th element and column 3, 2nd element) The snapping is expected to work 100% as it is a square and it has been duplicated.
-
18 hours ago, MEB said:
I 5argon,
Welcome to Affinity Forums
Do you mind attaching the afdesign file shown in your screenshot for us to take a look please? You can delete all other non-related content/layers or I can provide you an upload link if you wish to keep the file private. Thanks for your report/support.Here you go. (Designer version is 1.7.1 by the way) repro2.afdesign
Smart duplicate didn't take account of target position's artboard
in V1 Bugs found on macOS
Posted
I refer to the function where if you duplicate something and it also tries to repeat the previous transformation as well. It works, but if that transformation results in the object going to a new artboard, it requires a "nudge" to have it really entering that artboard layer hierarchy wise.