Page MenuHome

Node group discrepancies between EEVEE and Cycles
Closed, ResolvedPublicBUG


Blender Version
Broken: 2.82, master, ece4515fc8aa, 2019-11-04
Worked: Never

Plugging a Vector/Colour into a Scalar node group input produces a Scalar output in cycles, however in EEVEE it remains a vector.
I understand this is due to node group optimisations in Cycles, while in EEVEE node groups "disappear" during shader compilation.
I don't know which behaviour is preferred, but I assume there would be some small performance impact if every node group input/output was cast to it's respective type in the generated GLSL, so maybe a conditional check to see if the inputs match the expected type?

Steps to reproduce:
Left is LookDev/EEVEE, right is Cycles.

Event Timeline

Could you please attach a sample file?

Here you go, everything as defaults aside from the creation of that node group

Brecht Van Lommel (brecht) lowered the priority of this task from 90 to Low.Nov 6 2019, 3:09 PM

I think this is to be solved in Eevee, if a link goes to a different socket type it should convert.

Clément Foucault (fclem) changed the subtype of this task from "Report" to "Bug".