And, every couple months I go to the Downloads page to see if there are newer versions (with more or diff. features) listed relative to the versions I have installed.
I wasn’t pampered growing up so guess it was drilled into me to be proactive.
I uninstalled 3.3.4 and also deleted the Sharpen AI folders in my Windows AppData folder that were left hanging around. Then I reinstalled 3.3.4, but the berserk behavior is still there. Over the last few months I have seen other people report this or similar bugs for earlier versions, but it never hit me until 3.3.4.
Application & Version: Topaz Sharpen AI Version 3.3.4
All working fine on my system now (Win10, AMD CPU and GPU). It gets confused at times when I try lots of repeated model changes and have about 8 GB of Lightroom RAM in play, but otherwise does fine.
This is almost comical. I have been patiently waiting for WEEKS on a response as to why Topaz Sharpen will not load on my system. Its just hangs. Same for both plugin and standalone The only feedback I have received thus far per my support requests are, make sure my monitor is plugged into my video card, not the pc/motherboard.
I guess I messed up and didnt attach a picture of proof, so my second response after I stated that yes, the monitor is plugged into my card was that a picture was still necessary.
did that as well…
still waiting. Im patient, but maybe someone on here has had a similar issue resolved that can chime in? Nothing happens when I attempt to load either version. However it does show up on my task manager as an app running.
AMD Threadripper system with geforce 3070 - windows 11 - displayport connection.
It sems the update check is broken since version 3.3.2. Didn’t get any updates since them automatically. Download and install 3.3.3. and 3.3.4 manual. Must login after download
I don’t see that as here is a EOS 5D mk3 image at 25600ISO and you can see the result in the split screen, using ONLY Auto model and Auto model parameters …
Sorry everyone, the update was pulled over night due to an issue with authenticating causing people to be put in trial mode incorrectly. This will be fixed ASAP and the update restored.
No, but I understand the confusion. We’d renamed a element related to the model manager, and added it to the changelog. At a later time we decided to disable the model manager for now, but didn’t remove the now unnecessary line item from the changelog. When 3.3.4 is restored the changelog will be updated accordingly.
Will I need to download and install 3.3.4 again after it is re-released? Or is the change only in the authentication server and not the program itself?