@Mike Futcher (yogyog) I think I used an Array Modifer with count set to 1.

wll udims be added to 2.81?

"So a possible workaround to get tangents for now is to just add a modifier that does nothing."

Still happens in the latest 2.81 alpha. 4ce3fbd52ae8
I'm not getting errors in the console.

In T69619#771183, @Rodger Davis (RodDavis) wrote:

Normals do not behave normally if the bump node is within a node group. The Bump node has extra hidden code now. These hidden values are Height_dx and Height_dy.
Steps:
If you group a single bump node you can get these hidden Height values. Once grouped, the Height_dx/dy can be influenced outside the node. Even if it doesn't look like it's connected to anything.

Just adding more info

I can confirm this bug on OSX 10.12.6

I cannot reproduce this on OSX 10.12.6

Change rotation method to axis angle

Keep patch up to date

@Clément Foucault (fclem) : I have added this to 2.81 milestone (since it was set to "High"), mind checking again?

I'm having this error, too. Principled is still working, probably because of this: rBf962c701fe5d6fc14956892de58bf4f7d875348d

Manual changed to diff to work with master.

Arc seems to be broken with my workflow...
Might need to open a new one. It doesn't seems to rebase with master

• Cycles/EEVEE: Viewport HDRI Intensity Slider

• Cycles/EEVEE: Viewport HDRI Intensity Slider

• Cycles/EEVEE: Viewport HDRI Intensity Slider

• Added settings back to Material Shading menu
• Enabled eevee viewport settings when cycles is active

Just a thing, we use "Use Scene Lights" and "Use Scene World" a lot in look&dev.

Updated versioning code

I get a pink world light when doing the following:

IMO the about the use_scene_light and use_scene_world topic is that there are 2 workflows that we need to address

• combined the settings for material preview and render preview; Actually reverting the DNA changes to keep file compatibility, therefore there is still a field named lookdev_light.

Archiving then...

More than a week without reply or activity. Due to the policy of the tracker archiving for until required info/data are provided.

In terms of user level interaction, there are two things I'm not sure about:

• The choice of studio light and its settings are currently decoupled between lookdev and rendered mode. I think most of the time when you're doing lookdev, you actually want those to be in sync. Then you can easily see the preview, and then same thing more accurately under the same lighting. Having to keep these in sync manually would get annoying. I think it would be similar for Eevee once we add more settings to lookdev to reduce preview quality.
• For the availability of "Scene Lights" and "Scene World" settings in material preview mode, I'm going back and forth on that a bit. It can be useful to preview lighting with Eevee when using Cycles as the render engine. But in general this doesn't work so well, not to the level that you can for materials, and it's not something I want to prioritize for development either. Just the materials is already challenging. If we limit the lighting we can expose a smaller set of Eevee settings when Cycles is the render engine, and make sure those work well. So my opinion here is still to keep that only for rendered as in this patch, and for those would want to use Eevee as a lighting preview there is still the possibility to switch the render engine.

I have reopened T68826: eevee not showing multi material object properly when blend is loaded until mesh is updated, will merge this report in.