Eevee nodes (e.g., Checker Texture) has different coordinates than Cycles when no UV #52528

New Issue

Dalai Felinto · 2017-08-24T18:02:46+02:00

Dalai Felinto commented

2017-08-24 18:02:46 +02:00

Short description of error
Eevee nodes with vector input have a different default coordinate than what is used by Cycles. In blender 2.78, material draw mode, this worked fine.

Exact steps for others to reproduce the error
Open: eevee_default_uv.blend

Then alternate between Cycles and Eevee. The scale of the brick texture is entirely different.
If you connect the Texture Coordinate node in the checker texture it works the same for Cycles and Eevee.

**Short description of error** Eevee nodes with vector input have a different default coordinate than what is used by Cycles. In blender 2.78, material draw mode, this worked fine. **Exact steps for others to reproduce the error** Open: [eevee_default_uv.blend](https://archive.blender.org/developer/F724336/eevee_default_uv.blend) Then alternate between Cycles and Eevee. The scale of the brick texture is entirely different. If you connect the Texture Coordinate node in the checker texture it works the same for Cycles and Eevee.

Dalai Felinto commented

2017-08-24 18:02:46 +02:00

Changed status to: 'Open'

Dalai Felinto commented

2017-08-24 18:02:46 +02:00

Added subscriber: @dfelinto

Dalai Felinto commented

2017-08-24 18:03:24 +02:00

Added subscriber: @Sergey

Dalai Felinto self-assigned this 2017-08-24 18:03:24 +02:00

Dalai Felinto commented

2017-08-24 19:21:11 +02:00

When nothing is connect the coordinated used is the generated (aka orco). The glsl code used to calculate the coordinates is:

var0 = OrcoTexCoFactors[0] + position * OrcoTexCoFactors[1];

@Sergey is this the multiplication you were referring to? Or we actually need something else?

When nothing is connect the coordinated used is the **generated** (aka orco). The glsl code used to calculate the coordinates is: ``` var0 = OrcoTexCoFactors[0] + position * OrcoTexCoFactors[1]; ``` @Sergey is this the multiplication you were referring to? Or we actually need something else?

Sergey Sharybin commented

2017-08-24 20:59:08 +02:00

@dfelinto, think so but would double-check tomorrow.

Dalai Felinto commented

2017-08-25 11:53:16 +02:00

A related issue, which I believe is the exactly same problem.
If you take this Eevee file:

orco.blend

And apply the object scale, the resulting orco (aka generated) texture coordinates are different. I believe the orco attributes passed to the GLSL shader in 2.8 (eevee) is wrong. The shader itself seems to be fine since 0e29a97813.

A related issue, which I believe is the exactly same problem. If you take this Eevee file: [orco.blend](https://archive.blender.org/developer/F725111/orco.blend) And apply the object scale, the resulting orco (aka generated) texture coordinates are different. I believe the orco attributes passed to the GLSL shader in 2.8 (eevee) is wrong. The shader itself seems to be fine since 0e29a97813.

blender-admin commented

2017-08-25 14:19:27 +02:00

This issue was referenced by 0feeef89f0

This issue was referenced by 0feeef89f06cf48e1ba14db6aeef296140bd04cb

Dalai Felinto commented

2017-08-25 14:22:51 +02:00

Changed status from 'Open' to: 'Resolved'

Dalai Felinto closed this issue

2017-08-25 14:22:51 +02:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Eevee nodes (e.g., Checker Texture) has different coordinates than Cycles when no UV #52528