NotMyFault

Maybe i need more coffee, but i really don’t get what the actual problem is. normally the document doesn’t move at all, unless you use the move tool and drag the image Click a window slider or move inside its sensitive area use mouse, menu or keyboard shortcuts to zoom, move or rearrange the document views. Otherwise, using the mouse for other editing actions it only moves inside the image, without moving the image itself. So you are requesting a kind of „view lock“ disabling moving the image view (window) even when the move tool is intentionally active? Or is it something different. Again, sorry for me not getting the point.

It is mentioned in help that blend modes can be assigned to mask layers. But it does not give any explanation what this is good for. https://affinity.help/photoipad/English.lproj/pages/Layers/layerBlendModes.html There is another post where moderators explain it has no use (except for brushes used on mask layers)

I‘m referring to that statement. open cmd.exe, and execute: Set it will show the current settings, scroll to find the actual line. add the following line before the start Photo.exe into the „goPhoto.cmd“: Set <name>=„path“ Exchange <name> by the name of the environment variable Exchange „path“ by the path for the 1.x config file. ensure using proper „“ (only upper for Windows)

Can you please deactivate OpenCL. We have seen several similar reports where this solved the issue (Intel GPU driver issues) Edit>Preferences>Performance

When you add nodes to the default linear coverage map (without moving them), the anti-aliasing rendering changes every time despite just added at the already existing (linear) curve. This does not make any sense at all. To reproduce create new document of low resolution (20x20px) add vector shape of 1/4th of document dimension rotate by 20 degree open blend range UI (cog wheel) open coverage map UI recognize diagonal line add node exactly on line, in the middle of of last two right side existing nodes repeat several times. and inspect how rendering changes. To toggle, delete node by right-clicking node. Despite all nodes added exactly on existing curve, and not changing nodes or curve in any way, the rendering differs every time. Perfect example of "what you see is not what you get". The file is high res to include screenshots of coverage map. Pleas start with new doc in low resolution. coverage map adding nodes issue.afphoto

Don’t overthink. If possible: visit a camera shop where you can hold the camera in you own hands for 1/2 an hour and check you are comfortable with all physical knobs and dials. Check weight balance, reach of your fingers to buttons. View Finder. Display. Menus. etc. Physical comfort is extremely important! For guys with large hands, larger camera bodies are better than smaller Camera should support RAW files, without limiting too much e.g. frames/ second, number of images in burst situations or autofocus performance vs shooting JPG. All camera vendors allow to download manuals before purchase. Load them and read them. Most are just shy of 1.000 pages. Are you capable to fully understand all these functions, customize the buttons (if possible), and does the camera provide all the essential functions important to you? Do you know which matters for you? If you’re unsure or don’t understand these topics, just buy the cheapest camera you like (new or used) Use it for 3-6 month. Write down what you like and what not. Sell camera for any price. Buy a better one based on your findings.

To give this another direction: It would be really really great if Affinity (James?) would provide some tutorials how all this combines: Color opacity Layer opacity Fill opacity (from Layer FX) Blend differences wrt alpha /opacity of Fill layers vs. all other types of layers And other areas or arcane secrets like Brush Opacity Brush Flow Brush Accumulation Fun explosion: In combination with all these alpha blend options mentioned above And more arcane secrets of layer blending layers following normal alpha compositing blend rules (pixel, curves, ...) layers able to overwrite blend rules (PT Filter, alpha-impacting adjustments levels , curves, channel mixer: just set/define new alpha value) How all this integrates layers flat atop each other layers nested to description of ordinary layers layers nested to thumbnail of ordinary layers (masking / clipping position) layers nested to description of group layers layers nested to thumbnail of group layers layers nested to stacking groups (alpha reduced to 0 / 1)

Hi, i created a test file to compare how alpha blends in different situations, especially "color opacity vs layer opacity". The file contains 16 tiles 4 "large" tiles showing top: vector shapes, bottom: fill layers, left: raw, right: copy of left rasterized & tim 4 "small" tiles, showing left: red left color opacity / layer opacity : 50 / 100, right 100 / 50 blue top 50 / 100, bottom 100 / 50 As visible, the fill layer blend result differs from vector blend result, and rasterized layers blend results (bottom left corner) I strongly assume a bug with fill layers alpha blending - except someone from Affinity can provide a good explanation in layman's terms (or exact math formula) color vs layer opacity vector vs fill bug.afphoto

Yeah I added another post into the write-only part of the forum.

It would be great and avoid a lot of confusion for users if Affinity would disable all UI elements which are non-working (in specific situations), e.g.: blend ranges for mask layers (blend mode, anti-aliasing settings) Layer FX for mask layers refine button in selection brush tool for unsupported layer types (groups, masks, fill layers) is active Disable means gray-out and prevent clicking clickable elements which would open other UI elements which cannot work in the situation (refine mask for fill layers) Gray-out sliders, numeric input and all other UI elements not applicable (blend in blend range for mask layers)

@delpi767 @Ron P. can you please share example files and layer types, showing if it is related to fill layers, or a separate issue?

Curves seem to work, too. i used a curve with bitmap fill.

Thanks for your answer. Would it be possible to give the user an explicit message (instead of simply not working) when he is able to select a function and adjust lots of sliders, to avoid this kind of frustration? Or better, disable (making non-clickable) those UI elements when not working?

The it should not be offered in the first place, and should not start the refine process if clicked. What layer types will work, only pixel layers? Does it work for image layers? From a user perspective, I see no reason why not using it. The “by design” decision of Affinity to limit refine to (1) a single layer and (b) to pixel layers is by no means obvious for end users, showing an clickable UI for dysfunctional parts is really inconsistent UI. Photo stills shows lots of UI elements which do not work at all, confusing users, e.g.: Blend ranges for masks layer FX for masks

For those running into this issue and in need of an workaround: Create an group add nested fill layer with desired color add nested voronoi filter use circle (or any shape) as clipping mask to group

They become transparent which is another way of wrong. More visible if using a colored fill instead of white.

Have the same issue on my PC and iPad. It could be caused by using a non-pixel layer when starting selection: If you create a fill layer, make a random selection by brush, click refine cycle through the preview modes almost all seem broken when clicking apply, or create a mask as output result seems to be ok if you start with a pixel layer the selection is shown correctly. FullSizeRender.mov

Steps to reproduce: create any vector shape with current selected color (should be white for simplicity) immediately activate layer fx, color overlay Click again on color overlay name area to get the UI Element active (needing this as separate step is annoying. I understand that it might be handy in other situations) start changing the color from black to blue If you click on the right arrow to switch blend mode the color gets reset. (37s in video) it seems you need to “correctly” close the color chooser by clicking one of “approved” UI elements (Color Circle, blend mode name). It does not happen when clicking the blend mode name to open the list. FullSizeRender.mov

Another miracle of color magic when using transparency (alpha channel). What result would you expect if you blend two layers with 50% alpha, top in red, bottom in blue? Below you find 4 variants. It depends on using transparency on color or layer level. It depends on using fill layers or procedural texture layers. ad 1: I assume the difference (top left/right) may result from blend gamma. ad 2: using layer transparency gives same result as fill layer. good. Bottom right seems buggy: Using color transparency (settings alpha to 50% in PT filter) : Only the upper layer is visible. It seems PT filter overrides the alpha value, instead of blending with provided alpha value. color vs layer opacity.afphoto

If you nest (to thumbnail position) a voronoi filter to a circle shape, some edge cells get a wrong color (black instead of white fill). the circle uses fill in white, no strole. same if voronoi is atop the vector shape. If nested to „layer description“ level, some edge pixel become transparent.

When you use layer FX, Color Overlay, and switch through the blend modes, the color always resets to black.

In an ideal word every scale would have a reasonable UOM. As the slider already allows 1 decimal digit, it would be best to convert the old value 6 into 1px, or change the UOM to 1/6px. Photo is full of inconsistent UOM, just look at (Windows) defringe filter (Develop/Photo Persona) - a colorful mix of px and %. If % is used, it is unclear what the 100% reference is (100px, width of document, …)

The Voronoi filter has 2 parameters, both measured in px. For line width the unit or scaling is off. To get a 1px wide line you need to enter about 6. When entering 1 the line is barely visible (by anti-aliasing)

Suggest a 2 step approach: use Develop Persona / Lens correction straighten lower edge (rotate) straighten hor/vert as good as posible Click apply use Mesh Warp tool to further straighten top line

Well that is the well known formula. The formula itself is OK The real issue is one level below: When Photo & co starts anti-aliasing, it sets the opacity of the to be blended pixels according to their fractional share of pixel area. In case of 50-50, both get 50, and the blend formula advantages the top layer (explained before. But this choice of alpha is wrong! Only the upper layer should get the partial transparency according to its share. The lower layer should get 100% alpha. Then, using the same unchanged alpha compositing formula, we would get rid of all the issues we currently observe when anti-aliasing steps in for adjacent objects.