Blender Git Commit Log

Fix T80138 Node Editor: Add Frame turns background gray

The removed `UI_ThemeClearColor` made no sense in this context. It must
have been a leftover from previous refactor.

Rename File menu item text.

Rename files to shorten the name, remove ex/im.

Two letter abbreviations were not deemed good.

Cleanup: Add description, rename conflicting name

max/min are also functions, so better not keep them as variables.
No functional change.

Add transform options in the importer UI.

removed extra str in cloth

Fix minor bugs in logging.

Solved merge conflict

Increased the frame number for visible differnce

Remove extra import statement

Re-enable modifer and bmesh_boolean tests.

These were disabled in the newboolean merge commit.
This commit renables them, using the original 'FAST' solver
so that the result objects need not change.
A TODO to add more tests using the 'EXACT' solver,
though most functionality there is now covered by unit gtests.

GPUShader: Improve shader compilation log

- Print shader type (fragment, vertex, geom)
- Support for Apple + intel error format.
- Handle formatting a bit more gracefully.

Minor fix

EEVEE: Fix broken rendering caused by SSR + Alpha blended material

This was affecting Mesa drivers as well as AMD pro driver. But it
might have been noticeable on other config too.

This was introduced by rBa9f2ebb21508.

GPUFramebuffer: Tag dirty after recursing downsample

Also do not bind automatically. This is fine since the framebuffer will
update next time it's bound.

GPUState: Move Scissor and Viewport state to framebuffer

This way it is way clearer what each viewport state is. There is
no more save and reset. The scissor test is also saved per
framebuffer.

The only rule to remember is that the viewport state (size and
origin) is reset for both the viewport and scissor when a texture
is attached or detached from an attachment slot.

BLI_math_vector: Add equals_v4v4_int

GPUContext: Update internal framebuffer size when activating context

This is to ensure the FrameBuffer extents are always up to date.

BLI_utildefines: Fix assignment in binary ops for ENUM_OPERATORS

That was an overlook from the review when we introduced it.

WM: Remove 10year old workaround for buggy drivers

This should have no consequence nowadays.
Can be reverted if needed.