We test the apps with consumer hardware. I personally have a computer that is very average in term of performances. We have Macs, Intel Macs, Snapdragon, AMD and NVIDIA graphics card.
Still, some issues can arise and we are investigating. Right now, the challenge is that other people with the same hardware don’t have the issue, why is that? We need to find out and that’s why I ask all the questions 
Uff, so there ARE consumer-grade hardware testing.
That’s VERY curious, as to why Recover v3 fails on users’ hardware, but, apparently, not Topaz team ones, right? Unless there are cases, where Topaz can replicate the issue? For example, testing on fully updated Windows 10 ESU? I can say, I have totally no issues with either AI workloads nor the usual Topaz model executions (until Recover v3, Remove v2 in Photo, and then Wonder v2 models appeared) on my RTX 3090 with Studio 591.74 driver. I had issues with black screens after RTX 5000 series was introduced (that was even worse for the fresh buyers of these cards), so I rolled back to the pre-5000-series Studio driver at the time, so I could enjoy the stability. I also never overclock the card nor the system, I even optimized the 3090 curve to lover voltages, since I want the longevity, not the performance.
The moment local Recover v3, Remove v2 and Wonder v2 models issues are fixed - it’s going to be a revel!
I wouldn’t say the results are great on that image, but I don’t get the honeycomb issue:
Left is me - Right is you
NVIDIA drivers are 591.44 - I will test with 591.74 (latest Studio drivers)
Yours is fine, there is no honeycomb. But it happens to me systematically. I have NVIDIA 591.74 GeForce RTX 4070 (8 GB dedicated)) Laptop type.
I am curious why there is something red on the top left edge of my picture (probably a piece of the photo it was cut from) and it’s not there on yours?
I updated the drivers to the latest one, 591.74, and I still get the same results, no honeycomb issue.
If you want, I would like to book a screenshare with you to see why this is happening. Can you contact us at help@topazlabs.com and mention my name?
Anyone with the honeycomb issue can contact me by email for a screenshare so we understand why it’s happening.
I can spot tiles in your result.
Yes, results were not good as I mentioned, but I am only investigating the honeycomb issue for now.
This is not the same; it’s a grain texture. The results are not good with Recover 3, but my side-by-side shows that I can’t reproduce the issue. If I had the issue, I would get the same results.
We are not discussing the quality of the render on this specific photo; I want to investigate the honeycomb issue.
With this photo, even Recover 2 doesn’t work well, but the BG is smoother
**
Recover 2 results:**
I’ve just sent it (mentioning you). Thanks for the help.
Thank you, I replied to the email
Did you change the system memory fallback in the nvidia control panel?
No, I didn’t change anything. It is set to Driver Default as I can see.
For me, I have the ‘default driver setting’ for the system memory fallback (and I’m also the one with honeycomb and smear issue).
I can also confirm, that “prairie wind” tile-wallpaper image from Windows XP is a great test case.
GPU:
CPU (low, because medium was cached on GPU):
Curious, CPU result also shows bits of the patterns, not as egregious and dense as done by the GPU.
Following examples are done on CPU (Recover v3) and GPU (Recover v2) respectively, based off of the small 256x256 original image posted below:
The 2x zoom-in I did on Gigapixel 4.x back then (first 2 examples are based on that):
Original (it was 8-bit BMP format, but it’s better to have PNG):
I did a test now and can confirm: The honeycombing issue definitely is caused by regional number formatting (in regions that use a “,” as decimal seperator instead of a “.”).
Original:
Recover V3 with german region settings / number formatting:
Severe artifacts/honeycombing.
The exact same source on the same system with the exact same Recover V3 settings but this time windows region and number format set to US:
→ no honeycombing
I hope its an easy fix.
Oh my. So it IS a ‘dot’ VS ‘comma’ curse, yet again! Phew.
).
