Jump to content
Our response time is longer than usual currently. We're working to answer users as quickly as possible and thank you for your continued patience.

Nox

Members
  • Posts

    23
  • Joined

  • Last visited

Recent Profile Visitors

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

  1. The Affinity apps crash my AMD display driver a lot and very random. Most of the times they happen when I move/pan or zoom the view. The screen where the App is running then will turn black, the system is still a little bit responsible (for example: media buttons still work) but not the display, the secondary display is frozen and it takes around half a minute for AMD to restore the graphics driver (I use the appearing crash report every time), in 99% of the cases the Affinity App has crashed too then. Sometimes (rarely) the graphic driver isn't able to restore itself, then I have to reset the PC, this will result in no crash reports on both sides. It is more likely to happen when I have Live Effect layers in the document. But sometimes the driver also crashes when I edit vector curves or for example change letter kerning/tracking on Artistic text. This problem is present in Affinity Photo, Affinity Designer, Affinity Publisher in Version 2 and 1. Enabling or disabling OpenCL hardware acceleration also has no effect on this issue. I have this issue for quite a while now and I've waited to report this issue for the OpenCL bug to be fixed, because I thought this might fix the issue. But no luck as it seems. Just for clarification before the blame is put on AMD again: Adobe Products, DaVinci Resolve, Krita, Blender, Inkscape do not have any issues on my hardware nor did the graphics driver ever crash once while I was using these Apps. In fact Affinity Apps (and Valheim in Vulkan) are the only source of display driver crashes on my PC. My PC configuration for reference: CPU: AMD Ryzen 7 3700X GPU: AMD Radeon RX 6800 XT (Driver: AMD Software: Adrenalin Edition Version 22.11.2) RAM: 32GB @ 3200MHz Display: 2x 1080p (144Hz + 72Hz) OS: Windows 11 Version 22H2 (OS Build 22623.1020) Crash Reports are attached 49f1e9ca-17cc-4679-931a-835f091b3c53.dmp attachment_Log.txt
  2. Sounds amazing, thank you so much for listening to your community and customers!
  3. From a bit of testing everything seems to work, apart from the presets and Studio Link (Publisher). I'm sure Studio Link can be fixed by hacking some Symlinks in place, not sure how to fix the presets tho. Going to set up a VM later to test this stuff.
  4. I already think about doing serif's job and writing an application which extracts the MSIX archives, installs the files to the users destined location and registers the file associations automatically. I have to look if there's something like this out there already, so I don't have to "waste" my time on that matter. (didn't find anything yet) PS: It's also not "really" portable that way, the program settings and license information are stored in %localappdata%\Affinity
  5. I'm not sure why you defend this behaviour, these are lame excuses. Of course it is a bit more work but that this will benefit the customer. The applications are self containing (apart from the user settings which are generated by the application itself), there is no cumbersome work to do to package them. it is as simple as that. They already have the tools and infrastructure for creating their MSI/EXE-installers from Version 1. Modifying this toolchain to work with V2 isn't an undoable task. Considering how much more customer and user friendly this approach is make the little bit of extra work worth to do. I have a software development background myself and for my projects I take extra steps to make the user experience pleasant and convenient. I don't want to attack you but I'm not sure if you are trolling, have no clue or think too complicated. I honestly don't know what you are talking about. This was already part of Version 1. And from my experience fetching update information on the client side isn't complicated and serving the release info via an API (or even just a normal string) on the server is also not a big deal. The testing of these features maybe takes a few hours up to a day for one person. They make a product and they want people to buy it, there is no defending in anti costumer practices because it's a little more comfy for the developers.
  6. This FAQ mostly is a sham, I can see some valid points, but there is no reason not to simply give the customers the option to download either MSI/EXE or MSIX. Just offer MSIX as the first option for the non-technical users but give everyone who wants it the option to use the non-windows-app-crap MSI/EXE format. Not really, it's just a different installer packaging format. You can even simply one-click convert MSI/EXE installers to MSIX, so in that regard they can just have to maintain one version really.
  7. I agree, delivering the suite as "Windows Apps" and not normal ".exe"-applications is extremely customer and user unfriendly. Not even Adobe dared to take this tainted path. It rips off all the control the user have about their PC and the programs and makes things unnecessarily complicated. I'm very disappointed.
  8. Adobe products use OpenCL on AMD GPUs, they have zero issues running on there. DaVinci Resolve uses OpenCL, but surprisingly it doesn't have any issues on AMD either. Blender switched from OpenCL to HIP on AMD GPUs, because this API is more reliable, versatile, faster, future proof and very similar to CUDA. Also OpenCL as a whole has really big problems in general, it's hard and annoying to implement for hardware manufacturers, that's why everyone sticks to 2.0. OpenCL 3.0 is a big reset which makes most features optional because Khronos (standardisation organisation) has realized 2.0+ was a big mistake. Serif has 3 options to handle this: - fix the OpenCL bug like all other creative apps, make use of OpenCL 3.0's feature query function in the future. - think straigh forward, future proof and switch to a better API (HIP and CUDA) - or just do nothing and blame AMD for not supporting a broken API Obviously the latter option does not fix anything.
  9. Blender uses HIP on AMD hardware, which is a CUDA competitor. HIP runs on AMD and Nvidia GPUs, it even has an automated CUDA to HIP source code converter, so there is absolutely no excuse to not include this acceleration technique in your application if it already has CUDA support! And yes DaVinci Resolve has zero issues with AMDs OpenCL driver, it performs a lot better on my new AMD GPU compared to my previous Nvidia 1060. The fact that the Affinity suite is the only software collection which has these problems makes me believe that this is not an AMD problem at all, just an excuse to not bother fixing the bugs for which Serif don't care much about.
  10. This needs to be fixed ASAP, a lot of my multi-layer projects just look like this in task manager and when I try to do something it freezes my entire PC for a few seconds: my poor Ryzen 7 3700X can't handle this. I literally cannot work under these conditions and until the problem is fixed I will probably have to switch to an Adobe subscription, I would like to avoid this... My System for reference: CPU: AMD Ryzen 7 3700X / 8C/16T RAM: 32GB / 3200 MHz GPU: AMD Radeon RX 6800 XT / 16GB VRAM
  11. I had the same idea already but I don't think I'm going to fiddle with that, the drivers will definitely have some conflicts with one and another and getting them to work somehow together is not a task I'm willing to dedicate time towards. In the case it will somehow work with the Affinity Suite, there still can be problems because I do also game on this PC and in this case driver conflicts are more prominent and annoying to deal with. But also: 2 GPUs wont't fit in my PC case anyways. I'm also heavily disappointed in the way serif is handling this issue, instead of giving your mature audience the freedom to enable this feature even if it crashes your software, they are holding hands and prohibit any interaction. A better way would've been a warning message you can dismiss and still enable it to see for yourself if the new driver update has fixed the OpenCL bug or not. I hope this issue is getting fixed soon, because it seems - if it is still a problem at all - it is something serif can fix, other software I use which utilise OpenCL, do not have any issues with my AMD GPU (DaVinci Resolve for example).
  12. I just bought a RX 6800 XT and finally switched from my 1060, a purchase for which I have saved money for over 2 years. I'm experiencing worse performance in my project files than before, now I'm here, read the thread and my disappointment is unmeasurable...
  13. Ok this is really helpful, now I understand how this works. I took a look back into the document, checked "Show Orientation" and immediately saw what's wrong, thank you so much!
  14. Oh I see, the N was on Winding. But I have another letter (R), which is also holed and is not getting filled with the Winding fill mode (which it is on by default), if I switch to Alternate it stays the same. I think I don't quite understand how these modes work.
  15. Thanks, why does it switch to Winding (Non-Zero) when I combine shapes?
×
×
  • 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.