Topic: [BUR] Blender 3D Modelling

Posted under Tag Alias and Implication Suggestions

The bulk update request #9110 is pending approval.

create implication blender_logo (2) -> blender_(copyright) (26)
create implication blender_cycles (4278) -> blender_(artwork) (19946)
create implication blender_eevee (1080) -> blender_(artwork) (19946)
create alias blender_eevee_(copyright) (1) -> blender_eevee (1080)
create alias blender_eevee_next (4) -> blender_eevee (1080)
create alias eevee_next (0) -> blender_eevee (1080)

Reason: Various implications and aliases relating to the Blender 3D animation software.

Regarding blender_eevee_next: Blender released version 4.2 LTS, which came with a complete rewrite of the Eevee render engine. I'm unsure off whether it should be aliased to or implied towards blender_eevee.
On one hand, it's a full replacement of the original, but on the other, it's still going to be referred to as Eevee in the future.

Also.. Should the blender_eevee and blender_cycles tags be changed to meta tags?

dirtyderg said:
create alias blender_(copyright) (24) -> blender_(artwork) (19061)

These are two separate things. The _(copyright) tag is for things owned by Blender: logos, characters, the software UI, etc. While the _(artwork) tag is for images rendered with Blender, and don't necessarily show anything owned by them.

all tags referencing a renderer or shader should be aliased away. I would remove blender_(copyright) from the list as the blender logo(or its user interface(modifer tabs, pie menus and the like)) being visible in the image is a relevant feature to have its own tag.

watsit said:
These are two separate things. The _(copyright) tag is for things owned by Blender: logos, characters, the software UI, etc. While the _(artwork) tag is for images rendered with Blender, and don't necessarily show anything owned by them.

Changed to a logo -> copyright implication

  • 1