Maniphest T101523

Path-guiding settings are ignored when rendering
Closed, Resolved
Actions

Assigned To
Brecht Van Lommel (brecht)
Authored By
liang yunfei (LemonBranny)
Oct 1 2022, 1:56 PM
Tags
  • BF Blender
Subscribers
Germano Cavalcante (mano-wii)
liang yunfei (LemonBranny)

Description

System Information
Operating system:Windows-10-10.0.19041-SP0 64Bits
Graphics card:NVIDIA GeForce RTX 2080/PCIe/SSE2

Blender Version
Broken: version: 3.4.0 Alpha, branch: cycles_path_guiding, commit date: 2022-09-24 03:41, hash: 4bb41ed43954, type: release
Worked:

Short description of error
With path-guiding turned on, the style of the previewed and rendered noise is completely different under the Directional quad tree method.
The noise pattern in the rendering mode of the Directional quad tree method does not look any different from the VMM and Parallax-Aware VMM methods.
It seems that the calculation method specified in the settings is ignored in the rendering.

Distribution Typeviewport (1600 samples)render (1600 samples)
Quad tree
VMM
Parallax-Aware VMM

Exact steps for others to reproduce the error

  • open the project provided for rendering,
  • reproduce the problem described (check viewport and render).

All the same settings except the calculation method：

project:

caise.blend2 MBDownload

Revisions and Commits

rB Blender
rB124df79e784b Fix T101523: Cycles path guiding debug settings not affecting final render

Related Objects

Mentioned In
T101568: Caustics not work as expected
Mentioned Here
T101529: Blender crashes when using Path Guiding
rB4bb41ed43954: Fix Metal build errors

Event Timeline

liang yunfei (LemonBranny) created this task.Oct 1 2022, 1:56 PM
liang yunfei (LemonBranny) mentioned this in T101568: Caustics not work as expected.Oct 5 2022, 12:14 PM
liang yunfei (LemonBranny) added a comment.Oct 5 2022, 12:25 PM

I also confirmed a new problem, you can create a new file, make a Suzanne as glass, make a ground, and then let the path-guiding method render, depending on your computer hardware, the software will crash after a fixed number of sampling. The number of samples to crash varies with the hardware of the computer, good computers may crash after a very high number of samples, bad computers will crash after fewer samples, but they will eventually crash. This is the current problem with the path-guiding branch, kind of like what issue T101529 describes.

Germano Cavalcante (mano-wii) updated the task description.Oct 5 2022, 6:55 PM
Germano Cavalcante (mano-wii) changed the task status from Needs Triage to Needs Information from User.Oct 5 2022, 7:03 PM
Germano Cavalcante (mano-wii) added a subscriber: Germano Cavalcante (mano-wii).

Thanks for the report. It appears that this is reporting on a feature branch.

Feature branches might include (partially) broken or missing functionality (which most of the time developers are already aware of). For this reason, bugs in feature branches are not handled on the bug tracker.

Please also test this on the master branch and if the issue is present there as well, please update the report.

NOTE: Debug options are generally intended for developers to test. They must not be used for production.
Brecht Van Lommel (brecht) closed this task as Resolved by committing rB124df79e784b: Fix T101523: Cycles path guiding debug settings not affecting final render.Oct 5 2022, 7:34 PM
Brecht Van Lommel (brecht) claimed this task.
Brecht Van Lommel (brecht) added a commit: rB124df79e784b: Fix T101523: Cycles path guiding debug settings not affecting final render.