Frozen Death Knight

Well, it is up to the community to make Linux a viable platform for developing software. If you want it you have to work for it. That's just the nature of open source. Epic is also a massive company with billions in their pockets. They have a long history of providing easily accessible tools and funding for game development through their Unreal Engine, Quixel, and donations to projects like Blender. They are charitable because they can afford it and because it is in their best interest to strengthen their own brand that encourages working within their ecosystem. Also, if Serif was so against people using Wine, why did the lead developer for Windows just post how to fix the GUI on Linux? Being against using Wine and not putting resources into supporting Wine and Linux are not the same thing.

Yep, exactly. It is also a play on words by replacing a word of a common phrase for making an insult to imply that.

None of those were insults, however. Which was implied from the start.

Or the more common term (check the plural form): https://www.merriam-webster.com/dictionary/son of a bitch

It is pretty obviously meant as an insult. What other phrase starts with "sons of"? The rest you should be able to figure out.

3D programs solve the naming issue with having batch renaming of objects. Just search for a specific name or object type, then change the name with different settings like based on selection hierarchy, all, etc. Would be nice if Affinity adopted that feature as well.

That is most certainly not a gimmick tool. It's one of the big reasons I didn't pick up Krita or Clip Studio Paint back when I was still actively searching for a Photoshop replacement. This comes off as being fairly out of touch in a pretty ironic way considering that liquify is one out of many transformation options for paintings, photos, etc. used for professional work. The non-destructive Liquify Filter was most certainly not a gimmick either, since now you can combine a lot of various transformation Filters without ruining your work underneath. Non-destructive features are professional features.

When I was doing UI design work with Artboards for school, the problem of pixel misalignment became a very, very big problem. I had to constantly change the placements of Artboards just to fix things like export slices having the wrong dimensions (every texture needed to use power of two, so a ton of errors), text and frames being misaligned so active and inactive versions of the same button did not match, etc., etc. The thing is that this problem can reappear depending on how you place Artboards. If you move an Artboard the misalignment problems can start appearing on Artboards that you previously fixed. This to me is the most annoying aspect of doing this type of work in Affinity. I was able to learn how to use the various snapping options to fix stuff (Pixel View Mode was a life saver as well), but it would be much appreciated if this kind of workflow was a lot more streamlined so very little tinkering was needed to get pixel accurate results.

@Abdurhman If your tablet has buttons you can keybind the rotation operators to your tablet and then hold them down to rotate the canvas. Some tablets support sliding values by having a ring you can drag with your finger, so there's that too. I know Wacom supports scroll up and scroll down, so you can get more fine adjustment rotations that way. Personally I use a regular keyboard for rotating using these keybinds for ease of access. I stopped using tablet buttons a long time ago unless it's to toggle between multiple screens. Would be cool though if modern Wacoms actually had a scroll wheel on the pen. Would make things so much easier...

The reason it was removed was because it simply was not even close to being ready. When I was testing the feature at the time there were multiple issues with it that could not just be solved with a flick of the switch. - The export settings were broken with tons of encoding artefacts across all settings. It just did not look good. - On Windows you couldn't even export with specific settings because it required an encoding library that is not even native on many Windows versions. - The camera options were limited and did not work work well with Artboards and large canvases. If you wanted the video to follow your brush strokes the camera would sporadically jump all over the place and you could just not keep track of what was going on. The camera would zoom in super far if you did small brush strokes, so you couldn't see the rest of the painting. If you were painting across several Artboards the camera would jump from canvas to canvas while being zoomed in a ton, thus disorienting the viewer. - If you disabled the camera following your brush strokes it would record every Artboard at the same time, thus making everything look small (no way to direct the camera or decide the zoom level). - There was no way of cutting stuff out in the timeline to decide where you wanted to start or stop recording. It only recorded the entire timeline and this was a big problem if you had literally thousands of history states to record from. Since you couldn't preview the results of your recording, you would have to wait for the recording to finish completely to have an idea if it was better or worse in quality. - No way to cancel the rendering of a video in a simple way. Once you hit that record button, the entire program started to freeze and you would have to wait. - It was very unstable and crashed a lot. - Rendering took very long to finish, even if the document was very simple like line art on a single layer. So yeah, it was removed for a good reason. Hopefully they revisit the idea someday since it is indeed pretty cool to have, but it has to address the problems it had before it should be even considered for an official release. Here is also a recording I made using the feature with the best settings that were available: 1649479991_Morevaluepracticing3.mp4.d8ec2ddae8bce168ba3fc267f8310e36.mp4

@AftemplateI agree that there should be easy ways to customise these. Like a presets system where you choose your own default Blend Options whenever you make a new layer/group/whatever. One trick I have found though is that you can actually select multiple layers at the same time and drag the value down to 1 so you don't have to manually change one at a time. Might be a good thing to know. 2022-04-22 23-30-15.mp4

As carl123 mentioned, there is the Channel panel with global lock for alphas. Though, one thing I wish was added is just simply locking alphas of individual layers. It's honestly simpler than having to toggle it on for individual tools.

Bump.

@DWrightThanks for documenting the problem! Though, I have to point out that Affinity actually supports this type of brush stroke on Mac. I know this since I tried it out during the 90 day trial you had some time ago. If you use a regular round brush with Size Jitter and/or Accumulation Jitter activated with the Pressure setting you will get a typical Photoshop type round brush. On Mac you will get brush strokes that remember the pressure of the last stroke when you shift+L click, which is identical to how Photoshop behaves. It's the Windows version of Affinity that is the outlier here. There are more Windows specific bugs that I know of as well that Mac are free from. I.e. Affinity on Mac remembers which layers were open in the Layers panel when closing and opening each program, but Windows does not. I actually made a thread where I documented some of the feature discrepancies I found during that testing period that I hope gets addressed, since they are all pretty annoying to deal with on a regular basis (only one of them has been fixed on Windows since then, which is the keybind shortcuts for changing brush size/hardness).

Adding this image to show the expected result (Photoshop) and the actual result (Photo) when shift+L clicking on the canvas.

Bump. What are the devs' thoughts on this?

Bump.

Bump.

Would be a neat quality of life feature, indeed! My one workaround I found to make it easier to work without relying on the Brushes panel is using the Synchronise from Selection operator. I added it as alt+C to make it easy to remember and access. If you want to brush with a specific brush type you just simply select one brush stroke and alt+C (if you have keybinded it) to copy the style for your Vector Brush Tool to use on every stroke.

@Gabe @Dan C I have been able to solve the problem of Merge Selected and Merge Down on my own, including fixing the moving layers bug and not being able to merge Pixel Layers with other layer types by making my own macros. They are also significantly faster than the current operators, since they use Groups and Rasterize as a part of the macro to achieve the exact same effect as these operators. I've had multiple times where Merge Down and Merge Selected have either not worked at all, slowed down Affinity, or even crashed. Meanwhile there are zero downsides with these macros and are also significantly faster than the current ones since they don't create any waiting times for the operators to finish. Nor do they crash for that matter. Here's another related bug thread where I managed to fix a bug with my macros. I suggest to the devs to incorporate these into Affinity instead of the current Merge Selected and Merge Down operators. They do everything I could ask for when merging layers. Here are some video demonstrations as well as the macros themselves. 2022-03-09 22-20-33.mp4 2022-03-09 22-38-45.mp4 Merging Macros.afmacros

It happens regardless of OpenCL being on or off. You need to grab all linked layers and move them to make the bug work when you undo the action. Redoing the action also creates the same bug, but it gives different results. It works both ways. Even tried this with just two linked layers with OpenCL off. Same results. I made a simple file with history states saved to show the bug in action. Hopefully this helps. Linked Layers Movement Bug.afphoto

Anyone on staff that has been able to reproduce this yet?

Anyone who has been able to reproduce my problem?

You're welcome! To be fair, the feature is pretty new to Affinity. Only came out last year with 1.9. I really hope they port it over to Designer in the next version, though. Feels weird needing to switch to the Photo Persona to use Duplicate Linked every time you need it. Anyway, here's a file I threw together quickly just using Symbols to play around with. You can do a lot of symmetry work in Designer and you don't need to work from the middle of the canvas to achieve it like in Illustrator, which to be honest has a lot of overly complicated steps to do live symmetry. Symbols Symmetry.afpub

@ahnaySymbols are the only practical way to do non-destructive vector symmetry in Designer that updates live as you go along. Though, the ultimate method is only achievable by owning all three programs while working in Publisher. There you have easy access to Linked Layers, a Photo feature which is basically Symbols but with more custom options, and they work with Compound Layers for non-destructive booleans, unlike Symbols. Here's a brief tutorial I made showing the power of Linked Layers: If you ask me, this feature should frankly be a Designer feature as well. It is insanely powerful and is a lot better than the Illustrator method, especially since it can be combined with Symbols, Groups, Compound Layers, etc. to create very complex patterns and be completely non-destructive.