I can confirm that it is still broken for GPU.
Remove V2
Recover V3
and now Wonder 2
all Local are broken.
Lets pray everything does get fixed.
@Fotomaker
@david.123
@zelenooki87
Which Nvidia driver are you using?
Mine is: 591.74 Studio
Maybe Nvidia messed up.
They haven’t been known for reliability lately.
I actually installed the latest Nvidia Studio driver just yesterday, but oddly enough, they seem to have pulled it from the download section of the Nvidia website. That said, I was experiencing the same issues with the driver revision you mentioned as well.
Take a look at how CPU/GPU Recover v3 runs on my end. I haven’t really tested it much since it’s practically unusable with GPU acceleration due to artifacts, and CPU rendering is painfully slow.
I get the same type of result with Recover 3
I found something regarding Wonder 2 local. Maybe also Recovery 3.
Waiting for confirmation from TL.
But what system do you have? And does your Recover V3 also have honeycomb artifacts?
RTX 5070-Ti. No grid / honeycomb artifacts here.
Which driver do you have? The Game Ready or the Studio version? The December version or the January version?
I’m using 591.44, as later versions are badly unstable with my laptop.
And everything works correctly even with the latest driver?
I see. The portable versions of Drivers are different from the desktop versions. I’m using the desktop version.
NVIDIA drivers, comparing those for laptops versus those for desktop computers. They are not exactly the same. They won’t necessarily have the same bugs or the same optimizations.
Yes, everything works as it should in Topaz Photo no matter what I test, or which driver I use.
I have a desktop Ryzen 7 9800X3D, RTX 5070-Ti system where the GPU is undervolted at 0.845V max with memory OC to 2000 MHz, and GPU capped at 2700 MHz. Bandwidth is 1024 GB/s.
I did have an unrelated problem with the latest Game Ready Driver (Black Screen Reset when not under any load) so I went back to the Studio Driver.
He was able to fix the recovery 3 artifacts.
Now we know whats different from our systems.
Mine is German. 
Seems like there is more related to (.) & (,).
Mine as well. But that cannot be the culprit of the Recover V3 honeycombing, or can it??
If the scaling is incorrect somewhere and the model has to enlarge an image that is much too small, then that could well be the case.
A description with the help of gemini.
""Subject: Critical Locale Bug - Decimal Separator Mismatch causing Scaling Issues
Issue Description:
There is a significant discrepancy in how scale factors are handled between US and European (specifically German) system locales.
On systems using a comma (,) as the decimal separator, the AI models receive incorrect or truncated input data, which does not occur on US-based systems.
Technical Details:
Root Cause: The UI (Qt/QML) respects the system locale and formats decimal values using a comma.
However, the AI backends (ONNX, TensorRT, etc.) strictly expect the US standard (period/dot).
Truncation Error:
When a value like 0.5 is passed as “0,5”, the backend engine often truncates the string at the comma, interpreting the value as 0. Similarly, a scale of 2.5 is misinterpreted as 2.
Resulting Symptoms:
Tiny Input/Output:
The model processes an extremely small fraction of the image or scales to an incorrect, minimal resolution.
Red Marble Artifacts:
The mathematical overflow caused by truncated scale factors leads to memory addressing errors in the VRAM, resulting in uninitialized data being rendered as red/magenta marbled noise.“”
Could also lead to an offset of an AI model in the Wonder 2 local model.
Wonder 1 consists of three models.
I think this is also the case with Wonder 2.
Do you use the software in english or german translation?
I use mine with english.
I use English as well.
We created this thread to group everyone that have the honeycomb issue. So far it seems it’s related to the computer being from a foreign contry that uses comma instead of the dot like in the USA. Our team is looking into this.
Thank you everyone for your patience 
I just switched it over myself.
Recovery 3 can look really good.
I’m currently testing it on a large image.
