forked from bartvdbraak/blender
bfaf4f2d0d
Root of the issue goes back to the on-fly normals commit and the latest fix for it wasn't actually correct. I've mixed two fixes in there. So the idea here goes back to storing negative scaled object flag and flip runtime-calculated normal if this flag is set, which is pretty much the same as the original fix for the issue from me. The issue with motion blur wasn't caused by the rumtime normals patch and it had issues before, because it already did runtime normals calculation. Now made it so motion triangles takes the negative scale flag into account. This actually makes code more clean imo and avoids rather confusing flipping code in mesh.cpp. |
||
|---|---|---|
| .. | ||
| app | ||
| blender | ||
| bvh | ||
| cmake | ||
| device | ||
| doc | ||
| kernel | ||
| render | ||
| subd | ||
| util | ||
| CMakeLists.txt | ||
| SConscript | ||