Search the Community

Seeing openCL is causing problems on AP version 1.9, the old version 1.8 should be made available again.

Hi! I'm encountering a crash in Designer during the update process from 1.86 to 1.9 - the programme successfully finds the update on launch, downloads the data but then crashes during extraction. I've had a search of the forum but can't see anything similar; I've updated Photo and Publisher to 1.9 successfully but Designer won't play ball! Please could you advise - is there any further info I can provide to help? I've attached the crash report as text doc - not sure if that's helpful? Many thanks, Andy. Affinity Designer Crash Report.rtf

Ich arbeite mit Affinity Photo, Affinity Designer und Affinity Publisher (Version 1.8.6) auf dem MacBook air (Mac OS 11.1 Big Sur). Wenn ich eine pdf-Dateien öffne, bearbeite und dann wieder als pdf-Datei exportieren will, stürzen die Programme ab, sowohl Photo, Designer als auch Publisher. Ich benütze jetzt wieder Version 1.6.1 ohne Abstürze. Ich möchte aber die neuesten Versionen anwenden. Was kann ich machen?

I am using Affinity Photo 1.8.5.703 on Windows 10 on a quite powerful machine (Ryzen 2700X, 32GB RAM, NVidia 2070 Ti) and try to stich a largeish panorama of 30 shots. Unfortunately, Affinity Photo repeatedly crashes when creating the panorama. The program crashes directly after creating the panorama, i just see a short flash of the window showing the stitched image when trying to use any tool in the panorama editor, it's enough to click the tool icon to make afifnity photo crash when minimizing and restoring affinity photo after the panorama has been stitched and is shown in the panorama editor I don't think it's a memory issue since the total system ram usage is just 20GB according to Windows' task manager (so ~12GB left). I use Nvidia's studio drivers, so those should be quite stable. I uploaded the source files to google drive since they are quite large (1 GB): https://drive.google.com/file/d/1EZI_VKYCYUlnFZkEj-P_FObZWtHYS76r/view?usp=sharing Some crash reports are attached to the post. reports.zip

Hello, I am new to Affinity Photos, and yet in the short time I used it, it already crashed on me twice (once when just loading a TIFF file and once during editing). I have activated automatic error report sending. When it crashes, I notice that the entire process is just gone. I would expect that an exception occurs, that goes all the way through, resulting in the termination of the host process itself. 1) Is it possible to incorporate a global exception handling? I suppose that most functions are using try/catches for specific situations, that safeguard against specific exceptions. But there are always the unforeseen ones that cannot be anticipated. And having at least an error message and possibly the option to at least save the work currently in memory would help a lot! I come from the Microsoft C# / .NET corner, which offers a global exception handler: https://stackify.com/csharp-catch-all-exceptions/ You can even go as far as catching deep native exceptions using Win32 like this: https://stackoverflow.com/questions/150544/can-you-catch-a-native-exception-in-c-sharp-code I don't know if the programming framework you use for your products provides similar possibilities, I would hope... 2) Sadly knowing that a crash might come at every action is there at least a way to save incrementally? Using a keyboard shortcut or a macro? Let's say I open a TIFF xyz.tif and edit that (and include layers). Then Every time I run the incremental save it would increase a counter in the filename xyz1.tif and so on. That way one could at least be sure, that some version is at least readable and not totally destroyed (I had read posts of unfortunate users that ended up in that predicament - having lost hours of work). One could even think about an incremental auto-save in background. Thanks for considering!

Video: https://giphy.com/gifs/bsAW6gYkFJgMNfhEvu Whenever I try to save a new document custom preset the app immediately crashes when I click the "+ Custom" button. I'm not sure this was ever working for me. I can say this has been happening for a few months. I am able to create custom presets for Photo, though I need to close the New Document dialogue after creating one in order to rename it without crashing the app. MacOS 11.1 Affinity Designer 1.8.6 No unusual hardware attached. Let me know if there is any other information I can provide to help. Thanks!

I've been working on a document with around 60 pages for a few weeks now. Everything worked fine until I noticed a few days ago that the background image at the right bleed is no longer displayed for some pages. So I wanted to apply the master page again, but Publisher crashed. I tried to isolate the error a bit. The error occurs with the file attached if I drag the master page "Text right" towards the right side of the master page "Text". The app crashes the moment the mouse cursor reaches the right side of the master page "Text". Interestingly, when I delete pages 4 and 5 or 6 and 7, the app does not crash anymore (but the right bleed is still wrong). Publisher used: 1.8.6 (MacOS 10.15.7 and 16 GB RAM) Kind Regards, Martin Test.afpub

The program closes without warning when, in layers panel: I try to nest one layer into another and/or I click to expand the layer to show its contents.

I open a 50 side catalog that is finished, and as soon as I open the "resource manager", the Affinity Publisher crashes and the application is closed. There is no error message.

Hello, I am having repeat difficulty rendering panorama's since latest update to 1.7.3.481 Continual repeat crash when rendering panorama's (regardless 50-350photos each) PC Specs: i5, 4670k, 4.1ghz (water cooled, temps under 75 Celcius when 100% cpu) 32gb DDR3 / 1600 (XMP 2400) Raid 0 2x1tb Windows/Program Raid 10 4x4tb (Source folder's) 4tb Spare drive (stand alone) RX590 8gb "fatboy series" AMD Video Card. 3x Benq 24" Displays (1920x1080). Windows 10 Latest updates. All drivers thoroughly up to date. Page file not on Raids, just the spare 4tb. Affinity Photo, i've set for 8, 16, or 24gb's (it uses upwards to 28gb's if I max it of the original ram, before page). Still same issue. Right now I have 4x "pano" source folders, (1,2,3, & 4). All Source files are JPG/ Taken by Samsung S8+ 13mp each I believe. Folder 1: 355 Jpegs, Total 2.19gb Folder 2: 310 Jpegs, Total 1.98gb Folder 3: 276 Jpegs, Total 1.53gb Folder 4: 116 Jpegs, Total 723mb (0.72gb ish) I've tried a catch all at once, toss them all in and see. What is found, then render. I've tried separately to just do folder 4, or 3, etc, smallest first I figured... It can get to the preview part, but when rendering... after a few hours the app fully exits/crashes. I've monitored on Task manager. The drive/memory/cpu and some GPU is used. I'm grasping at straws here. I have done the intel raid check. 0 errors entirely. I've defragged thoroughly. I've trimmed startup apps, scheduled tasks, etc. Literally minimized to maximized performance. I've even set priority of affinity photo to "above normal" I'll happily adjust or customize settings further if any theories help. I recognize panorama's take TIME. I know this thoroughly. I check back every few hours to see progress pro/con. If anyone has suggestions/idea's, hugely appreciated. What else is needed here to proceed/gain support, but proactively in the right direction? - RMLeLoup P.S. Thanks in advance for the thorough read. Edit: Updated version #, Edit 2: How do I get a "crash report" ? If needed, i'll attach, and upload samples if required also. (Have 185/185 fiber/unlim, happy to ts, don't mind)

Hi all, Publisher crashed during an export to PDF. I get to the export screen, but while exporting it crashes. Exporting to JPG works fine. Attached is the report from the Apple System. I have a: MacBookAir10,1, BootROM 6723.61.3, proc 8:4:4 processors, 16 GB, SMC. Any suggestions? Thank you and all the best! Crash report.rtf

Whenever I open this particular file that I've made 2 days ago on this same program, it keeps crashing. There are 300 pages in the file, not sure if it's too many to handle for the program ? Once I open the file, the app crashes - every single time. At first, I worked on the Beta version but the beta version crashed, so I thought it was because of the bug on beta Therefore, I transfer the pages one by one to the newly created file on the full version instead. I managed to export the pdf from it - but after that - I can no longer open the file. It seems to crash the same way as the beta did. I'm using iMac Pro 2017 and just updated the OS this morning. so the file was made prior to this OS version.

No matter what image file I open, when I attempt to export, I see the export dialog very briefly and then it crashes the application. I just bought this to get off of Photoshop. Hopefully there is a solution here. I'd consider this pretty severe. Any idea of what I can do to get around this? Exporting is sort of... important. I'm on the base Macbook Air M1 (8core/7core GPU).

Hi, I am having heavy problems with crashes using this app (1.8.6.198) on my iPad Pro (12,9 Zoll, 3. Generation) 256GB. When I edit portraits, I have constantly crashes at least 5-10 crashes per photo edit. I open the raw file the first 10 minutes or so run prematurely good but then it starts to crash almost every 1 to 3 minutes. I even started to flatten the image almost after every step of my edit when using layers but it mostly does not hinder the app from crashing. The heaviest amount of crashes I had was 3 days ago where I had at least 20 crashes until the photo was finished! This is very, very annoying and in my opinion not acceptable. There is also a bug with the frequency separation function. After selecting it, it does not show the value selection screen, only after clicking FS the second time from the menu the value screen is shown! I hope you can provide help with this! thanks1

Prior to exporting my document to PDF, preflight said TOC needed updating. I hit the FIX option and Publisher crashed. I have version 1.8.5.703 on Windows 10.

Hi, Just wanted to list this bug that I've been getting. I used to get it way less frequently, but with the latest update it happens very frequently (sometimes on the 2nd export and definitely by the 5th export). More specifically, I have a file with multiple artboards in it. I export elements out of one of the active artboard, in PNG format (I select 'export only selected without background' in the Area tab). The window then disappears, nothing is exported (because the save dialog window does not appear) and nothing works afterwards. This error is more likely to happen when I drag and drop a previously exported PNG file into the file (to test that it is okay) and nothing happens! The file does not appear. Same if I try to drag and drop it in Photo. Might be because it got corrupted during the export? The only fix for me at the moment is to close the software through task manager and start again, until the same crash occurs. I have created clean files, only one artboard at a time etc, I reset the settings by having the CTRL button pressed on launch, the error will keep happening. It is a Windows 10, tower PC with 32gb of RAM, Nvidia 2070RTX, AMD Ryzen 7 2700X, so I don't think it is my specs. I even lowered the max ram to be used in the performance tab and that seemed to make it work better for a couple more exports than usual, and then the same crash happened. Thanks for your time! Edit: Additional info: So I have been looking at the exported files that seem to cause a crash and cannot be drag and dropped, when I open them by right-clicking and select 'Open With', Designer will open them, but the file will have a shortened name and appears in all caps - vs other exports that can be dragged and dropped, whose naming appears correctly. Some elements that could not be dragged and dropped eventually fixed when I re-exported them, but some are always problematic and I have done nothing different to their exporting process. -- Manually renaming the files, allows them to be opened & dragged and dropped normally. But the naming is exactly the same as before (!?). Final Edit - I have narrowed it down to something within that specific file I was trying to export from, other files (exact same multiple artboard style, same exporting process and naming), have been exporting just fine. There is obviously a bug there, but I cannot share the file in question as it is work related.. As this is something that has happened before though it might be worth looking into ( consecutive exporting from multiple artboards from within the same file, has caused my Designer to crash on numerous occasions).

Hello, I am using Affinty to replace PS for about one mounth. It works mostly, but there are many glitch which feel weird. I will list a few: - Select (lasso) is extremely slow. The lasso is late compare to the mouse pointer. Sometimes is also does not work: You draw your selection, but nothing is selected, you redraw it, it works.. This kind of function was already instant on an Amiga 500.. how can it be slow on a modern PC ? - Change the brush size using the mouse (using Ctrl-Alt) is totally weird. Sometime the position on the pointer jumps to somewhere else. And even it it does not change, its a total painful experience. One ends up using the brush properties in the tool bar on the top - Exporting to Tiff (16bit with layers) usually produce a corrupted tiff and the picture is lost - Performance is sub optimal. PS CS6 on a MBP 2012 feels way faster than Affinity on a PC i7 8 cores/64Gb/RTX 2080 - I deeply dived in mask.. still could not figure out how the works. I could not thing about any logical function.. Sometime it works, sometimes it does, sometimes, it remove parts of the pictures.. -> Is it possible using one mask, to mask the content of a group ? If yes, how -> Would it be possible to add the option: "Mask behaviour like in PS" `? - Open a big tiff, resize, correct prespective and then flatten -> Affinity can not save this picture anymore. -> Work lost. -> the same without flatten -> it works - The Level tools only show the per channel clipping, if the master level is >0. - Afffinty crahes a lot. mainly while loading big file, Inpainting or just like this. Questions: Are others experiencing such issue ? Will the usability of the software be improved anytime soon ? Regards

Hey there, I've just downloaded the new version of Affinity Publisher. So it would be version 1.7.1. I did not have access to beta prior. This is my first experience with the software. Since I opened it up, I've been having crash issues. Can barely get through adding images to one page and the spinning/not responding starts. Sometimes if I wait a while it works it's way out of it and sometimes not. I've been working for over an hour and have only gotten through page 3 of my document. I've been searching for solutions. Here's what I've tried so far. 1. Downloaded High-Logic and uninstalled a few hundred fonts that I wasn't using. 2. Checked the appdata folder for crash reports. Those folders are all empty 3. Held down the CTRL key when I started up Publisher and checked all boxes/ set it all back to defaults. The issue persists. As I've been typing this message, Publisher finally came out of it's spin, but I'm not going to get very far at this pace. Also, for some possibly further useful information, I had this problem sporadically with Designer and since that latest update, all those issues seem to have disappeared. I'm not sure if this is something going on with my PC or ? But I did see a forum thread somewhere that suggested this is not normal for Publisher and it should not be running this way. Any ideas or treasure trails you all can send me down to try and get this handled would be most appreciated. I was so excited to use this program and cut my time in half or more, but so far it's taking me more than twice as long to get anything done. Help?

Note: Font used in the document is Coval and can be downloaded here, it is open source: https://localfonts.eu/freefonts/bulgarian-cyrillic/coval/ OS: Windows 10 v. 1909 Processor AMD Ryzen 7 4800H with Radeon Graphics, 2900 Mhz, 8 Core(s), 16 Logical Processor(s) RAM: 32 GB (I also attached a copy of the System Information file) Attached are 3 crash dumps from Affinity Publisher and all produced doing the same operation. Issue: 1. Open the attached document. 2. Attempt to add a new single page to the document. Add the page before page 1 and use Master B as the Master. 3. Affinity Publisher will crash immediately. I was not LRB_single_page_layout_A6_.bg.afpub JeffShergalis_SystemInfo.nfo 70575138-a163-4217-930e-feccfdddde5f.dmp 2a7c5215-17bb-49a6-ba83-fab4681bdf75.dmp 324eb7b3-14f7-4f7b-9847-3acc7a2df453.dmp

Affinity Photo won't launch (launches, briefly shows in Task Manager. then quietly dies). I figured I'd try to update and see if the latest version works, but the installer does the same thing. Briefly launches, then dies without any error messages. I do not have any of the listed conflicting software installed, I disabled my antivirus. That didn't work. The Uninstaller does work fine (meaning I uninstalled and can't check which version I had installed. New installer won't run after uninstall either). Affinity Designer has the same issue and won't launch either. Installed version for that is 1.7.3.481 on Windows 10 x64 All other software on my PC (that I've tried so far) opens perfectly fine. 6c225bb1-655f-4d28-a8bb-dff32b7f52c9.dmp

After Photo and Designer I also use Publisher. After the installation I tried to create a first new document and every time Publisher crashes. It does not matter what I do, Publisher crashes when I try to create a new document. After that I tried to open an already existing PDF document. The same problem, Publisher crashes immediately. Photo and Designer on the other hand work perfectly! Any idea? Thanks a lot! Malcolm

Computer and Software are up to date, but Designer keeps crashing when I try to enter export persona.

Hello! So, i was working on a new template for a CD cover, and as i was doing my thing, it crashed. I tried again, same results without knowing why. Then i discovered that writing the word "oeuvre" without the œ is fine, until i press spacebar to go to the next word, the autocorrect from Publisher that switches "oeuvre" into "œuvre" is causing the crash. I searched for similar problems, tried the cache clear, tried different fonts, same conclusion. BUT something is odd because when i'm trying to reproduce the crash, it doesn't come necessarily on the first try (i mean just writing the word oeuvre for example), i can write 5-6 times the word. FUN FACT : c/c the word with the œ included doesn't make the software crash. Sometimes it crashes right away, sometimes i have to write with the text tool, sometimes with the image box converted into a text box, sometimes i can do both. And the crash has two "endings", one is a clean crash, Publisher closes itself, the other Publisher freezes (blabla is not responding), and i have to close it manually in the tasks manager. I've been using Publisher since march 2020, never been bothered, even with the font i used to crashtest the problem, already used the word oeuvre for sure, so the question is : is it a bug from my side, or from the software side ? Sincerely, Azs.

Affinity Photo version: 1.9.0.820 (Beta) Flow: Start Affinity Photo Open WebP image file Use Crop tool to change image size Affinity Photo unexpectedly closed I attached photo that I tried crop. 1.webp

Affinity Photo 1.8.4 crashes when using the patch tool on Mac 10.13.6 High Sierra. Whenever I use the patch tool and click to set the patch, spinning ball appears, then eventually AP crashes. I don't want to update my Mac since I still use the stand alone Lightroom 6. Occasionally AP will crash with the healing brush tool also. Attached screen shot of problem report.