Closed jczarnowski closed 2 years ago
Hey,
thanks for this report.
We are currently working on integrating the semantic segmentation inside the usual render call removing this issue completely.
Best, Max
Hey,
I started on a PR for this, see #693. This will solve this problem completely.
This PR is not done, yet. I haven't tested it properly.
Best, Max
This should no longer be an issue as the segmap rendering is now integrated into the normal render pass.
Issue
Setting the cycles film exposure via
bpy.context.scene.cycles.film_exposure
to a value sufficiently larger than the default 1 shifts the colors in the instance segmentation render, causing them to map back to incorrect object indices and trigger a check inrender_segmap()
:Steps to reproduce
Solution
For a workaround, I added setting the exposure to the safe value within the
UndoAfterExecution()
block inrender_segmap()
:Alternatively, the indices saved in the EXR with changed exposure should technically still be unique as exposure is a global change. Maybe you could re-enumerate them to new sequential indices?