Search the Community
Showing results for tags 'overwrite'.
Found 4 results
Hello everyone! Does anyone know if there is a way in Photo to stamp alpha values? While RGB values will overwhrite A, A does not get picked up by the stamp or it will simply not overwrite RGB. Here are two images to illustrate what I am talking about: Image1, showing where I pick up colors: Image2, showing where I want to stamp: In Image2, parts of the green should be overwritten by alpha ("erased"). If this is currently not supported, could anybody move this to feature requests? Thank you for any help! Best wishes, Shu
Hello there, I've been using the Affinity products for a couple of days now and I'm really amazed by their capabilities. However, there seem to be a few disruptive bugs regarding the brush dynamics, both in Photo and Designer. (Note: I decided to name the bugs for future reference) "Prokaryote bug": When using the velocity control on a paint/pixel brush (Photo and Designer), there always appear big blobs at the beginning of each stroke followed by a much thinner tail, no matter how fast or slow I’m drawing. This bug has been reported here and there almost 2 (!) years ago and, yet, remains unfixed. Also, in the brush dynamics window (almost) every slider is called a “jitter”. The word “jitter” is a bit confusing as it implies that the brush is modified randomly over time while, at the same time, corresponding to how fast, or with how much pressure, etc. you draw. In other words, not completely (!) random. This doesn’t seem to be standard/what’s happening in affinity. In my understanding those “jitters” only adjust the (output) amplitude of the effect produced by the (input) controller and don’t yield actual jitter. If randomness is desired, the only option in Affinity would be to set the property to random and, thus, lose control. You cannot have both (control and randomness). Am I correct? And is this the intended behaviour? If so, the use of another word might be advised. "Diamond bug": When velocity is set for a vector brush or pencil, Designer creates jagged (diamond-shaped) brush strokes. If the stroke is rather straight and drawn with high velocity, the rough edges will stay. If the stroke is longer and curvier the jagged stroke tends to turn into a much smoother stroke as soon as the mouse button is released. Nonetheless, the stroke doesn’t seem to reflect the actual velocity changes applied and sometimes the jagged lines don’t disappear entirely. This behaviour has been demonstrated here as well. (Images 1 and 3 are before releasing the mouse button, 2 and 4 are after) "Umbrella bug": Additionally, the (vector) stroke often ends very abruptly in a big semicircle (umbrella), especially when drawing circles/spirals. All of the above-mentioned bugs appear not only in editing mode but also in the exported files: So, it’s not just a visual bug. They, unfortunately, render the velocity control pretty much useless. They also occur with clone brush, dodge & burn, sponge, erase tool and any other brush descendant. Other bugs: When the screen resolution is set to 1366 x 768 (typical laptop display resolution) or lower, the toolbar gets cut-off in Photo. I am aware of the option to undock the toolbar in the view menu but this is quite cumbersome when you start Photo for the very first time. CRITICAL: Batch processing of photos into the same directory and in the same file format as the original files (e.g. to create a lower quality copy) will result in overwritten (yes, deleted!) original photos without any prior warning. A message and an option to append some text to the exported file names would be strongly required. This, also, has been reported (here).I hope this was somewhat helpful and I'd love to see these issues resolved in the near future. Best wishes! ------------------------------------------- Affinity Designer Version: 184.108.40.206 Affinity Photo Version: 220.127.116.11 Operating System: Windows 10 Pointing device: Mouse
thomaso posted a topic in Affinity on Desktop Questions (Mac and Windows)... or is it usefull/working to have more than 1 beta installed to compare versions? Usually I do keep the previous beta versions to be able to compare just in case. Last week it happened that a beta appears to have overwritten a feature which - as far i remember - did work well in its previous beta. (https://forum.affinity.serif.com/index.php?/topic/659-mask-layer-selection-page-size-instead-object/?p=2226) So I wonder: Are beta versions independent to each other – or do they use some common files? In other words: Does a former beta still work exactly like its original beta stage - or are some files in common use and features get overwritten by a beta update (pref, system, library files)?