I believe this used to work fine a couple of 2.8 versions back. idk what happened, or why it works on lookdev but not on solid

Screen space effects like Screen space reflections and refractions, ambient occlusion and contact shadows, only work with what's available on screen and fade on the edges. They're not real raytraced effects. You can increase the virtual border during render by going to Render properties > Film > Overscan. Only works during render though

I like Alt 3. My main problem Current and Alt 1, and to an extent with all of them, is that the thin parts don't look realistic. Maybe an actual simulation with flip fluids would be nice

The shader does work, it has an Eevee fallback, maybe not the intended fallback but I do use it with hair quite often

can you provide a blend file with the hdr packed in it?

I hope they fix this. The Bump node basically causes bumps at half the resolution of the render. My understanding is that it uses the difference of value between adjacent pixels and that's why it's half res. It was also like that in 2.7's material viewport, but I think Eevee needs it if it's going to be used in final production. Maybe internally sampling the bump texture at double the render resolution, or with a jittered approach for each sample. I had to render at 4k so it's less noticeable 😂, luckily Eevee is fast. Btw, actual normal textures with a Normal map node, like tangent space normals, look fine and fullres.

Can I provide a blend file on their behalf?

In T59275#580219, @ronan ducluzeau (zeauro) wrote:

confimred on 21523b5 on ubuntu 16.04

Your .blend file contains a shapekey. Problem also exists with modifiers.

Proper handling of auto-texture space is probably a complicated todo.

Your gif doesn't convey well. Please attach a blend file with the simplest example. Is it possible you are referring to this?

It reminds me to some months back when matcaps, the HSV color picker, and the lookdev hdrs were all filmic. Now it's better for the matcaps and lookdev, but the color picker is hard wired to corrected filmic, regardless of the color management settings. There should be more options for the color picker, depending if you want the HSL and HEX to be corrected for srgb, filmic, your scene color management settings, etc

I'm going to side with Julien. Being able to switch between UV editing with or without images, Image viewing with or without UV's, and Painting with or without UV's, is more easy as one editor. There are enough permutations and combinations that separating it into two editors will make some of those permutations not possible unless they are added as redundant features from one editor to the other, which is more work for developers. Also, the bespoke UV editing mode was a great adition for handling tools and the toolbar, I don't see how that isn't enough for things like Object mode uv editing

Automerge is under Mesh options, both in the tool properties, and the topbar to the right

Even after changing the viewport steps to 9 you don't see it happening on the viewport?

I can confirm and I have a gtx 1060 6gb as well (blender-2.80.0-git.e79bb957fc3-windows64)

Will you consider adding unlinked collections management to this design document? I made a small proposal to not use another outliner for orphan collections. I hope you check it out https://blender.community/c/rightclickselect/ltcbbc/

Sadly, that's a known limitation, sorry. Parallel faces with 0 distance on the same space don't work, and some volume needs to overla. Here is an exagerated example, but you can separate faces and overlap the volumes just a very very little ammount like this and it would still work. I heard Howard Trickey might work on improving booleans in the future :)

I have a 4k monitor as well and don't have that problem. But it does behave differently to 2.7, which I understand it can be seen as a bug but it's probably a design decision. In wireframe mode, you can basically end up selecting an object by the faces even though the faces are not visible, which doesn't happen in 2.7 where it always selects the closest wire to the mouse. I don't quite understand the heuristic but it hasn't been that much of a problem for me, and to be fair, 2.8's wireframe has options to perceive the faces like the Xray slider in the shading popover.

Yeah, I agree with you

Suggestion. Overlap threshold in Boolean modifiers to 0, and merge threshold for the Intersect(Boolean) command in edit mode to 0 as well. For the longest time I thought the boolean algorithm wasn't good enough for some cases, producing non manifold meshes from my perfectly manifold ones, but it turns out that the merge threshold is what messes it up for me most of the time.

It works fine for me. Consider providing a blend file with an example of this. Also, check that the Overlap threshold in the Boolean modifier is set to 0.0 exactly, since merging vertices can give problems

Yes, this is another report of the same bug https://developer.blender.org/T58726

I have the same problem, on Windows10 64, Nvidia 1060, driver 417.01

Also, the Cut tool and Annotation tool themselves don't allow for connecting nodes by the socket, or dragging nodes, forcing you to go back to box selection

I noticed that some N gons go really slow. Please attach an example file

Attach the blend. Also remember to turn on your GPU devices on Edit> Preferences> System

You are using Blender Internal, which doesn't exist in 2.8 anymore. Only Cycles and Eevee. Once you manually convert your materials in 2.7 from Blender Internal to Cycles, you can open it in 2.8 and see the shading and textures in the Lookdev shading

Using the menu is not for corners, but for vertical or horizontal edges. And you don't have to make a gesture with the mouse, the arrow will appear. Joining is also limited to same size adjacent areas

Using Ctrl+G and the Collection panel in the Object properties to create collections, creates Unlinked collections, meaning that they haven't been linked to the Scene collection. I agree that the interface here should be improved, but it's not really a bug. Use Mkey on the viewport instead (the old key to move to layers) or the New collection button on the Outliner's header. In the meantime, you can use a second outliner and change it to Orphan data to see the unlinked collections and objects, and drag them from one outliner to the other

Not a bug. What you see in the viewport is the preview of the data of the probe, which is just an overlay (you can disable and enable overlays to see what im talking about)

I tested it, it seems that the alpha affects the green channel. I saved it as EXR and it doesn't give that problem.

It could still be limited to just the most immediate node plugged to it, with that node having a constant to fallback if something else were to be plugged to it in return, not evaluating further. Another way of handling it is like unreal engine does, where the scattering is it's own data type that can't do operations with the regular vector3's, that would make the socket another color and nothing else but that data type could be plugged into it

Aw that's a shame. Even without texture support, it would be nice to have this work with single colors, otherwise it forces me to duplicate and make unique nodegroups to change the color inside of each

https://developer.blender.org/rB3bf7c846eeb4a728c62100b40463874d83f5b3e0 This should fix it

Make sure to change the UV/Image editor mode from View to UV edit in its header

I think https://developer.blender.org/rB68b670698fc791e15379b68f508f7b69bb19d2e2 fixes this

Well, as far as I know, Screen space refractions aren't aware of the backfaces of your object, like it goes to infinity. the refraction you get is like deleting the back half of your sphere. when you do that cycles and eevee look more similar

I wonder how the material slots would work there. Thinking forward for the eventual asset manager, it would have to show the slots when you want to work with a selected object, but not when just working with a material from the asset manager

Yeah, I'd like for the HDRs of Lookdev to use the scene's Color Management settings as well, minus the exposure settings, unless you turn scene lights on

For reference, zbrush uses flat face normals. not smoothed or vertex normals, but the edges of those face normals seem blurred or averaged on a constant screen space radius. For example, the brush remains flat on a face until you get close to the edge and it starts making a smooth rolling instead of a constant snap as you get to the other face. If faces on screen space are small, it doesn't matter if they are too noisy. But at the right scale of noise on screen, the problem of the brush rocking back and forth still happens. Blender could improve on that or be the same

Not a bug. It's an option, just uncheck it

Consider having this ready for the beta milestone

Are you sure the triangulated cube is part of the original bug? You guys might want to click File> Load Factory settings. I remember that the default cube was triangulated by accident on new files, until it was fixed more recently

Didn't Pablo say that Flatty dark should be changed to be dark gray instead of blueish? Gray would be great

How about removing Ctrl+U as save start-up file? I've accidentally overwritten the startup file many times because of it, destroying my carefully crafted file.

Could Matcaps be consolidated inside the Studio Lighting menu? After all, they look similar, a menu of spheres, even if what they draw (lights vs images) and how they're mapped is different. Matcaps would only need a third folder in datafiles/studiolights and be processed differently, not as equirectangular 6 lights things.

Any plans for the data type icons to be displayed vertically? There can be too many at any given time and they get cramped horizontally in the header, forcing to grab and drag with middle mouse, or use a wider area, this would only get worse if the plan is to have a narrower properties editor by default. This is a common thing that people have surely suggested in the past, but I guess it was turned down because headers cannot be vertical, on the sides. But the icons could ocupy their own vertical region inside the editor instead of the header, leaving the header for other things. It would also look more in line with the new toolbar design. Another posibility could be dropdown menus

Could the material shading view be active with Eevee as the render engine as well? It seems useful to have the flat lighting and studio lighting options in hand, maybe with scene lighting greyed out or removed from the list, forcing you to switch to the rendered view

Thank you!

This one happens to me on newer builds like blender-2.78-9cd6b03-win64. Tried with both a machine with Nvidia gtx 970 and other with Intel HD 530.

@Brecht Van Lommel (brecht) I meant to say a method to avoid it going above 100% reflected, sorry. If it's below 100% then it should stay the same.

@Mike Erwin (merwin) latest one I downloaded from the device manager 20.19.15.4624

I was reading this thread regarding how the Subsurface slider should work and wanted to give my two cents. Currently, you can't create a pure white material with mixed 0,1,1 diffuse and 1,0,0 subsurface like in fig1, because with the slider at 0.5, the shader converges to a total reflectivity of 0.5,0.5,0.5 . Would Renderman give that same result?

Crashes on Windows 10 + Intel HD 530