![]() ! WARNING ! Doing this will clear all the app settings so you will have to set them again so make sure you copy the "Settings" folder as a backup! %APPDATA%\Affinity\Photo\1.0\Settings <-all files in this folder delete you could also try to delete file by file until the issue is fixed so that you do not loose all the settings ![]() Set up is W10, Intel i58600, NVidia 1050Ti, 32GBDDR4 running latest Affinity.Īll other photo processing software are running perfectly.įor me I solved my problems by deleting all the files in the "Settings" folder and then starting the software again. What I've noticed of late is that, since doing the Ctrl-open app, the opening splash screen appears every time that I open Affinity, even if I uncheck the box.Īnd, if I do get as far as 'Photo' the image from 'Develop' darkens after a few seconds and then Affinity closes down. I've turned Tones and Exposure on and off in Develop Asst, and ensured I'm running RGB and it's 'managed. I've read all the posts on this Blog and tried all the suggestions, pressing Ctrl when opening Affinity, uninstalling graphics card driver, changing driver from Studio to Game Ready, re-installing latest Affinity update, etc., etc. It has now degenerated to dark images in Develop and then closing in Develop or after progressing to photo. It started when I noticed that refreshing the display was slow and obvious then becoming blocky (grey squares). Of late however, Affinity is a pain to use. I was therefore delighted to have a programme that just did it's job. I originally switched to Affinity because the software I was using (not Adobe) kept crashing. So corrupt font seems unlikely.Īny help would be appreciated, as I was really looking forward to being Adobe-free. No third party fonts are in the system folder, and all fonts in the system folder render in Nexusfont. I had this process stopped in the previous Windows installation, and Affinity programs worked fine. ![]() Windows font cache service is disabled to allow for speedy font scanning in Nexusfont (not just stopped, disabled). "Let apps run in the background" is globally disabled. I took ownership of the folder at "C:\Windows\System32\spool\drivers\color," and moved the skipped color profiles to a different folder. Possible corrupt color profiles - Reading the attachments in the crash report folder at "C:\Users\.\AppData\Roaming\Affinity\Photo\1.0\CrashReports\attachments" showed Affinity Photo was skipping some color profiles, which were under 5 kb size. Opening different file formats to repeat the crash, making sure the files open in other programs, and trying to open the same file from a different drive location. For example, I can run several images through GIMP, CaptureOne trial, and Topaz Denoise without issue. Affinity Photo worked fine on the previous installation of Windows, and I'm not experiencing errors in other programs, or imaging programs. So there does not seem to be a consistent and repeatable action causing the crash/close. The abrupt closing/crashing happens during cropping, moving file with hand tool, creating/editing adjustment layer, etc. The issue occurs whether I am opening/editing a. I've tested to make sure I can repeat the crash if I open images from different drive locations. It will then crash within 1 or 2 of the next images I try to edit. Sometimes it closes after I work a few seconds, and on rare occasion I can edit and save an image. Sometimes it closes after I have just opened an image, or while trying to open an image. ![]() ![]() Photo closes/crashes with no consistent cause. Since performing the re-installation of the OS, Affinity Photo is unstable. System is Windows 10 64bit Pro (build 19041.388), first-gen i7 950 processor, 12 gb ram. I recently got off the Adobe train, and decided to do a fresh install of Windows on a clean drive (Adobe leaves so many residual files). No 3rd party clipboard manager is installed. While I am using a 1060 6gb Nvidia card, I am NOT experiencing render issues as suggested in that thread. I am NOT using the 3rd party software mentioned in the "Issues caused by third party software" thread. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |