Stop enforcing Bilinear filtering

[Frank Jonen]

You keep bringing that "feature" back for some reason. Bilinear just means I get inaccurate rendering towards object edges and have no idea what the alignments are based on as they constantly change.

I now have to turn it off for each session. I'm not allowed to have it set permanently.

[Chris B]

Looks like a macOS bug. Windows remembers this. I'll let dev know—apologies. 

[Chris B]

Hi Frank,

Can you take some screenshot comparisons of what you mean?

The actual bug here is that you should not be able to switch to Nearest Neighbour whilst Metal compute is enabled as Bilinear is as quick as NN with Metal compute enabled.

However, if you're seeing a difference between the two, we'd like to see exactly why Bilinear is causing you issues.

[Frank Jonen]

Here's a quick way in Photo to illustrate the problem in a very binary way.

The clean looking one is NN.

What you're looking at is a single pixel column selected on the artboard edge. When that pixel column is filled, it automatically blurs and bleeds into adjacent colours. Yes, feathering and anti-aliasing are off.
This is not a vector shape but a pure pixel marquee.

The bug is only in Photo. In Designer the setting sticks until I reboot the system. In Photo it's until I restart the app.