Regression: Compositor artefacts #119973

New Issue

HMage · 2024-03-27T18:16:55+01:00

HMage commented

2024-03-27 18:16:55 +01:00

System Information
Operating Systems: Windows 10 and macOS 14.4 (Intel)
Graphics Cards: NVIDIA GeForce RTX 4090 and AMD Radeon Pro 5700 XT

Blender Version
Broken: 4.1.0
Worked: 4.0.2

Short Description of Error

Visual artifacts appear, resembling issues where some compositor chunks seem to abort compositing unexpectedly.

Based on my experience as a programmer, I suspect that recent code changes to some of the nodes might have caused a buffer overrun or a similar issue.

Exact Steps for Others to Reproduce the Error
The issue does not occur 100% of the time, which suggests it might be related to a memory error. However, muting and then unmuting the 'Flip X' node before the 'Lens Distortion' node, and setting the chunk size to 32x32, seems to make it easier to trigger.

Steps to reproduce:

Open the default startup file.
Go to the Compositor.
Add a 'Glare' node.
Add a 'Flip X' node.
Add a 'Lens Distortion' node with projector on and dispersion set to 1.
Add another 'Flip X' node.
Connect to the output.

This issue occurs on both macOS (iMac) and Windows 10 systems.

A .blend file that reproduces the issue is attached.

I discovered this issue by opening an old .blend file and rendering it.

If you have trouble reproducing this error or need more assistance in debugging this problem on my machines, please feel free to reach out, and I'll be happy to help.

**System Information** Operating Systems: Windows 10 and macOS 14.4 (Intel) Graphics Cards: NVIDIA GeForce RTX 4090 and AMD Radeon Pro 5700 XT **Blender Version** Broken: 4.1.0 Worked: 4.0.2 **Short Description of Error** ![image](/attachments/e7776d47-2baf-4b46-844f-c0647bdca6a1) Visual artifacts appear, resembling issues where some compositor chunks seem to abort compositing unexpectedly. Based on my experience as a programmer, I suspect that recent code changes to some of the nodes might have caused a buffer overrun or a similar issue. **Exact Steps for Others to Reproduce the Error** The issue does not occur 100% of the time, which suggests it might be related to a memory error. However, muting and then unmuting the 'Flip X' node before the 'Lens Distortion' node, and setting the chunk size to 32x32, seems to make it easier to trigger. Steps to reproduce: 1. Open the default startup file. 2. Go to the Compositor. 3. Add a 'Glare' node. 4. Add a 'Flip X' node. 5. Add a 'Lens Distortion' node with projector on and dispersion set to 1. 6. Add another 'Flip X' node. 7. Connect to the output. This issue occurs on both macOS (iMac) and Windows 10 systems. A .blend file that reproduces the issue is attached. I discovered this issue by opening an old .blend file and rendering it. If you have trouble reproducing this error or need more assistance in debugging this problem on my machines, please feel free to reach out, and I'll be happy to help.

compositor-artefacts-4.1.0-repro.blend

112 KiB

image.png

2.0 MiB

HMage added the

labels 2024-03-27 18:16:56 +01:00

Richard Antalik commented

2024-03-27 20:12:54 +01:00

Can reproduce issue in 4.1, but not in 4.2, so will close.

@OmarEmaraDev Not sure if this bug is known for 4.1 in case there will be corrective release.

Can reproduce issue in 4.1, but not in 4.2, so will close. @OmarEmaraDev Not sure if this bug is known for 4.1 in case there will be corrective release.

Richard Antalik closed this issue

2024-03-27 20:12:57 +01:00

Blender Bot added

and removed

labels 2024-03-27 20:13:00 +01:00

HMage commented

2024-03-28 17:55:26 +01:00

Hello.

What are the recommendations to users living on latest release? Roll back to 4.0?

Apologies for writing in a closed issue, since this issue seems to be the most relevant place to write. If this is not an appropriate place, I'll be thankful if you point out where should I seek that answer.

As an end-user, I am stumped as for what to do here - I understood the response as "wait for 4.2", since I don't see any activity towards fixing it in 4.1. I could be wrong, but for the moment it seems like I have to ignore 4.1, roll back to 4.0, and wait until 4.2 is officially released.

Feel free to close again, but would welcome any pointers for a user like me who encountered this issue.

Hello. What are the recommendations to users living on latest release? Roll back to 4.0? Apologies for writing in a closed issue, since this issue seems to be the most relevant place to write. If this is not an appropriate place, I'll be thankful if you point out where should I seek that answer. As an end-user, I am stumped as for what to do here - I understood the response as "wait for 4.2", since I don't see any activity towards fixing it in 4.1. I could be wrong, but for the moment it seems like I have to ignore 4.1, roll back to 4.0, and wait until 4.2 is officially released. Feel free to close again, but would welcome any pointers for a user like me who encountered this issue.

HMage reopened this issue

2024-03-28 17:55:30 +01:00

Blender Bot added

and removed

labels 2024-03-28 17:55:33 +01:00

Richard Antalik commented

2024-03-28 19:35:44 +01:00

Sorry, I missed, that this worked on 4.0. Will confirm since this is regression.

To me it seems, that there will be corrective release for 4.1, so this could be fixed. But in case there won't be one, depending on what you do, alphas are fairly safe to use. Obviously it is best to backup and save often, but that is just good practice anyway.

Sorry, I missed, that this worked on 4.0. Will confirm since this is regression. To me it seems, that there will be corrective release for 4.1, so this could be fixed. But in case there won't be one, depending on what you do, alphas are fairly safe to use. Obviously it is best to backup and save often, but that is just good practice anyway.

❤️ 1 🎉 1

Richard Antalik changed title from ~~Compositor artefacts~~ to Regression: Compositor artefacts

2024-03-28 19:35:58 +01:00

Richard Antalik added

Module

VFX & Video