Texture coordinate object reference not interactively updating in Eevee #57489

New Issue

William Barber · 2018-10-29T14:25:31+01:00

William Barber commented

2018-10-29 14:25:31 +01:00

System Information
Windows 10 (Tested in Linux too)

Blender Version
blender-2.80.0-git.c750ebe113e-windows64

The Texture Coordinate Node's ability to reference an external object to manipulate coordinates does not function in Eevee. You can select an empty, for example, and move it about and it has no impact on the resulting texture coordinates.

**System Information** Windows 10 (Tested in Linux too) **Blender Version** blender-2.80.0-git.c750ebe113e-windows64 The Texture Coordinate Node's ability to reference an external object to manipulate coordinates does not function in Eevee. You can select an empty, for example, and move it about and it has no impact on the resulting texture coordinates.

blender-admin commented

2018-10-29 14:25:31 +01:00

#65305 was marked as duplicate of this issue

blender-admin commented

2018-10-29 14:25:31 +01:00

#63405 was marked as duplicate of this issue

blender-admin commented

2018-10-29 14:25:31 +01:00

#65099 was marked as duplicate of this issue

blender-admin commented

2018-10-29 14:25:31 +01:00

#63150 was marked as duplicate of this issue

blender-admin commented

2018-10-29 14:25:31 +01:00

#62896 was marked as duplicate of this issue

blender-admin commented

2018-10-29 14:25:31 +01:00

#61858 was marked as duplicate of this issue

blender-admin commented

2018-10-29 14:25:31 +01:00

#60819 was marked as duplicate of this issue

William Barber commented

2018-10-29 14:25:32 +01:00

Added subscriber: @BlenderBrit

Philipp Oeser commented

2018-10-30 10:21:13 +01:00

Added subscribers: @fclem, @lichtwerk

Clément Foucault was assigned by Philipp Oeser

2018-10-30 10:21:13 +01:00

Philipp Oeser commented

2018-10-30 10:21:13 +01:00

Confirmed.
Hasnt worked in 2.79 viewport either. Just doesnt seemt to be implemented (as opposed to cycles)?
@fclem: is this a known limitation?

Confirmed. Hasnt worked in 2.79 viewport either. Just doesnt seemt to be implemented (as opposed to cycles)? @fclem: is this a known limitation?

Clément Foucault commented

2018-10-31 14:40:00 +01:00

Added subscriber: @Sergey

Clément Foucault commented

2018-10-31 14:40:00 +01:00

Yes it is not implemented. I don't know how feasible it is to do it before the beta.

I think the glsl/material code would be simple but the depsgraph need to make update the shader if the picked object changes. Maybe @Sergey will have some insight on how to do it.

Yes it is not implemented. I don't know how feasible it is to do it before the beta. I think the glsl/material code would be simple but the depsgraph need to make update the shader if the picked object changes. Maybe @Sergey will have some insight on how to do it.

Jacques Lucke commented

2019-01-24 14:54:53 +01:00

Added subscriber: @gentleclockdivider

Daniel Paul commented

2019-02-08 10:39:23 +01:00

Added subscriber: @DanielPaul

Jacques Lucke commented

2019-02-25 15:29:15 +01:00

Added subscriber: @zanqdo

Brecht Van Lommel commented

2019-03-18 16:57:58 +01:00

Added subscriber: @brecht

Brecht Van Lommel commented

2019-03-18 16:57:58 +01:00

This limitation is currently documented, so does not strictly need to be a bug report anymore:
https://docs.blender.org/manual/en/dev/render/eevee/materials/nodes_support.html

If this is implemented, then I think it is best to just use a dynamic GPU uniform and set the value again for every redraw.

I don't think any extra dependency graph work would be needed. If the object is unlinked or deleted the shader must be recompiled, but the tagging and relations for that should already be in place.

This limitation is currently documented, so does not strictly need to be a bug report anymore: https://docs.blender.org/manual/en/dev/render/eevee/materials/nodes_support.html If this is implemented, then I think it is best to just use a dynamic GPU uniform and set the value again for every redraw. I don't think any extra dependency graph work would be needed. If the object is unlinked or deleted the shader must be recompiled, but the tagging and relations for that should already be in place.

Brecht Van Lommel commented

2019-03-25 10:59:36 +01:00

Added subscriber: @StijnTas

Clément Foucault removed their assignment 2019-03-29 17:48:33 +01:00

Sergey Sharybin was assigned by Clément Foucault

2019-03-29 17:48:33 +01:00

Clément Foucault commented

2019-03-29 17:48:33 +01:00

Well actually it is not in place. I've commited the GPU nodetree part but there is missing tagging. This makes the coordinate only update if the material is forced to update.

Test file:
test_object_texture_coord.blend

Note: Adding a driver in the nodetree referencing the object itself does work (tagging is set appropriately).

Well actually it is not in place. I've commited the GPU nodetree part but there is missing tagging. This makes the coordinate only update if the material is forced to update. Test file: [test_object_texture_coord.blend](https://archive.blender.org/developer/F6899150/test_object_texture_coord.blend) Note: Adding a driver in the nodetree referencing the object itself does work (tagging is set appropriately).

Brecht Van Lommel commented

2019-03-31 19:58:35 +02:00

Added subscriber: @zhanghua

Brecht Van Lommel changed title from ~~Texture Co-ordinate Object reference not working in Eevee~~ to Texture coordinate object reference not interactively updating in Eevee

2019-05-25 21:03:38 +02:00

Brecht Van Lommel commented

2019-05-25 21:03:46 +02:00

Added subscriber: @LessLyrics

Brecht Van Lommel commented

2019-05-29 03:50:29 +02:00

Added subscribers: @crantisz, @ZedDB

Brecht Van Lommel commented

2019-05-30 14:44:00 +02:00

Added subscriber: @WilliamReynish

heini commented

2019-06-06 17:26:22 +02:00

Added subscriber: @heini

blender-admin commented

2019-06-12 16:57:56 +02:00

This issue was referenced by 04c54dec44

This issue was referenced by 04c54dec44568a4903b5f8e29cad4b3e466fb6e0

Sergey Sharybin commented

2019-06-12 16:58:50 +02:00

Changed status from 'Open' to: 'Resolved'

Sergey Sharybin closed this issue

2019-06-12 16:58:50 +02:00

Michael Soluyanov commented

2019-07-09 10:39:32 +02:00

Still doesn't work with world.

This is test file:

hdri-test.blend

System Information
Operating system: Linux-4.15.0-51-generic-x86_64-with-debian-buster-sid 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.116

Blender Version
Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-07-08 22:16, hash: a42cae1600

Exact steps for others to reproduce the error

Open file. Rotate selected empty object.
Result: world background and light doesn't changes.
Switch to cycles. Rotate the empty object.
Result: now works correctly.

Gif: works in cycles, but not in EEVEE

Walk around: use drivers setup for EEVEE:

Still doesn't work with world. This is test file: [hdri-test.blend](https://archive.blender.org/developer/F7578674/hdri-test.blend) **System Information** Operating system: Linux-4.15.0-51-generic-x86_64-with-debian-buster-sid 64 Bits Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.116 **Blender Version** Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-07-08 22:16, hash: `a42cae1600` **Exact steps for others to reproduce the error** 1. Open file. Rotate selected empty object. Result: world background and light doesn't changes. 2. Switch to cycles. Rotate the empty object. Result: now works correctly. Gif: works in cycles, but not in EEVEE ![Peek 2019-07-09 11-35.gif](https://archive.blender.org/developer/F7578679/Peek_2019-07-09_11-35.gif) 3. Walk around: use drivers setup for EEVEE: ![Peek 2019-07-09 11-37.gif](https://archive.blender.org/developer/F7578681/Peek_2019-07-09_11-37.gif)

Sergey Sharybin commented

2019-07-09 11:14:29 +02:00

@crantisz, this is always a good idea to make a new report. It covers different aspect from the original report and for the discoverability of issues it totally makes sense to have separate report.

@fclem, when running with --debug-depsgraph i do see calls of BKE_world_eval(). So not sure this is a depsgraph related?

@crantisz, this is always a good idea to make a new report. It covers different aspect from the original report and for the discoverability of issues it totally makes sense to have separate report. @fclem, when running with `--debug-depsgraph` i do see calls of `BKE_world_eval()`. So not sure this is a depsgraph related?

Sebastian Parborg commented

2019-07-09 11:14:50 +02:00

Changed status from 'Resolved' to: 'Open'

Sebastian Parborg reopened this issue

2019-07-09 11:14:50 +02:00

Sergey Sharybin removed their assignment 2019-07-09 11:25:38 +02:00

Clément Foucault was assigned by Sergey Sharybin

2019-07-09 11:25:38 +02:00

blender-admin commented

2019-07-10 13:46:23 +02:00

This issue was referenced by 91b4262728

This issue was referenced by 91b42627287e47abe3845b56edb5532f32dcdb31