Search the Community

If you're having issues exporting to PDF, you may be advised by the Support team to enable PDFLogging. This will allow our developers to look into your issue further and hopefully figure out what's causing the issue. For Windows: Create a folder called temp on the root of your C:\ drive so you have folder at C:\Temp\ Run PDFLibLogging.reg - this will create a registry entry that enables logging for PDF Export Run Affinity and export to PDF and then click OK to accept the error message. Go to C:\Temp\ and send the newly created PDFlib.txt file to the support team as requested Now run PDFLibLoggingRemove.reg to return your settings back to normal PDFLibLogging.reg PDFLibLoggingRemove.reg

Unfortunately, we're aware of an issue affecting users on macOS Ventura when trying to save to an external drive such as a flash drive that has a FAT partition. You will be able to initially save to the flash drive as expected but any subsequent saves to the same file will give the error: "Failed to save document. Save failed because access to the file was lost. The document must now be closed." This issue is logged with our developers for further investigation but saving locally and to a non FAT partitions is unaffected.

Thank you Serif/Affinity team for the new release! can't wait to use Affinity V2 apps... Could anyone please explain what the difference between Affinity V2 Universal License (Multi-user) and Individual Affinity V2 Universal License. is Multi user version like a floating license? Also, is there a discounted upgrade price for V1 user?

Hello guys, Could you please help me? When I take the Frame text tool, unwanted black line appears there (in all the suite) - I attached the screenshot - doesn't happen when I use artistic text tool - the outline color is off, even outline itself is off Thank you, hopefully you know, whats going on

I have an issue with UI scaling the brush variable settings on the side of the workspace when in my usual landscape orientation (iPad) The three options for hardness, size & opacity bleed off the screen and make them unusable at the higher or lower values (see pictured example) These options fit on screen just fine in portrait mode, however I almost never work in portrait mode, and having to flip my iPad around every time I need to change brush values is annoying. Is there a future fix for this?

Pros: MSI had an installation success rate of ~85% (and we have many requests to our tech support team for v1 install failures). MSIX promises a 99.9% success rate. MSI requires admin privileges to install. MSIX installs per-user, but files are deduplicated so that disk space isn't wasted. MSI apps are not sandboxed from other applications, meaning other applications can break those apps (we have seen this with several third-party apps in the past). MSIX apps are sandboxed to prevent this. MSI updates require a manual download of the full ~550mb installer which must be manually installed. MSIX can perform in-app delta updates which are smaller and faster. MSI updates can only be performed one at a time. MSIX can update all three apps simultaneously. MSI cannot guarantee that an uninstall will leave your machine in the exact state prior to install. MSIX installs are segregated and don't rely on the registry or special filesystem locations meaning an uninstall always leaves you in a clean state. Installation and app data paths are cleaned on uninstall. MSI apps cannot integrate with Microsoft Photos app to provide "Edit In..." style features. MSIX can. MSI does not require a digital signature. MSIX does (this means any MSIX that appears to be from Serif, will be guaranteed to be from us and only us). Cons: MSI can allow the user to change the installation directory. MSIX can move installed apps to different drives, but it cannot choose a specific directory (due to the sandbox). See below: MSI can allow an option to install a desktop shortcut. MSIX doesn't provide this as an option, but you can pin the apps to either the Start Menu or the Taskbar. There is also the secret Shell:AppsFolder location in Explorer that allows you to right-click or drag the icon to your Desktop for a shortcut as a workaround if you need it. MSI has easy discovery of undocumented app locations for launching from a third-party. MSIX hides the install location due to the sandbox, but we use App Execution Alias to enable this scenario. You can find the aliases in the following location: C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityDesigner2.exe C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityPhoto2.exe C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityPublisher2.exe Remembering to replace username with your Windows username. Also, those paths are already in your %PATH% variable so you can often launch them without even specifying the full path, e.g. just AffinityPhoto2.exe. There are bugs in some third-party applications with the App Execution Alias , and the next post includes aflaunch.exe as a work around if you need that instead.

This is one my side projects for 2022. I run a FaceBook group on the BOAC Speedbird aircraft and "The BOAC Speedbird Adverts" book which contains 133 rare adverts (B&W and colour) from 1940-1970. The adverts were cleaned up using Affinity Photo and the cover was put together with Affinity Designer and of course the book was put together using the Affinity Publisher. For more info visit https://speedbird.shop

Hello Folks, here is my feedback - I loved v1 and it was a no-brainer to buy v2 instantly. But I am a bit disappointed - and I would like to give you some feedback why: Affinity Photo: I expected some AI involvement, like background removing. Even the iOS Photo app has great results doing so, but Affinity Photo stucks at this point where it started with v1 years ago. Also some KI upscaler would have been great. Affinity Designer: A lot of people requested and it is one of the main gaps between Affinity Designer and Adobe Illustrator: Auto Trace: Transforming pixel files into vector files. All apps (on windows): Pls add std. executable Files instead of the "new" format which has so much limits (no chance to choose a specific path etc). So tricky to get manual Shortcuts to the Desktop and Affinity Folder. Also: I understand due to new possibilities v2 cannot be opened by v1 Apps, but there should be the possibility to export from v2 into a format v1 can read (with limitation, like live filters will cause permanent etc.) Hopefully you will hook up (like in the past) with new features like I mentioned with upcoming Versions. In the end, yes I am disappointed but a lot of the new features are really good! Not everything is black and bad

I installed and registered my three new Version 2 programmes yesterday. I also had the chance to work with them, yesterday. This evening 11/11/22 I wanted to play a bit with them and they do not initialize. They do not load fully.

Is there anyway to switch off the preview pane from the export dialogue box? It is taking time to compose the preview and to a certain degree it is not needed for me.

I am trying to run the Affinity suite on Windows 11 ARM64 (4GB RAM), installed from the Microsoft Store. I expected that the apps would be slow but usable under x64 emulation, but all three (Photo, Designer, Publisher) crash after displaying the splash screen (and a warning about lacking a DirectX 10 graphics card and falling back to software rendering). The Windows Event Log shows the following backtrace: Application: Photo.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.Runtime.InteropServices.SEHException at <Module>.Raster.Hardware<Raster::DefaultImplementation>.GetHardwarePossible() at Serif.Interop.Persona.Settings.PerformanceSettings.get_CanUseHardwareAcceleration() at Serif.Interop.Persona.Settings.PerformanceSettings.get_UseHardwareAcceleration() at Serif.Interop.Persona.Services.InteropService.Initialise() at Serif.Interop.Persona.Application.OnServicesInitialised(Serif.Interop.Persona.Services.IServiceProvider) at Serif.Affinity.Application.OnServicesInitialised(Serif.Interop.Persona.Services.IServiceProvider) at Serif.Interop.Persona.Application.OnStartup(System.Windows.StartupEventArgs) at System.Windows.Application.<.ctor>b__1_0(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.DispatcherOperation.InvokeImpl() at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object) at System.Windows.Threading.DispatcherOperation.Invoke() at System.Windows.Threading.Dispatcher.ProcessQueue() at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef) at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame) at System.Windows.Application.RunDispatcher(System.Object) at System.Windows.Application.RunInternal(System.Windows.Window) at Photo.Application.Main(System.String[]) I have the saved event log if that is of interest to the developers (please contact me privately).

The error "The data area passed to a system call is too small" can appear when trying to run Affinity V2 on Windows. This issue is related to how Affinity V2 installs into the WindowsApps folder and Microsoft SQL Server. The below KB update from Microsoft should resolve the issue: https://support.microsoft.com/topic/kb4073393-fix-the-data-area-passed-to-a-system-call-is-too-small-error-when-you-start-a-desktop-bridge-application-on-a-sql-server-5ae0994d-023a-d32b-3aad-526500b53993

I’ve been trying out V2 on the iPad. I traditionally draw single frame cartoons, now I'm shifting to single-frame stories. Getting use to the interface change has been a bit time consuming, but overall it's been a positive experience. I'm looking forward to seeing how the iPad platform evolves. Working while sitting on the couch instead of an office desk is a major bonus. I hope you enjoy my submission.

For more information on the Affinity V2 licence and registration process, please read the following guides: Affinity Licensing and Activation Guide (Affinity Store) Affinity Licensing, Registration and Activation Guide (Mac App Store) Affinity Licensing, Registration and Activation Guide (iPad App Store)

In order to enable Hardware Acceleration in Affinity V2 apps, your graphics card will need to have Direct3D 12 Feature Level 12.0. To find out if your graphics card(s) has Direct3D 12 Feature Level 12.0 please follow the below steps: Press the Windows Key + R Type dxdiag into the Run dialog and press OK This will bring up the DirectX Diagnostic Tool. Click the Display tab and look at the Feature Levels under the Drivers section - this will show you the feature levels your graphics card supports: Please Note: If you have multiple displays connected to your machine you will have multiple Display tabs listed. You need to make sure that you have the correct Display tab selected to show the correct details for any dedicated graphics card you have installed or connected.

Affinity V2 apps require a DirectX 10 compatible graphics cards and above to run. To find out which version of DirectX your graphics card(s) supports please follow the below steps: Press the Windows Key + R Type dxdiag into the Run dialog and press OK This will bring up the DirectX Diagnostic Tool. Click the Display tab and look at the Feature Levels under the Drivers section - this will show you the feature levels your graphics card supports: Please Note: If you have multiple displays connected to your machine you will have multiple Display tabs listed. You need to make sure that you have the correct Display tab selected to show the correct details for any dedicated graphics card you have installed or connected.

This can happen if the AppX Deployment Service (AppXSVC) is disabled for some reason. It can be enabled by following the below steps: Press the Windows Key + R Type Regedit into the Run dialog and press OK Navigate to Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AppXSvc In the right pane double click on Start Change Value data to 2 and press OK Now restart your computer and try installing your Affinity V2 app again.

Affinity V2 does not currently have scripting support but it's something our developers are working towards, as mentioned here and demonstrated here.

If you're getting the message "Sideloading is blocked by policy. Contact your administrator to allow you to install apps from anywhere." when trying to install Affinity V2 apps, please go to Settings > Apps > Advanced App Settings and select Anywhere from the Choose where to get apps dropdown. Once you have done this, please try installing Affinity V2 again. Please Note: This option can also be controlled by Group Policy, so if your machine is managed by an administrator please contact them. If you're using a personal machine and you're the administrator you can read the Group Policy section from this Microsoft Article to see if the resolves your issue.

This message can occur if you don't have Microsoft App Installer installed. It can be downloaded from within the Microsoft Store here. Alternatively, you can install the app using the Powershell method as described here:

If you're getting the error "... CONCRT140.dll is either not designed to run on Windows or it contains an error" when trying to run any Affinity V2 app on Windows, please download and install the Microsoft.VCLibs.x64.14.00.Desktop.appx package from Microsoft here. Once installed you will be able to run Affinity V2 without any issues.

For V1, I had submitted plenty of feature requests and some bug reports. I presume that any logged bugs/ improvements won't have to be resubmitted. But what about those who did not make it to V2? Shouldn't it be possible to selectively restore the topics that are still relevant? Or is the idea that you do have to repost them? I wasn't around during the pre 1.9 era, so I don't know the conventions sadly.

As the new apps are shipped as .MSIX package for Windows and there is some confusion about the location and accessibility of the executable (.exe) - the 0KB exe files are in the specific user folder (as opposed to C:\Users\Default) . I am wondering if it can be used by the second user (non admin) on the same computer - could anyone please clarify?

If you're looking to access Affinity V2 from another app on Windows - for example, using Affinity Photo V2 as an External Editor in Raw Therapee, you will need to point to the app's execution alias. They can be found here (assuming default installation location): Affinity Photo V2: C:\Users\[USERNAME]\AppData\Local\Microsoft\WindowsApps\AffinityPhoto2.exe Affinity Designer V2: C:\Users\[USERNAME]\AppData\Local\Microsoft\WindowsApps\AffinityDesigner2.exe Affinity Publisher V2: C:\Users\[USERNAME]\AppData\Local\Microsoft\WindowsApps\AffinityPublisher2.exe

Hello Affinity fam! I would like to start using these forums more often and share with you the pieces I'm creating. Here is my latest completed piece. I leave you the information of the piece below. Greetings and thank you so much! https://i.imgur.com/d52WZnm.jpg