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

Wanesty

Members
  • Posts

    170
  • Joined

  • Last visited

2 Followers

Contact Methods

  • Website URL
    https://liz.pet/

Recent Profile Visitors

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

  1. if it's not allowing you to enable it from the settings then it's likely what i theorized before: Wine does not come with windows-like GPU drivers, it only translates the application calls to the corresponding Linux drivers. So, the check affinity does to enable OpenCL is likely a GPU driver call, and since those are missing, it simply fallback to not allowing you to enable it also so you get a better idea, the UI is likely using some flavor of Windows Presentation Foundation libraries, and those are using DX9 so we can guess that the UI is using DX9 while the canvas and filters might be using a latter version of DirectX
  2. 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
  3. i don't have any to try but maybe in affinity's path itself? : <WINEPREFIX>/drive_c/Program Files/Affinity/Publisher 2/Resources/ICC/
  4. 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)
  5. 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
  6. just because linux users don't go outside doesn't mean we don't exists :( /j
  7. 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
  8. ugh.. if only a distro agnostic way of distributing packages existed :( (it does. https://flatpak.org/ https://flathub.org/en)
  9. try both ! and use the most usable one, performance/stability wise, for your usecases
  10. only the free version, said codecs are distributed by windows and macOS because win and macos payed for those codecs (namely h264, h265, aac and ac3) this is contradicting your previous sentence "only works on one specific Linux Distribution": they officially support only a single distro and yes, if you want it somewhere else you're on your own, they would have probably chosen to distribute it through Flatpak if it was available back when they chose CentOS. anyway to get back on track and stop talking about an irrelevant product: the last part about education edition of software was just to explain my point that most people that will give them money, ie not crack/endless trial the software are companies from this i can assume that most of their incomes are from companies (no matter what size), and thus a linux version of serif's products would need to be targeted toward companies, game dev, VFX, webdev, any graphic related company that would benefit from a non subscription model and from the ease of deployment linux can offer
  11. i really think you underestimate what could come from having Serif's software suite on linux they have, with the correct marketing and enough effort, the power of making linux a viable graphic related work environment it already is one for development, VFX, music production, office work, day to day use and gaming from my perspective, a lot of people are getting fed up with Microsoft and adobe's monopoly think about companies, as people not earning money directly from a software are less likely to buy it anyway this is why education licenses of software are a thing, and this is also why Davinci Resolve has a free version: it lets you learn the software on your side/at school so the company that will hire you will buy the software/ already have commercial licenses
  12. @desguacemarquesado did you have any warning during the configuration part before building it(with make) ? try the entire building part again and make sure you don't have any warning/errors then in a new wineprefix, install dotnet40 and dotnet48, make sure they completed without GUI errors and then check the location of your winmetadata files
  13. please don't just paste logs without context expecting a solution
  14. rum is only a script allowing you to manage the wine build you made, nothing more also this looks like a compile issue more than a running issue, check that you have all of the necessary dependencies, compile it again and watch if there's any dependencies missing warning/errors the configure part some dotnet 3.5 keys i believe, i don't have a reg file available but you can look at a diff of a .reg between dotnet48 installed through winetricks and a .reg with dotnet48 installed through Bottles
  15. i believe there's multiple ones, so don't bother honestly this is probably a winetricks issue not a rum issue
×
×
  • 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.