Page MenuHome

Eevee Image Texture Box mapping inconsistent with Cycles if object is scaled
Closed, ResolvedPublic


System Information
Operating system: Windows 10
Graphics card: GTX1080Ti

Blender Version
Broken: 2.8 latest master
Worked: Probably never

Short description of error
Eevee Image Texture Box mapping is inconsistent with Cycles output if object is scaled. The fact that it works but unreliably is even more dangerous than if it did not work at all.
Left is Eevee and right is Cycles:

Exact steps for others to reproduce the error
1, Open the attached blend file:

2, Switch right viewport to Rendered mode
3, Notice the difference in the result despite Eevee having support for Box mapping

Result: Eevee box mapping result is different if the object is scaled

Expected: Eevee box mapping result is identical to Cycles in all cases, even if the object is scaled.

Event Timeline

Sebastian Parborg (zeddb) triaged this task as Confirmed, Medium priority.

I'm not sure, but it seems there is something in cycles code which seems not in eevee's code:

When we apply this, it seems both have the same behaviour:

Maybe the codes to compare are in D:\Compilation\Blender\BFBlenderSources\intern\cycles\render\nodes.cpp for Cycles and
D:\Compilation\Blender\BFBlenderSources\source\blender\nodes\shader\nodes\node_shader_tex_image.c for EEVEE

I think the issue is caused by the Orco optimization I did for Eevee. Investigating...