Chimes Posted August 5, 2021 Posted August 5, 2021 Yeah, this one crashes just like the previous version did. Really goes against the grain that I have to disable hardware acceleration to maybe make it work or find out the hard way it doesn't by having all my careful editing go down the chute, so, guess I'm stuck with the BETA and constantly being updated every other week. Such a shame Affinity didn't address this widely reported problem for the new version. Quote
Staff Chris B Posted August 11, 2021 Staff Posted August 11, 2021 Hi Chimes, Which previous version? The Beta or Retail 1.9.2? Do you have any crash reports? What graphics card and driver do you have? Most issues relating to OpenCL are either unsupported cards or issues with the driver. Quote How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials
TPVPRO Posted August 11, 2021 Posted August 11, 2021 I have had zero luck using the “NVidia RTX Render” on every machine I have. It will just constantly crash making anything impossible. But, if I select the WARP render the software functions fine on both of my machines so I am guessing the render method is the culprit and not Hardware Acceleration. Quote
Komatös Posted August 11, 2021 Posted August 11, 2021 Hello @TPVPRO and welcome to the forums. With the configuration with two GPUs, you should deactivate the hardware acceleration as a test. You can then put the renderer back on the card to which the monitor is connected. Quote MAC mini M4 | MacOS Sequoia 15.3.1 | 16 GB RAM | 256 GB SSD AMD Ryzen 7 5700X | INTEL Arc A770 LE 16 GB | 32 GB DDR4 3200MHz | Windows 11 Pro 24H2 (26100.3194) Affinity Suite V 2.5.7 & Beta 2.6 (latest) Interested in a free (selfhosted) PDF Solution? Have a look at Stirling PDF Ferengi Acquisition Rule No. 49: “A deal is a deal is a deal.”
Staff Chris B Posted August 13, 2021 Staff Posted August 13, 2021 I have a laptop with an RTX 2060 in it and it works fine so it is absolutely supported - try uninstalling the graphics driver and doing a clean install - don't simply check for updates. Quote How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials
TPVPRO Posted August 13, 2021 Posted August 13, 2021 Sorry guys no such luck on my AMD 3700x PC I ended up having to revert back to 1.9. I perform a clean install with every update. Affinity worked ok after disabling all hardware acceleration but still crashed about 3 to 4 times a day. Runs fine on my intel box but the AMD rig is a nightmare with 1.10. There is something the developers are missing I see too many people complaining about 1.10 for it to be a fluke. I think it’s a real stability issue. Chimes 1 Quote
Staff Chris B Posted August 13, 2021 Staff Posted August 13, 2021 Most of the complaints are from people with outdated or corrupt Nvidia drivers. Because we've enabled OpenCL by default, it's catching them out. For some reason, just updating the drivers doesn't cut it - a clean install of the dirvers usually does and in some cases, DDU is required to remove the old traces of the driver. Whilst I appreciate a simple upgrade should not be causing trouble, there should be no difference between 1.9 and 1.10. If anything, 1.10 should be way more stable due to all the fixes. If you prefer, stay with 1.9 for now and follow the 1.10 beta threads and hopefully one will work for you. In the meantime, if you want to submit the crash reports, I'd be happy to go through them and see if I can find the trigger for the crashing. Quote How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials
Chimes Posted August 13, 2021 Author Posted August 13, 2021 I have the BETA 1.10 because the release crashes just like the 1.9 did. The 1.8.5 release also works ok with my "corrupted" card so I'm probably not going to spend copious amounts of time experimenting by losing my edits. I enclosed the last crash report for the 1.10 release, which has taken up enough of my time, already, it says either the event was not installed or it's a "corrupted installation". I wasn't sure I should post the log entry itself on a public forum, so have deleted it and enclosed screenshots instead. I have uninstalled and reinstalled the display driver, which is intel. Instead of asking me for so much of my time shouldn't Affinity be looking at why the BETA works and the release doesn't? Quote
Komatös Posted August 14, 2021 Posted August 14, 2021 Hello @Chimes I would like to steal some of your time to ask you for a crash report from Affinity Photo. Press Windows key + R, type %Appdata%\Affinity\Photo\1.0\Crashreports\reports and press Enter. If there is more than one .dmp file in the directory, please paste the file with the latest timestamp into your next post. Quote MAC mini M4 | MacOS Sequoia 15.3.1 | 16 GB RAM | 256 GB SSD AMD Ryzen 7 5700X | INTEL Arc A770 LE 16 GB | 32 GB DDR4 3200MHz | Windows 11 Pro 24H2 (26100.3194) Affinity Suite V 2.5.7 & Beta 2.6 (latest) Interested in a free (selfhosted) PDF Solution? Have a look at Stirling PDF Ferengi Acquisition Rule No. 49: “A deal is a deal is a deal.”
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.