Critical Error: Edit Affinity Photo 1 file with Photo 2 -> Save -> Not opening in 1

[Garden-User]

Hello People,

I think I found a critical Bug in the Photo 2 Application:
We are currently Testing Affinity Photo 2. Since BOTH 1 and 2 use the same file Format we assumed, that they are compatible with each other. That is sadly not the Case.

We have opened a afphoto file in Photo 2 and edit the HSL Color, what both 1 and 2 support, saved the file and tryed to Open it with Photo 1 expecting it to open just fine, because well NORMAL behavior. Nope We get the nice Error:

"The file includes features from a later version of Affinity."

 

WHY is there NO WARNING in Photo 2 that the file will not be usable in Version 1 even if you don´t use any of the new Features?

This should NEVER ever happen. There should be either:
A: Totally new file format so that you can´t render Affinity 1 Files useless.
B: A Message in Affinity 2 when saving that says "This file includes features that are not compatible with Version 1. Do you wish to save under a new Name?" or maybe something similar (can be disabled in the options)
C-> Let Affinity 1 open that File and let it open what it can read with a Warning. I mean I can open a Photoshop psd file and have edit functions so why not the same?

Because FUN FACT, IF you copy the entire File (the Layers) in Affinity 2 and in Affinity 1 click on "New from Clipboard" ALL Layers will be copied and with full edit mode on them like they are on Affinity 2 even with the modified HSL Color. So there is clearly an Error here.

Hope that this bug / error will get fixed soon and this Topic will then be useless  

[David in Яuislip]

7 minutes ago, Garden-User said:

Since BOTH 1 and 2 use the same file Format

Not quite, they use the same file extension but the formats are not the same

Re your fun fact, try using something in V2 that doesn't exist in V1 eg a Live Mesh Warp, now copy that into V1 and see what doesn't happen. Now double click the filter layer and V1 will probably crash, it does here

[Garden-User]

28 minutes ago, David in Яuislip said:

Not quite, they use the same file extension but the formats are not the same

Ok but it should not happen, that Affinity 1 refuses to open the same file but with the only difference that the HSL color is -10.4 and not -12. I mean yes there may be more differences but then Affinity should have a Checkbox like Photoshop that says "Basic Compatibility with preview Versions of Affinity". 

29 minutes ago, David in Яuislip said:

Re your fun fact, try using something in V2 that doesn't exist in V1 eg a Live Mesh Warp, now copy that into V1 and see what doesn't happen. Now double click the filter layer and V1 will probably crash, it does here

This should also not happen, either it should not copy this filter or it should give you a Warning that you try to paste a non-compatible Filter. I simply mean, that the same Feature in Version 1 is the same in Version 2 and should work in both directions.

[Callum]

Hi Garden-user,

I apologise for the delayed response to this thread.

I understand your frustration regarding this but we do warn users on opening a V1 file in V2 will render it in-editable in V1 once saved you can see a copy of this message below. This isn't a bug and is something that is very unlikely to change in the future.

Thanks
C

[R C-R]

3 hours ago, Callum said:

I understand your frustration regarding this but we do warn users on opening a V1 file in V2 will render it in-editable in V1 once saved you can see a copy of this message below.

The warning was missing from the first Mac V2 versions but as of (I think) V2.0.3 it was added.

[walt.farrell]

3 hours ago, Callum said:

I understand your frustration regarding this but we do warn users on opening a V1 file in V2 will render it in-editable in V1 once saved you can see a copy of this message below.

The iPad apps don't have this warning yet. It would be nice if they did

[Vex]

Since v1 and v2 are not intercompatible in any way, why not use a different file extension, or offer the ability to save in the older version of the file format?

I use Mac and PC, but I do not use the latest MacOS. I need 32-bit support, so I'm using Mojave forever, and v2 won't let me save files that I can open on my Macs in v1.

I definitely understand why there are incompatibilities due to new features and the like, but Adobe has an advantage here - every Adobe app I use allows me to save files in older versions of Adobe's file formats.

[walt.farrell]

1 minute ago, Vex said:

Since v1 and v2 are not intercompatible in any way, why not use a different file extension

That would require a lot of new extensions. For example, .afphoto2, .afdesigner2, .afpub2, .afstyles2, .afmacro2, .afmacros2, .afassets2, etc. 

They have at least provided a warning now to help avoid accidentally having a problem.

[Vex]

It's better than nothing, but it's making it unnecessarily difficult to work on projects between platforms.,,