Gemini 3.5 image generation program is malfunctioning.

[syakkaw]

The watermark cannot be removed from newly generated images using the Gemini 3.5 model.

[allenk]

Hi @syakkaw — thanks for reporting this.

Gemini 3.5 changed the watermark position and alpha layout vs the
earlier Gemini outputs, so the old 0.2.x profile no longer matched.

Fixed in v0.3.0, just released. The new release:

• Targets the Gemini 3.5 profile by default — no flag needed for
  newly generated Gemini 3.5 images.
• Keeps the old profile available via the new "Legacy (pre-Gemini 3.5)"
  toggle in the GUI, or the --legacy flag in the CLI, for users still
  processing older Gemini outputs.

Could you grab the v0.3.0 build, try your image again, and let me know
if the watermark is cleanly removed? If a specific image still has
trouble (e.g. low confidence on busy backgrounds), feel free to attach
it here and I'll take a look — the detector defaults to skipping below
25% confidence to avoid touching non-watermarked images, but you can
either lower the threshold (--threshold 0.20 in CLI, slider in GUI
batch) or use Custom mode in the GUI to draw the watermark region
manually.

[Sappurit]

Dos and Windows 10, can't detect v1. I have to use --legacy

[allenk]

Hi @Sappurit — yes, that's the correct way to handle legacy (pre-Gemini 3.5) images on the CLI. The auto-detector only runs against the active profile, so for older Gemini outputs you do need to pin --legacy explicitly:

.\GeminiWatermarkTool.exe --legacy -i ".\old_image.png" -o ".\out.png"

[Sappurit]

We can't auto detect between v1 and v2 ?

Then could you please add %ERRORLEVEL% to the DOS version?
Normally, every dos/console/cli .exe returns %ERRORLEVEL% to 0 if everything succeeds.
And return 1+ if something goes wrong.

e.g.,

can't detect v1 (--legacy) then return %ERRORLEVEL% to 1
can't detect v2 then return %ERRORLEVEL% to 2

Then we can run multiple commands by
if %ERRORLEVEL% neq 0 goto :FAILED

Nowadays, I check the out.png; if it doesn't exist, then run another command.

.\GeminiWatermarkTool.exe -i ".\old_image.png" -o ".\out.png" --legacy
.\GeminiWatermarkTool.exe -i ".\old_image.png" -o ".\out.png"
.\GeminiWatermarkTool.exe -i ".\old_image.png" -o ".\out.png" --legacy --force
.\GeminiWatermarkTool.exe -i ".\old_image.png" -o ".\out.png" --force

[allenk]

@Sappurit thanks again for the ERRORLEVEL suggestion — shipped in v0.3.1:

• 0 = processed, 1 = single-file skipped (no watermark), 2 = real error (bad args / IO)
• Default CLI now auto-tries V2 → V1 fallback, so one call handles both Gemini-3.5 and legacy images; --no-legacy disables the fallback if you want the old behaviour
• Simple drag-and-drop mode also accepts --legacy / --no-legacy directly now

@syakkaw v0.3.1 covers your original case out of the box — just drop the file onto the exe and the auto-fallback handles it.

[Sappurit]

Oh wow,

• V2 → V1 fallback works well.
• ERRORLEVEL works well.
• --force equivalent to force mode V2.
• --force --legacy equivalent to force mode V1.

BTW, my region removed the V2 watermark. I have only V1 to test.