Jon W

Hi Jeremy, I'm afraid we have decided to keep the current behaviour for 1.8. We currently show all installed fonts regardless of language, in common with other non-Apple software. If we start hiding fonts of certain languages, there will be problems for any documents that already use such fonts. We would like to fix this properly by adding language filtering to the font list, but there is currently no timeline for this.

Not a regression - the previous fix was for iOS only, we now need to do something similar for Mac.

Please note, the term "pointer devices" here refers to devices that use the Windows Pointer Input API, i.e. Surface pen and Wacom tablets. We have always had right and middle click support for mice!

OK, well I've never seen ripples like that. Before we disabled them, the click ripples were smaller, thinner and whiter than those. The expected right-click feedback is more a little white circle than a ripple - see attached.

Hi Aongus, This shouldn't be happening. As Mark mentioned, we explicitly disable feedback ripples for clicking. I can't reproduce your behaviour, either on an Intuos 4 or Cintiq 13HD. It's a long shot, but have you tried turning off "Enable press and hold for right-clicking"? This unfortunately seems to be unavoidable. See 1. You should be able to long-press a word to invoke the selection UI.

Hi all, We have recently identified the cause of this problem, and we'll be fixing it in a forthcoming beta. Thanks, Jon

Hi all, There are several tablet issues which we have fixed for the next beta, including the cursor / brush outline one and right clicking. @Frozen Death Knight - disabling Windows Ink will make your tablet work like a mouse - you won't get any pressure information.

We did change the default - several years ago. I'm guessing you've uninstalled this time (which would delete your previously saved install location and product key) where before you always did an upgrade?

Yes it is. The thumbnail handler is used by Explorer to generate thumbnails for all our file types (.afdesign, .afphoto, afpub). Only one DLL can be registered for each file type. It absolutely has to be a shared component - sorry!

Hi meadow, The thumbnail handler is a shared component, which means that if you install multiple Affinity products there will be only one thumbnail handler, shared between all the products. This is why it's in a folder called "Common", and not the one you chose for the application specific files.

Hi monzo, This will be fixed in Publisher 1.7.2.

Hi Aammppaa, Have a look in %temp%\AffinitySetup. We've done this for the 1.7 betas.

Hi Dieter, Thanks for reporting back. I'm glad it's working now. I hadn't realised .NET 3.5 could be disabled; we will have to a check in the installer for this situation. All the best, Jon

Hi Dieter, Since build 109, the installer depends on the Microsoft .NET Framework. This should be available by default on Windows 7, but perhaps it's not working on your computer for some reason. Please could you try installing this: https://www.microsoft.com/net/download/dotnet-framework-runtime/net462 Then try to install Affinity Photo again.

I see. Is there even an AffinitySetup folder in %temp%?

Hi Dieter, The installer should have saved a log file called SetupUI.log in a subfolder of %temp%\AffinitySetup. Please could you post this file here? Thanks, Jon

Hi rubs, We're currently working on this - expect a fix in the next (or next again) beta. Jon

When you install the full version and enter your product key, the installer saves it in the registry. The beta installer reads the key from there. If it can't find it (e.g. if you're installing the beta on a different computer) it will ask you to type it in again.

Hi m850, I see that video was uploaded before we released 1.6.0.75. Does it still happen in that build? Does it still happen if you check or uncheck Preferences > Tools > High precision table input?

Hi sigepon, Have you tried enabling Preferences > Tools > High precision table input?

This is because Help.exe is missing due to an installer error. You can copy it from another Affinity installation to the program folder. However, you may then encounter a bug where the help viewer crashes if you have never switched themes. To fix this, go to Preferences > User Interface and click the Dark or Light button. Both these problems will be fixed in the next build. NB. CrashReport.exe is also missing, so if you're trying to report a crash, you'll need to copy that too.

Hi willernest, This should be fixed in the next build. Thanks, Jon

Hi PaulAffinity, There is always a risk of that, especially when hardware is involved. So we'll be adding an option to revert to the previous behaviour.

Hi abphoto, The reason we made these changes was to allow us to use input points direct from the tablet driver, instead of through the Windows mouse API. The benefits of this approach are: 1. Increased input point precision, independent of screen resolution and zoom level. 2. Increased input point frequency (especially under load), resulting in smoother lines. We are reverting this feature because to make it work reliably, more extensive changes are needed, which we have decided are unsuitable for a minor patch. The feature will hopefully appear in 1.6.

Hi everyone, This build includes support for high precision tablet input. We are now using features of the Wintab API which we weren't previously using, so driver problems may emerge that may have previously gone undetected. Wacom drivers have been known to exhibit problems if one is installed without uninstalling the previous one. If you experience tablet input problems in this build, please help us rule out this as a cause by uninstalling the Wacom driver and then reinstalling the latest driver. We will shortly be releasing a new build containing a preference to revert to the previous low precision tablet input method. Thanks, Jon