NotMyFault

Yes, by design. If you nest layers as child to a parent, the parent needs to be a filled curve. Only the area inside the curve leads to nested clipped child layers. just convert an ellipse to curves. Use the node tool to inspect nodes and the area build by the curve. strokes will be rendered after clipping, and never reveal anything from clip-nested child layers.

Can you please upload the actual afphoto file? For the screenshot of transform panel, the move tool must be active, and the bottom layer selected in layer stack. and zoom level must be exactly 100% if you want to inspect sharpness. did you use the crop tool to cut off edges?

I‘m sure the process can be simplified, using designer only. But it will require some advanced methods. Basic idea: use Designer, and create one artboard per color. Create slices from artboards edit the individual content per artboard, use as many layers as you like. When finished editing, use export persona to export all slices as tiff or png create another document, where you place the exported files (linked) as layers in the desired sequence. ideally, you need to setup those 2 documents only once. You can activate continuous export, and the 2nd file should update the layers automatically. Exporting as png will flatten the layers, no need for manual merging, grouping etc.

Those issues re-occur occasionally. Just wait a few minutes/ hours. Happened to me recently, too. Mostly server side / cdn issues, you can’t do nothing on your end.

Hi, old bug reappears in V2.2: create new document create any circular (symmetric) shape in a off-center position activate move tool use transform panel to center hor and vert if you change to hand tool, position gets reset / not saved workaround: while move tool active, add pixel layer. Now you can change tool.

The ressource panel shows an image stretched extremely in x and y axis, with different factors. if you reset the scaling to 100%, you get the pixels in original size.

This file looks distorted right in Apple Safari / preview, unrelated to Affinity software. What SW are you using to get the „correct“ rendering?

Any chance you can upload the actual PDF? If it is private / not to be seen publicly, you can request a private upload link from moderators.

Hi and welcome. Westie will not answer, as he never logged in again after 2021. we would need more information for your specific case, e.g. size (both pixel dimensions and file size). Tone map Startup time is linearly proportional to pixel count (x * y), but only if the file fits into RAM entirely. Try tone map with a file of 1000x1000px, and stop the time. If you file is 10000x10000, it will take 100x the time. If you work on RGB/32 files, every pixel layer requires 16bytes, so 1Mpix 16MB, 24Mpix about 0,4 GB. So you may hit your RAM limit sooner than expected.

A reboot of the PC might help in this specific case. If not, Antivirus software maybe blocking the file - check those apps / logs. Sysinternal suite has a tool to show which process is locking a file - if nothing else helps. https://learn.microsoft.com/en-us/sysinternals/downloads/handle

Thanks for this update. Never the less, without a test document to reproduce the issue it will be impossible to work on the issue.

RPReplay_Final1695310159.mov

It is possible even today, with a workaround (snapping) duplicate the node active node snapping Handles and nodes will snap to the copy of the curve.

Can you please upload a test image as Photo V1 file, and screenshots or screen recordings of the exact settings used, and a full app window „after resize“ in both versions, zoomed at exactly 100%? There are many settings and activities potentially causing unwanted blurriness. If V2 Settings (Performance, view mode, view quality etc) or layer position/size/dpi differ, this can explain the issue.

By chance i found some discussion on hacker news discussing the fundamental underlying issue. https://news.ycombinator.com/item?id=37575377 It explains that all vector apps have this issue, and recommends the same workarounds i gave 2 years ago which are still valid.

Can you upload the actual test document? clipping works identical for shapes and curves, but it works only on closed objects with a fill, not on stroke colored areas. so I can only assume you used only the stroke color in the right side circle. Give it a fill color (and transparent stroke color).

You have 2 types of nesting child layers to a parent layer: regular child layer position / half way ident masking position / full ident depending on positions, nested layers may or may not impact or interact with the alpha channel of the parent layer.this will become obvious if the parent layer is not fully opaque.

The addition of data entry in V2.2 is great. can you please add the option to change the colors in parallel, e.g. by defining a start color (current color of layer) and target color, so that the objects change the fill / stroke color in defined steps (# of duplicates) similar to a gradient?

The issue is cause by using RGB/16 format (instead of RGB/8). The color values are somewhere between 139 and 140 (using 16 bits), probably it was a gradient. So info panel rounds these values. Set the color panel to 16 bit resolution, and use the sampler to get accurate values (divide by 2^8 or 2^16) If you want to use the info panel, use RGB/8. Otherwise it is useless, as it will round color values to 8 bit, and it seems buggy rounding up or down for same color values.

Please find a test image below with PT filters who show a mask where pixel of a chosen color (variable a) are located. The test image is a gradient from 0 to 255. So when choosing a, the column with the exact number gets highlighted in white- If you place your own test file, you can exactly spot those colors. The filter works both in RGB/8 and RGB/16. GRAY8 bug color 255.afphoto

Just try this old test image. It shows red color where no red is present depending on zoom level rendering bug at 100% rasterized blend rangeafphoto.afphoto

The rendering difference comes again from mipmaps rendering, and you file containing specific features who amplify issues: layer fx on image/pixel layers with semi-transparency I filed a feature request long ago to at least offer a (slow) accurate preview mode. You may add your vote.

There seems to be a huge gap between theoretical benefits and actual demand, plus implementation effort, compatibility issues (no other app capable). And you seem to be the first and only user requesting this feature. Would you (as developer in the place of Affinity/Serif) spend some 100.000€ development cost for such a feature? Or can Affinity sell some 10.000 more licenses just for this feature?

Thank you for the test files. Topic 1: Discrepancy Info panel / color panel As explained before, the info panel ist not trustworthy for exact color values, except in special cases (e.g RGB mode, sRGB profile). When using a GREY/8 document, there is no 1:1 mapping between GREY and RGB values. More serious, there is no way to inspect GREY values in info panel. If you set the info panel picker to „greyscale“, it shows percentage values, on an inverted scale based on K values. The only way to correctly inspect stored color values inside Photo is using special procedural texture filters (i can provide later). Similarly, specifying GREY values in color panel is limited to %, which won‘t exactly to convert to the 256 values stored in the file. Using RGB in color panel could lead to unexpected conversions (based on which color profile is used). Photo has issues and principle limitations with color management. Topic 2: blurriness by non-integer positions This topic has been discussed in depth before in other threads. To avoid, you need to follow (not centrally documented) best practices wrt move tool, snapping options, view mode, when and how to rasterize, etc. Summary It is possible to use Photo for pixel-art, but honestly it is not big fun based on countless UI traps and functional shortfalls like you observed with colors and layer fractional positions.

There are variois things which could break the workflow: a selection I still active. Single pixel selections may be unnoticeable. Try to use CTRL-D before adding / inverting layers how do you set the blend mode, by mouse or (new in 2.1 beta) keyboard shortcuts? A common issue is that keyboard shortcut depend on where the input focus lies, and some keys may change the function depending on position. Old bug: Some numeric input requires Enter key before getting applied. brushes are notorious for causing trouble. E.g. brush settings / brush not as expected. Try to paint on a new pixel layer to check if brush works as expected.