R34V3r

Glad it is n't a bug, I do use fill layers,

R34V3r what PDF export settings are you using and what application are you using to view the exported PDF in? I can only see this when I open the PDF (Exported using default PDF for Print) in Chrome and zoom in.

If you inspect the original branch objects prior to export and change the fill layer to be black you will see a white outline going around them - after inspecting further it looks like the source images you've used have a very hard edged, non aliased alpha channel which I think is PDF viewers to show those objects the way they do. I've attached a screenshot of the Alpha Channel of what of those objects from the PDF export show, and also what they look like with a black shape underneath (essentially making it easier to see the non transparent areas of the image). You can see that fringe line around them that is likely causing PDF viewers to show those objects the way they do.

I don't believe its a bug within the software, just a side effect of the original source images you used and how PDF viewers render them. The best situation in this example would to just be to rasterise the group containing the Fill layer and those two branch images. This way the branches no longer have any transparency and sit on a flat background.
 
This changes nothing. Replacing the Fill Layer with a rectangle still shows the problem when the PDF is exported and viewed in a browser (and a little bit, but not as bad in Acrobat), despite nothing getting rasterised.

The Fill Layer is being rasterized. If you do that rasterizing before export then nothing will be rasterized. Alternatively you could use a Rectangle in place of the Fill Layer, or best would be to just colour the Artboard.
 
I think that the behaviour of the Fill Layer affecting the rasterizing need of the PDF export is wrong and therefor a bug.

I mainly like to work on a surface for photo editing thanks to the great screen, pen input and touchscreen. I think a lot of people also like surface as a photo editing machine.
 
After seeing the Ipad version of Affinity photo it left me a bit wanting of the traditional desktop UI on devices like the surface however. It is a great UI experience when using the device in laptop/desktop mode, but when you want the paint with the pen for example, the experience turns bad quickly. I allready struggled with the fact that touch input is seen as the same as a mouse click instead of panning the canvas, so using the touchscreen as a main navigation tool is not that intuïtive, but after seeing the Ipad version, a lot more things pop out to me like "damn that's a good idea, I wish my surface could do that".
 
I was wondering if Windows 10's tablet mode could be more integrated with the application, like switching to the Ipads UI when tablet mode is activated, so that editing on a device like the surface is a lot more comfortable. This would mean that someone could just flip the keyboard and work in the document with a UI tailored for tablets, and flip it back to tablet mode when wants a more desktop like experience.
 
Are there plans to implement such features into the desktop app? Or is there a touch based UWP app in the works?
 
I was really blown away in how good the Ipad UI actually is, and I really think a more integrated experience into Windows' built in tablet mode will help a lot of people in their workflow.

I mainly like to work on a surface for photo editing thanks to the great screen, pen input and touchscreen. I think a lot of people also like surface as a photo editing machine.
 
After seeing the Ipad version of Affinity photo it left me a bit wanting of the traditional desktop UI on devices like the surface however. It is a great UI experience when using the device in laptop/desktop mode, but when you want the paint with the pen for example, the experience turns bad quickly. I allready struggled with the fact that touch input is seen as the same as a mouse click instead of panning the canvas, so using the touchscreen as a main navigation tool is not that intuïtive, but after seeing the Ipad version, a lot more things pop out to me like "damn that's a good idea, I wish my surface could do that".
 
I was wondering if Windows 10's tablet mode could be more integrated with the application, like switching to the Ipads UI when tablet mode is activated, so that editing on a device like the surface is a lot more comfortable. This would mean that someone could just flip the keyboard and work in the document with a UI tailored for tablets, and flip it back to tablet mode when wants a more desktop like experience.
 
Are there plans to implement such features into the desktop app? Or is there a touch based UWP app in the works?
 
I was really blown away in how good the Ipad UI actually is, and I really think a more integrated experience into Windows' built in tablet mode will help a lot of people in their workflow.

The Equations filter outputs a pixel layer - the text will not be editable anymore. For rasterised results you can also use the Mesh Warp Tool which offers visual control over the distortion.
Unfortunately it's not possible create this type of distortions keeping the text editable or as vectors no matter the program used (unless you edit the nodes of the letters manually).

I believe this feature is on the roadmap, but there is currently no efficient way to do it in Affinity Designer.

Not available in Designer but you can get close with some Equations if you also have Affinity Photo.
First create your text with varying font sizes for each character to get the basic shape (figure 1 below)
Then distort the text with the Equations shown (figure 2 below)
Use sliders A and B to change the effect
 
Here are the formulas
x+(100*a)*sin(360*x/w)
y+(200*b)*sin(180*x/w)

I wanted to illustrate the severity of the performance issue with a very simple situation. I want to know if this is happening to just me or others as well. I am having performance issue with both Designer and Photo on all 3 machines I have tested it on (Desktop, Laptop, Surface). To illustrate the severity of the problem I tested the following situation on Affinity Designer on my desktop with the following specs:
 
- i7 3770K 3.4Ghz CPU
- 16 GB RAM
- AMD R9 390X 8GB OC GPU
 
note that the issue is just as bad in Affinity Photo.
As you can see, Affinity is recognizing my GPU as the renderer and has permission to use all of my 16 GB RAM.

 
I started by creating a simple 512 X 512 document and loading a 512 X 512 PNG of a box in it. As I rotated the image you can see CPU usage jumped to 100% with a whopping 80% going to Affinity, If I do this on the same machine in Photoshop, CPU usage only jumps to 12% max.

 
I continued by scaling the image with shift-down (so no ratio lock). As before the CPU usage jumps to 100%, but you can also see fragments in the image from areas that still need to be computed. Photoshop has no issue with scaling the same box whatsoever.

 
So let's stress it a little more shall we? Masking is something I do every time I fire up Photoshop and Affinity, so I created a donut shape and but it as a mask on the box image, I also put an inner shadow effect on the image (something I use a lot as well). When scaling the image now my CPU level is ... you guessed it: 100%. Fragments are now really annoying at this point and happen a lot more often:

 
I continued by changing the donut a bit by making it a Half donut, Fragments are now a real problem:

 
Lastly, I converted the donut to curves, selected all corners with the corner tool, and rounded them all at once, In this operation there is a lot of lag present and if you wanted to reach an exact corner radius on sight, you wouldn't be able to do that:

 
when scaling the image now, fragments are still an issue but a lot of stutter occurs now as well, this lag is on a level that isn't workable anymore.
 
I feel like my 2816 core counting gaming GPU isn't used at all here and every pixel is calculated by my 8 threaded CPU. I feel like the only way I can have good performance would be to buy a Intel Xeon CPU with a lot of cores that costs 2K+. Note that in real life, 512 X 512 is a small size for content so the fact it has performance issues with this on a machine like this is unacceptable to say the least.
 
I don't want to bash Affinity here to be a bad application, because it isn't. It's feature packed and in some ways it does more than Photoshop. I really want to make this my Photoshop/Illustrator replacement because the workflow is much more streamlined and more fun. But as a Windows only guy, I feel like this is a bad port of a mac application and the weak performance is really a dealbreaker for me. I don't know if mac has the same issues but if so, they can't call this the smoothest image editor on the market, not by a long shot. I really want this issue to reach the developers and judging by the response on this forum, this might not be the most efficient way to reach them.

Hello, would it be possible to limit input from tools, specifically the brush tool, to only stylus input? That was we could freely place our hands on the screen, pan, zoom, etc. without the fear of making marks. As it is now, whenever I'm drawing or paining, I have to go back and cleanup marks made by my hand.
 
Thanks!

Hi,
 
I'd like to cutomise the wet edges of my brush on my PC version of Affinity Photo. But as you can see from the screenshot, I don't have the option to do so. I've checked my version of the software and it's 1.6.0.89. I've checked a number of brushes and can't find the custom dialog box that appears in the 1.6 features video at 00.21. Am I missing something?
 
Cheers,
Simon

Hi drippy cat,
These controls are missing in the Windows version. I already logged this to be looked at.

I've already fixed the EPS loading crash (will be available in build 82).

It's almost impossible for me to do smooth adjustments on hi-res images (ie. 7360 x 4912) with a small 1024 brush size for larger areas of the picture. Instead of limiting brush sizes to a small number of pixels, it could be to limit it to something related to the actual image loaded - for example match the longest side of the image.
 
PS: The limit of 4096 pixels in Photo Persona is also quite restricting for work on hi-res images.
 
Thanks in advance :-)
 

Vertical text align is an excellent addition.

I get that, but there are more forum posts that reported these issues, and eventhough I understand that ironing bugs and platform optimalisations take time, we didn't get a solid response that this serious issue is present and being investigated.
 
Instead, they seem to work on new features and other mac optimalisations like the touchbar. To the Windows user community, this does not give the feeling that they take their multiplatform strategy very serious, but is more like a slap in the face.
 
The least you can expect is a "we know the issue exists and are working on it" message.

I mainly like to work on a surface for photo editing thanks to the great screen, pen input and touchscreen. I think a lot of people also like surface as a photo editing machine.
 
After seeing the Ipad version of Affinity photo it left me a bit wanting of the traditional desktop UI on devices like the surface however. It is a great UI experience when using the device in laptop/desktop mode, but when you want the paint with the pen for example, the experience turns bad quickly. I allready struggled with the fact that touch input is seen as the same as a mouse click instead of panning the canvas, so using the touchscreen as a main navigation tool is not that intuïtive, but after seeing the Ipad version, a lot more things pop out to me like "damn that's a good idea, I wish my surface could do that".
 
I was wondering if Windows 10's tablet mode could be more integrated with the application, like switching to the Ipads UI when tablet mode is activated, so that editing on a device like the surface is a lot more comfortable. This would mean that someone could just flip the keyboard and work in the document with a UI tailored for tablets, and flip it back to tablet mode when wants a more desktop like experience.
 
Are there plans to implement such features into the desktop app? Or is there a touch based UWP app in the works?
 
I was really blown away in how good the Ipad UI actually is, and I really think a more integrated experience into Windows' built in tablet mode will help a lot of people in their workflow.

I think this problem occurs with AMD RADEON video cards after testing Affinity Photo on 3 different systems,
 
First system: Windows 10 home intel core i7 6700k cpu 4gz , memory 24,000 mb video card  NVIDIA GEFORCE 750 TI   memory 2,048 mb NO PROBLEM
 
Second system :Windows 7 Pro  Intel Xeon 3360  2.8 gz   memory   8,000 mb  video card  NVIDIA GFORCE GT 220    memory 1,024 mb , a little bit slower but  NO REAL PROBLEM
 
Third system : windows 7 Pro     intel core i7 3770 3,4 gz  memory  16,000 mb  video card  AMD Radeon HD 7800 series  memory 2,048 mb Very very slow and crash!!

AFFINITY PHOTO 1.5.0.45
 
Slow on my system too.
 
System specs:
Windows 10 Home
Processor : AMD A4-5000 APU
Video : AMDRADEON HD Graphics 1.50 GHz
RAM : 8,00 GB
System : 64-bits, x64-processor
 
..
Opening  RAW-files
..
 
A single Canon RAW-file (xxx.CR2) 23,3 MB (5184 x 3456 px) takes about 38 sec or more !!
In photoshop, opening THREE RAW-files (panorama shoot) takes about 7 sec ... Huge difference !!
..
Developing RAW-files
..
lack of performance
Fragments are anoying
etc.
 

This video screen recording explains what I mean.
 
 
 
 

I can't speak for anyone besides myself, but while some tasks in AP do use a lot of CPU power, I am not seeing any significant difference from what other apps would use doing similar tasks. In fact, AP usually seems to complete comparable tasks more quickly, maybe because it is multithreaded & uses all CPU cores when possible.

I wanted to illustrate the severity of the performance issue with a very simple situation. I want to know if this is happening to just me or others as well. I am having performance issue with both Designer and Photo on all 3 machines I have tested it on (Desktop, Laptop, Surface). To illustrate the severity of the problem I tested the following situation on Affinity Designer on my desktop with the following specs:
 
- i7 3770K 3.4Ghz CPU
- 16 GB RAM
- AMD R9 390X 8GB OC GPU
 
note that the issue is just as bad in Affinity Photo.
As you can see, Affinity is recognizing my GPU as the renderer and has permission to use all of my 16 GB RAM.

 
I started by creating a simple 512 X 512 document and loading a 512 X 512 PNG of a box in it. As I rotated the image you can see CPU usage jumped to 100% with a whopping 80% going to Affinity, If I do this on the same machine in Photoshop, CPU usage only jumps to 12% max.

 
I continued by scaling the image with shift-down (so no ratio lock). As before the CPU usage jumps to 100%, but you can also see fragments in the image from areas that still need to be computed. Photoshop has no issue with scaling the same box whatsoever.

 
So let's stress it a little more shall we? Masking is something I do every time I fire up Photoshop and Affinity, so I created a donut shape and but it as a mask on the box image, I also put an inner shadow effect on the image (something I use a lot as well). When scaling the image now my CPU level is ... you guessed it: 100%. Fragments are now really annoying at this point and happen a lot more often:

 
I continued by changing the donut a bit by making it a Half donut, Fragments are now a real problem:

 
Lastly, I converted the donut to curves, selected all corners with the corner tool, and rounded them all at once, In this operation there is a lot of lag present and if you wanted to reach an exact corner radius on sight, you wouldn't be able to do that:

 
when scaling the image now, fragments are still an issue but a lot of stutter occurs now as well, this lag is on a level that isn't workable anymore.
 
I feel like my 2816 core counting gaming GPU isn't used at all here and every pixel is calculated by my 8 threaded CPU. I feel like the only way I can have good performance would be to buy a Intel Xeon CPU with a lot of cores that costs 2K+. Note that in real life, 512 X 512 is a small size for content so the fact it has performance issues with this on a machine like this is unacceptable to say the least.
 
I don't want to bash Affinity here to be a bad application, because it isn't. It's feature packed and in some ways it does more than Photoshop. I really want to make this my Photoshop/Illustrator replacement because the workflow is much more streamlined and more fun. But as a Windows only guy, I feel like this is a bad port of a mac application and the weak performance is really a dealbreaker for me. I don't know if mac has the same issues but if so, they can't call this the smoothest image editor on the market, not by a long shot. I really want this issue to reach the developers and judging by the response on this forum, this might not be the most efficient way to reach them.

Hi R-C-R,
 
Do you work for Affinity and thus have access to actual statistics? If not, then you cannot assess the confidence of statistical inferences.  And, BTW, nobody is making statistical inferences in the first place, nor jumping to conclusions. For me, the code is slow and crashes often. This seems to be an issue with a sample population of others -- this is why I asked. I am not the only one. 
 
The Beta is closed, and we are now in Production. Are the developers interested in diagnosing the "why" that some group of Windows users are having issues? Again, I really like the design of Affinity and really would like it to be a successful Adobe replacement. I would be more than happy to help trap bugs.  
 
Cheers,
--Tim