Three things: 1) "Light path" node doesn't work like that. 2) Nodes in example images are not collapsed, so additional information in socket tooltips seems to be useless. 3) Tooltip on the wire should show names and types of two connected sockets. IMHO that will be more convenient way to show types of connected sockets than coloring wire by two different colors interpolated in the middle like in some other proposal.

For array node its better to add "4x4 Matrix" type socket and nodes to operate with them. Matrix can hold location, rotation and scale all in one. If user connected Matrix output to Vector input, then only location component must be used for vector. If it was Vector output to Matrix input, then matrix with this vector as location, and with scale of (1,1,1) must be created. This is how Sverchok addon does it.

Examples of nodes for creating new geometry have location sockets shape as for non singular values. Is this another oversight? Or there will be possibility to create several objects on different locations (thus there must be array of vector values rather than vector texture, like vertices of some other mesh)?

There also this old "cycles_camera_nodes" branch: https://developer.blender.org/rB0e1f34a0c8b7f2a6ecddbca65f44bbd444c1386a

About example nodes on image: How shrinkwrap node know to which mesh it must wrap its input mesh? Mirror node can go without merge function with separate weld node. Boolean i believe uses threshold only to prevent errors with overlapping geometry? Even if it will stay useful after "newbooleans" branch will be merged, controlling this parameter with socket seems like overkill.

There also "topology rake" feature of dyntopo which allows to orient edges in the direction of the stroke for sharper creases. Maybe if re-meshing with spline guides to control edge flow will be introduced...

What about weight painting? Its integration will be more straightforward than with colors as weights assigned per vertex and cant be rendered.

I believe it was fixed at some point. In 2.82 rotate brush now works as expected.

It is now uses bump mapping instead of true displacement by default. See: https://developer.blender.org/rBS3a527357a556491406ee9d33a79ab0af5f79e326

@Campbell Barton (campbellbarton) must know if there exist a easy way to solve remaining issues.

SPAM.

All people wo do staff for Blender, are working for Blender team in some way already. So this bug is solved, closing then.

Maybe self-collision setting of cloth simulation ON by default?

Eevee is a GPU renderer, not CPU.

In T54963#518938, @Andrey Sarafanov (ACap) wrote:

Also, in 2.79 - If you hit C and try to paint selection over the model - you can not navigate around the object and it is just destroys my workflow, because, if I have a large object and want to select multiple elements on its surface - I will have to hit C every time I want to paint selection then hit C again to tun off painting mode - then navigate to the next element - hit C again - paint - hit C - navigate to the next etc.
In modo it would be like - I am freely flying around and paint select necessary vertex/edge/poly. Suuuuper handy. I really want to switch on Blender after 2.8 release and I hope this feature will be there)

If only Modo using it this way, then its not an industry standard.

In T55402#514169, @Antonio Vazquez (antoniov) wrote:

Example of two effects added:

GeForce 9600M GT does not support OpenGL 3.3 which is minimum req for Blender 2.8.

It's on "Create" tab of the tool shelf.

Here video proof:

Cursor orientation will be in euler rotation or in quaternion or just as direction vector?

In T54908#499320, @Alberto Velázquez (dcvertice) wrote:

What about a retopo mode?

Lukas T. I just hope what this doesnt go in perpendicular with your work in hair_guides branch.

On related note: preset "Sandyslate" does not show text cursor in text editor because of similar problem.

Can it have anisotropy not hardcoded to zero? In arnold it can be changed.

You have "lock to object" view option activated.

Worth to add: it moves, but only by 0.000something. And after using "smooth selected vertices" it start to moving normally.

But "radial symmetry" or "tiling offset"?

This new orientation manipulator for lamps is too small. And sometimes it is not visible on the screen at all. The arrow that changes the size of the spot is also not too obvious (maybe it's better to use a large circle instead of it for the spot lamp?)

Works fast. I hope someone review it someday. Its great for creating procedural textures ("Compositor nodetree" is better for this purpose than "texture nodetree" anyway).

Way to activate views from the top, side and others without touching the keyboard. As in this video: https://youtu.be/UlUssM353Rw?t=68

It's a reflection probe. Light probe is a different thing.

linux drivers somehow allow Intel HD Graphics 3000 to support OpenGL 3.3, even though Intel says it's impossible. But it seems it's only partiall support.

Scipy can realy help to terrain heightfield generation and image processing addons. Like "Sverchok" one, or "ANT landscape". scipy module and Sverchok

In T50253#408560, @soulfire (vejn) wrote:

In T50253#408554, @Konstantin (Ko) wrote:

Shadow for lamp is turned off

Turn off specular to get rid of highlight

It seems that is the case.
Hm,by turning the specular off, highlight on plane is turned off.

But how is specular calculated on the plane when point light is behind the object?

Shadow for lamp is turned off

It works as expected with low roughness of mirror surface:

Do not hope for a quick solution to this problem. Developer of modelling tools and bmesh has withdrew from active blender development. It could take years before bmesh boolean mode will be corrected by someone else

You must join these people: Bullet physics

gracias por el mensaje, pero al principio no entendía lo que quería decir, y el segundo informe de los errores que escribir de manera diferente. se necesita mucha más información - imagen y el archivo con el error, y preferentemente en Inglés, de lo contrario no hay nada claro.

I tried. Doesn't work. Sorry.

Perhaps a meta-strip can help?