emmrecs01

@Sean P I realised this morning that the upload of my AppData had failed! And, as a result of my end-of-day housekeeping, I no longer have the zipped file or its unedited contents. My sincerest apologies. To all other users experiencing this problem: on my computer it seems the installer created a file in the %appdata%\Affinity\Designer\1.0\temp folder which it did not delete once the installation was complete. This is what seems to have caused the app to crash on first start. Simply deleting that file resolved the issue. Perhaps worth checking? HTH Jeff

@Sean P There was an 863 KB file in the Temp folder! (Nothing in backups). Deleting that file allowed me to reset 1.0 old to 1.0 and everything kept working! Happy Days! As always, my very sincere thanks. Jeff

@Sean P Thanks for that information! The Autosave folder in 1.0 old is empty, unfortunately, as it is, obviously, in the new 1.0 folder. Jeff

@Sean P The requested files are uploading as I write, though the on-screen message says the upload will take anything up to between 3 and 4 hours to complete!!! However, also renaming the AppData folder to 1.0 old has allowed the app to open. Now for the fun of trying to discover which part of that folder's contents has caused the problem!! 😭😭 Jeff

Having just received notification of the release version 1.10 of all three apps, I opened the previous release versions of each of them but did not receive any on-screen message to update. So, I went to my Serif/Affinity account and downloaded the installers for all three. All seemed to install, without problem; Photo and Publisher both opened and could be used. But Designer crashed/disappeared almost immediately! The splash screen appeared, got as far as "Loading fonts" and then simply disappeared! The Beta 1.10.1127 still opens without problem! Checking Crash Reports, I see three files (corresponding to the three attempts I made to open the app!). They are attached. All ideas/thoughts/suggestions gratefully received. TIA Jeff dcfc2e8f-2af7-4fb8-bdd3-acdee1bdace3.dmp dff89533-e348-4bd2-8f3d-0b0c726b2335.dmp ff91d3b4-2dba-4ab1-ab5f-7a93719a327f.dmp

@LeonardoT Welcome to the Affinity forums. Affinity Photo for iPad can be purchased from the iPad App Store only so you need to go to your iPad Store Account, log in, and see what options are available to you. I suspect Apple/Serif will not be pleased to see you were refunded for your earlier purchase of Affinity Photo, but continued to use it! I believe such actions are a direct contravention of the conditions attached to the grant of a refund. As to whether this will affect the opportunity for you to buy the app again, I have no idea. Jeff

@Putterer If you are running APh in Windows then DXO Viewpoint 3 plugin doesn't cause the crash that @firstdefence reports for Mac. Jeff

@Chris1239847493 Welcome to the Affinity forums. How shortsighted of your administrator!! However, there is no need to cancel your trial, I think. At the end of the trial period access to whichever Affinity app(s) you have will simply be lost and it/they will no longer run. HTH Jeff

Why have you started a new thread about this when you already have one which has received numerous replies, here? Jeff

@Mike_D You've posted to the "Affinity on iPad Questions" forum but I think this really needs to be posted to the appropriate forum for Mac OS. Jeff

@rsmcguitar I wonder whether this is a case of Windows Protected Folders preventing access for writing the licence file? https://docs.microsoft.com/en-us/microsoft-365/security/defender-endpoint/controlled-folders?view=o365-worldwide#windows-system-folders-are-protected-by-default gives more details, including how to check exactly which folders are being “protected”. Jeff

@Frank Van Atta @user2021 has obviously resolved whatever problem he/she had! Hence he/she has edited the post to remove the actual question.

You asked that earlier, and the answer is still No, sorry

@Gro Fykse OS = Operating System

@NATORI You need to attach the actual RAW file, not a screenshot of what you see in AP. Jeff

@Jo Martin Welcome to the Affinity forums. Assuming you are using Windows, and following on from what @John Rostron has written, the first thing to check is the OpenCL setting. Do not attempt to start a new file but Close the initial splashscreen and then go to Preferences>Performance. It should look something like this: Check the setting I have highlighted; if it is ticked, untick it! HTH Jeff

@Jack Hanson No problem opening your file on Windows, using the latest release version (1.9.2.1035) or the latest Beta (1.10.0.1085). Jeff

@k5astro Apologies for the delay in replying! I think the "Authorize Global" is a setting specific to Mac OS? Certainly, I don't see it on Windows so really can't advise whether it should or should not be active. Hopefully a Mac user will see your question and be able to help. Jeff

@k5astro Is this "missing" licence key the one for StarShrink or the one for Affinity Photo? I assumed it was for StarShrink but it seems that @Old Bruce believes you are asking about the licence key for APh? If you are asking about the key for StarShrink being "missing", I suspect this is due to some "problem" with its installation, and perhaps nothing to do with Affinity? I don't have this particular plugin but I do have quite a number of other "licensed" ones and have never experienced this problem of being asked to enter the licence key on each opening of any of those plugs. Jeff

@George911 Welcome to the Affinity forums. From where did you purchase whichever Affinity app you have? Affinity Store or Microsoft Store? If it was the latter, no keycode is needed and I think the app will have installed automatically, so should now be listed on your Start menu. Which app, by the way? Jeff

@Mischugo Have you explored the option in Designer of File>Edit in Photo and in Photo of File>Edit in Designer? I'm not sure whether that is what you need but it is how to "Link AD and APh". Jeff

@Stojan Your computer spec, as previously requested, might possibly offer a clue. Also, did you actually disable OpenCL, as explained in that linked FAQ? (I realise you can't disable it from within the apps - because they don't open at all - but you can disable it following the method given in the FAQ. It's what I had to do, as a first stage, to restore operation of all the Affinity apps, before then downgrading my GPU drivers.) Jeff

@SwiftilySquirrel If you tag @carl123 he will get a notification that you have mentioned him in a post. Or, you could use the Private Message system to contact him directly.

@SwiftilySquirrel To remove the document, simply go into the specific post that includes it, click on the ellipsis (three dots top right corner), choose Edit and then delete the file from your post. Jeff

@Stojan What is your computer spec., in particular, (if you have a discrete GPU) exactly which one is it (make and model) and which driver do you currently have installed? I ask this because I wonder if this is another example of OpenCL causing the problem because of GPU driver incompatibility. I experienced exactly the same as you recently, which turned out to be caused by a driver update for my AMD Radeon graphics card. My post in this thread gives rather more details, along with a link to an FAQ which shows how to disable OpenCL even if none of the apps will open. HTH Jeff