Jump to content

Renzatic

Members
  • Posts

    406
  • Joined

  • Last visited

Recent Profile Visitors

1,628 profile views
  1. Nvidia GPUs don't really have any problem in Linux, besides flaky Wayland compatibility, and having to go a little above and beyond to install the drivers for them. I don't think I've used the Hide Nvidia GPU proton flag once in my entire life.
  2. The only way I've managed to get past that is to create a bottle tailored to applications. It installs Mono automatically, which seems to fix the .Net 3.5 issue. Of course, that limits you to only using Caffe 7.5. When I try creating a custom bottle with another runner, it always fails to grab its own version of Mono. Installing it from the dependencies does nothing. Installing dotnet35 fails to complete, and, well, it seems my options are limited. Changing the runner manually in the yml file doesn't seem to do much of anything at all. Shame this isn't a big game everyone wants to play. We'd have a fully running version by now if it were.
  3. Out of curiosity, what changes have you made to my base configuration? I still can't access the Preferences panel. Also, switching to a Wayland session does lead to a slightly less flicker filled experience.
  4. If you really want the best example for how that'd turn out, look to the Google v Oracle lawsuit that popped up in the courts here a few years back. The way Android translates Java calls isn't entirely dissimilar to how WINE works with Windows APIs.
  5. Most EULAs are filled to bursting with stipulations that sound scary on paper, but are unenforceable from a legal standpoint. Did you all read the license agreement when you installed your Affinity apps? Do you REALLY think Serif has total ownership of our immortal souls?
  6. Think this could be because you're using Wayland? Since I've got an Nvidia card, I tend to stick to X more often than not.
  7. Here you go. Just let me add that it's far from perfect. For some odd reason, I can't access the preferences from the instance that can open a canvas, but if I lead the Run Executable command directly to the .exe in the Program Files folder, it can open the preferences, but crashes when it open a new file. Also, when you make your brush size overly large, it gets very, very flaky. backup_Affinity-Photo.yml
  8. That helped out tremendously. The canvas is buggy, flickering when you drag, pan, and zoom, and occasionally it'll stop drawing portions of your image (which you can get back with a quick pan), but it's actually functional. I opened up an old image, threw a couple of quick adjustment layers on it, then opened a new canvas, dragged the tab over a slot, then ran a paintbrush over it. Didn't notice any lag or hiccups beyond the canvas issues. So you CAN edit in it, even if the experience is sorta janky at the moment. Edit: Here's a quick little video showing off some real basic functionality.
  9. This is the closest I've yet managed to get. I can open the application, and screw around with all the various bits and bobs in the UI, but when I try to open a document, it crashes on me. This is the farther I can go. Edit: Okay, further experiments. I managed to get it to open both a new document, and an old, fairly complicated Photo file I had lying around. The good news is that it works, and it looks like it works well. That old complicated Photo file I opened up has a fair amount of adjustment layers stacked on top of groups of layers each with their own adjustement layers within. It looked like it was handling things like a champ. The bad news is that the UI is a flaky, flickering mess that's nearly impossible to use. So we're 3/4ths of the way there. Underneath it all, there's a working program. We just need to wait until a fix comes by that stabilizes the UI.
  10. There is Krita, which is a helluva lot better than GIMP, though I still wouldn't quite consider it a 1:1 match for Affinity or PS.
  11. WINE Is Not an Emulator! It's even says so in the name! Though WINE is fairly performant compared to their Windows counterpart. You usually get native, or 99% native performance out of applications running through it. On rare occasions, you actually get better performance.
  12. No, there's a good reason. The developers actually spent a good amount of time improving Blender, and keep to a regular release schedule, always offering features people want, and are comparable to the competition. GIMP? Well, GIMP doesn't really do that. Their devs are planning on some nice new features, but we probably won't see them for another 4 to 6 years.
  13. Unless things have changed recently, Gnome Boxes doesn't let you passthrough a GPU. I wouldn't use Photo or Designer in a VM that lacks that option.
  14. Because it's cheaper to let everyone else do their work for them. It's already worked wonders for AMD.
×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.