-
Posts
6,692 -
Joined
-
Last visited
Everything posted by NotMyFault
-
How to avoid clickbaiting threads?
NotMyFault replied to thomaso's topic in Affinity on Desktop Questions (macOS and Windows)
The logic is simple: match threads created by user X, and remove/hide them for me, specifically for the „unread content“ view which is what i use the most. I want to find mostly new threads with zero or a small number of answers, but not those of user X. The regular „ignore user“ function catches all remaining issues. i simply don’t want to get bothered by any thread of user X started, as even replies from otherwise valued users cover those topics (from X) which I don’t want to see at all. -
Hi, I often create a group with a symbol layer inside, allows me to deactivate a single instance on group level without deactivating sync. This does not work on iPad, as the UI mistakes a symbol as group and only offers to ungroup which would destroy the symbol instance.
-
You are free to post feature requests in the feedback section of the forum. Walt and I simply explain the current situation and try to help other forum users to solve or work around issues. The discussion about hw acceleration issues has already filled countless threads, I’m no longer interested as every argument has been stated multiple times. Nothing against you, I’m just tired.
-
How to avoid clickbaiting threads?
NotMyFault replied to thomaso's topic in Affinity on Desktop Questions (macOS and Windows)
Maybe it is possible by a custom adblocker rule. -
It is complex. Using HW acceleration to achieve highest performance is a bit like formula 1 racing, but on unknown race tracks which could change the surface conditions and layout after you finished your car and fitted tires for dry wether. Affinity actually compiles a GPU program from source code live for every filter or adjustment you add during editing. They cannot test every possible combination of GPU and GPU driver version, and especially newest version could be a challenge.
-
When you invert the mask of the filter and paint in only small areas with a brush width distance to the edges this does not impact the result in any way. If you want to blur the full area, you may activate „protect alpha“, but the edges will always look slightly different.
-
The blur effect is barely noticeable, this has been raised as issue multiple times before. I recommend to not use the blur brush, it is next to useless in my experience. Instead, use a non-destructive workflow: add a blur live filter of you choice. set a suitable strength, e.g. 2 to 8px radius zoom in to exactly 100%. This is really important invert inherent mask of filter choose brush tool select a basic round brush (one with hard edge, not a soft one) choose color white set opacity to 25% Set hardness to 80% paint in mask This gives far better control over strength of effect and allows to reduce or remove blur any time later if overdone or applied in wrong area.
-
When the brush preview shows a transparent circle on a non-transparent pixel layer, this is a bug which occurred multiple times. It could be related to hardware acceleration/ gpu driver, or using an outdated Affinity release.
-
Almost all adjustment layers modify color channels in a way which can be „exported“ as LUT. The functionality is build in to Photo. So those websites cheat a little bit. They don’t sell presets, but LUTs which mimics the same adjustment results without using the adjustment layers. This means you can’t use them as e.g. slider presets which can be fine-tuned in the original adjustments.
-
Very high CPU usage with Procedural Texture and Mesh Warp
NotMyFault replied to M1000's topic in V2 Bugs found on Windows
This is probably by design and no bug. A get high CPU utilisation on Mac mini (up to about 50%), too whenever the PT filter is active, and a bit lower (30%) when inactive. As long as Photo renders the file correctly and with good refresh rate and reacts snappy to any user input there is no reason to assume any bug, as the sw works as designed. -
If you copy the mis-behaving layer into a new document and use "expand stroke", you see the same issue that the stroke color gets converted as fill color, but the inside/outside is buggy as the curve is self-overlapping. This is a bug of expand stroke, and I think already reported. It becomes visible in the exported PDF as the combination of features (probably a pressure profile on the stroke, and/or layer FX) leads to Affinity apps expanding the stroke do to feature discrepancy between Affinity functionality and PDF.
-
Alternatively, use a non-destructive workflow: add a curves adjustment (or hsl or levels or exposure …) adjust curves to achieve the burn effect you want. It is applied globally but invert the inherent mask use any suitable brush, color, opacity, hardness and paint over mask to apply effect where you want it the big advantage is you can adjust the strength of the effect any time
- 7 replies
-
- burn
- tonalrange
-
(and 2 more)
Tagged with:
-
You can create a new square brush in the brush panel. if you want to burn all lightness areas, use the brush tool and set the blend mode of brush to e.g. linear burn and choose a mid grey color. Experiment a bit with brush color and opacity.
- 7 replies
-
- burn
- tonalrange
-
(and 2 more)
Tagged with:
-
Color rendering wrong when mixing vector and pixel
NotMyFault replied to NotMyFault's topic in V2 Bugs found on iPad
This has been fixed for iPad in some of the later V2 versions. Info Panel for Desktop is a different topic. -
effects of cloning brush goes beyond the brush circle
NotMyFault replied to srg's topic in V2 Bugs found on macOS
The outline shows roughly the 50% opacity topology line. Outside below, inside above this threshold. -
effects of cloning brush goes beyond the brush circle
NotMyFault replied to srg's topic in V2 Bugs found on macOS
As Loukash said, the brush is probably a soft brush, either by the brush „image“ itself or by reduced hardness settings. it is always advisable to use the non-destructive workflow: add a new pixel layer set clone tool source to current&below or layers below. this allows to inspect the editions separately, e.g. a soft brush will create a soft result on the new pixel layer
