albertkinng Posted February 19, 2023 Posted February 19, 2023 When I get this I just quit the app and re-launch it and my life goes on, but I was wondering if you guys are having this issue too. The only thing I did recently was add a bunch of gradients (V1) from an old archive. Does that have something to do with this issue? debraspicher 1 Quote Ask for my services: albertkinng.com
walt.farrell Posted February 19, 2023 Posted February 19, 2023 9 minutes ago, albertkinng said: The only thing I did recently was add a bunch of gradients (V1) from an old archive. How many is a "bunch", and where did you add them? Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.3.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
albertkinng Posted February 19, 2023 Author Posted February 19, 2023 @walt.farrell Oh, 68 palettes and add it with the import palette option on the swatches window. Why? You think that may be the problem? Is there a limit? Quote Ask for my services: albertkinng.com
walt.farrell Posted February 19, 2023 Posted February 19, 2023 I don't know for sure that it is related, but given that the V2 apps share that kind of data, and coordinate updates to it, it's possible it could be related. Especially as the problem started after you added the palettes. albertkinng and Paul Mudditt 2 Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.3.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
carl123 Posted February 20, 2023 Posted February 20, 2023 Similar post, yesterday albertkinng 1 Quote To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time.
albertkinng Posted February 20, 2023 Author Posted February 20, 2023 Oh wow... Quote Ask for my services: albertkinng.com
Dan C Posted February 28, 2023 Posted February 28, 2023 Hi @albertkinng, Thanks for your report and our sincerest apologies for the delayed response here. We are exceptionally busy following the release of V2 and we thank you for your continued patience and understanding here. The users in the above thread are reporting this issue for Windows and my colleague is investigating issues with OpenCL Hardware Acceleration there, however this would not apply to the macOS version of the Affinity apps. I note that one user in the above thread has been loading, editing and saving files on a server - are you editing files from an external or cloud source etc please? Quote
albertkinng Posted February 28, 2023 Author Posted February 28, 2023 (edited) 2 hours ago, Dan C said: are you editing files from an external or cloud source etc please? Yes, all my work is on external drives. I have used a project manager network app to access my document files for a long time now. Never had a problem until now. Main drives are on an external dock and others are on a shared cloud such as Google Drive, Dropbox and so on. (I'm running a Mac Mini M1 / 16g RAM with latest Ventura OS) Edited February 28, 2023 by albertkinng Mac info added Quote Ask for my services: albertkinng.com
Dan C Posted March 2, 2023 Posted March 2, 2023 Thanks for confirming that for me - I've been testing this further and the only way I'm able to see this occur is if one Affinity app is in a 'not-responding' state, then I try to launch a different Affinity app. Did this by chance occur when the app was 'not-responding' or the 'spinning wheel' was shown for your cursor? If not, we can enable some further logging, to provide our team with more information when this occurs. Can you please: Open terminal and type the following, then hit enter:launchctl setenv AffinityIpcVerbose 1 With Terminal open, launch the Affinity app and wait for this error to appear Depending on where the Affinity app was installed from, navigate to the following location: MAS: ~/Library/Containers/Affinity Designer 2/Data/Library/Application Support/ Affinity Store: ~/Library/Application Support/Affinity Designer 2/ In this folder you should see the ipc.log file, please attach a copy of this to your reply here. Many thanks once again Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.