In T98122#1360729, @Brecht Van Lommel (brecht) wrote:

I thought this was about actual displacement, but if it's bump from the displacement socket that's indeed not ideal.

In T99087#1378537, @Omar Emara (OmarSquircleArt) wrote:

The issue seems to be with Clear Coat in Principled BSDF in this case. A simpler example is to have two planes, the lower one has a default Principled BSDF with Clear Coat set to 1, while the upper plane has a completely transparent shader. A lamp is positioned away from them along the x axis.

One would expect no different since the upper plane is transparent, but it seems to be less noisy and brighter.

cyclesTransparentClearCoat.blend782 KBDownload

In T54642#1369535, @thin soldier (thinsoldier) wrote:

Since variations typically all exist in a single .blend file, I wouldn't really need the "Variations" feature in the short term if there was a way to sort/group the list of assets by the .blend file they came from.

For example I have 4 .blend files with many materials in each: fabric.blend, metal.blend, stone.blend, nature.blend.
All of them contain multiple materials whose names start with: privacy_screen-*.
Instead of having to manually create "Variations" in the asset system, and also without needed to add things to the catalog heirarchy, I'd be satisfied with just being able to see all assets that come from nature.blend all grouped together in the list and then it would be easy for me to find the privacy_screen-antique_bamboo-painted-blue material

Indeed! Thanks for pointing out my blind spot.
Well, if I switch the "subdivide mesh" to "subdivide surface", the points will probably hit the icosphere.

No, the normal is the box's normal. I made some hleping arrow to help visualizing the inversed normal of the box. Just play with the "Shrinkwrap factor" to see the problem.

In your test file, I tried to switch the principled bsdf to a glass shader, then set it to MGGX. Just found another BUG.

It's basically the same bug I found?
https://developer.blender.org/T85259

Thanks, Alaska! I've posted a devtalk thread.

a pixel pusher with the correct view set for an Apple Display P3 Display, ends up baking in the Display P3 transform into file encodes

Please do consider add a option in

preference->file Paths

to allow set the path of generated .tx files!
I used to use arnold and have .tx files in my cloud drive which are all over the place and I hate that!

I just tried your blend file. Found that just move your mesh in the x axis+28mm or - 81mm the artifacts will gone! ( DeltaX>=28∪DeltaX<=-81)

In T92450#1253376, @Fernando Alcala (TriFractal) wrote:

You should create another report for the rough one

Tested on build

version: 3.1.0 Alpha, branch: master
commit date: 2021-11-04 21:35
hash: 3364a5bea6c9
build date: 2021-11-05, 01:00:16

In T92493#1241553, @Philipp Oeser (lichtwerk) wrote:

Cannot reproduce here.

(I am also unsure where those update_model and undo options come from?)

Please try with File → Defaults → Load Factory Settings to see if you still can reproduce this issue.

This transparent shading bug makes it unable to render decals over glassware using cycles.

It remains me of another annoying bug which hasn't been solved yet.
https://developer.blender.org/T85259