Grunt

Not to run SetupUI. It is 32-bit .NET application and just source of different problems. As you run installer, there should be directory C:\User\yourusername\Temp\AffinitySetup\ in wine c_drive. Installer is self-extracting archive. Pause installer/wine after execution (SIGSTOP) and simply find Affinity.msi in this directory and copy it somewhere. Then it is just question of double-clicking or msiexec. If I remember correctly, MSI installers where provided somewhere in history but Serif replaced it wit this 32-bit SetupUI.exe. Or ask Serif for MSI installers. If you really have to, run exe installer on Mono (32-bit version). Here MSI installer resides. In your case. Good luck.

@redluci4 And could you describe your problem more specifically? What registry keys? Either install dotnet48 through winetricks or manually. Switch wine ver to Win.7, dotnet40 first, dotnet48 after this. It works absolutely the same way as installing dotnet in Windows. I have no idea what are you two talking about.

@redluci4, @Wanesty: What registry keys? Could you two please describe the problem with dotnet48? For us as we never encountered any problem.

It is really MSI? wine msiexec /i Affinity.msi is the command. More info here. And i don't think in current form GPU acceleration in Affinity over Wine is viable. Rather don't try luck.

@Jon_TA Grunt never managed to get all three Affinity apps to work on Linux reliably/smoothly. There are bugs, there are crashes. Mostly because Affinity suite was not intended as multi-platform application in the first place. But for very basic work is sufficient and I am surprised myself how good it works. At my workplace I have almost hundred page document/catalogue (created using Photo/Designer/Publisher) and I would love to see this document running on Wine. Only problem is I don't own license for Affinity v1 (personal-license) anymore. Simple steps: Avoid using Ubuntu and Ubuntu based distributions. Use Wine ver. >= 8.16. By now it is probably everywhere other than Debian stable. Satisfy all dependencies. Use Vulkan backend. Good luck.

Well, thanks to Mike Fedora Update-testing repository already contains Wine 8.17 (staging): Tested Affinity Photo, Designer and Publisher. Works fine. Rolling release distributions like Arch Linux, VoidLinux, propably Gentoo, there is nothing to talk about. Wine with dxcore.dll support is already compiled some time (by some time I mean week), Fedora just got wine-8.17 today (it's in update-testing but it should bubble-up to main repository eventually) and for Debian, there is Debian WineHQ Repository and wine-staging 8.17 (from yesterday) so as long you own license for Affinity suite version 1, just update and I guess enjoy. And please don't forget to report bugs and tips

Don't use Ubuntu! Ubuntu is stupid distribution (sorry if I offended anyone but this my own experience). If you really have to use something Debian based, use Debian. Debian is very, very conservative but no so stupid as Ubuntu. Why are you people still using such non standard things like Proton-GE build or whatever? I don't get it. Patches are mostly out of main tree and when lucky, merged in mainline Wine. Definitely not in some custom GloriousEggroll build. Affinity won't even budge there. Bottles, rum. If you have to use it. I can manage my life without one bottle but if it has to be…

And just for fun, this morning I've played in Affinity Photo. Basic editing, RAW development, just few basic tasks. There is constant non-ending stream of "fixme", stubs (mostly in D3D, DirectX and mostly graphical portion - I guess it's slowing application a little bit) in console but so far no crash. Not one! Actually just Photo works so great I'm craving for Affinity version 1 license as I own only license for version 2. 😀 Few issues: There are still some weird UI issues. In example if you don't like official black UI you can't tweak it much (only switch it to pure white) as sliders are unresponsive. Something not yet implemented in Wine. It isn't great idea to use the most memory hungry environment and distribution (Fedora + KDE) on low memory HW and combine it with Affinity. Constant swapping guaranteed. This is something Serif could work on, because in comparison with GIMP, Photo is terrible memory eater. But I get it. There are official HW requirements. I just have to look for much lighter DE and running environment or get memory upgrade. 0098:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 0098:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 0098:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 0098:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 0024:fixme:ntdll:EtwEventSetInformation (deadbeef, 2, 00000001800725A7, 28) stub 0024:fixme:ntdll:EtwEventSetInformation (deadbeef, 2, 00007FFFFE8FCDA4, 28) stub 0024:fixme:heap:GetNumaHighestNodeNumber semi-stub: 000000000041F9A8 0024:fixme:seh:WerRegisterRuntimeExceptionModule (L"C:\\windows\\Microsoft.NET\\Framework64\\v4.0.30319\\mscordacwks.dll", 00007FFFFE100000) stub 0024:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION 00e0:err:ole:CoGetContextToken apartment not initialised 0024:fixme:combase:RoGetActivationFactory (L"Windows.ApplicationModel.DesignMode", {2c3893cc-f81a-4e7a-b857-76a80887e185}, 0000000000419948): semi-stub 0024:err:combase:RoGetActivationFactory Failed to find library for L"Windows.ApplicationModel.DesignMode" 0024:fixme:wintypes:RoResolveNamespace name L"Windows.Web.UI", windowsMetaDataDir L"", metaDataFilePaths 0000000000419AB8, subNamespaces 0000000000000000 stub! 0024:fixme:combase:RoGetActivationFactory (L"Windows.ApplicationModel.DesignMode", {2c3893cc-f81a-4e7a-b857-76a80887e185}, 0000000000419948): semi-stub 0024:err:combase:RoGetActivationFactory Failed to find library for L"Windows.ApplicationModel.DesignMode" 0024:fixme:wintypes:RoResolveNamespace name L"Windows.Web.UI", windowsMetaDataDir L"", metaDataFilePaths 0000000000419AB8, subNamespaces 0000000000000000 stub! 0024:fixme:ntdll:RtlGetCurrentProcessorNumberEx (000000000041BD48) :semi-stub 0024:fixme:nls:get_dummy_preferred_ui_language (0x8 0x405 000000000041CE14 0000000000000000 000000000041CE10) returning a dummy value (current locale) 0024:fixme:nls:get_dummy_preferred_ui_language (0x8 0x405 000000000041CE14 000000001A29DB40 000000000041CE10) returning a dummy value (current locale) 0024:fixme:virtual:NtFlushProcessWriteBuffers stub 0024:fixme:ntdll:EtwEventSetInformation (deadbeef, 2, 000000000139A418, 51) stub 0024:fixme:ntdll:EtwEventSetInformation (deadbeef, 2, 00000000013A3A38, 64) stub 0024:fixme:ntdll:NtQuerySystemInformation (0x000000ce,0x41bd60,0x00000008,(nil)) stub 0024:fixme:bcrypt:BCryptGetFipsAlgorithmMode 000000000041BB30 - semi-stub 0024:fixme:ntdll:EtwEventSetInformation (deadbeef, 2, 000000012B17AEF1, 28) stub 0024:fixme:system:NtUserSystemParametersInfo Unknown action: 8220 0024:fixme:file:NtLockFile I/O completion on lock not implemented yet 0120:fixme:file:NtLockFile I/O completion on lock not implemented yet 0120:fixme:process:SetProcessShutdownParameters (00000100, 00000001): partial stub. 0024:fixme:msg:ChangeWindowMessageFilter c04a 00000001 0024:fixme:dwmapi:DwmAttachMilContent (0000000000010060) stub 0154:fixme:gdi:GdiEntry13 stub 0154:err:winediag:wined3d_dll_init Using the Vulkan renderer. 0154:fixme:d3d:get_vulkan_physical_device Multiple physical devices available. 0154:fixme:dwrite:dwritefactory_CreateMonitorRenderingParams (0000000000000001): monitor setting ignored I was surprised as I saw RoResolveNamespace call and Windows.ApplicationModel.DesignMode and Windows.Web.UI fixme/stub issues. I thought it was Affinity2 issue but obviously not. It is more crucial thing to have implemented in Wine than I thought. Yeah and this:Nobody so far had an issue with using god old faithful GTK File dialog "Wine File dialog"? I don't know how this dialog should be used in tandem with graphical editor or any other graphical application. It's horrible experience. I recommend to save files/exports straight to C:\ drive as there is minimal possibility to crash application with strange file paths, but using it for serious work is horrible. I agree with that. Good lord, thank you for Drag&Drop! So to elaborate a little on file dialog: It isn't infamous Gtk.FileChooserDialog (is just mimicking one) but component called comdlg32. There are two variants of file chooser. filedlg.c - "File Open Dialogs Win95 look and feel" and filedlg31.c - "Win 3.1 Style File Dialogs". I would love to see Win 3.1 in action but so far this has nothing to do with Affinity suite and obviously, I'm not only one having issues with this file dialog: Bug 42645 - File dialog usability. So one bug I'm taking back. 😅 It is a feature!

ElementalWarrior: Oh I lived in illusion it was already merged long time ago. So I was wrong. Anyway, it works. It is possible to save your projects just fine. I presume it would be nice to test entire suite thoroughly. I don't have all installers accessible right now, but give me some time. I'm volunteering to Linux task force already.

Yep. Works pretty fine. Just as exporting files (PNG/JPEG). Or at least in Photo. MoveFileTransactedA bug is closed for some time. Thanks to James McDonnell aka @ElementalWarrior. You just need recent enough Wine. I don't use Ubuntu, i avoid Ubuntu and I have very good reason for that.

If you volunteer to maintaining such installer, you can prepare RPM or DEB installer for yourself So as reported already, initial dxcore patch was added to Wine I_DONT_KNOW_WHICH. Wine 8.16 i guess. So I've tested functionality of unpatched vanilla Wine on Fedora: It WORKS out-of-box! For Affinity ver. 1 no more compilation needed. Of course so long as dependencies are satisfied: binary drivers for your GPU installed and properly used .NET Framework 4.8 corefonts for basic functionality and I strongly recommend using Vulkan driver as default Wine D3D driver is still experiencing UI flickering Dependencies could be installed using winetricks or of course manually (if you know how). Installation might still be little tricky as Serif was able to produce installer not compatible with dotnet48 (it crashes) so I recommend Mono package from your repository prepared at least for installation. After installation Mono can be removed. Tested just Affinity Photo 1 as I do not own license for version 1 and have only installer for Photo by my hand. Guess there shouldn't be any issue running any Affinity application from version 1 Suite. Any distribution of your choice. For binary package on Fedora I recommend just watching koji. Package should be prepared very soon, literally any minute. On any other distribution simply wait, until patched version will bubble up to mainstream repository. Technically next Fedora Design Suite might be prepared to allow running Affinity Suite (ver. 1) but I'm not very much fan of GNOME 3 Desktop Environment so if you have any other recommendation, I'm one big ear.

People on this forum are obviously forgetting one very crucial thing: GNU/Linux is open-source software, while entire Affinity suite is strictly proprietary. After all these years I remember few proprietary project on Linux. If i count out NVIDIA GPU drivers, they ended up pretty much the same. Hostile operating environment I guess. 😁 But I have to give a point to @Wanesty. The criticism is at least factual. So, for staying on the topic this evening: Three weeks ago, there was merge request/commit in mainline Wine tree - apisetschema: Add ext-ms-win-dxcore-l1-1-0. In current situation there is not possible to use ElementalWarrior's dxcore patch. Are there any information what might be next in future? Shouldn't be effort focused rather in this direction?

It is a normal thing to draw when you're developing anything. I'm used to it from OSS development. Sorry if I asked for something secretive. That didn't occur to me.

Is there any roadmap/feature plan for what is planned next or when will be Affinity Suite v3 released? Is there even any future plan?

So just for fun, I've merged (localy) patches for Wayland and you were right: Wine is able to create window and mouse input works. But creating any sub-menu doesn't work yet: 0024:fixme:wtsapi:WTSQuerySessionInformationW Unimplemented class 8 0024:fixme:wtsapi:WTSRegisterSessionNotification Stub 0000000000070090 0x00000000 0024:fixme:uiautomation:UiaReturnRawElementProvider Unsupported object id -4, ignoring. 0024:fixme:wtsapi:WTSUnRegisterSessionNotification Stub 00000000000400B0 0024:fixme:wtsapi:WTSQuerySessionInformationW Unimplemented class 8 0024:fixme:wtsapi:WTSRegisterSessionNotification Stub 00000000000500B0 0x00000000 0024:fixme:uiautomation:UiaReturnRawElementProvider Unsupported object id -4, ignoring. 0024:fixme:wtsapi:WTSQuerySessionInformationW Unimplemented class 8 0024:fixme:wtsapi:WTSRegisterSessionNotification Stub 00000000000B00B2 0x00000000 0024:fixme:uiautomation:UiaReturnRawElementProvider Unsupported object id -4, ignoring. 0024:fixme:wtsapi:WTSUnRegisterSessionNotification Stub 0000000000070090 0024:fixme:wtsapi:WTSUnRegisterSessionNotification Stub 00000000000500B0 0024:fixme:wtsapi:WTSUnRegisterSessionNotification Stub 00000000000B00B2 0024:fixme:wtsapi:WTSQuerySessionInformationW Unimplemented class 8 0024:fixme:wtsapi:WTSRegisterSessionNotification Stub 00000000000C00B2 0x00000000 0024:fixme:uiautomation:UiaReturnRawElementProvider Unsupported object id -4, ignoring. 0024:fixme:wtsapi:WTSUnRegisterSessionNotification Stub 00000000000C00B2 0024:fixme:wtsapi:WTSQuerySessionInformationW Unimplemented class 8 0024:fixme:wtsapi:WTSRegisterSessionNotification Stub 00000000000D00B2 0x00000000 0024:fixme:uiautomation:UiaReturnRawElementProvider Unsupported object id -4, ignoring. 0024:fixme:wtsapi:WTSUnRegisterSessionNotification Stub 00000000000D00B2 0024:fixme:wtsapi:WTSQuerySessionInformationW Unimplemented class 8 0024:fixme:wtsapi:WTSRegisterSessionNotification Stub 00000000000E00B2 0x00000000 0024:fixme:uiautomation:UiaReturnRawElementProvider Unsupported object id -4, ignoring. 0024:fixme:wtsapi:WTSUnRegisterSessionNotification Stub 00000000000E00B2 0024:fixme:wtsapi:WTSQuerySessionInformationW Unimplemented class 8 0024:fixme:wtsapi:WTSRegisterSessionNotification Stub 00000000000F00B2 0x00000000 0024:fixme:uiautomation:UiaReturnRawElementProvider Unsupported object id -4, ignoring. 0024:fixme:wtsapi:WTSUnRegisterSessionNotification Stub 00000000000F00B2 0024:fixme:win:UnregisterPowerSettingNotification (00000000DEADBEEF): stub 0024:fixme:wtsapi:WTSUnRegisterSessionNotification Stub 0000000000010096 0024:fixme:dwmapi:DwmDetachMilContent (0000000000010060) stub and window control and keyboard input doesn't work as well. Are there any other patches for Wayland support not merged in mainline i do not know of yet? It's my bad because back in June i was testing dxvk (not just Wayland) and I just found log. I wasn't even able to create a surface: 024:fixme:file:NtLockFile I/O completion on lock not implemented yet 0134:fixme:file:NtLockFile I/O completion on lock not implemented yet 0134:fixme:process:SetProcessShutdownParameters (00000100, 00000001): partial stub. 0024:fixme:ntdll:EtwEventSetInformation (deadbeef, 2, 00000000015EF2F0, 46) stub 0124:fixme:ole:thread_context_callback_ContextCallback 000000001A86FBD8, 00007FFFFE652E30, 00000000199FF820, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, 0000000000000000 0124:fixme:ole:thread_context_callback_ContextCallback 000000001A86FBD8, 00007FFFFE652E30, 00000000199FF710, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, 0000000000000000 0124:fixme:ole:thread_context_callback_ContextCallback 000000001A86FBD8, 00007FFFFE652E30, 00000000199FF710, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, 0000000000000000 0124:fixme:ole:thread_context_callback_ContextCallback 000000001A86FBD8, 00007FFFFE652E30, 00000000199FF710, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, 0000000000000000 0124:fixme:ole:thread_context_callback_ContextCallback 000000001A86FBD8, 00007FFFFE652E30, 00000000199FF710, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, 0000000000000000 0024:fixme:msg:ChangeWindowMessageFilter c042 00000001 0024:fixme:dwmapi:DwmAttachMilContent (0000000000010060) stub 0170:fixme:gdi:GdiEntry13 stub info: Game: Designer.exe info: DXVK: v2.2-145-g9b019d26 info: Vulkan: Found vkGetInstanceProcAddr in winevulkan.dll @ 0x2d4ad3f40 info: Built-in extension providers: info: Win32 WSI info: OpenVR info: OpenXR info: OpenVR: could not open registry key, status 2 info: OpenVR: Failed to locate module 0170:err:vulkan:init_vulkan Failed to load Wine graphics driver supporting Vulkan. 0170:err:vulkan:init_vulkan Failed to load Wine graphics driver supporting Vulkan. info: Required Vulkan extension VK_KHR_surface not supported Presentable Surfaces: ===================== GPU id : 0 (NVIDIA GeForce): Surface types: count = 2 VK_KHR_xcb_surface VK_KHR_xlib_surface Formats: count = 2 SurfaceFormat[0]: format = FORMAT_B8G8R8A8_UNORM colorSpace = COLOR_SPACE_SRGB_NONLINEAR_KHR SurfaceFormat[1]: format = FORMAT_B8G8R8A8_SRGB colorSpace = COLOR_SPACE_SRGB_NONLINEAR_KHR But this might be a graphical issue on my side. When Wayland support in mainline will be done, I'm going to test it again.