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

Affinity Photo Windows Customer Beta - 1.10.0.1115


Recommended Posts

Click here to download the latest beta

Status: Customer Beta
Purpose: Fixes
Requirements: A valid product key (for Affinity Store purchases), or an installation of the full retail version from the Microsoft Store

As 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.

  • Updated help and translations
  • Improved performance of importing PDFs
  • Improved OpenAsset support
  • Fixed issues with documents that have large numbers of embedded documents, failing to load because we exceed the maximum number of open file handles (leading to Future Version Error)
  • Fixed copying clipboard data as PDF forcing a conversion to RGBA8
  • Fixed Convert to Curves on text giving unwanted transforms on child nodes
  • Added a message box on Astro Stacking completion to say if any light frames could not be aligned 
  • Fixed rare hang in Info page sampler when hardware acceleration is enabled
  • Improved performance of LUTs when there are less target pixels than LUT entries
  • Improved performance of rendering tiny clips

Previous release notes

Link to comment
Share on other sites

14 minutes ago, jaizon said:

Is the Hardware acceleration causing random and constant crashes issue being addressed?

A lot of the reports that we see are to do with out of date drivers, or drivers that need a clean uninstall and reinstall. Is there a crash you are specifically referring to? For crashes, it's really useful to try to locate the crash report, as well as the log file. 

Link to comment
Share on other sites

10 minutes ago, Mark Ingram said:

A lot of the reports that we see are to do with out of date drivers, or drivers that need a clean uninstall and reinstall.

My whole system was a clean install and Nvidia drivers were up to date. Turning off hardware acceleration worked and a new driver just came out today. I've seen plenty of posts in forums where the only solution was turning hardware acceleration off and it did work for me.

Now, I'm unable to reproduce those crashes, since I installed the drivers today both Affinity photo versions are stable (normal one and beta), so it seems it had something to do with the graphic drivers, but not because they were old ad the time but I'll keep it in mind that if it ever starts crashing again I should find the crash logs. Where is it located?

Link to comment
Share on other sites

1 hour ago, jaizon said:

My whole system was a clean install and Nvidia drivers were up to date. Turning off hardware acceleration worked and a new driver just came out today. I've seen plenty of posts in forums where the only solution was turning hardware acceleration off and it did work for me.

Now, I'm unable to reproduce those crashes, since I installed the drivers today both Affinity photo versions are stable (normal one and beta), so it seems it had something to do with the graphic drivers, but not because they were old ad the time but I'll keep it in mind that if it ever starts crashing again I should find the crash logs. Where is it located?

What GPU do you have?

Crash reports are in %APPDATA%\Affinity\Photo\1.0\CrashReports\reports or similar, depending on product, and whether it's a beta (beta is in "1.0 (Beta)" folder).

Link to comment
Share on other sites

I've seen that Photo on MacOS has evolved to RC, and the frequency of betas increases - normally a sign that

the next official release for Photo on Windows will come very soon.

Now i fear that Affinity rushes the process (again), despite lots of (in my eyes) partially major issues are unsolved since month (back to 1.9.1):

Major

https://forum.affinity.serif.com/index.php?/topic/142436-multiple-masks-lead-to-alpha-failure/

https://forum.affinity.serif.com/index.php?/topic/137301-curves-alpha-not-working-when-child-layer/

https://forum.affinity.serif.com/index.php?/topic/142433-crash-with-lighing-filter-bump-map/

https://forum.affinity.serif.com/index.php?/topic/139792-pt-filter-anti-aliasing-issues/

https://forum.affinity.serif.com/index.php?/topic/143068-develop-persona-info-panel-blemish-removal-tool/&tab=comments#comment-792789

 

Normal

https://forum.affinity.serif.com/index.php?/topic/140702-coverage-maps-profiles-for-blend-ranges-and-pressure-profiles-for-strokes-mix-up/ajor

https://forum.affinity.serif.com/index.php?/topic/140371-histogram-pixel-count-error-1941048-rgb32/

https://forum.affinity.serif.com/index.php?/topic/137647-rendering-issue-1921005/

https://forum.affinity.serif.com/index.php?/topic/128674-beta-190864-guides-and-grid-in-develop-persona/

https://forum.affinity.serif.com/index.php?/topic/142485-potential-bug-layer-fx-clip-canvas/

https://forum.affinity.serif.com/index.php?/topic/139232-threshhold-adjustment-issue/

 

What really bothers me: the handling of alpha channel is broken in several aspects (with nested alpha-channel adjustments / filters), and seems to never get fully fixed.

 

Affinity is still an exciting product, but the endless wait starts to really frustrate me.

Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5

iPad Air Gen 5 (2022) A2589

Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps.

 

Link to comment
Share on other sites

There is a very significant difference in the benchmarks between builds 1112 and 1115 for the GPU performance Raster and Combined Single GPU.  Both builds are nominally benchmark version 1920.  Build 1112 numbers are comparable with all versions back 1.9.4.1079 but the latest build 1115 now has numbers comparable to 1.9.4.1048.   This looks like a reversion? It would be really helpful to have consistency here.

Link to comment
Share on other sites

On 7/21/2021 at 11:47 AM, Subclavius said:

There is a very significant difference in the benchmarks between builds 1112 and 1115 for the GPU performance Raster and Combined Single GPU.  Both builds are nominally benchmark version 1920.  Build 1112 numbers are comparable with all versions back 1.9.4.1079 but the latest build 1115 now has numbers comparable to 1.9.4.1048.   This looks like a reversion? It would be really helpful to have consistency here.

What are your numbers? How many tests did you run? I tend to run 5 or so, and average the results.

Link to comment
Share on other sites

Note: the CPU only numbers have always been comparable

Raster (single GPU)

Builds 1079 to 1112  362-384   Build 1115  3354

Combined (single GPU)  444-479

Builds 1079 to 1112  444-479  Build 1115  2683

Typically, I haven't been able to repeat the figures for build 1115 - I tried reinstalling build 1115 but the results are comparable with previous builds.  I must say I haven't tried averaging a few runs but I try to keep the conditions consistent between tests - that is, test straight after installing with no other apps running.  As the figures are so different, my only thought is that the test somehow runs in a different way just occasionally.  Apologies for the false alarm.  Will upgrade my testing to average several runs from now on.

 

Link to comment
Share on other sites

On 7/19/2021 at 6:06 PM, Mark Ingram said:

A lot of the reports that we see are to do with out of date drivers, or drivers that need a clean uninstall and reinstall.

This simply isn't true and you know it. There are plenty of reports here: 

 Not a single person has said that updating or reinstalling drivers has fixed it. 

Link to comment
Share on other sites

9 minutes ago, FYITom said:

This simply isn't true and you know it. There are plenty of reports here: 

 Not a single person has said that updating or reinstalling drivers has fixed it. 

I'm the lead engineer for Windows, so I'm pretty well placed to comment on what common crashes we see.

Looking at the thread you provided, I identified the original crash was within the NVIDIA driver. We know of a problem with Capture One's Explorer integration, which caused a crash within the NVIDIA driver in other applications, and I notice that the original poster mentioned that they have Capture One installed, so that crash will have been caused by them. I reported this issue to NVIDIA, and they are now aware of it (and can reproduce it). 

So yes, to re-iterate, the original crash was indeed caused by a crash in a graphics driver, caused by a piece of third party software being installed.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • 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.