[kalebbroo]

Why

Upstream's Paint 2.1 pipeline scales each view's guidance by its azimuth (cam_mapping), but only when the caller passes camera_azims. Its texturing pipeline (textureGenPipeline → multiview_utils.forward_one) never does, so every view is guided at scale 1.

The engine applied the azimuth scale (ViewScale), which guided side and back views at twice the strength.

How it was checked

1. I ran the official Python pipeline in Docker on upstream's own demo picture (assets/demo.png, the penguin).
2. I captured exactly what it feeds the diffusion: the reference image, the 12 geometry maps and the starting noise. I replaced the VAE posterior sample with the mean, as the engine does.
3. I fed those to the engine.

Results:

• The geometry maps the engine renders itself match upstream's exactly (0.00–0.01/255 mean).
• The reference matches to 0.03/255.
• With this fix, the 12 generated views match upstream's to 0.4–0.7/255 mean (1.5 on the bottom view).

Tests

ThreeD paint tests: 45 passed, 11 skipped.

[kalebbroo]

@codex review

[chatgpt-codex-connector]

Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-15T07:32:08.350638Z	b9f2dc5	Manual request

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b9f2dc51f4

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Remove the bug-fix narrative from the changelog

This entry documents only a bug fix and its verification history, whereas docs/Agents/AGENTS.md explicitly excludes fixes and review follow-ups from changelog entries and requires eligible entries to be a single line. Remove this narrative; durable numerical evidence belongs in the parity ledger rather than the release changelog.

AGENTS.md reference: docs/Agents/AGENTS.md:L58-L60

Useful? React with 👍 / 👎.