-
Posts
3,337 -
Joined
-
Last visited
Posts posted by Pauls
-
-
seems to be related to preflight checking -you could try disabling that and seeing if the app is more stable. You would have to do this for any document you open
-
@PyanepsionYou can use this link if you find any files that can recreate the problem
-
Hi @anto after reviewing the crash reports there is definitely something in the the way you work, the documents you use and the hardware you run on which is causing this problem to appear very easily for you. In order to really help us track it down we could do with a video of a session where the problem occurs (full app screen), a sample document ideally with history turned on. We appreciate this is not straight forward but it would really help us track down the problem.
Finally just prior to the crash does the app appear to be laggy at all? -
Hi Walt it does look like the content is only available of Mac - I'll log that
-
-
We're pretty sure its OpenCL causing the issue and turning that OFF in
Edit > Settings -> Performance - > Hardware Acceleration
should allow the documents to open
In 2.3.1 (on an ARM device) Hardware Acceleration was not available. in 2.4.0 Hardware Acceleration is available and enabled. If you simple disable OpenCL it should allow you to use 2.4.0 and for it to behave just like 2.3.1 did
-
We suspect this might be due to some Open CL changes in the newer build. Could we get a screenshot of preferences / performance in 2.3.1 and if possible 2.4.0.
If we could also get a file that is not opening as well. You can upload it securely here.
If you do install 2.4.0 could you try turning off openCL and setting the renderer to warp then seeing if your documents open.
-
@mchansy - the best way is to create your own thread as this will raise a support ticket for you
-
I'll reset the software translation to match the current help here - thanks for the suggestions
-
-
no that's normal if it cant find one
-
the list is basically repeated twice for 2 different internal contexts - I can't see anything obvious that would be causing a startup problem I'm afraid
-
-
can you post the whole log file please
-
that would work around the problem. If it happens again also try enabling
--
font
-
cache
-logging
that might identify the problem font
-
-
do you have any custom or unusual looking ICC profiles ?.
could zip up the profiles folder ( C:\Windows\System32\spool\drivers\color) and post it here please -
@demonweasel - i've split your issue off - makes it easier to keep track. Could you zip up your windows fonts folder and I'll see if I can spot any issue there. You can upload the zip here. Could you also include a recent event viewer log and crash report please
-
Looking back through the posts you said that reinstalling .Net 4.8.1 got things working for a bit - I would be interested to know if you did that again would that get things going?
-
One more thing to try and you'll need to check that doing this won't totally disable any display options of your laptop or even it it is possible.
Try disabling the Intel Graphics adapter.
In you log.txt file there is a reference to skipping an unsupported device. This could be the intel adapter or something else that has been left behind -
better have the log.txt file as well - I still suspect it's something to do with OpenCL and that nvidia card
-
and the event viewer to see if that has changed
-
can you post the crash dump from that run please
-
interestingly the log.txt file does not list the Nvidia card - try disabling that in device manager.
Affinity Publisher: Incompatibility with linked files from lower versions
in V2 Bugs found on Windows
Posted
Please upload the files they'll still help with testing around this