pekranodon

- Create a file, place down a square and apply a 45deg bevel with a radius to see the effect. - Save the file. - Create a new empty file, go to "File -> Place" and select the previous created file. - Rotate the placed file and see the bevel change as you rotate. Also shadows and embossing etc are all messed. This bug is present since several versions now and I wonder if there is any news on this. Will this be resolved at some point?

- Create an object and apply a layer style (i.e. some bevel or embossing). Press CTRL+C. - Create a new object at a different size (make it much bigger to best see the effect) - Select the new object and press ALT+SHIFT+V (Paste FX) or CTRL+SHIFT+V (Paste Style) and see how the effects are scaled wrongly. This is a inconsistent: - When you duplicate the object and scale it manually, then let's say change the radius of the bevel and then press ALT/CTRL+SHIFT+V, the styles are applied correctly. This bug was already reported over and over since v1.7 by numerous other users and I did not get tired to report it for all the releases since then. Is there any chance this will ever be fixed?

Hello everyone! Does anyone know how to fix the "low-polygon" look of the emboss filter? If I use the "soften" parameter, all I get is basically a blurring that destroys the inner edge. I tried to point out what the problem is in the attached files. This problem has been reported long ago, I wanted to bring it up again, as it is still not fixed. embossing.afdesign

Well, I did not want to be too picky about this as it's not relevant if it's the drivers, DirectXs or the OSs fault. Let's call it the platform then. Wording does not matter, my argument still stands: hardware accelerated software like this is done out there, so it can be done. So it is after all Affinity's fault that they don't do it. I guess they have their reasons, maybe it's resources, maybe it's the architecture, maybe it's something else. I am just saying, I have been able to smoothly drag a circle with embossing around in other user interfaces without the choppyness. So if it's fixed it's fine, but while it's not, I do not really care who's fault it is after all. To me, if it doesn't work as it should (=has functionality that it doesn't work), it's probably bad implementation/design choices/whatever and if it doesn't provide the expected functionality (=functions are not present at all), it's probably not suitable for that workflow. In this case, I just use it for light work where it's strengths shine. And for the other stuff, I (sadly) still go back to Illustrator. All in all I like the Affinity's software, but some things are just such a pity. I'd love to see proper working HW acceleration or for example fixing those bugs that are around since ages (like that "Layer effect's settings break when you copy them around on differently sized objects" or "Emboss/3D light sources do not rotate when used and rotated as in embedded images"). How it is done or who's fault it is, I don't care in the end. 🤷‍♀️

Edit: Found this: This offers some insight. You need at least Direct3D12, Feature level 12.0. Windows 10 as of April 2020. In addition, too old or too new AMD cards will not work and there will be problems with OpenCL on AMD cards.

Hm, I am with @Sclong134 here. It seems like a lot of assumptions and semi-knowledge is mixed and what comes out is a bit wishy-washy. To me it doesn't really make sense that hardware acceleration would not work on all setups where the OS provides it for. I am using a AMD-manufactured graphics card with the proper, up-to-date AMD drivers and with all diagnosis tools reporting fully functional hardware acceleration. It can't get more "off the shelf" than this. If Affinity does not run smoothly (as in "renders a simple shaded circle without choppy flickering") on a beefy "non-exotic" machine like mine, I really wonder where it does. Not only do tons of triple-A and smaller games get it done, so does Blender, Adobe's CS, video encoders and many others with similar workloads. So no, while I can accept the functionality just not working, I can not accept something like "it's probably something down the driver chain that is out of our control" as an excuse. ... so just curious, can anyone provide a screen capture of a AD running smoothly on a Windows machine? Just let's say, drag a gradient-filled, beveled circle smoothly around.

I also wonder what the problem could be. My system specs are pretty ok I suppose, AMD Ryzen 5900x with 24 cores, 128GB Ram of fast DDR4 RAM. Graphics card is an AMD Radeon RX Vega, of course everything with the latest drivers. With OpenCL + Hardware Acceleration activated with stock settings of AD (made sure it's set to use the dedicated graphics card though), still I get chunky movement when moving a simple object around. (see video). Can Affinity help here? What am I doing wrong? unknown_2021.09.25-16.40.mp4

Hello everyone! Does anyone know how to fix the "low-polygon" look of the emboss filter? If I use the "soften" parameter, all I get is basically a blurring that destroys the inner edge. I tried to point out what the problem is in the attached files. embossing.afdesign

Just upgraded to 1.9 (Windows) today and sadly those super old bugs are still present. Me and others reported them literally years ago, is there any chance they get fixed? If not, it's also an answer just this limbo of "We can't tell you anything" is a bit ridiculous after such a long time. Anyway, there you go: First thing: tl;dr: Create a rectangle, add an bevel for example, set the radius to 10px. Create a new rectangle with a different size and paste the first rectangle's style to the new one. Enjoy a totally different radius. This happens wether or not the "scale with object" box is checked and it's not proportional to the different rectangle sizes. 2nd thing: tl;dr: create a rectangle in Designer, add a drop shadow to the rectangle with some angle to it, let's say 45deg. Save the file as .afdesigner file and create a new empty file. Embed the first created file. Now rotate the embedded object. You will find that the drop shadow does not rotate with the rest of the file (this makes totally no sense. and appears with other effects too (i.e. bevels). Additionally, the effect changes upon zooming in and out...)

Ok, I'll just bump them then from time to time, when they come to my attention. 👍

The bugs I am reporting since over a year, are still present. 😕 Here's the links: @Sean P last time you forwarded it to the devs. Can you try to make them look into this again? Maybe with a tiny bit more .... "energy"?

Thanks Sean. Fingers crossed they are bump'ed high enough for getting fixed soon. Cheers!

This is still present in 1.8.4:

This is still bugged in 1.8.4:

This is still present in 1.8.4: