Jump to content
You must now use your email address to sign in [click for more info] ×

Designer V.2 - Files not backwards compatible with older versions


Recommended Posts

I use Affinity Designer & have been using V.2 since its release. I own all the programs but only use Designer actively, so I'm not sure if the other Affinity programs also have this. I just recently had a client who had figured this out and reported it back to me, but when trying to open an Affinity V.2 file I gave to them in Affinity V.1, the program didn't open the file at all and gave this message:

image.png.a5bba63d97c108ce9df535fe391bfe3f.png

This makes sense since V.2 has a lot more features than V.1, however everything that was included in the file I gave was all converted to curves and shouldn't have interfered with anything from V.1. I expected the program to at least try and open the file and anything that it couldn't replicate exactly would just be turned to a raster image or something along those lines. The only possibility I can think of that would conflict with the older Designer version is the layer effects menu I utilized for certain parts of the project, but then when both I and my client copied the entire group from V.2 into an empty art board in V.1, it worked perfectly and nothing was lost or rasterized at all.

Like I said I understand why this system is here in the first place, but at the very least could V.1 attempt to open a file if it recognizes most If not all of the objects and effects? Literally everything within the file itself I tried to open was a curve, the only thing that could have fought with V.1 was the layer effects but even then all of the effects I had used had already existed in V.1. I double checked to be 100% sure and literally nothing was different between Designer V.1 & 2:

image.png.1cf529e0bf59f7f643210bf4692311fd.pngimage.png.a698b22e8ce6f2715cc3f437504b8bbb.png

There shouldn't be any reason for Designer V.1 to reject my new file at all. It's one thing If I used effects and features now exclusive to V.2, but I didn't and what I did use had already existed in V.1, it just got carried over.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.