Daegalus

The most popular open source Publishing app is Scribus https://www.scribus.net As for fonts, did you run `sudo fc-cache -fv` after copying then into the folders? `~/.fonts` `~/.local/share/fonts` `<wine prefix>/drive_c/windows/Fonts` These are the 3 places you can install fonts at the user level and prefix level.

I know how to make Affinity into a flatpak and have it working. The problem is it would be a bit inconvenient for many for multiple reasons: 1. WinMetadata can not be included, has to be downloaded on first run, due to distribution rights concerns with Microsoft. Not an issue per say, but makes the first run take a bit longer and would need some kind of visual letting the user know what s happening. 2. You can't include or pre-install the Affinty products. And not the installers either. You would either need to make an App that you login and parse the website to get the installer only after a successful login. This is filled with edge cases and potential issues. Along with security issues. The other is to ask the user to place the installer in a folder th Flatpak has access to, and the flatpak runs it from there on first run. This would be the same for AppImages, because it's not the technology that is stopping us, but legal and distribution rights.

Yes all 3 work. I have it working in both Bottles and Lutris. I use Flatpaks versions of both Disclaimer: I am writing this entirely from memory on my phone. I am not 100% sure on the Lutris runner path , only like 90%. Bottles: 1. Launch at least once after install to setup, then turn it off. 2. Download the Fedorabuilt version, extract it, and move the whole folder to `~/.var/app/com.usebottles.bottles/data/bottles/runners` 3. Launch bottles and add a new Application. I call mine Affinity because I install all 3 in the same bottle. Set the Runner to the Wine-tkg-affinity one you added earlier. 4. Let it create, then select the Affinity bottle. 5. Go to Dependencies and install allfonts, dotnet48 6. Download vcredist latest from https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170. The one in bottles is buggy. 7. Go to Settings, Advanced Display Options, and scroll down and set Renderer to Vulkan. 8. Back to main page, hit Run Executable and install vcredist. 9. Get WinMetada and install it into `~/.var/app/com.usebottles.bottles/data/bottles/bottles/Affinity/drive_c/windows/system32` 10. Go back to Bottles and hit the power button in the top right corner, and hit Force Stop All Processes (so when they are started again it has proper references to WinMetadata) 11. Hit Run Executable and select the affinity photo installer. Should run, install, etc. then just launch Photos. Do the same for Other affinity apps. Lutris: 1. Install lutris Flatpaks, launch once and close it. 2. Install wine to `~/.var/app/com.lutris.Lutris/data/lutris/runners/wine` the same way as Bottles. You can even copy your bottles runners folder to this one. The `wine` folder might not exist, make it. If you want to be extra sure, launch Lutris and install wine-8.x from the little packing box next to Wine in the runners when you hover over it. It will make the folders and you can find it, then close it again before doing this setup. 3. Start up Lutris and Create a blank Lutris entry for Affinity Photo (use the last manually option in the add dialog) 4. Configure the new entry (little arrow next to Play or right click to entry) And select the wine you want as the Runner and in the next tab, set the Prefix path (you might need to make the new folder) and save. 5. Run Winetricks (little wine glass next to Play) and install corefonts, dotnet48, dxvk-latest, vkd3d-latest. Also set the Renderer to Vulkan with Winetricks and the windows version to Window 10. 6. Hit the wine glass again and select Run EXE in Wineprefix, and select the vcredist.exe like in the bottles instructions, install that. 6.1. install WinMetada into the prefix system32. `<path to prefix>/drive_c/windows/system32` 7. Hit Run in Prefix again and select your Photos installer. Should run. 8. Once installed, go to the Configure tab, go to The tab with path stuff and working directory. Use the browse to find the Photo.exe, and then save. 9. Hit Play and it should run and work with export working and all. 10. Use the Run EXE in Prefix to install all other Affinity products you want. 11. Once you are done installing, right-click and hit Duplicate. In the new entry change the name and in the next tab for the path to the app you want. And save. 12. Do this for all off them. Done. Most people have better success with Lutris. The Bottles sandbox can cause issues for some. I recorded a video of the working result, but forgot to upload it from my work computer and currently busy. So I can post it later. And if needed, I might record a video of a fresh install in Lutris to show it working and how its setup.

No clue. I don't use those guides or scripts. I just add the wine as a runner in Bottles, and use bottles for everything after that.

For the wine-tkg-affinity, if you download the Fedorabuilt one, the `usr` folder is the top level folder with the long wine-tkg name and random string. (See the screenshot of the with just the one folder). Just rename that folder to `usr` If you download the Archbuilt one, the usr folder is right there.

Hey guys, just letting you know I have a 10.6 build using wine-tkg with the 2 patches built for RoResolveNamespace and the Installer Icon fix. You can find the builds here: https://github.com/daegalus/wine-tkg-affinity/releases/tag/25Y07.598 Currently working on a 10.7 build

Nice work. My wine-tkg-affinity does the same thing. I just have been busy and never did the second patch or update to 10.4. I can do it later tonight.

Which repo/branch is that commit in? I'll pull it out as a patches and add it to my wine-tkg-affinity builds

I added the iconw patch posted by ElementalWarrior, I then enabled the built in childwindow patch. That's it. The rest is all build automation. I don't think I tweaked much else. I had a lot more patches for Wine 9.x but with 10, not much is needed.

I have rebuilt wine-tkg-affinity with 10.3 and the icon patch. It also inlcudes the childwindow fix I have always enabled. Feel free to try it. On the topic ProtonUp or ProtonGear, if my wine-tkg-affinity is stable enough for people, i can ask either of the apps to include the builds i release, they are automated and create Github Releases. [Edit] Oops, I just realized its called ProtonPlus not ProtonGear. I was confusing it with GearLever for AppImages

You would need the developer of ProtonUp or Proton Gear to add the repo as a source for builds. But ElementalWarrior doesnt make precompiled builds. So o don't know if we should even be using his name in the repos and projects where we use his patches for builds.

I maintain an Affinity TKG at https://github.com/daegalus/wine-tkg-affinity with builds. I only use the patches from @__avg__ as I wasn't sure which of the many commits on the Elemental warrior repo I needed and I could only track down some to their PRs where they were pulled from. But my builds are on Wine10 already. There is an Affinity Linux discord I was in for a while and many in there had success with it, but others didn't. So YMMV.

No, but you are acting like an entitled asshole and expecting fast support for an issue that isn't easy to solve and behaves differently on every computer. Wanesty and ElementalWarrior are busy people and have their own lives and priorities. Everything they do is in their free time and for the community, but they are not obligated to you. If you haven't noticed, they haven't messaged at all for a while. Also ElementalWarrior has mentioned that his changes aren't easily upstreamable as they might break many other apps. It might be possible, but it would take time to get it just right. Finally, have you considered using Rum, or Bottles, or any other means of setting it up? Each one has different success rates for people. I get great success using Bottles for my affinity, but not Heroic. Others are the opposite. No one can guarantee it working on Linux for you, especially since Serif does nothing to make it easier for us. This is a long shot in the dark to begin with. So maybe cool your jets. Linux is not perfect and I am not sure why you expect everything to work when trying to use Windows software on Linux.

Also, if you copy your `.wineAfinity` to say `.wineAffinity2`, you can experiment with the upgrade and vcrun2022 without breaking your primary installation. Just use the new folder when running the commands. Or just use it as the backup folder Incase you need to revert.

Did you make sure to only build within the distrobox? Once its built, you leave the arch distrobox, and go back to the host bazzite. Then do the rum steps from bazzite using the stuff you built under arch.