Affinity Suite v2.0.4 on linux [ Wine ]

Psych · January 4

I'm getting mscoree.dll not found when running Photo v1 with ElementalWarrior's wine build. I suspect it has to do with dotnet not installing correctly as I get "there's a newer version already installed" message in the GUI installer. I just have no idea what to do. I tried winetricks --force as well.

azuredusk10 · January 5

21 hours ago, Frank Incense said:
Hi! I'm trying to follow the guide and I'm already stuck at compiling Wine. (I had a look at https://wiki.winehq.org/Building_Wine#Satisfying_Build_Dependencies but couldn't find a solution at first glance.) The command (I created a folder "WineMod" instead of using Documents)
/home/myuser/WineMod/ElementalWarrior-wine/configure --prefix=/home/myuser/WineMod/ElementalWarrior-wine/wine-install --enable-win64
fails with the error
...
checking for ft2build.h... no
configure: error: FreeType 64-bit development files not found. Fonts will not be built.
Use the --without-freetype option if you really want this.
I'm on Ubuntu 22.04.3 LTS x86_64, I enabled i386 with "sudo dpkg --add-architecture i386", and it seems like the packages should be there:
➜  wine64-build git:(master) ✗ sudo apt list --installed | grep 'libfreetype'

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

libfreetype-dev/jammy-updates,jammy-security,now 2.11.1+dfsg-1ubuntu0.2 amd64 [installed]
libfreetype-dev/jammy-updates,jammy-security,now 2.11.1+dfsg-1ubuntu0.2 i386 [installed]
libfreetype6-dev/jammy-updates,jammy-security,now 2.11.1+dfsg-1ubuntu0.2 amd64 [installed]
libfreetype6-dev/jammy-updates,jammy-security,now 2.11.1+dfsg-1ubuntu0.2 i386 [installed]
libfreetype6/jammy-updates,jammy-security,now 2.11.1+dfsg-1ubuntu0.2 amd64 [installed]
libfreetype6/jammy-updates,jammy-security,now 2.11.1+dfsg-1ubuntu0.2 i386 [installed]
What am I missing?

Update: Ok, I found out that ft2build.h could be the issue. However, I checked that it is there:
➜  wine64-build git:(master) ✗ ls /usr/include/freetype2/ 
freetype  ft2build.h
Do I need to tell the configure script to look at that location? How? Or am I on the wrong path here?

I didn't manage to get Wine to compile on Fedora with the steps in the guide. However, Daegalus - another forum member - has written a package that will compile Wine for you. You won't need to download the dependencies yourself; the package does it all automatically.

These are the steps I followed: https://forum.affinity.serif.com/index.php?/topic/182758-affinity-suite-v204-on-linux-wine/&do=findComment&comment=1091579

Here's a link to the repo: https://github.com/daegalus/wine-builder

Frank Incense · January 5

12 hours ago, azuredusk10 said:

I didn't manage to get Wine to compile on Fedora with the steps in the guide. However, Daegalus - another forum member - has written a package that will compile Wine for you. You won't need to download the dependencies yourself; the package does it all automatically.

These are the steps I followed: https://forum.affinity.serif.com/index.php?/topic/182758-affinity-suite-v204-on-linux-wine/&do=findComment&comment=1091579

Here's a link to the repo: https://github.com/daegalus/wine-builder

Thanks, but I was able to proceed with compilation by finding Wanesty's webpage ( https://codeberg.org/wanesty/affinity-wine-docs/src/branch/guide-wine8.14 ) and installing lots of missing packages (like pkg-config). Before that I tried to follow the steps at the beginning of this thread.

When running

rum ElementalWarrior-8.14 $HOME/.wineAffinity wineboot --init

I opted to install the Mono package. (Should I have not?) Now I'm stuck when installing dotnet48! Simply executing

rum ElementalWarrior-8.14 $HOME/.wineAffinity winetricks dotnet48 corefonts

aborts with the statement that dotnet48 is broken with the compiled Wine version (7.9.something). When I use winetricks --force it stops at some point when extracting files:

warning: Running /opt/wines/ElementalWarrior-8.14/bin/wineserver -w. This will hang until all wine processes in prefix=/home/david/.wineAffinity terminate
------------------------------------------------------
Executing cd /home/david/.cache/winetricks/dotnet48
Executing wine ndp48-x86-x64-allos-enu.exe
0090:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0090:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0090:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0090:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0024:err:environ:init_peb starting L"Y:\\dotnet48\\ndp48-x86-x64-allos-enu.exe" in experimental wow64 mode
0024:fixme:heap:RtlSetHeapInformation HEAP_INFORMATION_CLASS 1 not implemented!
0024:fixme:clusapi:OpenCluster ((null)) stub!
0024:fixme:clusapi:ClusterOpenEnum (DEADBEEF, 4) stub!
0024:fixme:clusapi:ClusterEnum (DEADBEEF, 0, 0012F858, 00BEDBD0, 261) stub!
0024:fixme:clusapi:ClusterCloseEnum (DEADBEEF) stub!
0024:fixme:clusapi:CloseCluster (DEADBEEF) stub!
0024:fixme:advapi:DecryptFileW (L"C:\\6bbc2762a9efcf76abd10f62\\", 00000000): stub

Don't know what to do next to overcome this.

Frank Incense · January 6

Ok, I tried it again this morning, reset .wineAffinity, and started. After the --init I again made sure that Mono is not installed and removed it. For some reason, after I opted to install Mono once at a previous attempt, wine uninstaller always shows it after the init step. Not sure if this is relevant.

Anyway, the installation of dotnet48 works now as well as Affinity 2 Publisher installation. I have no idea what I've changed to make it work. Unsure if that is good or not 😁

Thanks for any help, and especially to @Wanesty for the guide and effort. I just hope that Affinity will follow Valve's example with Proton and will enhance Wine to make Affinity installation a seamless experience for Linux users.

Frank Incense · January 6

On 1/4/2024 at 11:26 PM, Psych said:

I'm getting mscoree.dll not found when running Photo v1 with ElementalWarrior's wine build. I suspect it has to do with dotnet not installing correctly as I get "there's a newer version already installed" message in the GUI installer. I just have no idea what to do. I tried winetricks --force as well.

First, double-check that you followed the steps from the guide https://codeberg.org/wanesty/affinity-wine-docs/src/branch/guide-wine8.14. Then remove your $HOME/.wineAffinity folder and start from the wineboot --init step again.

Run

rum ElementalWarrior-8.14 $HOME/.wineAffinity wine uninstaller

and check what libraries runtimes are installed. Also run

rum ElementalWarrior-8.14 $HOME/.wineAffinity winetricks dlls list

and post the output. Then proceed with the other steps as per guide and post the output when the error occurs again (make sure that enough lines are included). Finally, I think it would be useful to know which distro and version you use. I'm not proficient with Wine and such but maybe others can help based on the terminal output.

J.S. Bach · January 11

Hi all, thank you for your effort in trying to make these apps work on Linux. I've followed wanesty's guide on codeberg but get tripped up by this command:

rum ElementalWarrior-8.14 $HOME/.wineAffinity wineboot --init

I get this result (on EndeavourOS / Arch)

Rumming /opt/wines/ElementalWarrior-8.14 (wine-7.9-8960-gc12ed146994) in: ~/.wineAffinity
002c:err:wineboot:process_run_key Error running cmd L"C:\\windows\\system32\\winemenubuilder.exe -a -r" (126).
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
00d4:err:wineboot:process_run_key Error running cmd L"C:\\windows\\system32\\winemenubuilder.exe -a -r" (126).
[$ winewow64-build]$ 00f0:err:rpc:I_RpcReceive we got fault packet with status 0x1c010003
00e4:fixme:service:scmdatabase_autostart_services Auto-start service L"MountMgr" failed to start: 1053
00e4:fixme:service:scmdatabase_autostart_services Auto-start service L"wineusb" failed to start: 1115
00e4:fixme:service:scmdatabase_autostart_services Auto-start service L"winebus" failed to start: 1115
00e4:fixme:service:scmdatabase_autostart_services Auto-start service L"PlugPlay" failed to start: 1115
00e4:fixme:service:scmdatabase_autostart_services Auto-start service L"Eventlog" failed to start: 1115
00e4:fixme:service:scmdatabase_autostart_services Auto-start service L"nsiproxy" failed to start: 1115
00e4:fixme:service:scmdatabase_autostart_services Auto-start service L"NDIS" failed to start: 1115

Wanesty · January 11

17 hours ago, J.S. Bach said:
wineboot --init

this step and most wine run commands will give you some errors, this is only for logging purpose and those are likely not an actual issue.

try to proceed with the rest

J.S. Bach · January 16

On 1/11/2024 at 2:45 PM, Wanesty said:

this step and most wine run commands will give you some errors, this is only for logging purpose and those are likely not an actual issue.

try to proceed with the rest

Thank you, I was able to install it by skipping that step! I can now launch the app and see the little splash screen/image, but instantly get a pop-up telling me to use a Windows Aero theme, then the app shuts down.

walt.farrell · January 16

11 hours ago, J.S. Bach said:

Thank you, I was able to install it by skipping that step! I can now launch the app and see the little splash screen/image, but instantly get a pop-up telling me to use a Windows Aero theme, then the app shuts down.

J.S. Bach · January 16

Thanks Walt but I'm not sure how that translates to WINE. I added --no-hw-ui to the launch command in Wanesty's guide but it doesn't do anything.

Edit: adding "wine" in front of the flags changes the pop-up wording to a message about reduced performance without an aero theme. I click OK and then the app crashes / shuts down.

Edited January 16 by J.S. Bach

ElementalWarrior · January 16

14 hours ago, J.S. Bach said:

Thank you, I was able to install it by skipping that step! I can now launch the app and see the little splash screen/image, but instantly get a pop-up telling me to use a Windows Aero theme, then the app shuts down.

Run winecfg and make sure you have your windows version set to something new, like windows 10

J.S. Bach · January 16

6 minutes ago, ElementalWarrior said:

Run winecfg and make sure you have your windows version set to something new, like windows 10

It is set to Win 10 at the moment. I also tried enabling the "virtual desktop" in Wine but get the same error.

azuredusk10 · January 19

Are there any plans to base the patched version of wine on wine 9.0? I wonder if running the Affinity apps with Wine 9.0's Wayland implementation works, and if that gives us support for multitouch gestures and fractional scaling in the Affinity apps.

ddamien · January 20

Thank you so much, Wanesty and ElementalWarrior. Your solution worked perfectly on my Arch system. I can say goodbye to windows now !

Wanesty · January 23

On 1/19/2024 at 10:18 PM, azuredusk10 said:

Are there any plans to base the patched version of wine on wine 9.0? I wonder if running the Affinity apps with Wine 9.0's Wayland implementation works, and if that gives us support for multitouch gestures and fractional scaling in the Affinity apps.

wine 9 doesn't yet have full wayland support, it could probably works as of now but it's not the default yet, i think waiting for the wine devs to make it the default would be the move; unless it now performs better under wayland that it does under Xwayland, it'd need testing

Wanesty · January 23

On 1/20/2024 at 4:27 PM, ddamien said:

Thank you so much, Wanesty and ElementalWarrior. Your solution worked perfectly on my Arch system. I can say goodbye to windows now !

glad to hear!

did you follow the guide on codeberg or the one on the first page of this topic ?
(the topic one is older and not as good)

PancakeWizard · January 29

So I managed to get this working with some trial and error using the codeberg instructions so thank you Wanesty and ElementalWarrior for figuring this out, I'll catalogue the pitfalls here in case they're of any use before I ask my question relating to an issue I'm having:

System:
Linux Mint 21.3, intel i3-10100F@3.6x4, 16GB RAM, 1TB SSD, Geforce RTX 3050 8GB.

Annotations:

1. DO NOT use sudo commands except for the sections on creating folders/copying files to outside of the home directory, which you will 100% need root for eg:

sudo cp $HOME/Documents/rum/rum /usr/local/bin/rum

sudo mkdir /opt/wines

2. Use full absolute directory pathing. $HOME just caused issues further down the setup and had parts installing in different places (especially if you're using sudo to brute force some of the permissions here). using '/home/user/' in place of every $HOME in every instance was effective way through all this.

3. You need to do the extra part in bold here, or you'll just get a warning that dotnet48 is 'broken'.

rum ElementalWarrior-8.14 $HOME/.wineAffinity winetricks --force dotnet48 corefonts

4. The vulkan display changes in the 'tips and tricks' proved fairly essential for decent usability, the flickering gets absurd.

Apart from all that, I followed the codeberg instructions and got it working.

Now for my issue,

Tables. They really slow the application down and will increase crash likelihood (didn't have a single crash until I started experimenting with tables), I'm guessing it's a memory issue of some kind. It doesn't take a big table either, but the bigger the table the harder it falls. Just getting the table tool and creating one that crosses an a5 portrait width in a document that's only a few pages in size is enough to start things chugging. I've experimented with running it as a VM, regediting some direct3D memory, or playing with the performance settings - none of which seem to help.

I'm hoping people are also experiencing this or hopefully have a solution for it.

Edited January 29 by PancakeWizard

PancakeWizard · January 31

Another question: is there a way to install ICC color profiles under rum/wine? Copying them into the system 32 folder where they normally go isn't being picked up by Publisher as available.

Wanesty · January 31

1 hour ago, PancakeWizard said:

Another question: is there a way to install ICC color profiles under rum/wine? Copying them into the system 32 folder where they normally go isn't being picked up by Publisher as available.

i don't have any to try but maybe in affinity's path itself? :

<WINEPREFIX>/drive_c/Program Files/Affinity/Publisher 2/Resources/ICC/

PancakeWizard · January 31

Legend, looks like that worked, thanks! For reference it was the color profile supplied (and insisted upon) by drivethrurpg.

techknowcat · Friday at 05:52 AM

Thank you so much Wanesty and ElementalWarrior you guys rock!

I am so happy to finely have Designer up and running on my system.

even though the install was quite the harrowing experience because my system needed to download so many extra files, and my internet is barely better than a 56 k modem at the moment literally took me the whole day to get done. but it was worth it!

Zode · Monday at 10:54 AM

This is pretty awesome, I remember trying Photo 1.x a long while ago and having a lot of issues (including not even being able to use the canvas or save lol). Seeing 2.x fully functional is making me seriously think about jumping ship from PS.

One issue I do have is uneven scaling on zooms (like what you'd see on low resolution screens back in the day when the content is zoomed in or out, think mode 7 on SNES) and brush display flashing or leaving 'dirty zones' on the screen if the brush is large enough compared to the canvas viewport, any solves for either one? These are both things I can live with if no fix is found as PS under Wine had the same issues but worse 😅

Wanesty · Monday at 10:26 PM

11 hours ago, Zode said:

This is pretty awesome, I remember trying Photo 1.x a long while ago and having a lot of issues (including not even being able to use the canvas or save lol). Seeing 2.x fully functional is making me seriously think about jumping ship from PS.

One issue I do have is uneven scaling on zooms (like what you'd see on low resolution screens back in the day when the content is zoomed in or out, think mode 7 on SNES) and brush display flashing or leaving 'dirty zones' on the screen if the brush is large enough compared to the canvas viewport, any solves for either one? These are both things I can live with if no fix is found as PS under Wine had the same issues but worse 😅

you can try switching from openGL renderer to vulkan, back and forth and see the most usable one

you can see: Fixing flickering and other visual glitches from the guide

Zode · Monday at 11:02 PM

28 minutes ago, Wanesty said:

you can try switching from openGL renderer to vulkan, back and forth and see the most usable one

you can see: Fixing flickering and other visual glitches from the guide

Should've probably noted i already tried that heh. Its currently using Vulkan as GL causes the entire canvas to flash constantly. Also noticed issues with the liquify tool, it keeps alternating between the original state and the modified state every render frame as if it has issues swapping with the backbuffer 🤔 Could try with dxvk instead of wine's implementation but for some magical reason installing dxvk to the prefix causes Photo fail to find its own dll files

Affinity Suite v2.0.4 on linux [ Wine ]

Recommended Posts

Link to comment

Share on other sites

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Wanesty

TheMightyFozz

Wanesty

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Join the conversation

Important Information