Gianni Becattini
Members-
Posts
366 -
Joined
-
Last visited
Profile Information
-
Location
Italy
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
Hi Thomaso, maybe that with your help I could solve the problem. I don't describe all the work to arrive there, but the problem seems to have been in two of the twice linked image (I cannot guess why). I replaced two of them with GIF files instead of AP, and until now I could not find any problem. The problem was near to the page where first I thought I found the problem and, in all this work, I could separate a small file that crashes also on M2. I test it more deeply and update you. Thanks for now.
-
Thanks for replying. Was the AP document linked or embedded? All linked. Are there more instances of that Affinity document placed within the affected APub document … or any other Affinity document? Yes many. Can you open their originals (not their instances in APub layout)? This is more difficult to answer because they are very many, but I understand the point and try to work on it. Anyway I cannot understand why sometimes it works, sometimes not. A locked or damaged file should be always OK or KO. All the files are well synchronised on both computers by iCloud. Do the placed documents use font files that aren't identical on the two computers? No, as far as I know. But I am rather sure. Can you exclude a font issue / corrupted font file? I have many APub files that use the same fonts and they work normally. Is only this file that creates problems.
-
UPDATE & SOLUTION (I hope) After a long and travailed road, I found a reason for the problem. It seems to be in a AP file, included by the APub document. The file is the image with the silver boxes (see attachment). I just rasterised it, and now the problem seems to be gone. Currently the situation is absolutely repetitive: with the old file it always crashes, without it works (but only on i9). I upload also the offending file. I hope the problem will not appear again for something else, in the case I will update. 7A13 schema original with problems.afphoto
-
walt.farrell reacted to a post in a topic: APub does not start on Intel platform only
-
The problem arises independently from the acceleration settings and only with this file, a chapter from a book. I could edit it only on the M2 Mac, but when I need to generate the full book, the operation is possible only on the iMac, because it crashes on the M2... Resuming: iMac: just one file systematically crashes when I open it M2: the book systematically crashes on export A dead lock....
-
Gianni Becattini started following Affinity Photo no longer starts and APub does not start on Intel platform only
-
I am currently annoyed by the following problem: when I open an Apub file on my iMac i9, it opens but not completely, i.e., some image remains in low resolution, as it uses to do for the first seconds. The user interface is partially operative; I can scroll the pages but if I click somewhere everything locks and I must kill the application (if I ask to quit, the file window closes but Apub does not quit - it seems it is doing something in background). The same file continues to work normally on M2. This behavior changes from time to time; maybe that deleting a page it returns to work. If I continue to work on the file from M2, maybe that this evening it can start again correctly or not on i9, but when it starts locking, the problem is absolutely repetitive. I already tried deleting the hidden lock files with no success. Any help is welcome, my iMac became totally unusable.
-
walt.farrell reacted to a post in a topic: Affinity Photo no longer starts
-
walt.farrell reacted to a post in a topic: Affinity Photo no longer starts
-
Hi Walt, thanks for replying. After some tribulations, I believe I found the problem, probably of hardware origin. The possible culprit could be a USB adapter used for the second monitor. After I removed it, everything seems again to work correctly, including Nicepage and I had no more crashes. This evening I will try with a different adapter. Sorry for the false alarm.