I load a photo from LRC, set sharpening (doesn’t matter what model) with subject All, and set amount. Every time the result is totally destroyed in preview and saved result. See Screenshot.
Topaz Photo AI [v3.2.2] on Windows
I load a photo from LRC, set sharpening (doesn’t matter what model) with subject All, and set amount. Every time the result is totally destroyed in preview and saved result. See Screenshot.
Topaz Photo AI [v3.2.2] on Windows
We’ve had a few reports of this being a problem with recent updates, and it is usually associated with the system needing to meet the Minimum System Requirements or associated with the GPU driver. I suspect that your machine is more well-equipped than your father’s computer, judging by the screenshots you sent to us to review.
To investigate this problem better, we’ll need to examine your full system profile information. This will help us understand what might be causing this issue.
I would also like for you to try updating the GPU driver to ensure that you are on the latest updated driver for your card. You can do this by following the steps below:
Open your Device Manager
Go to Display adapters and double-click on your GPU. Then go to the Driver tab and Update the driver.
i’ve been a little pressed for time. I will obtain the Windows driver and data hopefully tonight. I do want to point out that 3.2.0 worked OK on my system. Does 3.2.2 impose different requirements?
Hello, @mark.mcveigh - The System requirements have not changed and will be the same for any Photo AI versions. On every version, the development team makes updates that benefit the computers that meet requirements, but if your machine is under our requirements, there might come a time where the new features go over what your computer can handle!
To confirm this, we will need to see the System Profile John mentioned, and we will be able to send steps to optimize both your machine and Photo AI.
Let us know when you have sent that in!
I have attached the DxDiag output. Windows says my video device drivers are up to date.
MMcVeigh_DxDiag.txt (93.0 KB)
Thanks for sending over that requested information. Your machine’s GPU’s are only showing about 2GB of VRAM, which our minimum requirement for the application is 6GB.
It is recommended that v3.0.4 or v2.4.2 be used, which may give you a more stable application for this machine. You can use the following links to download these installers for your review:
Topaz Photo AI | v2.4.2 | Windows Installer
Released March 28th, 2024
Topaz Photo AI | v3.0.4 | Windows Installer
Released June 13th, 2024
Newer interface that all v3 have, but v3.0.4 does not have the new Autopilot updates
Can sometimes work on underpowered machines, however will be slower than v2.4.2
Please be sure that once you have chosen a version and downloaded the application, you go to Edit > Preferences > General > AI Processor and set the option to CPU . Using the CPU is not ideal since the CPU RAM memory is not dedicated to graphics, but it can give you better performance for this machine.
As a developer on Linux and Windows, I am very disappointed in Topaz development. It is so easy programmatically to query Windows for hardware particulars. Topaz should be creating backward compatibility especially for customers that have been with them since the beginning. I am able to successfully use Photo AI 3.2.0, but there it ends. I will continue using it with CPU rather than graphics card processing enabled, but will be looking into competitive products that care more about the user base.
I do understand that hardware moves on and new processing capabilities exist, so I suggest providing backward compatibility, but with hard to miss notification during installation about features/performance that may be missing.
Thank you for your replies,
Mark
Well, the good news is that regardless of the discussion of how my ancient hardware can’t work with Photo AI 3.2.2 or newer, magically 3.3.0 fixes the sharpen subject identification (smudging) and the app is working again.
This topic was automatically closed after 60 days. New replies are no longer allowed.