Search the Community

The image is not showing.

Hello everybody, the following error already occurs since version 1.x of Affinity Photo and was already described in the respective forum and declared as a bug. When applying an HSL adjustment layer to a 32-bit RGB file, the hue selection does not work correctly. The bug can be reproduced. I am running Affinity Photo 2.0.3 on Windows 10 Pro x64 22H2. Hardware acceleration is active, but the error occurs even if it is disabled. The following step-by-step guide can be used to reproduce the bug and for details about it. The screenshots are from version 1.x of Affinity Photo, but the procedure is the same for version 2.x as well. Start Affinity Photo. Go to "File" --> "New...". Create a new file with the following properties: Place a new image (from file) by going to "File" --> "Place..." on the background. Add a HSL layer. The work area should look like this: Now open the HSL adjustment layer and pick one of the six predefined colors. Since I want to change the red and yellow colors I pick the red dot. Now decrease the saturation to 0 %. First of all, it seems everythings works fine: Now drag the four color dots to another color like blue. The expected behaviour would be that the red colors get saturated again and the blue colors get gray. Since there are no blue colors in the picture the picture should look like the original again. But what is happing actually is, that the red colors are still unsaturated and although the outer ring of the color wheels shows gray "blue" colors nothing has happend in the picture: It does not change anything if you try to use the "Pipette" instead of draging the four dots. When working with an 8 or 16 bit RGB file, the HSL adjustment layer works just fine and as expected. The original posted bug was found on MacOS. I guess the MacOS version is still affected. Feel free to ask me for more information. I hope my findings provide some information on how to deal with this issue and find a solution to it for me, as well.

Hello, I am using Affinity Designer V2, and this problem is existed since Affintiy Designer V1. When I draw a line by Pen Tool, the line display doesn't look straight sometimes for 1 pixel broken Like this. (Seems depend on Zoom size, Some scale look normal, some scale look wrong) Zoom Out (The line broken) This one is the line after Zoom In display Zoom In (The line normal) Did anyone know how to solve this problem? To make the display correctly?

There appears to be a bug on the iPad apps where the grid is not anchored to the top left corner properly. This causes some sort of “parallax effect” when panning the canvas. When rotating the canvas past 180º, the grid disappears. Currently, this appears to affect all V2 apps though the V1 apps are unaffected. FullSizeRender.MOV

Steps 🪜: Insert some text. Try and search for a font. Crash. Expected Result 😀: Query the fonts on the system. Actual Result 😔: Crashes the application on keystroke while searching a font. System Specs 💻: Edition Windows 11 Education Version 22H2 Installed on ‎9/‎29/‎2022 OS build 22621.755 Experience Windows Feature Experience Pack 1000.22636.1000.0 Processor 11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz 2.30 GHz Installed RAM 16.0 GB System type 64-bit operating system, x64-based processor

Not sure if this is a known bug or not, but I’ve found that when exporting a project and going to the share button in the bottom left corner, it uses an old version of the file for sharing (e.g. from a few edits ago.) If I actually go to share this (e.g. save to photo library), it saves an old version. One way to get around this, after opening the share sheet menu, is to tap off the share sheet and then tap on it again and it usually refreshes with the correct version of the file.

Attached is an iPhone movie of an Affinity Photo 2 (v2.0.0 for Mac), canvas rendering problem in Masking mode when the cursor is hovered (not clicked, not drawing) over the canvas. 00:00 - We see a Layer Effect of Gradient Overlay has been applied to a photo (IMG_1146.CR2) and it's Mask layer is all white. 00:13 - We are in brush mode and hover the white brush (00:17) over the canvas just fine, then at 00:27 we switch to black brush and do the same, again all's fine 00:35 - We merely select the Mask layer, and then hover (not paint, not click, not select) the same black cursor over the canvas 00:37 - As the cursor hovers into the canvas boundary, rendering gets all screwed up. Note, again, we are NOT painting. Hover only. 00:47 - We switch the the white brush, still in mask layer, still hovering (not painting, not clicking, not selecting) 00:48 - As the brush enters the canvas area again, portions of the canvas far away from the brush show artifacting 00:53 - "Interacting" with the artifacting does some weird pixel-refresh behavior; note again, we're NOT painting, just hovering. 01:05 - Switching back to the image layer, the rendering problem goes away 01:11 - Switching back to the masking layer causes the problem to return (01:12); again, only hovering ( Unfortunately, I don't have the file, or I'd pass that along to you. ) EDIT: Uploaded Video didn't render when posted. You can get it for the next 14 days at https://fromsmash.com/Affinity-Photo-v2-Masking-Bug EDIT 2: The vertical nature of the iPhone movie seems to be not working on this forum software. Please double check the file you get from the above URL matches this information before opening. 121997913 Nov 12 20:15 Affinity Masking Bug.MOV (size) 35dd53703f0bff463a98f4b4350b6b64a68611f20972ebbe305893f8edd8fdc5 Affinity Masking Bug.MOV (sha256) Affinity Masking Bug.MOV: ISO Media, Apple QuickTime movie, Apple QuickTime (.MOV/QT) (file type) Affinity Masking Bug.MOV

Hello, the grid is not displayable in Affinity Photo V2. I can activate "view > grid", but no grid will be displayed. System: Windows 11, latest updates Regards Anja

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.

In Affinity Publisher V2 I have a Master Page with a Picture Frame. When I set an image for this frame in a page that has this master page applied and add an adjustment to the image I can't change or delete the adjustment afterwards. This is a bug. It is possible to edit or delete an adjustment for an image in a picture frame when the picture frame is not defined in the master page, but the current page itself. There might be another bug: Using the context menu on an adjustment and clicking "Release Adjustment" crashed the App.

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).

Can not enable OpenCL on Windows 10 Pro

Here's a short and simple issue I found on starting Publisher V2: When I click Help->Quickstart Guide, it takes me to the Designer Quickstart (https://affinity.serif.com/en-us/learn/designer/desktop/quickstart/) Confused the heck out of me at first!

Affinity Publisher 2 / Help: Publisher 2 Learning Portal Quickstart Guide What's new in Affinity Publisher 2 point to pages about Designer.

When I set margins for my document it works just fine right up until I convert my document into an artboard. Then when you drag the numbers up they snap right back to 0 and show no preview. Current workaround is to either create a completely new document and ban myself from clicking the artboard button or create manual margins using invisible boxes while crying softly.

I can't snapping to the curve exactly. The wrong result is displayed while still some distance away from the curve.

Affinity Photo Version 1.10.5 I work a lot with JPEG and PNG images. When exporting these images using File > Export and saving them as JPEG or PNG files I will quite often (1/30 times) later discover that the exported image (when re-loaded) has artefacts that were not on the original and not visually apparent at time of export. The artefacts are always square or rectangular and usually wide letterbox sizes. The Artefacts are quite large relative to the image size. ~ 100 x 10 px for example on a 1000x1000px image. Artefacts are mid-tone gray or sometimes transparant and appear to maybe be caused by overlay windows (possibly even the export modal window) seeming to make Affinity "forget" part of the underlying image underneath the export window. I have found today that the artefact was caused by the "flatten image" command from the menu (image was an edited JPEG to be saved as-is). This is more common with large images (3k+ px width or height) and very furstrating. Once an artefact is seen, it's very hard to then keep exporting the same image until there are no artefacts on the export. Usually requiring 5+ exports. If the Artefact is not seen in time, then the source of the exported JPG image will need to be reopened and rebuilt (cos, you know, JPEGs are flat). Interested to know how to establish the cause of this issue. DXDiag attached herewith and most recent image this has happened to. I have edited/captioned the image to highlight the problem. DxDiag.txt

Hello, I making the product catalog of my company, i using the page title from <section name> in my master page. When i add the new section , crash application with no error. Sorry my bad english. System : Windows 10 12gb ram GTX 1070 i7 4790k Also i added prefences tab to attechments Best Regards Mert Efe Cerit

Fix it, please

The Designer is crashing when using shortcut in font selection. Steps: Open document Select text Go to dropdown to change font Select/scroll to change the font (different font name) Selection with mouse is working. If you decide to start typing starting letters of the font in the input...designer will close/crash Any idea...it's my configuration/language? ...what can cause this. Thank you for suggestion.

Bug report. Using the latest version at the point of writing this ( v1.10.5.1342 ) Video with explanation attached below. (Has audio) Thank you for taking your time looking into my report. Please do correct me or provide other inputs for me to further update this post. The asset text change is permanent and will look deformed on other new documents too. Affinity Designer 2022-10-04 17-39-54.mp4

I am experiencing a frequent upside down interface when I use affinity designer on my 11 inch iPad Pro. I currently have Stage Manager enabled. In addition, I am noticing some buggy behavior when the iPad is that a slight angle using the folio case. In order to alleviate the issues, I have to pick up the iPad and turn it sideways in order to get the interface to refresh. I have attached a video that demonstrates the issue. you will notice that when I open and close a document the next interface shows up upside down. IMG_4085.MOV

Hi! I'm using the newest Affinity Designer (1.10.5.1342) on WIN 10. 1. I select some nodes on a curve using the node tool. 2. I would expect to be able to use the node spacing tools in this situation. But they stay disabled. Only the alignement tools are active. Videos seem to show this feature working properly. Has this function been removed? Is this a bug, or some kind of wrong settings or mistake I do? See the screenshot. Thanks!

AD version: 1.10.5.1342 OS: Windows 11 Home, version 10.0.22000 Build 22000 I've noticed that when selecting this object, even though it has a 40.6 pt stroke, the slider ball stays all the way to the left at 0.

Dear Community I'm getting wrong results withe the same .APHOTO file using the Mac version (1.10.5 and all before) of Affinity Photo. When I use Blend Mode: "Darker Color" in Layer Effects it only works correct with the PC version. Settings (for the red square): Result on the PC (desired): Result on the Mac (buggy?): I also attached the source file. Can anyone reproduce the error or is it only on my machine (MacBook Pro running MacOs 12.3.1)? afphoto-shadow-darker-color-test_01.afphoto Additional fact: When I switch to Affinity Designer (1.105) the result is correct. I would really appreciate equal results for equal settings on both systems. Greetings, Henry