Using the removal tool in 2.4.0 when operating as a plug in with Affinity Photo results in odd items remaining after removal.
Using the tool with 2.4.0 working standalone doesn’t have same issue, but has resulted in the app crashing (once so far).
None of this behaviour was seen in the pre 2.4.0 version.
Also if you can, please try to recreate this error message in Topaz Photo AI, then go to Help > Open Log Folder, please send me all of the files within that folder. You should be able to attach them directly as a response to this email.
You can securely submit your files(s) to my Dropbox using the link below. Please be sure to send me a note to let me know you sent something.
I’m unable to replicate the problem fully as described.
The only thing that is consistent is that the removal tool operates with varying degrees of success when running as a plug in with Affinity Photo 2 (ver 2.4.0), often leaving/creating odd objects. Standalone it works much more consistently and no more crashes so far.
I checked for a log created on the day of the problem and none is present.
Rather than uploading the whole dxdiag.txt, here is the system info.
System Information
Time of this report: 3/13/2024, 14:00:43
Machine name: DESKTOP-8IAQ1V3
Machine Id: {08E0B4F7-6E77-44BA-8498-D9DEE04C1566}
Operating System: Windows 11 Pro 64-bit (10.0, Build 22631) (22621.ni_release.220506-1250)
Language: English (Regional Setting: English)
System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: X570 UD
BIOS: F34 (type: UEFI)
Processor: AMD Ryzen 7 5800X 8-Core Processor (16 CPUs), ~3.8GHz
Memory: 32768MB RAM
Available OS Memory: 32710MB RAM
Page File: 10116MB used, 24642MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 12
DX Setup Parameters: Not found
User DPI Setting: 144 DPI (150 percent)
System DPI Setting: 144 DPI (150 percent)
DWM DPI Scaling: UnKnown
Miracast: Available, no HDCP
Microsoft Graphics Hybrid: Not Supported
DirectX Database Version: 1.5.0
DxDiag Version: 10.00.22621.0001 64bit Unicode
Had a crash again while operating as plug in to Affinity Photo. Sent what I think is correct log file to the Dropbox. Its only the second time it’s happened, so hardly a major issue. Forwarding just for your info.