Affinity Suite V2 on Linux [ Wine ]

[azuredusk10]

3 hours ago, Daegalus said:

I could probably make one, I use bottles a lot, the issue is the metadata files and if we are legally allowed to distribute those. That would defeat the purpose of an intaller if we need those files.

I did wonder that. From what I read, the Windows licence doesn’t let you do anything other than run Windows on one machine. I wonder if there’s a way an installer can do everything except copy the metadata files, so that’s the only big manual step a user would have to do?

Alternatively, is it feasible to develop the Metadata files that Affinity needs and upstream them into Wine? (Might be a stupid question - I’m not sure what the files do, what the limits of the Wine project are, and how much work that would be. I’m assuming it’s a lot of work and wouldn’t expect someone to do it for free)

[__avg__]

Got my hands on an AMD GPU for a few hours today & got OpenCL to at least initialise to the GPU. You need the ROCm drivers (and you also need them to not segfault lmao), since Affinity V2 requires the "cl_amd_device_attribute_query" extension when it detects an AMD GPU, and that's only present on the ROCm drivers. I still haven't got it to fully work in my tests since it hangs after trying to flush the some buffer, but that may simply be because I'm using an ancient RX480 and the ROCm drivers haven't officially supported that for a good while. If it hangs for you too, then you can turn off OpenCL with a dll override.

For future reference, you can run something like this to see what opencl extensions it's looking for

strings "$WINEPREFIX/drive_c/Program Files/Affinity/[app]/libraster.dll" | grep cl_

Anyway, give it a try with the latest opencl patch, and see if it works for ya.

[ElementalWarrior]

2 hours ago, __avg__ said:

Got my hands on an AMD GPU for a few hours today & got OpenCL to at least initialise to the GPU. You need the ROCm drivers (and you also need them to not segfault lmao), since Affinity V2 requires the "cl_amd_device_attribute_query" extension when it detects an AMD GPU, and that's only present on the ROCm drivers. I still haven't got it to fully work in my tests since it hangs after trying to flush the some buffer, but that may simply be because I'm using an ancient RX480 and the ROCm drivers haven't officially supported that for a good while. If it hangs for you too, then you can turn off OpenCL with a dll override.

For future reference, you can run something like this to see what opencl extensions it's looking for

strings "$WINEPREFIX/Program Files/Affinity/[app]/libraster.dll" | grep cl_

Anyway, give it a try with the latest opencl patch, and see if it works for ya.

I found I was using a rocm driver from back in January. After installing opencl-amd from aur, the error from the driver went away.

Now I get a lot more opencl logs, but I'm guessing the opencl implementation in wine isn't good enough yet for amd here. I am seeing that clSetEventCallback issue as well.

0150:trace:opencl:clGetDeviceInfo (00005555777DDD80, 0x4039, 8, 00007FFFFE4F0F98, 0000000000000000)
0150:trace:opencl:clGetDeviceInfo (00005555777DDD80, 0x101f, 8, 00007FFFFE4F0F90, 0000000000000000)
0150:trace:opencl:clGetDeviceInfo (00005555777DDD80, 0x101f, 8, 00007FFFFE4F0F90, 0000000000000000)
0150:trace:opencl:clCreateBuffer (000055557D491230, 1, 4096, 0000000000000000, 00007FFFFE4F0EC0)
:3:rocdevice.cpp            :2418: 48075526256 us: [pid:718937 tid:0x79eeb281a740] Device=0x5555777ddd70, freeMem_ = 0x1feffeffc
0150:trace:opencl:clGetMemObjectInfo (000055557A39DC90, 4354, 8, 00007FFFFE4F0EC0, 0000000000000000)
0150:trace:opencl:clGetDeviceInfo (00005555777DDD80, 0x1035, 4, 00007FFFFE4F1000, 0000000000000000)
0150:trace:opencl:clEnqueueWriteBufferRect (000055557D6027F0, 0000555576884390, 0, 00007FFFFE4F0F80, 00007FFFFE4F0F80, 00007FFFFE4F0F98, 4, 0, 4, 0, 000079EE900D8000, 0, 0000000000000000, 0000000000000000)
0150:trace:opencl:clEnqueueFillBuffer (000055557D6027F0, 000055557A39DC90, 00007FFFFE4F0E70, 1, 0, 324, 0, 0000000000000000, 000079EB96992B90)
0150:trace:opencl:clSetEventCallback (0000555576A1D050, 0, 00006FFFE09FB207, 000079EB971D0C10)
0150:fixme:opencl:wrap_clSetEventCallback not yet implemented
0150:trace:opencl:clFlush (000055557D6027F0)
:3:rocvirtual.cpp           :724 : 48075526441 us: [pid:718937 tid:0x79ee8b1396c0] Arg0: void* buf = ptr:0x79edd2601000 obj:[0x79edd2601000-0x79edd2602000]
:3:rocvirtual.cpp           :799 : 48075526456 us: [pid:718937 tid:0x79ee8b1396c0] Arg2: uint pattern_size = val:1
:3:rocvirtual.cpp           :799 : 48075526462 us: [pid:718937 tid:0x79ee8b1396c0] Arg3: uint alignment = val:16
:3:rocvirtual.cpp           :799 : 48075526467 us: [pid:718937 tid:0x79ee8b1396c0] Arg4: ulong end_ptr = val:134062343721280
:3:rocvirtual.cpp           :799 : 48075526471 us: [pid:718937 tid:0x79ee8b1396c0] Arg5: uint next_chunk = val:256
:3:rocvirtual.cpp           :3028: 48075526476 us: [pid:718937 tid:0x79ee8b1396c0] ShaderName : __amd_rocclr_fillBufferAligned
:3:rocvirtual.cpp           :724 : 48075526487 us: [pid:718937 tid:0x79ee8b1396c0] Arg0: void* buf = ptr:0x79edd2601140 obj:[0x79edd2601000-0x79edd2602000]
:3:rocvirtual.cpp           :799 : 48075526494 us: [pid:718937 tid:0x79ee8b1396c0] Arg2: uint pattern_size = val:1
:3:rocvirtual.cpp           :799 : 48075526499 us: [pid:718937 tid:0x79ee8b1396c0] Arg3: uint alignment = val:1
:3:rocvirtual.cpp           :799 : 48075526504 us: [pid:718937 tid:0x79ee8b1396c0] Arg4: ulong end_ptr = val:134062343721284
:3:rocvirtual.cpp           :799 : 48075526507 us: [pid:718937 tid:0x79ee8b1396c0] Arg5: uint next_chunk = val:256
:3:rocvirtual.cpp           :3028: 48075526512 us: [pid:718937 tid:0x79ee8b1396c0] ShaderName : __amd_rocclr_fillBufferAligned
:3:rocvirtual.hpp           :66  : 48075526524 us: [pid:718937 tid:0x79ee8b1396c0] Host active wait for Signal = (0x79ee005fae00) for 100000 ns
:3:rocvirtual.hpp           :75  : 48075526632 us: [pid:718937 tid:0x79ee8b1396c0] Host blocked wait for Signal = (0x79ee005fae00)

 

[ElementalWarrior]

Well I got opencl checked on amd. Although it doesn't work if dxvk is installed into the wineprefix.

New branch:

affinity-photo3-wine9.13-part3

I immediately call the clSetEventCallback. Which means it likely isn't working as expected. Because it should be asynchronous, after the job is done. But :shrug:.

I tried writing a wrapper function. But it just crashed. I'm not sure how easy it is to call PE functions from wine server process.

[__avg__]

16 hours ago, ElementalWarrior said:

I tried writing a wrapper function. But it just crashed. I'm not sure how easy it is to call PE functions from wine server process.

The issue here seems to stem from calling Wine code from within Unix space a non-Wine thread. You can create a function that just does a printf, pass that in as the callback and it will work, but the second you call any Wine code it'll crash lmao. I'm not really experienced enough to solve this problem at the mo, but I'll have a read around! We almost need another callback function for the callback function lmao...

[Zode]

Oh man, working openCL? awesome!

Tried building the affinity-photo3-wine9.13-part3 branch but ran into redefine issues in dxcore header related stuff, but with @Daegalus 's build i got openCL enabled on a nvidia card.

Things noted:
- scaling canvas is still bad, i'm suspecting wine's implementation for filtering/antialiasing is just bad. (and naturally can't check dxvk under which fonts render WAY better but canvas is invisible or the thing just straight up crashes)

- brush still flashes if you zoom close enough, and contents under brush don't update properly, but generates less garbage on screen than before (somehow).

- bigger the window is, slower the app seems to be as if drawing the contents is somehow slower almost as if openCL just claims to be enabled but all operations are still being done on CPU, but might also just be a xorg+nvidia thing lol

 

Even with the minor faults its still very much usable 👌 

[Daegalus]

Just a reminder my build has only some of the TKG patches (child window fixes and some game related stuff) and then the patches from __avg__.

It's missing some of the patches from ElementalWarrior. Like transparent windows, and some other child window fixes. Along with other stuff I'm not sure.

I am only building the stuff, I am not as familiar with Wine's codebase.

[jhob101]

I'm getting an error when trying to install dotnet48 with winetricks:

rum ElementalWarrior-9.13 /home/john/.wineAffinity2 winetricks dotnet48

I've googled the error, but can't see a way around it.

Executing load_dotnet48 
------------------------------------------------------
warning: This package (dotnet48) is broken in wine-7.9-15231-ga7c9b19e1a2. Broken since 5.18. See https://bugs.winehq.org/show_bug.cgi?id=49897 for more info. Use --force to try anyway.

I can install Affinity Photo, but unsurprisingly when running it complains about the lack of dotnet48:

rum ElementalWarrior-9.13 /home/john/.wineAffinity2 wine "/home/john/.wineAffinity2/drive_c/Program Files/Affinity/Photo 2/Photo.exe"
Rumming /opt/wines/ElementalWarrior-9.13 (wine-7.9-15231-ga7c9b19e1a2) in: /home/john/.wineAffinity2
002c:err:wineboot:process_run_key Error running cmd L"C:\\windows\\system32\\winemenubuilder.exe -a -r" (126).
007c:fixme:wineusb:query_id Unhandled ID query type 0x5.
0024:fixme:mscoree:parse_supported_runtime sku=L".NETFramework,Version=v4.8" not implemented
0024:fixme:mscoree:parse_supported_runtime sku=L".NETFramework,Version=v4.8" not implemented
0024:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
0024:err:kerberos:kerberos_LsaApInitializePackage no Kerberos support, expect problems
* Assertion at /var/hostdir/mono/mono/metadata/object.c:4677, condition `is_ok (error)' not met, function:prepare_run_main, Could not set up parent class, due to: Could not load type of field 'Serif.Affinity.Application:<CurrentMicrosoftStorePrices>k__BackingField' (19) due to: Could not load file or assembly 'Windows.Services.Store.StoreContract, Version=4.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. assembly:C:\Program Files\Affinity\Photo 2\Serif.Affinity.dll type:Application member:(null) assembly:C:\Program Files\Affinity\Photo 2\Photo.exe type:Application member:(null)

0024:err:mscoree:expect_no_runtimes Process exited with a Mono runtime loaded.

This is on ZorisOS 17.1 (Ubuntu 22.04)

Any ideas how I can get past this?  Should I try the force install?

[ElementalWarrior]

6 minutes ago, jhob101 said:

I'm getting an error when trying to install dotnet48 with winetricks:

rum ElementalWarrior-9.13 /home/john/.wineAffinity2 winetricks dotnet48

I've googled the error, but can't see a way around it.

Executing load_dotnet48 
------------------------------------------------------
warning: This package (dotnet48) is broken in wine-7.9-15231-ga7c9b19e1a2. Broken since 5.18. See https://bugs.winehq.org/show_bug.cgi?id=49897 for more info. Use --force to try anyway.

I can install Affinity Photo, but unsurprisingly when running it complains about the lack of dotnet48:

rum ElementalWarrior-9.13 /home/john/.wineAffinity2 wine "/home/john/.wineAffinity2/drive_c/Program Files/Affinity/Photo 2/Photo.exe"
Rumming /opt/wines/ElementalWarrior-9.13 (wine-7.9-15231-ga7c9b19e1a2) in: /home/john/.wineAffinity2
002c:err:wineboot:process_run_key Error running cmd L"C:\\windows\\system32\\winemenubuilder.exe -a -r" (126).
007c:fixme:wineusb:query_id Unhandled ID query type 0x5.
0024:fixme:mscoree:parse_supported_runtime sku=L".NETFramework,Version=v4.8" not implemented
0024:fixme:mscoree:parse_supported_runtime sku=L".NETFramework,Version=v4.8" not implemented
0024:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
0024:err:kerberos:kerberos_LsaApInitializePackage no Kerberos support, expect problems
* Assertion at /var/hostdir/mono/mono/metadata/object.c:4677, condition `is_ok (error)' not met, function:prepare_run_main, Could not set up parent class, due to: Could not load type of field 'Serif.Affinity.Application:<CurrentMicrosoftStorePrices>k__BackingField' (19) due to: Could not load file or assembly 'Windows.Services.Store.StoreContract, Version=4.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. assembly:C:\Program Files\Affinity\Photo 2\Serif.Affinity.dll type:Application member:(null) assembly:C:\Program Files\Affinity\Photo 2\Photo.exe type:Application member:(null)

0024:err:mscoree:expect_no_runtimes Process exited with a Mono runtime loaded.

This is on ZorisOS 17.1 (Ubuntu 22.04)

Any ideas how I can get past this?  Should I try the force install?

Try with

rum ElementalWarrior-9.13 /home/john/.wineAffinity2 winetricks dotnet48 -q -f

[jhob101]

9 hours ago, ElementalWarrior said:

Try with

rum ElementalWarrior-9.13 /home/john/.wineAffinity2 winetricks dotnet48 -q -f

Thanks, I tried that but still getting the same issue:

rum ElementalWarrior-9.13 /home/john/.wineAffinity2 winetricks dotnet48 -q -f
Rumming /opt/wines/ElementalWarrior-9.13 (wine-7.9-15231-ga7c9b19e1a2) in: /home/john/.wineAffinity2
Executing mkdir -p /home/john
------------------------------------------------------
warning: You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.
------------------------------------------------------
Using winetricks 20210206 - sha256sum: 0f21da98811e0bfda16a7d6d6b8e860a9cedbd4e836c7dd9b02f068d3092ee2e with wine-7.9-15231-ga7c9b19e1a2 and WINEARCH=win64
Executing w_do_call dotnet48
Executing mkdir -p /home/john
------------------------------------------------------
warning: You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.
------------------------------------------------------
Executing load_dotnet48 
------------------------------------------------------
warning: This package (dotnet48) is broken in wine-7.9-15231-ga7c9b19e1a2. Broken since 5.18. See https://bugs.winehq.org/show_bug.cgi?id=49897 for more info. Use --force to try anyway.

This was the output of the previous stage, there's a few errors in there which I'm not sure if they're significant or not:

rum ElementalWarrior-9.13 /home/john/.wineAffinity2 wineboot -i -f
Wine prefix doesn't exist, do you want to create it? [Y/n] 
Rumming /opt/wines/ElementalWarrior-9.13 (wine-7.9-15231-ga7c9b19e1a2) in: /home/john/.wineAffinity2
002c:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
004c:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
0054:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
004c:err:system:NtUserChangeDisplaySettings Changing L"\\\\.\\DISPLAY2" display settings returned -2.
004c:err:explorer:initialize_display_settings Failed to initialize registry display settings for L"\\\\.\\DISPLAY2".
0054:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hr 0x80004002
0054:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, hr 0x80004002
0054:err:ole:apartment_get_local_server_stream Failed: 0x80004002
0054:err:ole:start_rpcss Failed to open RpcSs service
004c:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hr 0x80004002
004c:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, hr 0x80004002
004c:err:ole:apartment_get_local_server_stream Failed: 0x80004002
009c:fixme:file:NtLockFile I/O completion on lock not implemented yet
009c:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
00a4:fixme:file:NtLockFile I/O completion on lock not implemented yet
00a4:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
00ac:err:environ:init_peb starting L"C:\\windows\\mono\\mono-2.0\\support\\removeuserinstalls-x86.exe" in experimental wow64 mode
00b4:err:environ:init_peb starting L"C:\\windows\\mono\\mono-2.0\\support\\installinf-x86.exe" in experimental wow64 mode
00a4:fixme:msi:internal_ui_handler internal UI not implemented for message 0x0b000000 (UI level = 5)
00a4:fixme:msi:internal_ui_handler internal UI not implemented for message 0x0b000000 (UI level = 5)
009c:fixme:msi:internal_ui_handler internal UI not implemented for message 0x0b000000 (UI level = 1)
009c:fixme:msi:internal_ui_handler internal UI not implemented for message 0x0b000000 (UI level = 1)
010c:err:environ:init_peb starting L"C:\\windows\\syswow64\\rundll32.exe" in experimental wow64 mode
010c:fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet
0114:err:environ:init_peb starting L"C:\\windows\\syswow64\\iexplore.exe" in experimental wow64 mode
0130:fixme:wineusb:query_id Unhandled ID query type 0x5.
0168:err:wineboot:process_run_key Error running cmd L"C:\\windows\\system32\\winemenubuilder.exe -a -r" (126).
john@john-xps15-zorin:~$ 004c:err:ole:start_rpcss Failed to start RpcSs service
0184:err:rpc:I_RpcReceive we got fault packet with status 0x1c010003
0178:fixme:service:scmdatabase_autostart_services Auto-start service L"MountMgr" failed to start: 1053
0178:fixme:service:scmdatabase_autostart_services Auto-start service L"wineusb" failed to start: 1115
0178:fixme:service:scmdatabase_autostart_services Auto-start service L"winebus" failed to start: 1115
0178:fixme:service:scmdatabase_autostart_services Auto-start service L"PlugPlay" failed to start: 1115
0178:fixme:service:scmdatabase_autostart_services Auto-start service L"Eventlog" failed to start: 1115
0178:fixme:service:scmdatabase_autostart_services Auto-start service L"nsiproxy" failed to start: 1115
0178:fixme:service:scmdatabase_autostart_services Auto-start service L"NDIS" failed to start: 1115

And prior to that I deleted the install directories and re-copied everything over fresh (at least what I hope is fresh, I didn't re-compile the wine):

sudo rm -rf /opt/wines/ElementalWarrior-9.13
rm -rf /home/john/.wineAffinity2
sudo cp --recursive "/home/john/ElementalWarrior-wine9.13/wine-install" "/opt/wines/ElementalWarrior-9.13"
sudo ln -s /opt/wines/ElementalWarrior-9.13/bin/wine /opt/wines/ElementalWarrior-9.13/bin/wine64

Any ideas where I can go from here?  Re-compile the wine maybe?

It sure is a learning curve, but I do feel that I'm learning more about wine through this process, which should be a help in the future.

[__avg__]

@jhob101 I believe the order of arguments matters for winetricks, try putting the flag args first

 rum ElementalWarrior-9.13 /home/john/.wineAffinity2 winetricks -q -f dotnet48

 

[jhob101]

2 hours ago, __avg__ said:

@jhob101 I believe the order of arguments matters for winetricks, try putting the flag args first

 rum ElementalWarrior-9.13 /home/john/.wineAffinity2 winetricks -q -f dotnet48

 

Thanks, that worked.  Should have spotted that one myself 🤦‍♂️

I've now got dotnet48 and the corefonts installed, but am stuck on installing Affinity Photo, it bombs out pretty quickly before any modal dialog has been displayed:

rum ElementalWarrior-9.13 /home/john/.wineAffinity2 wine /home/john/Downloads/affinity-photo-msi-2.5.3.exe
Rumming /opt/wines/ElementalWarrior-9.13 (wine-7.9-15231-ga7c9b19e1a2) in: /home/john/.wineAffinity2
002c:err:wineboot:process_run_key Error running cmd L"C:\\windows\\system32\\winemenubuilder.exe -a -r" (126).
0090:fixme:wineusb:query_id Unhandled ID query type 0x5.
0024:err:environ:init_peb starting L"Z:\\Downloads\\affinity-photo-msi-2.5.3.exe" in experimental wow64 mode
011c:err:environ:init_peb starting L"C:\\users\\john\\AppData\\Local\\Temp\\AffinitySetup\\a610f24d-5400-11ef-2389-dc41a9a1d9b6\\SetupUI.exe" in experimental wow64 mode
011c:err:module:fixup_imports_ilonly mscoree.dll not found, IL-only binary L"SetupUI.exe" cannot be loaded
011c:err:module:loader_init Importing dlls for L"C:\\users\\john\\AppData\\Local\\Temp\\AffinitySetup\\a610f24d-5400-11ef-2389-dc41a9a1d9b6\\SetupUI.exe" failed, status c0000135
0024:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFA, 0012FEB8

mscoree.dll is present:

./drive_c/windows/syswow64/mscoree.dll
./drive_c/windows/system32/mscoree.dll
./drive_c/windows/Microsoft.NET/Framework/v4.0.30319/mscoreei.dll
./drive_c/windows/Microsoft.NET/Framework/v4.0.30319/mscoree.tlb
./drive_c/windows/Microsoft.NET/Framework/v4.0.30319/mscoreeis.dll
./drive_c/windows/Microsoft.NET/Framework64/v4.0.30319/mscoreei.dll
./drive_c/windows/Microsoft.NET/Framework64/v4.0.30319/mscoree.tlb
./drive_c/windows/Microsoft.NET/Framework64/v4.0.30319/mscoreeis.dll

Although, shouldn't I be seeing framework v4.8 not v4.0 there?

Add/remove programs shows 4.8 as being installed:

I did find this: 

https://github.com/Winetricks/winetricks/issues/971

which sounds exactly like my issue, but says it should be fixed since 7.12 and as this is 9.13 I shouldn't in theory be seeing that issue so I'm not quite sure what is going on.

Anyone have a clue what's going on here?

[TrippyHippyDan]

Hi all new to this and I managed to get it all installed and  I can open Designer. However, I have been unable to get my canvas to show (Its always black)

I have;

1. Set the renderer=vulkan

2. attempted to set it to the virtual desktop in the winecfg

I followed https://codeberg.org/Wanesty/affinity-wine-docs, but checked out the https://gitlab.winehq.org/ElementalWarrior/wine/-/tree/affinity-photo3-wine9.13-part3?ref_type=heads branch.

Spent the last about 6 hours on it and am finally at the point of requesting help (removed and reinstalled once or twice @.@)

Was trying to figure out how to implement the version from this post but failed to do so.

On 8/2/2024 at 1:26 PM, Daegalus said:

On another note, I have gotten Fedora working along with Arch. New artifacts are available here:

Arch: https://github.com/daegalus/wine-tkg-affinity/actions/runs/10219597913

Fedora: https://github.com/daegalus/wine-tkg-affinity/actions/runs/10218978389

 

To my knowledge, these builds aren't actually specifically tied to a distro. But this is how TKG builds them, so there we go.

Ubuntu/Debian is a nightmare for Wine building, so still trying to get that builder working. 

 

These builds only have the patches from @__avg__ and any from TKG that are provided by default. I will look into adding some of the changes from Elemental's patches.

 

No idea what to even include for assistance in getting to the root cause since I didn't really see any other post with this specific issue.

[__avg__]

On 8/7/2024 at 5:39 AM, TrippyHippyDan said:

Hi all new to this and I managed to get it all installed and  I can open Designer. However, I have been unable to get my canvas to show (Its always black)

ElementalWarrior's wine fork is the way to go at the moment, I haven't updated my patches with his AMD GPU fixes yet since I'm still trying to work out if there's a way to get proper callback support. If that still freezes up, then stick with ElementalWarrior's fork, but disable OpenCL with 'WINEDLLOVERRIDES=opencl='. You will probs wouldn't notice much of a difference in Designer anyway since it's mostly vector based.

[TrippyHippyDan]

On 8/8/2024 at 5:52 PM, __avg__ said:

ElementalWarrior's wine fork is the way to go at the moment, I haven't updated my patches with his AMD GPU fixes yet since I'm still trying to work out if there's a way to get proper callback support. If that still freezes up, then stick with ElementalWarrior's fork, but disable OpenCL with 'WINEDLLOVERRIDES=opencl='. You will probs wouldn't notice much of a difference in Designer anyway since it's mostly vector based.

Sadly running the below results in the same I have a black canvas in witch nothing renders. When you mentioned the fork above were you referring to the master branch? (I had checked out 3.19-part3

rum ElementalWarrior-9.13 $HOME/.wineAffinity env WINEDLLOVERRIDES="opencl=" wine "$HOME/.wineAffinity/drive_c/Program Files/Affinity/Designer 2/Designer.exe"

 

[Wanesty]

ok i finally updated the guide with ElementalWarrior's updated fork and it launched affinity publisher 2.2.0 pretty much flawlessly

i have ROCm HIP drivers (hip-runtime-amd on archlinux) and i know they are working on blender, but i do not have my gpu available in affinity's OpenCL render selection

 

i still think about moving the guide to a documentation style website (think gitbook) but by the time it took me to update the guide, you can guess the website is not gonna be here anytime soon ahah

[__avg__]

8 hours ago, Wanesty said:

i have ROCm HIP drivers (hip-runtime-amd on archlinux) and i know they are working on blender, but i do not have my gpu available in affinity's OpenCL render selection

I think you'll want the "rocm-opencl-runtime" from the Arch Extra repo. "rocm-opencl" on Fedora.

[Wanesty]

6 hours ago, __avg__ said:

I think you'll want the "rocm-opencl-runtime" from the Arch Extra repo. "rocm-opencl" on Fedora.

i downloaded extra/rocm-opencl-runtime 6.0.2-1 and ran affinity but the checkbox was still telling me that my gpu is not compatible

i tried rebuilding wine and got the same issue, so.. shrug

[ElementalWarrior]

1 minute ago, Wanesty said:

i downloaded extra/rocm-opencl-runtime 6.0.2-1 and ran affinity but the checkbox was still telling me that my gpu is not compatible

i tried rebuilding wine and got the same issue, so.. shrug

Find a package appropriately named, but version 6.2.0 instead

[Wanesty]

4 minutes ago, ElementalWarrior said:

Find a package appropriately named, but version 6.2.0 instead

i think it would be the aur/opencl-amd 1:6.2.0-1 package but i'd need to build it(rocm takes ages and a lot of ram to build) AND i don't think putting an AUR package in the guide is a good idea :/

[jhob101]

I have finally got affinity photo launching using ElementalWarrior's affinity-photo3-wine9.13-part3 branch and following Wanesty's guide for 8.14 but replacing everything with 9.13:

git clone https://gitlab.winehq.org/ElementalWarrior/wine.git ElementalWarrior-wine

cd ElementalWarrior-wine

git switch affinity-photo3-wine9.13-part3

mkdir winewow64-build/ wine-install/

cd winewow64-build/

../configure --prefix="/home/john/ElementalWarrior-wine/wine-install" --enable-archs=i386,x86_64

make --jobs 4

make install

sudo rm -rf /opt/wines/ElementalWarrior-9.13
rm -rf /home/john/.wineAffinity2
sudo cp --recursive "/home/john/ElementalWarrior-wine/wine-install" "/opt/wines/ElementalWarrior-9.13"
sudo ln -s /opt/wines/ElementalWarrior-9.13/bin/wine /opt/wines/ElementalWarrior-9.13/bin/wine64

rum ElementalWarrior-9.13 /home/john/.wineAffinity2 wineboot --init

rum ElementalWarrior-9.13 /home/john/.wineAffinity2 winetricks -q -f dotnet48 corefonts

rum ElementalWarrior-9.13 /home/john/.wineAffinity2 wine winecfg -v win11

cp --recursive /home/john/WineShiz/WinMetadata "/home/john/.wineAffinity2/drive_c/windows/system32/WinMetadata"

rum ElementalWarrior-9.13 /home/john/.wineAffinity2 wine /home/john/Downloads/affinity-photo-msi-2.5.3.exe

rum ElementalWarrior-9.13 /home/john/.wineAffinity2 wine "/home/john/.wineAffinity2/drive_c/Program Files/Affinity/Photo 2/Photo.exe"

However I have an issue where it hangs on export.  The exported file does get created.

This is the command output:

0024:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 4 000000001AB827C8 0000000000416DD8 0000000000417B10 0000000000000000
0024:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 3 000000001AAB50A0 00000000004179B8 00000000004186F0 0000000000000000
0024:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 3 000000001AAB50A0 00000000004179B8 00000000004186F0 0000000000000000
0024:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 4 000000001AB82738 0000000000416F88 0000000000417CC0 0000000000000000
0024:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 3 000000001AAB5100 0000000000417B68 00000000004188A0 0000000000000000
0024:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 3 000000001AAB5100 0000000000417B68 00000000004188A0 0000000000000000
0024:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 4 000000001AB82738 0000000000418258 0000000000418F90 0000000000000000
0024:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 3 000000001AAB5100 0000000000418E38 0000000000419B70 0000000000000000
0024:fixme:combase:RoGetParameterizedTypeInstanceIID stub: 3 000000001AAB5100 0000000000418E38 0000000000419B70 0000000000000000
0024:fixme:dbghelp:fetch_thread_info Couldn't open thread 804 (87)
0024:fixme:dbghelp:x86_64_fetch_minidump_module RunTime_Function outside IMAGE_DIRECTORY_ENTRY_EXCEPTION unimplemented yet!
0024:fixme:dbghelp:x86_64_fetch_minidump_module RunTime_Function outside IMAGE_DIRECTORY_ENTRY_EXCEPTION unimplemented yet!
0024:fixme:dbghelp:x86_64_fetch_minidump_module RunTime_Function outside IMAGE_DIRECTORY_ENTRY_EXCEPTION unimplemented yet!
0024:fixme:dbghelp:x86_64_fetch_minidump_module RunTime_Function outside IMAGE_DIRECTORY_ENTRY_EXCEPTION unimplemented yet!

Saving a document I'm working on does work fine.

I've learnt an awful lot about wine/winetricks through trying to get this to work!

ZorinOS 17.1 (ubuntu 22.04)

Any ideas?

[ArcadeCrow]

On 8/10/2024 at 8:52 PM, Wanesty said:

ElementalWarrior's updated fork and it launched affinity publisher 2.2.0 pretty much flawlessly

Does this mean it works almost like windows now? Been trying to decide if I should do this for a while but so far has seemed like to much of a hassle (seeing as I already have a windows machine).

[Astonish]

Hello!

I have been a long time Affinity user on Mac and iPad. I bought them immediatly when they came out for iPad Pro and then for MacOS. And I have always loved them. Years passed (I am still using them on iPad) and I switched to Linux and my biggest issue has always been finding a replacement. I never liked the offerings that there was in Linux and every x months, I am checking if Affinity came to Linux by searching in google "Affinity is coming to Linux" and I have been coming to this thread often. Since I am not very technical on development side (I am a designer), I never wanted to try the guide as it seemed complicated for my level. Well, today I gave up and decided to try on my EndeavourOS device.

Well.. I am writing this post to say a HUGE thank you to everyone involved in this project. First of all to @ElementalWarrior for his Wine fork and all his work. Then to @Wanesty for his very detailed, step by step guide, with which, even a noob like me who never compiled any complicated surface or used Wine, was able to install, all of the three softwares. That is amazing! And obviously, everyone else who is involved in this project to make this happen!

When I was installing, after compiling..etc, I had some errors, which was saying fixme..etc but I googled them and people were saying that they were not a big issue. I had some others as well, but i could not find any info about them. I had arrived to the step to download and start the installer. But just because of the errors, I was discouraged and was just going to remove/uninstall everything (Even though I have no idea how to completely uninstall all the wine stuff as I mostly use package manager). But then I decided to run the installer, very convinced that it wouldn't even start, and then I saw it start! I was surprised and decided to continue. Thanks god I continued because it works!

I am currently on Wayland with Hyprland window manager and Nvidia card, and still, it works very well! Sure, I have some glitches, the OpenCL is not recognized..etc, the fonts on the UI looks weird (I suppose that it is an XWayland issue?) but still, the performance is very good, and the experience is very pleasing! The two "big" issue that I came to till now:

- When I am exporting, the program crashes, closes, with an error : `0024:err:seh:NtRaiseException Unhandled exception code c0000409 flags 1 addr 0x6ffffcbf03cc` which I have no idea what it means but the good news is that at least it exports it. When I save it with the .af* format, it does not happen. Tried it both on Affinity Photo and Affinity Designer.

- Even though I followed the Tips and Tricks page of the guide, about creating the .desktop file, I still am unable to find them on my launcher. But well, I still have to play with it, it may be a stupid typo that I may have done somewhere which I am not seeing.

How about when I update my system? IF there is a new wine version, even though I compiled the wine manually, from the fork, as shown in the guide, will my system update wine to the vanilla and break everything? How do you guys behave maintaining your Affinity installations? Please forgive me if it is a stupid question, but I am right now so excited to know that I may not have to dualboot anymore! Because I have Affinity Suite, Blender and will buy Substance Painter from Steam and I will have all I need on a computer, in Linux!

Sorry for the long post and thank you again! :)

[Wanesty]

  

On 8/13/2024 at 7:35 PM, ArcadeCrow said:

Does this mean it works almost like windows now? Been trying to decide if I should do this for a while but so far has seemed like to much of a hassle (seeing as I already have a windows machine).

ahah no sorry i meant flawlessly as in no regressions compared to the previous versions of wine

 

 

On 8/14/2024 at 10:42 AM, Astonish said:

which was saying fixme..etc

yes, fixme s are mostly harmful, unless you see the repercussion of it, as in: if it's talking about font rendering and the fonts are all wonky, then it's not really harmful ahah
but they do not cause crashed!
 

On 8/14/2024 at 10:42 AM, Astonish said:

But then I decided to run the installer, very convinced that it wouldn't even start, and then I saw it start! I was surprised and decided to continue. Thanks god I continued because it works!

i need to write in the guide issues that can/should be pushed through and the one that are likely to cause issues down the line, this will probably be in the web rewrite i want to do at some point
 

On 8/14/2024 at 10:42 AM, Astonish said:

the fonts on the UI looks weird

if you are referring to the lack of antialiasing, it's a wine thing as it's default settings is to have no font antialiasing
 

On 8/14/2024 at 10:42 AM, Astonish said:

When I am exporting, the program crashes, closes, with an error

yep, known issue, we know the fix but it can also create a regression: not being able to save or open .af* files
 

On 8/14/2024 at 10:42 AM, Astonish said:

I still am unable to find them on my launcher

you need to add the .desktop file to a folder getting checked for them!

/home/liz/.local/share/applications/

would be one of them
 

On 8/14/2024 at 10:42 AM, Astonish said:

will my system update wine to the vanilla and break everything?

no! this is why i decided to use rum! you can have customs version of wines installed that will not interfere with your system wide one (installed via your package manager)
however, new version of the fork will obviously require to rebuild wine
 

On 8/14/2024 at 10:42 AM, Astonish said:

How do you guys behave maintaining your Affinity installations?

can you precise that question ? x)

[Bloque9]

Just adding to bring Affinity to Linux. For the first time Linux passed the 4% market share. The only reason we dont buy more license is just that, and have to work around with online tools.