My understanding is the same. It's used to blur face corner colors into all the adjacent corners, but it doesn't actually blur like in Weight paint or with the blur brush.

Nice! Unrelated but, shouldn't displacement affect both the specular and clearcoat layer? Technically displacement is a stand in for real geometry displacement so it would affect both, which is what Cycles does btw, unlike Bump to Principled where each reflection has it's own normals for good reasons.

It's not as before. Pressing A once always selects, and pressing Alt+A deselects. You can also double tap A to deselect but it has to be fast. If you want to use the old behaviour from 2.79, go to Preferences, keymap, and click on Select All toggles

It's not per image file but per image datablock, you can have two image datablocks that have the same image file as pointer, but different color spaces. Just click the little number besides the datablock and this will duplicate it.

Then maybe we don't want those tools at all, or speaking for myself, I don't. They sound so specific that they're more fit to be part of an addon than anything else.

Any updates on this?

Considering that I model a lot and haven't encountered the problem again, even when I try to replicate my own instructions, I say this has been solved

Color management isn't applied until you save the image and it's not applied on EXR. You could've saved it as EXR, and applied the color management to that image later, to not have to re-render again

I can't replicate it on blender-2.80-e3c586e262dd-win64. Eevee and Cycles values look the same for me, and color management works as well.

Contact shadows are screen space. They have the typical limitations of the other screen space things like AO and reflections. The thickness of the wall behind doesn't exist as far as screen space is concerned. I barely use them because of that and other limitations with thin object.

I can replicate it in the sense that they happened to me in some frames of an animation but I couldn't pinpoint what angles point of view caused it. All that I can confirm is that they happened with AO+Bent normal + Subsurface. It was force to fix this using the Compositor to clamp the high values, erase the alpha and use the Inpaint filter.

Now that rBec0eeb918bac is implemented, objects with a modifier stack deform the textures correctly. All that's left is for objects with no modifier stack to work as well, those being deformed by shapekeys, which I think is the only non-modifier way of deforming meshes that's not being taken into account. Putting a disabled dummy modifier is my current workaround though

Not quite sure if I don't understand the controls or what's happening but I feel it's doing the exact opposite of what I want. It's sampling with max samples the already less noisy bright areas and using even less samples for the noisy dark ones. I'm trying to make the bright areas as noisy as the dark ones, and for the dark ones to remain the same as the base render without adaptative. Maybe it's the build I'm using, idk https://www.dropbox.com/s/s655x863joidbuu/adaptive-sampling.zip?dl=0

Thank you guys!

I agree. Even without an image I make annotations on the positions of UV islands, which needs canvas lock. So the idea of the warning is not ideal either, Annotations definitely have use without an Image open.

What seems to be truly happening is this;

The cross is just caused by a highlight with the Glare node. Either clamp that area of the render or adjust your glare nodes or use other nodes.

Every video editing software allows you to drag and drop entire image sequences at once and form a video strip

I too rely on viewport visibility for my rigs. Allowing me to use drivers to control from within the Armature things like outfits, hiding, showing different object parts

Line segments and Curve segments don't support Subsurface scattering while Triangles does.

You have different Subdivision count in render vs viewport. Set the same subdivisions for both render and viewport and they will look the same.

It was that all along? You guys are lifesavers! ❤

Thank you for the file. After seeing your model now I can definitely find it on mine, but to a lesser extent. It seems those flipped normal are areas where the combined normals go above 90 degrees away from the camera. I imported the model to unreal and it definitely happens there too, but less glossy, more similar to the rest of the material. It would be nice for Blender to do it that way but I'm not sure the developers would consider that a bug instead of a known Eevee limitation.

I can't replicate it with my own models and normal maps, some of which are directX, but all of them look perfect. That's why we need an example blend file with textures attached, to discard factors like the gamma and the kind of normal texture itself, the UV map used as tangent in the Normal map node for model with multiple UV maps, to help you if it's not a bug but just the setup, and ultimately to know if it's just a bug on that happens with one particular gpu driver or a more general bug.

Please provide a blend file with an example of the bug. The nodes are collapsed in that screenshot so it's hard to guess the settings of the math node and the normal map node

The default shadow settings are more on the side of speed than precision. Use ESM shadows with more exponent or use VSM shadows with high bitdepth and 0 bias, make sure walls are thick (double sided), and adjust the Clip Start of the shadows. You should not get any light leaks with this.

I love this! A couple of thoughts:

The noise is smaller than the size of a pixel in the cubemap, and thus the small noise disappears in the downscale process while the few ones that appear look big because that's how big the pixels are. It's like downsampling a picture of stars in photoshop, that's what happens, and no filtering algorithm would solve that 100%. It's definitely NOT procedural textures changing scale, because then it would change scale even with big textures like in the imaged I used above

What you see is a combination of a moire effect, due to small scale of the texture and the low cubemap resolution. Another way of putting it, the texture is so small than when it's captured on the cubemap filtered at a lower res, it just happens to look like a large scale version of the same texture, an optical illusion. But if you use any other procedural texture, or the texture at a larger size, you see that lowres cubemaps don't change their scale. Like in this image with the lowest cubemap resolution possible.

I know there are now some simple expressions that run without python and are considered safe so they don't require permission. Maybe try writting a more complex expression to eventually trigger the warning

It seems Separate Albedo gets forced on during renders. If you turn on Separate Albedo, the viewport and render look the same, but I think the fact that the render doesn't respect Separate Albedo being off is a bug

Count me as one of said users, but there's no hurry ☺ I even made a thread in DevTalk describing a really neat use case that my friend uses it for. Now that Local Cameras are back, this would be the other last feature needed

Thank you! I love it 😁

Yeah, this is due to the textures being 3D and the coordinates used. This doesn't happen with UV coordinates which are 2D or with Generated coordinates which stick to the surface, it's only when using Position or Object coordinates and the likes, the newly elevated surfaces intersect with the texture at a different point in space. I reccomend you using UV or Generated in the meantime.

Yeah, this seems like a bug, although specific to your graphics. Let's hope Clement sees this

I can't replicate it. Transparent clip shadows work fine for me, although at first it appeared mostly opaque because the texture is too bright above the clip threshold. By dissapear you mean the shadow becomes fully opaque or fully transparent?

Ideally Matcaps would be tagged with different color managements for each

Dupliframes is a real loss here, the array modifier and curves modifier don't cut it

Yeah, boolean doesn't work well with edges and faces that have 0 distance and are parallel. It's a known limitation

There's a big difference between times reported and actual times. It renders slower than it says. For example, after the first frame, not counting build time since im rendering a cube, the time reported goes down, but it it's actually the same. Regardless, these are the times on my machine when rendering, but I think they are slower

I see no bug. It works the same, except for the fact that it creates Ngons instead of Triangulation. Hide the cilinder or apply the modifier and you'll see that it works fine. Maybe you got confused because you are in Wireframe without Xray mode and you couldn't see the interior, press Alt+Z to toggle Xray. Also, that's a very old version of blender to compare it to. 2.79's boolean works much in the same way as in 2.8, with Ngons instead of triangulation

I can confirm too. win 10 64, nvidia 1060 6gb

Alright, so after some trial and error, I found a workaround, I still ask for this to be considered a bug though.

the problem that op points is that is not the default. not that it can't be done

That also is an option that was also there in 2.79 but now is a default. It's called Release Confirms and it's in Preferences>Input>Devices>Mouse

Not a bug. Those are the limitations of real time z depth shadows, since they are not raytraced. Very common in videogames.

Not a lie nor lost feature. Blender 2.8 still has Right click select, which you can change in the preferences of 2.8, and you don't have to deal with that "bug", you can select anything inside the circle of the gizmo with no problem. And Left click select existed in 2.79 as well, which you can change, again, in the user preferences of 2.79 and youll find a similar issue.

Another update. Turns out that plugging a texture into the Subsurface input of Principled BSDF throws another wrench into the mix. Not subsurface radius, which i know is not supported, but Subsurface. Meanwhile, using Subsurface just with a value doesn't break either the diffuse or the subsurface, at least during viewport.... sometimes... and using Separate Albedo in the render properties also can make things worse... sometimes...Let me explain:

I connected nothing in the second socket as a "simplest blend file" example. But in practice I was using it with emmissive shaders, and there it's a deal breaker

Now that the precision of the grid has been increased, can we have the Clip Start distance in all the Workspaces be 0.01? https://developer.blender.org/rBb5bc2158a07140e5463e209839bcf36d2ce2cddc