Affinity Publisher v2 keeps crashing? Especially in photo persona?

[Amirrora]

As stated! I included what I think is my most recent crash file?

72bbd043-39a6-4a45-baba-1125c32e78c3.dmp

Edited September 1, 2024 by Amirrora

[Amirrora]

If anyone has any ideas, I'd so appreciate it.
I prefer to work on publisher and switch the personas around for my work.
If you need any other details, I'd be happy to offer them.

If it helps, photo separately doesn't have this issue.

[walt.farrell]

Welcome to the Affinity forums.

Does this happen with all files, or one specific file? 

Is there anything consistent about what actions you're taking when the application crashes?

[Amirrora]

19 minutes ago, walt.farrell said:

Welcome to the Affinity forums.

Does this happen with all files, or one specific file? 

Is there anything consistent about what actions you're taking when the application crashes?

Hello, thank you Walt.
It seems to be with all files.

I am using Publisher v2, then specifically the 'photo' persona.
I am either: Erasing something, using the pixel tool to draw, duplicating or editing effects or layers, cropping, etc
Just some kind of edit to the project. It doesn't seem to be a specific action. Just randomly. But it happens constantly if I'm working.
It also almost always crashes if I change personas or try to open another file to bring into it.

My computer is also more than strong enough.
I have 64GB DDR4 RAM, 13th Gen Intel(R) Core(TM) i7-13700K (3.40 GHz) processor, an NVIDIA 3060ti GPU--
I'm also running it on the main drive, which is an 1TB SSD with 300GB of space open.
I tried disabling hardware acceleration, I gave it access to more power/memory, I just don't know why this is happening.

It happens with any file or project, even those with only one layer or folder

Edited September 3, 2024 by Amirrora

[walt.farrell]

Your .dmp file seems to show an error in d3d11.dll which is a Windows module from everything I can find.

But there have been a couple of problems reported in the Affinity forum related to that module, which were caused by 3rd-party applications that hook into it for their processing.

For example: 

and

Both of those are somewhat old, but it's possible you have a related problem.

There's also this list of known conflicts from V1, that would probably also affect V2:

 

[stokerg]

Hi @Amirrora,

Are you still having this crash with the 2.5.5 update installed?

[Like, would like more if…]

I seem to have regular crashes with working in the Photo Persona of Publisher - no records to share here – but am confused by the file extensions generated. I also like to "live" in publisher for most of the time switching personas rather than apps.

If I have a placed JPEG, edit it the Photo Persona and add layers etc, I get the option to save as a new file - which is fine.

Why then, does Photo Persona not generate .afphoto resources, instead assigning them .afpub? 

I know all formats can be read into all apps, but this seems to confuse and often ends up when you edit the resource direct from finder with the apps claiming the file is already open in publisher when it is not and therefore cannot open it.

[GarryP]

2 minutes ago, Like, would like more if… said:

Why then, does Photo Persona not generate .afphoto resources, instead assigning them .afpub? 

The Photo Persona is part of the Publisher application, and if you are using Publisher then that application will save new documents as Publisher documents.

[Like, would like more if…]

I know that is the outcome, I just find it slightly odd that the resources are not assigned to their specific apps given that you require the full suite for the personas to operate, and that when I see a "publisher" file in the finder I have an expectation of what sort of document that will be, likewise designer and photo. If I’ve edited a JPEG or similar photo and saved as a resource I would expect that file to be an independent .afphoto file for future editing purposes, straight from the Finder - and available to edit in Publisher direct while working on the document file (as it is).

If I've placed an .afphoto file and edit it in Publisher and save in, it remains .afphoto. 

It may well be just me! 🙂

[GarryP]

I don’t find it odd at all; if I create a Publisher document then I would expect the file to be of the type AFPUB when it’s saved.

And if I, for example, open a AFPHOTO file in Publisher then I would expect it to be Saved over the original AFPHOTO file so I could easily open it in the application that I originally saved it in. But if I used Save As then I would expect it to be saved as an AFPUB file as that’s the application which I am using now.

If you want to suggest that this should work differently then you can raise a suggestion in the relevant part of the forums.

[R C-R]

4 hours ago, GarryP said:

I don’t find it odd at all; if I create a Publisher document then I would expect the file to be of the type AFPUB when it’s saved.

Same here. In fact, if I used Save on a newly created file in APub I would find it extremely odd if it saved it as an *.afphoto or as any other file type. It would be like using Save with a new project in any other creative app & having it saved as something other than as its native file type.