Agreed. This long lasting bug has been affecting other areas of the software, including installation. It should be fixed now. As far as I can remember (and I didn’t come down in the last shower), US developers always have had difficulties taking language and region specifics into account. But in this case, I don’t see what kind of coding mistake can make a purely functional, non UI, software feature depend on these settings.
@Topaz
Beware : due to the current geopolitics, I’m observing a new trend in Europe. Many users (pros or hobbyists) are looking for software coming from non-US sources. Obviously, that’s not a wish that is easy to satisfy but US companies should pay more attention to this kind of details.
I really don’t understand why Topaz is so reluctent to re-add in Remove 1, as long as Remove 2 has issues for some users, given the issues seem hard to resolve.
I’m curious. How can regional settings be involved in such a purely technical problem ? This seems to imply that the processing results depend on the user’s country (culture ?). Are models taking the user’s language/region into account in order to compute their results ?
It’s because in the US there’s a point used as decimal seperator while e.g. in Germany a comma is used for that.
So with a german number format set an uneven number is e.g. “1,346” while the code expects “1.346” and thus misinterprets the value (maybe eveything after the comma is truncated?) - leading to that garbage output.
Hmmmm ! I know but I doubt. This would mean that the models used by TP contain numbers in text form, not in binary format. Even the json files in the models folder don’t contain such numbers in text form. And the tz2 files are binaries.
Regional settings should not affect a program beyond the user interface, not the data processing.
Of course it shouldn’t. But this exactly is the issue. And by that it’s also sufficient to only set all number format related settings to US, language and keyboard layout, time zone and everything other can be left at the correct setting.
Is such an error awkward? Yes, of course.
Is it even more awkward that this issue took so long to be solved (really shouldn’t be THAT hard once the culprit is identified)? Yes, of course.
P.S. just use the json posted above as this seems to fix the issue.
We released today Topaz Photo v1.6.0 with fixes on the new Remove Tool v2. You can install this version from your in-app updater (top right) or with this direct link > Windows: Download
Reach out to Support@topazlabs.com with your app logs (Help > Open Logs Folder > Grab all files) if any issues remain and we can relay to the development team!
If anyone updates to v1.6.0 over the weekend and encounters crashes, errors, hanging, or stuck behavior, please test the troubleshooting steps here first:
Multiple users have already confirmed that these steps resolved update conflicts and errors for them.
If issues still remain afterward, please reach out to Support with the details and files outlined in the guide so the development team can continue investigating.
Circling back to inform you all that we released Topaz Photo v1.6.0, which fixes the new Remove Tool v2. You can install this version from your in-app updater (top right) or with this direct link:
Here are the links for Topaz Photo v1.6.0; all you need is select the link that suits your machine:
Once on v1.6.0, ensure to be in AI Processor on Auto in Edit > Preferences > General > AI Processor. Being on the Auto AI Processor will use your full machine capabilities.
When you are able to test Remove Tool v2 on your machine, can you let us know if any issues remain, and we can let the development team know. Make sure to share:
