LuxCoreRender / LuxCoreRender/BlendLuxCore
Problem with pathtracing on Blender 3.1 & Luxcore 2.6
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 877
- Forks
- 108
- PR merge metrics
- No merged PRs in 30d
Description
.blend file:
Steps to reproduce:
When using Luxcore in pathtracing mode the caustics from a transparent object doesn't show on a base
surface, unless you flip the normal(s) of the base surface. Bidir works perfectly.
Screenshots or rendered images:
Error message from Blender console:
None.
OS: Win10
Blender version: 3.1 (& 3.01, possibly 2.93)
LuxCore version: 2.6 (& 2.5, don't know/remember about 2.4)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the report in Blender 3.1 with LuxCore 2.6: use pathtracing with a transparent object over a base surface, then compare it with Bidir and with flipped base-surface normals. Trace the pathtracing caustics entry point and verify that the caustics appear without changing the base-surface normals.
Written by the indexing model from the issue text.
Assessment
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100