Jump to content
You must now use your email address to sign in [click for more info] ×


  • Posts

  • Joined

  • Last visited

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. i gave GIMP a new try the other day(yes i also tried the beta), the UI/UX is pretty bad and the workflow way too destructive for my taste, i much prefer Krita over GIMP for most usecases. i usually prefer Krita over AP for most photoshop-like usecases too! however both lack real, good vector: tools, rendering and manipulation so AD is still necessary for my workflows.. also, if you need to do advanced text work Af Publisher is pretty much irreplaceable.. it's sadly not really.. because: :^)
  2. joke aside, i'm not sure what "problem" you're referring to.. i thought my post was covering most of your concerns ? please i'd love to know what you meant !
  3. i believe the windows and the MacOS code differs a bit so i don't know if it relies as much on dotnet stuff on the latter, anyway, yes building for arm is easier than a full port. With that said i would assume that porting to ARM and thus having to use a more limited instruction set had some meaningful impact and probably required some rewrite to get x86-64 specific optimization running on ARM (supposition, i don't know how low level Affinity is but that's the reasoning behind my troll-ish remark). from the top of my head i can list: Bitwig, DaVinci Resolve (which started on linux btw), VMware, Red Hat stuff, Discord, Spotify, Steam, Sublime Text, JetBrains IDEs, amd's own gpu drivers (AMDGPU-PRO) however yes, having to maintain for multiple distro is very time consuming, and that's why DaVinci Resolve sticked to only officially supporting openSUSE, but now flatpak exist ! And it makes it way easier for both small project and big commercial software like Bitwig(flatpak mention) ! :) i haven't looked into it but if it got pushed in main wine, removing the dxcore related stuff in ElementalWarrior's fork .patch files should probably do the trick ? OMG ALSO !! this means that pre-winmetadata-requiered version like the 1.10.4 (or 1.10.3 i forgor) SHOULD RUN ON LINUX WITH DEFAULT WINE !!! EDIT : my point here was that even tho Resolve is only on officially supported on openSUSE, it has been "ported" to other distro and maintaned by the community, so yes since most of the OS is open source/libre, having to rely on companies to fix stuff instead of being able to do it ourself is what makes most linux users hate proprietary software. ("fix stuff" : for example the fact that most proprietary soft (including nvidia drivers) took ages to get compatible with Wayland (or still aren't)) however it can be done right : Steam very actively rewrote a ton of stuff like hardware acceleration and the general UI framework for all three distributed version mostly because they wanted to improve the linux app ! for the steamdeck Also mandatory mention of Unreal Engine that is proprietary but with publicly available source code
  4. funny how quickly it got updated for ARM btw ^^ (...)
  5. Linux is a kernel. this is not an issue anymore, you can either chose a single distribution to support like Davinci Resolve did with openSUSE, OR even better, you could use Flatpak (Flathub) like most developers are currently moving towards as a mean of distribution (it can bundle dependencies easily instead of relying on distro packaged ones). The codecs Affinity uses are available freely(i.e.ie libre) on linux. And i believe Serif is already paying for distributing Pantone colors. (please do tell me if i'm missing a codec that wouldn't be on linux.) Linux's userbase is small yes but again, growing, and non/small pro users are the ones asking for it because : companies that are already using linux will see and that serif, adobe, etc are distributing a linux version and they know that it's useless to waste company time trying to convincing them to port it. But as Sorn pointed out that yes, there is professional interested in a linux port.
  6. my own followup: > okay... i just noticed but like, they did save but on my desktop ??? (not the folder i selected) mmh.. it's pretty bad then if the only fix is making a config file in a vm :/
  7. anyone experiencing saving issues with the experimental WoW64 compile ? (as reported in an issue)
  8. imo this isn't really a solution, getting it working correctly and smoothly enough for professional use requires your to have two gpu (or use vmware's emulated gpu driver idk how good it is but i heard nice things)... just don't bother and stick to windows/macOS, imo if you have to start an os(vm) or worse, loose your current flow of work by rebooting your machine just is not worth the trouble (like i much prefer the software crashing randomly than having to babysit two os with my settings etc) anyway, thank you @Sorn for your professional insight of your situation with the affinity products :)
  9. i mean.. for this instance you're right but Linux has a lot of pro userbase and software, especially DAWs, video editing, VFX, game development, most kind of dev actually ahah sadly Apple and Adobe really made macOS the standard for graphic design, (specifically talking about Adobe products, Sketch and Glyph) (as for windows, it simply have the largest userbase so they(serif and adobe) kinda have to make it available there..)
  10. ahah no, exporting to anything but vector format crashes all three affinity software, save, export, and if it stays stuck on a frozen state, kill wine with the command listed on the tips and fixes page it's kind of a pain ngl but as i said a few times, i sadly can not recommend using affinity on linux if you're using the affinity suite intensely, for professal work purposes. it is usable for most of it's usecases, but far from flawless..
  11. saving configs is... weird your best bet would be to save your workspaces with Window > Studio > Add Preset i also had some random success with the virtual desktop feature, explained in the tips and fixes page that and closing affinity using File > Exit would be the most likely setup for success
  12. was in your situation Affinity was the only software holding me back from switching but when i saw that some people got it working and that ElementalWarrior did a fork of wine for the V2, i finally switched completely, and even made the guide discussed over on it's not as simple as double-click installing affinity but the updated guide aims to make it easier for graphic designer, that are not devs nor really knowledgeable about linux to get it working ! Maybe try it for yourself and if you can deal with the few bugs and glitches, you'll probably see yourself ditching windows ! However ! i sadly cannot recommend it if you're using Affinity for professional purposes ! It will depend on your usecase tho so consider giving it a shot :)
  13. the content of the guide is too fluid to be made into a video, i moved the guide to codeberg to address this exact issue (the forum not letting me edit stuff like i need to) however please do tell us the issues your facing with the codeberg guide and it's likely ambiguity (;feel free to write an issue there directly with suggestion on what's lacking and how it could be improved! )
  14. won't even open on my side but it's an issue with wayland not being available as a wine driver, i'll spend more time on the wayland stuff later
  15. done ! i kept the previous iteration of the guide and referenced it as an alternative edit : i'll try and compile it again with wayland support to see how usable it is
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.