Is the appimage going to be updated?

[Leinatan]

Hi,

First of all, many thanks for the appimage. I tried other options but none did work, so appimage is my only choice, and it works fine.

However, it would be great if op would either:

• Update the appimage
• Better even, tell us how to do it ourselves! I've tried to extract the appimage and run the affinity.exe installer through wine using the wineprefix included in the appimage, but the gui fails to start, for some reason. So I couldn't repackage the appimage with the new version.
  (Ubuntu 24.04)

The main issue with outdated affinity version is that any file modified with a newer version is incompatible with an older one. As soon as the file was saved on a newer version, it becomes unusable for us linuxers.
This is very annoying but what would you expect from a closed-source for-profit software? Sarcasm aside, regular updates are needed to be able to collaborate with others.

Would that be something doable?

[peeweek]

I double down on that request. Even though It's a good idea to provide appimages for newcomers (especially this one, which is really user friendly), I'd like to customize the way I build the appimage and build it myself. I thought that this repo was hosting all the scripts in order to build the appimage but it doesn't seem so.

[Hydropanda]

Would also like to second this request. I'm also on Ubuntu and can't use the python installer because of dotnet issues, and am running into the issue of being unable to open a file saved with a later version of Affinity.

[yochaigal]

Third this request!

[Tri4c3]

The AppImage has already been updated, but they didn't include the link. Go to AppImage, look for "Release," and there's version 3.2! You need to update the repository so it refers to the full release instead of a specific version.

[Tri4c3]

I agree... we're already on 3.2 and I can't edit on Linux.... I have Ubuntu 26 LTS and I couldn't install it using the automatic installer because there are dependency issues that haven't been resolved yet for Ubuntu 26 :/

[christianbearslyclark]

Strongly Agreed

[Tri4c3]

The AppImage has already been updated, but they didn't include the link. Go to AppImage, look for "Release," and there's version 3.2! You need to update the repository so it refers to the full release instead of a specific version.

[Tri4c3]

The AppImage has already been updated, but they didn't include the link. Go to AppImage, look for "Release," and there's version 3.2! You need to update the repository so it refers to the full release instead of a specific version.

[Leinatan]

Thanks, I can see it's been update indeed! That's great :D

For upcoming releases, what can we expect in terms of update availability? I still think it would be optimal to have some sort of how-to explaining steps to be able to update the appimage.

This way the more impatient amongst us users can have a way to update and still be able to collaborate with other OS's users.

[peeweek]

Thanks again, I also agree and would love to be able to create my own builds of the appimage. So far I've understood what it does by extracting the appimage : Apparently the appimage self-contains the files already installed in /Program Files/ , and the wine runner. By running the appimage it first copies everything to a local wine prefix, then runs it from local (and forgets about files present in the appimage)

But I'm not sure of:

• How the files in the prefix got installed in the first place ? Are there tweaks ? Additional installs ?
• Which wine runner is it using ? Is it a patched version?
• Is the runner using vkd3d-proton to enable openCL acceleration ?

This project is really interesting in terms of simplifying the workflow for non-technical users. However the method on how to produce it is still quite opaque (at least I did not found any clues in the repo). My feeling is that we would all benefit from sharing this appimage build workflow (and also help improve it by contributing)