Try changing the path in the registry editor.
There is the key “PAI_MODEL_DIR” to modify the file in :
Computer\HKEY_CURRENT_USER\Environment
Then there’s the “path” key to modify the path here:
Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\IntelliPoint\AppSpecific\Topaz Photo AI.exe
And don’t forget to return the files to their custom location.
Thanks for the hint to the regedit. The setting that worked for me was:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Topaz Labs LLC\Topaz Photo AI
and the Attribute “ModelDir”
It was totally detached from the environment var and changing it to the correct directory worked! Thanks.
I can’t get past Detecting faces. It just spins and spins and spins - never progresses past that…
What are the specs for the system you are running TPAI?
And welcome to the group!
This is unrelated to Topaz but I’m a Mac user IT-person who also has to support high-end PCs for Art in higher ed and I recently learned to muck around in the Registry to try and solve some stupid Start menu-related critical error by deleting user profiles…
As for Topaz and Windows: It used to be Mac users would be having all the problems, but in my experience (M2 Mac), face recovery works just fine (see my earlier posts).
And Photo AI for Mac seems to save the models within the app itself, not separately, so deleting the app cleans all of this out for the next update.
You’re welcome. It was a pleasure to help you. 
But in some cases, there’s no choice. You just have to know what you’re doing to avoid mistakes .
v2.3.1 (macOS v13.6.3, LR Classic v 13.1 - plugin mode) is cropping content out of the original image.
After Auto-Pilot processing, with minor adjustment to settings, the DNG image saved to Lightroom has a different framing, with content cropped out of the original. And yes, I’ve followed the recommended procedure of launching Topaz Photo AI while LR is in Browse mode, by selecting Process with Topaz Photo AI from the File–>Plugin-Extras submenu. This has never happened before.
Hi, Are you saying the Nav Box does that? Or, something else?
The Nav Box is notorious for jumping to the upper left of the Nav Panel…instead of staying put.
I believe there may be a hotfix for the AMD drivers that may have a solution according to this user:
The problem with the constant downloading of the model files every time Photo AI is called from Photoshop still exists in version 2.3.1, although the problem is stated in the release notes for version 2.3.0 as fixed.
No, it isn’t fixed!
Have you reported this to support giving information such as: OS, PS version, network info (such as do you use VPN etc.) to help them debug the issue you are having.
Does this happen from the Automate menu or Filter menu in PS or both?
Does PS and Photo AI have full access to the location where models are kept?
I’ve reported this on January 9, 2024. Have a looks at here:
Since January 9, no one from Topaz has responded to my error message or requested further information.
It happens from the filter and automate menue in PS.
Why does PS need full access to the storage location of the model files? PS is installed by default and full access is not requested.
Photo-AI is launched from within Photoshop and only Photo-AI would need this access and not Photoshop.
The access for PS looks like this:
2024-02-07-08-46-43.tzlog (83.9 KB)
2024-02-07-08-49-37.tzlog (80.8 KB)
I believe that because it is launched from PS both would need full access as it would be a container.
So, as I read in your post that wasn’t responded to, that the main issue is the channels.
I have prompted @anthony.lawn to have a look at this issue.
There will be an issue if there are too many channels but PS will handle that when the layer is passed so there will not be any issue.
The community is designed for Users to discuss challenges and functionality but not specifically for tech support. It can happen but the community was not designed for that purpose.
If you want dedicated support then you need to open a support ticket. The are prompt at following up once a request is placed.
Hi,
This is something I already reported 1 year ago but has nothing to do with the current issue that arose when updating from v2.2 to v2.3
As a matter of fact, the problems I had regarding voltage/wattage, have not been solved either by Topaz or by AMD, but they disappeared switching to Windows 11.
Updating the drivers didn’t solve; anyway regarding the current issue I am living without the subject detection and just activate it when needed. Obviously enough if the issue will persist I will take into account when I have to renew the subscription.
I opened the help panel in Photo AI and selected the item “Report an issue” and then ended up here
https://topazlabs.com/my-account?redirect_to=/community/new-topic?category=photo-ai/ photo-ai-bugs&tags=new-issue
If this is wrong, then you should communicate this better in the help panel. So I assume that I end up in the right place when I report an issue.
Reporting an issue and requesting support to resolve a local issue you are having with the software are different choices.
I don’t work with the Topaz team, I am offering a suggestion based on my past experience and ALWAYS getting results from the support team when I reached out with a challenge I wanted to get resolved fairly quickly.
Just trying to offer the path of least resistance for you while you attempt to get a resolution.
