Legacy file refuses to open

[Zoli1989]

Hello, 

I started a family tree project in Designer Desktop V1, and now I fail to open it in V2, MacOS, Monterey 12.6.3. It's a small, less than 40MB file, yet nothing happens, "Loading 1 document" on the status bar forever. 

Anyone has any idea how to fit this? I forced closed the app, restarted, tried again, rebooted, tried again, nothing helps. 

Thank you. 

[MikeTO]

Are you trying to open it in 2.0.4 or the 2.1 beta?

Does the file have any linked resources? If so, try renaming them or the folders they're in to make them unavailable when the file is loaded. If it loads without them (don't relink them) then delete them and add them back one by one.

If you're trying to open it in the 2.1 beta, try deleting the mru.dat file. It's in <user name>/Library/Application Support/Affinity Designer 2 Beta.

Cheers

[Zoli1989]

Hi MikeTO, 

Sorry, I didn't get notification about your reply. Thank you! I am trying to open it in 2.0.4. 
No, it was already saved to my hard disk alone, without the files used in it, so I guess I embedded them back then. I can not even check it now that it doesn't open. 

[carl123]

Can you upload it to the forum?

[Zoli1989]

Sure, here it is. Thanks

Family Tree.afdesign

[GarryP]

I tried to load that document into V2.0.4 on Windows 10 and had to end the application task after about a minute.

I then tried to Place the document inside another one and the “Place images” dialog sat there with the progress bar ‘scrolling’, until I ended the task again after about a minute.

CPU was being used by Designer, around 17/18%, but memory use was steady with little change at around 780MB.

I know this doesn’t help the situation, it’s just in case it’s useful information to someone.

[carl123]

@Zoli1989

The document opens fine in the V2 Beta so it looks like something they have fixed already

You can download the Beta and use that to continue to work, or, if you still have V1 loaded, use that to work on the document

[Zoli1989]

Thanks everyone. I'll try with Beta and see if I make a V2 (even beta) 'save as' of it, perhaps it will open in V2 normal as well. 

[walt.farrell]

1 hour ago, Zoli1989 said:

Thanks everyone. I'll try with Beta and see if I make a V2 (even beta) 'save as' of it, perhaps it will open in V2 normal as well. 

If you Save it using the current 2.1 beta, it will not open in 2.0.4. It will only open in 2.1 beta or the eventual 2.1 retail release when you update to it.

[Pšenda]

Just out of interest - do you also find the "Close" button completely inappropriate for this type of dialogue?

Close of what? - closing the V2 app because apparently the wrong version is running? closing the currently open document to avoid accidentally making it unavailable for V1? or just close the dialog?
Why can't there be a standard OK, that is, an expression of agreement with the content and understanding of the message in the dialog, such as in the following dialog?!

 

And the fact that Affinity does not distinguish the seriousness of the message using the classic Error/Warning/Info/Question icons is also very awkward.

[GarryP]

Absolutely.
This first time I saw that dialog I thought that pressing Close would stop the document I was opening from being opened, i.e. close the document which was bring opened.

I would suggest that the text would be better as “I understand; open the document anyway”, or “Continue opening the document”, or something similar.

Even the second example could be improved by saying “I understand; keep loading the document(s)”, or “Continue opening the document(s)”, or something similar.

And I agree that the degree of error – warning, info, error, etc. – could be handled better.

However, this probably isn’t the right place to be discussing this sort of thing.