Jump to content

vczf

Members
  • Posts

    15
  • Joined

  • Last visited

  1. This bug reproduces reliably on all Affinity products (Publisher/Designer/Photo) on Windows as well as Designer for iPad. Prior discussion: Demo: out.mp4 nested layer pixel bounds.afpub
  2. With hardware acceleration enabled on Windows, I can sometimes get the behavior shown in @thomaso's example. However, the nested-layer bounds-clipping reliably occurs in my test file no matter if hardware acceleration is on or off. A clearer example video attached. 2022-06-25 17-20-44.mkv
  3. @NotMyFaultI see that the zooming refreshes the canvas on my file also, thanks. That's much quicker than hiding and showing the layer.
  4. @thomaso Based on the more erratic way your pixels are disappearing, I think these are different issues. With the nested layers in my test case, the behavior of the strokes being "clipped" by the layer bounds is very consistent and repeatable. In your case, it looks like rectangular chunks of the canvas are failing to update.
  5. I managed to whittle down the file to a simple case with nested vector layers. See attached. @thomasoThat vector-masked rectangle did not have an effect when I deleted it. The key is a top-level layer (with vector mask, disabled or enabled makes no difference). Then nest a vector layer inside it, and try to use pixel layers inside the child layer. @LeeThorpeTurning hardware acceleration on or off doesn't have an effect. @firstdefence I'm on Windows, but this also reproduces in Affinity Designer for iPad, and I now suspect it's universal. nested layer pixel bounds.afpub
  6. I can't pin down exactly what's triggering this. Maybe hardware acceleration related? The strokes stop rendering when reaching the previous bounds of the parent vector layer. Hiding and showing the layer resets it. 2022-06-24 00-52-31.mkv
  7. The selection logic takes only the stated width of the stroke into account, not the visual width when altered by the pressure curve. This means that if you draw strokes with significant pressure sensitivity (e.g. for dynamic linework with pencil or vector brush tool) you will not be able to select visually distinct strokes by clicking on them. You instead have to use the alt-key to select behind, or use the layer panel. Tested on Windows as well as iPad. Likely universal across platforms and Affinity products. 220531 selection bug.afdesign
  8. Just adding my interest in this. A common flow for me is selecting some objects, grouping them, and then naming the group.
  9. I actually haven't encountered this issue in Photo or photo persona publisher with the color picker. However, the alt-menu mainly gets in my way while using the move tool in combination with the Alt key to "select behind" an object and then pressing space to pan the canvas, while the menu is still focused. I have found an AHK solution to disable Alt menu acceleration in Windows. Affinity is unfortunately special in its input handling. While this script seems to completely disable the Alt-menu behavior in other programs, it only inconsistently blocks it in Publisher. As a workaround... the menu acceleration can be avoided during use of the move tool (without a script) by making sure to press Ctrl-Alt instead of just Alt to "select behind." I wasn't able to replicate this issue with the brush's color picker, and this solution will not work for the brush because Ctrl-Alt is bound to changing brush size. https://www.youtube.com/watch?v=vRld4bVFrpU
  10. @Lee D I have been dealing with this behavior, and it makes Designer extremely annoying to use for drawing. The selection logic takes only the stated width of the stroke into account, not the visual width when altered by the pressure curve. This means that if you draw strokes with significant pressure sensitivity... for dynamic linework... you will not be able to select visually distinct strokes by clicking on them. You instead have to use the alt-key to select behind, or use the layer panel. This occurs on iPad as well. With this current behavior, Affinity Designer is nearly unusable for drawing in vector persona with pressure sensitivity. It's more difficult to edit vector strokes than it would be to just work in raster because it is maddeningly difficult to select nearby curves when working in mid-to-complex areas. Some example videos I've seen seem use an inking process without pressure sensitivity, and then adjust the strokes as needed after the fact. If most people are using a similar process, that may be why this issue has not affected as many people. 220531 selection bug.afdesign
  11. @Halex Switching to High Precision stopped the double-tap stamp behavior for me with my Wacom Intuos Pro.
  12. I believe this is a solved problem (if brute-force) with supersampling antialiasing. I took the exported SVG from AD into Inkscape, rendered it at 4x resolution with no antialiasing, then downscaled 4x to get back to the original resolution. No more seams, and nicely smoothed anti-aliased lines. I really hope a feature of this sort can be added to fix exports. The current behavior does seem to be the norm for every vector program I've tried, including Inkscape and VectorStyler. However, it's both surprising and disappointing. From a logical standpoint, perfectly adjacent shapes should perfectly occlude what's behind them! Having to add background fills or extend the shape beyond its bounds with strokes defeats the neatness of geometrically precise shapes. Left: AD export at 400% magnification Right: 4xSSAA with Inkscape and ImageMagick at 400% magnification
  13. I had seams everywhere in the first thing I made with Affinity Designer, and I thought there was just something wrong with my technique since I am new to vector drawing. This is very frustrating and strange behavior. There are even seams between the stroke and the shape when you set the stroke to be external to the shape geometry. This makes no sense. (Edit2: workaround) Edit: trying out a few other vector programs. Inkscape and vectornator have antialiasing seams. Vectorstyler trial seems to avoid them on png export.
×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.