Mark Ingram Posted February 9, 2021 Posted February 9, 2021 Click here to download the latest beta Status: Customer BetaPurpose: FixesRequirements: A valid product key (for Affinity Store purchases), or an installation of the full retail version from the Microsoft StoreAs this is a beta it is considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity that may be adversely affected by the application failing, including the total loss of any documents. We hope you enjoy the latest build, and as always, if you've got any problems, please don't hesitate to post a new thread in this forum and we'll get back to you as soon as we can. Thanks once again for your continued feedback. If you have a general question about the software, please head over to the Questions Forum, or if you have any suggestions, please head over to the Feature Requests forum. Changes Fixed Studio Preset shortcuts not being restored after a subsequent launch Fixed slow Channel Mixer adjustment when using hardware acceleration Fixed potential crash on the pattern layer context toolbar sampler control Fixed potential crash when a updating the layer editability Fixed potential crash showing Product Key dialog Fixed New from Clipboard of raster data from external applications, as it was always prefering EMF/WPF over raster data (ignoring the 'Prefer metafile over raster ...' general setting Prevent multiple crashes at startup due to what I assume is a bad OpenCL driver. Previous startup crashes are detected, and hardware acceleration is prevented. Fixed crashes when attempting to register the product Fixed slow Patch Tool and Healing Brush when using hardware acceleration 1.9.1.943 release notes Frozen Death Knight, Wosven, eartner and 6 others 6 3
Subclavius Posted February 10, 2021 Posted February 10, 2021 I am unable to turn off OpenCL with build 944. I uncheck the box and then close it but APhoto no longer asks for a restart. Manually stopping and restarting shows OpenCL still enabled.
Move Along People Posted February 10, 2021 Posted February 10, 2021 To bad but this version only gives a splashscreen and quits. Move Along people,nothing to see here
Microvent Posted February 10, 2021 Posted February 10, 2021 24 minutes ago, haakoo said: To bad but this version only gives a splashscreen and quits. That whwt I get as well just splashscreen and quits
Gnobelix Posted February 10, 2021 Posted February 10, 2021 41 minutes ago, Subclavius said: I am unable to turn off OpenCL with build 944. I uncheck the box and then close it but APhoto no longer asks for a restart. Manually stopping and restarting shows OpenCL still enabled. the same here. Cheers Affinity Photo 2.5: Affinity Photo 1.10.6: Affinity Designer 2.5: Affinity Designer 1.10.6: Affinity Publisher 2.5: Affinity Publisher 1.10.6: Windows 11 Pro (Version 24H2 Build (26100.3037)
footeg Posted February 10, 2021 Posted February 10, 2021 42 minutes ago, Subclavius said: I am unable to turn off OpenCL with build 944. I uncheck the box and then close it but APhoto no longer asks for a restart. Manually stopping and restarting shows OpenCL still enabled. I get the same. I didn't try with build 943 so don't know if this was the same.
v_kyr Posted February 10, 2021 Posted February 10, 2021 1 hour ago, Subclavius said: I am unable to turn off OpenCL with build 944. I uncheck the box and then close it but APhoto no longer asks for a restart. Manually stopping and restarting shows OpenCL still enabled. Hmm, probably the property change/update listener for the OpenCL setting change then does not take effect here (will not be executed aka not triggert). - A manual stop and restart then might always read/get the previous so far in the properties file settings unchanged value. ☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan ☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2
Staff Pauls Posted February 10, 2021 Staff Posted February 10, 2021 for those with the crashing app does it crash on every attempt to run up ?
Move Along People Posted February 10, 2021 Posted February 10, 2021 Move Along people,nothing to see here
Ken Cope Posted February 10, 2021 Posted February 10, 2021 The app runs okay here. And restart requested if I change renderer from my graphics card to warp. Windows 11 Pro 64bit ¤ AMD Threadripper 3990x ¤ Nvidia RTX 3090 ¤ 256GB DDR4 Ram ¤ ROG Zenith II Extreme Alpha
Johann Dietz Posted February 10, 2021 Posted February 10, 2021 Hi, I´m user of Affinity Photo. Normally when I start the beta version and a popup informs me that a new version is available I click on the download button. I will then be transferred to the download page where I click on the download button and the download starts then ..... normally. This time the screen flickers shortly and then nothing happens. Appreciating your help with the problem Johann Dietz
Staff Chris B Posted February 10, 2021 Staff Posted February 10, 2021 Hey Johann Dietz, Try right-clicking the download link and open in a new tab. I had to do that this morning. Or copy the link address and paste into a new tab. Uncle Mez 1 How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials
Mark Ingram Posted February 10, 2021 Author Posted February 10, 2021 I've discovered the cause of the inability to disable OpenCL in the beta. That'll be fixed in the next build. Uncle Mez 1
Mark Ingram Posted February 10, 2021 Author Posted February 10, 2021 1 minute ago, Mark Ingram said: I've discovered the cause of the inability to disable OpenCL in the beta. That'll be fixed in the next build. This same problem also causes the crash on startup. To work around it, open the following file: %APPDATA%\Affinity\Photo\1.0 (Beta)\Settings\PerformancePreferences.xml And make sure it has the following entry (inside the <Settings> tags): <UseHardwareAcceleration>True</UseHardwareAcceleration> Apologies for the inconvenience. Uncle Mez and Chris B 2
AlainP Posted February 10, 2021 Posted February 10, 2021 7 minutes ago, Mark Ingram said: This same problem also causes the crash on startup. To work around it, open the following file: %APPDATA%\Affinity\Photo\1.0 (Beta)\Settings\PerformancePreferences.xml And make sure it has the following entry (inside the <Settings> tags): <UseHardwareAcceleration>True</UseHardwareAcceleration> Apologies for the inconvenience. That did not change anything for me. When I try to disable HA it does not ask for a restart. Going back to Preferences shows that the check mark is still there. But I Photo works fine and I don't have any crash. -- Window 11 - 32 gb - Intel I7 - 8700 - NVIDIA GeForce GTX 1060 -- iPad Pro 2020 - 12,9 - 256 gb - Apple Pencil 2 -- iPad 9th gen 256 gb - Apple Pencil 1 -- Macbook Air 15" - Mac mini M2-Pro - 16 gb
Mark Ingram Posted February 10, 2021 Author Posted February 10, 2021 1 minute ago, AlainP said: That did not change anything for me. When I try to disable HA it does not ask for a restart. Going back to Preferences shows that the check mark is still there. But I Photo works fine and I don't have any crash. That was for the crash at startup @AlainP. It won't affect the problem of being unable to disable hardware acceleration. Uncle Mez 1
AlainP Posted February 10, 2021 Posted February 10, 2021 OK thanks -- Window 11 - 32 gb - Intel I7 - 8700 - NVIDIA GeForce GTX 1060 -- iPad Pro 2020 - 12,9 - 256 gb - Apple Pencil 2 -- iPad 9th gen 256 gb - Apple Pencil 1 -- Macbook Air 15" - Mac mini M2-Pro - 16 gb
Move Along People Posted February 10, 2021 Posted February 10, 2021 @Mark Ingram Uninstalled beta 1.9.1.944>reinstalled>rebooted>ctrl+runup = no go run as administrator = no go Looked at appdata > folder photo\1.0(beta) created Settings folder is empty > so not able to edit the xml file Move Along people,nothing to see here
v_kyr Posted February 10, 2021 Posted February 10, 2021 9 minutes ago, AlainP said: That did not change anything for me. When I try to disable HA it does not ask for a restart. Going back to Preferences shows that the check mark is still there. That's actually just a temporary manual fix, so you can use this beta build at all without crashing. - Mark will address the UI based <UseHardwareAcceleration> change/update settings and triggering in the next beta version update. AlainP 1 ☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan ☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2
Staff Sean P Posted February 10, 2021 Staff Posted February 10, 2021 Hi Haakoo, If you do a ctrl run up, it will remove the value and cause the crash you're seeing again. Just copy the PerformancePreferences.xml from the non-beta folder, modify the line Mark mentions and DO NOT ctrl run up. You should find it should then run up. Uncle Mez and Mark Ingram 2
Move Along People Posted February 10, 2021 Posted February 10, 2021 Copied all from release version and now runs The ctrl+ runup was a run before I checked the appdata folder so the question remains why the empty settings folder? But all good now 👍 Patrick Connor 1 Move Along people,nothing to see here
Staff Sean P Posted February 10, 2021 Staff Posted February 10, 2021 Just now, haakoo said: The ctrl+ runup was a run before I checked the appdata folder so the question remains why the empty settings folder? Glad its all running up! A Ctrl Run up will literally clear your settings, so that is why the folder gets emptied. The issue was that if you don't have that value set it was crashing trying to set it. So a ctrl-run up would clear it and then fail to set and get stuck in a crashing loop! Move Along People 1
v_kyr Posted February 10, 2021 Posted February 10, 2021 In this actual context it might be generally useful to see also how to manually set/toggle hardware acceleration on/off until the next beta build fixes the UI based HA setting switching. [FAQ] How can I disable OpenCL compute acceleration on Windows? ☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan ☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2
Move Along People Posted February 10, 2021 Posted February 10, 2021 8 minutes ago, Sean P said: Glad its all running up! A Ctrl Run up will literally clear your settings, so that is why the folder gets emptied. The issue was that if you don't have that value set it was crashing trying to set it. So a ctrl-run up would clear it and then fail to set and get stuck in a crashing loop! I do ctrl+runup>reboot at every new beta to make sure it has the new features stick and have a clean install. Shouldn't it revert to a default state and leave the xml files with the basic settings? Move Along people,nothing to see here
Mark Ingram Posted February 10, 2021 Author Posted February 10, 2021 18 minutes ago, haakoo said: I do ctrl+runup>reboot at every new beta to make sure it has the new features stick and have a clean install. Shouldn't it revert to a default state and leave the xml files with the basic settings? It does - but it crashes as it's doing it. Move Along People 1
Recommended Posts