Glitchy viewport render animation #111699

Closed
opened 2023-08-30 16:00:38 +02:00 by Hjalti Hjálmarsson · 15 comments

System Information
Operating system: Linux-6.4.6-gentoo-x86_64-11th_Gen_Intel-R-_Core-TM-i9-11900K@_3.50GHz-with-glibc2.37 64 Bits, X11 UI
Graphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 535.86.05

Blender Version
Broken: version: 4.0.0 Alpha, branch: main, commit date: 2023-08-29 18:32, hash: ddbe073a6d3e

Short description of error
When exporting "Viewport Render Animation" it features very inconsistent glitches

Example file

Exact steps for others to reproduce the error
Open the example file (this is the lightest version I could make that replicates the bug)
In the left viewport, go to "View" and select "Viewport Render Animation" (it will export to your tmp folder)
Note: When you do this for the first time after opening the file, you will not see any glitches
After it exports, do the exact same thing again
Now you will see random frames get "glitched"

It seems to get a bit worse if you export it a few times, but which frames get glitched is totally inconsistent as far as I can see.

**System Information** Operating system: Linux-6.4.6-gentoo-x86_64-11th_Gen_Intel-R-_Core-TM-_i9-11900K_@_3.50GHz-with-glibc2.37 64 Bits, X11 UI Graphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 535.86.05 **Blender Version** Broken: version: 4.0.0 Alpha, branch: main, commit date: 2023-08-29 18:32, hash: `ddbe073a6d3e` **Short description of error** When exporting "Viewport Render Animation" it features very inconsistent glitches <video src="/attachments/1bf2f6ba-1fea-4cb7-a9f0-c9ebb1ab7da3" title="glitchy_viewport_render.mp4" controls></video> [Example file](https://drive.google.com/file/d/1xLACJ1IgXLBc7qquJutMxf0Zqwfwch5M) **Exact steps for others to reproduce the error** Open the example file (this is the lightest version I could make that replicates the bug) In the left viewport, go to "View" and select "Viewport Render Animation" (it will export to your tmp folder) Note: When you do this for the first time after opening the file, you will not see any glitches After it exports, do the exact same thing again Now you will see random frames get "glitched" It seems to get a bit worse if you export it a few times, but which frames get glitched is totally inconsistent as far as I can see.
Hjalti Hjálmarsson added the
Type
Report
Priority
Normal
Status
Needs Triage
labels 2023-08-30 16:00:39 +02:00
Member

Sadly, I can´t reproduce it. 🙁
I've tried with the exact same build from download.blender.org, but still no luck.
I'm using a Nvidia Gforce on Windows, so it might be driver or OS dependent.

There's some info that may be useful to narrow down the issue:

  1. Does it happen in the regular viewport playback?
  2. Does it happen in regular render mode (F12) with Workbench selected as the scene renderer?
  3. Does it happen in Viewport Render Animation with Material/Shading mode and EEVEE Next selected as the scene renderer?
Sadly, I can´t reproduce it. 🙁 I've tried with the exact same build from download.blender.org, but still no luck. I'm using a Nvidia Gforce on Windows, so it might be driver or OS dependent. There's some info that may be useful to narrow down the issue: 1. Does it happen in the regular viewport playback? 2. Does it happen in regular render mode (F12) with Workbench selected as the scene renderer? 3. Does it happen in Viewport Render Animation with Material/Shading mode and EEVEE Next selected as the scene renderer?
Miguel Pozo added the
Module
EEVEE & Viewport
label 2023-08-30 16:54:45 +02:00
Author
Member

Thanks for looking into it, Miguel! 😄

A couple of people tried it here at the studio and all got the same glitches, so I figured it would be easily reproducible. They are all using Linux, not sure if that's perhaps a factor.

  1. It does not happen in the viewport itself when I just scrub or play the animation.
  2. When I have 'Workbench' set as the scene renderer and hit F12 I get an immediate crash. ("Segmentation fault")
  3. If I do View Render Animation with 'Material' shading mode (and EEVEE as the scene renderer) the glitch does not appear at all. I tried it multiple times.
Thanks for looking into it, Miguel! 😄 A couple of people tried it here at the studio and all got the same glitches, so I figured it would be easily reproducible. They are all using Linux, not sure if that's perhaps a factor. 1. It does not happen in the viewport itself when I just scrub or play the animation. 2. When I have 'Workbench' set as the scene renderer and hit F12 I get an immediate crash. ("Segmentation fault") 3. If I do View Render Animation with 'Material' shading mode (and EEVEE as the scene renderer) the glitch does not appear at all. I tried it multiple times.
Iliya Katushenock added
Interest
EEVEE & Viewport
and removed
Module
EEVEE & Viewport
labels 2023-08-30 22:34:50 +02:00

Can't reproduce.

Can't reproduce.

I believe I did exactly as instructed:

  • Blender 4.0.0
  • Viewport Render Animation (2 or more times)

But I can't reproduce the problem on:

Operating system: Windows-10-10.0.22621-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 528.79

Perhaps it indeed has something to do with Linux.

In order to increase the priority of the report, it would be interesting if you could provide some additional information as:

  1. Have you encountered this issue with previous versions of Blender, or is it specific to version 4.0.0 Alpha?
  2. Does the issue occur only with this particular example file, or does it happen with other files as well?
I believe I did exactly as instructed: - Blender 4.0.0 - Viewport Render Animation (2 or more times) But I can't reproduce the problem on: ``` Operating system: Windows-10-10.0.22621-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 528.79 ``` Perhaps it indeed has something to do with Linux. In order to increase the priority of the report, it would be interesting if you could provide some additional information as: 1. Have you encountered this issue with previous versions of Blender, or is it specific to version 4.0.0 Alpha? 2. Does the issue occur only with this particular example file, or does it happen with other files as well?

When I rendered animation for second time, I got just gray blank frames, so I see some bug, not sure if related.
Re-checked with recent build, and everything seemed to work as expected.

When I rendered animation for second time, I got just gray blank frames, so I see some bug, not sure if related. Re-checked with recent build, and everything seemed to work as expected.
Member

When I have 'Workbench' set as the scene renderer and hit F12 I get an immediate crash. ("Segmentation fault")

@Hjalti In this case could you find if there's any crash logs? like this

It's funny because on my machine it just renders the viewport animation like this 😆 My driver do have some issues at the moment (like cuda version mismatch, no 32 bit libs, and likely some other problems).

Ubuntu 22.04.2 LTS x86_64
NVIDIA Quadro K5100M

图片

> When I have 'Workbench' set as the scene renderer and hit F12 I get an immediate crash. ("Segmentation fault") @Hjalti In this case could you find if there's any crash logs? [like this](https://docs.blender.org/manual/en/3.6/troubleshooting/crash.html#linux) It's funny because on my machine it just renders the viewport animation like this 😆 My driver do have some issues at the moment (like cuda version mismatch, no 32 bit libs, and likely some other problems). ``` Ubuntu 22.04.2 LTS x86_64 NVIDIA Quadro K5100M ``` ![图片](/attachments/6f342fe3-b6b2-434a-81c0-dcb9529cf636)
Author
Member

I believe I did exactly as instructed:

  • Blender 4.0.0
  • Viewport Render Animation (2 or more times)

But I can't reproduce the problem on:

Operating system: Windows-10-10.0.22621-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 528.79

Perhaps it indeed has something to do with Linux.

In order to increase the priority of the report, it would be interesting if you could provide some additional information as:

  1. Have you encountered this issue with previous versions of Blender, or is it specific to version 4.0.0 Alpha?
  2. Does the issue occur only with this particular example file, or does it happen with other files as well?

Hey Germano! 😄

  1. I've never encountered this issue before. I went on a trip a month ago and worked remotely (using the latest build from my departure) but as I came back to the studio last Monday and used the very latest blender build, this issue cropped up.
  2. It happens with other files also. But it's super flaky, I may have to export it a few times before I start seeing glitched frames.

I've attached here the crash log that shows up after trying to render the scene (F12) with Workbench set as the render engine.

> I believe I did exactly as instructed: > - Blender 4.0.0 > - Viewport Render Animation (2 or more times) > > But I can't reproduce the problem on: > ``` > Operating system: Windows-10-10.0.22621-SP0 64 Bits > Graphics card: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 528.79 > ``` > > Perhaps it indeed has something to do with Linux. > > In order to increase the priority of the report, it would be interesting if you could provide some additional information as: > > 1. Have you encountered this issue with previous versions of Blender, or is it specific to version 4.0.0 Alpha? > 2. Does the issue occur only with this particular example file, or does it happen with other files as well? Hey Germano! 😄 1. I've never encountered this issue before. I went on a trip a month ago and worked remotely (using the latest build from my departure) but as I came back to the studio last Monday and used the very latest blender build, this issue cropped up. 2. It happens with other files also. But it's super flaky, I may have to export it a few times before I start seeing glitched frames. I've attached here the crash log that shows up after trying to render the scene (F12) with Workbench set as the render engine.
Member

I've installed Fedora on my desktop, tried with both the open and the private Nvidia drivers, and still couldn't reproduce the issue,
If there are multiple users in the studio that can replicate the issue, at this point I have to wonder if there's something else interfering.

@Hjalti Could you try to download a packaged build from download.blender.org, place a config folder inside the 4.0 folder (so there are not any non-default addons or settings) and try to render the file you attached (maybe to a different (not tmp) location, just in case)?

I can reproduce the crash in the regular Render Animation mode, though. It's a recent regression and should be easy to fix.

I've installed Fedora on my desktop, tried with both the open and the private Nvidia drivers, and still couldn't reproduce the issue, If there are multiple users in the studio that can replicate the issue, at this point I have to wonder if there's something else interfering. @Hjalti Could you try to download a packaged build from download.blender.org, place a `config` folder inside the `4.0` folder (so there are not any non-default addons or settings) and try to render the file you attached (maybe to a different (not tmp) location, just in case)? I can reproduce the crash in the regular Render Animation mode, though. It's a recent regression and should be easy to fix.
Member

I've managed to reproduce the issue on 1 frame in the normal Animation Render mode (ie. not Viewport) on Windows, but only once and not anymore.
imagen

I guess there's some kind of race condition?

I've managed to reproduce the issue on 1 frame in the normal Animation Render mode (ie. not Viewport) on Windows, but only once and not anymore. ![imagen](/attachments/e75a8149-adb8-4136-bd62-1e051ba5b2e8) I guess there's some kind of race condition?
330 KiB
Miguel Pozo added
Status
Confirmed
and removed
Status
Needs Triage
labels 2023-08-31 18:36:53 +02:00
Author
Member

Yay it's reproducible! 🙈

I was worried it might be a race condition of some sorts... ah shucks

@pragma37 do you still need me to try out that experiment with a packaged build?

Yay it's reproducible! 🙈 I was worried it might be a race condition of some sorts... ah shucks @pragma37 do you still need me to try out that experiment with a packaged build?
Member

do you still need me to try out that experiment with a packaged build?

Yes, please. There must be a reason why it's so hard to reproduce for most people, but you can reproduce it reliably on several PCs.
If we find what it is, I may be able to reproduce it consistently. Otherwise, it's going to be nearly impossible for me to find the cause.

While you are at it. Please check if you have the same issue with the final Render Animation mode (now that it's fixed) with and without the "Lock Viewport" option enabled.

If I do View Render Animation with 'Material' shading mode (and EEVEE as the scene renderer) the glitch does not appear at all. I tried it multiple times.

Also, please confirm if this was tested with EEVEE Next.

> do you still need me to try out that experiment with a packaged build? Yes, please. There must be a reason why it's so hard to reproduce for most people, but you can reproduce it reliably on several PCs. If we find what it is, I may be able to reproduce it consistently. Otherwise, it's going to be nearly impossible for me to find the cause. While you are at it. Please check if you have the same issue with the final Render Animation mode (now that it's fixed) with and without the "Lock Viewport" option enabled. > If I do View Render Animation with 'Material' shading mode (and EEVEE as the scene renderer) the glitch does not appear at all. I tried it multiple times. Also, please confirm if this was tested with EEVEE **Next**.

I've helped Hjalti test out your suggestions.
Here is our findings:

Please check if you have the same issue with the final Render Animation mode (now that it's fixed) with and without the "Lock Viewport" option enabled.

We build the latest commit and tried it. It doesn't crash for us anymore.
It also seems like it is very hard to reproduce the glitchyness in with the viewport render animation now.

However it now glitches out for us everytime with "Render Animation" when using workbench. (Note that it still is not reliably reproducible in workbench as it happens on random frames still)
However it seems fine with both EEVEE and EEVEE next.

Locking the viewport doesn't seem to help as the glitches still happen with or without it on.

Are you able to reproduce this more reliably with "Render Animation" as well? 🤔

do you still need me to try out that experiment with a packaged build?

We tried the latest build for linux from today with a clean config without any addons. It was still broken.

I've helped Hjalti test out your suggestions. Here is our findings: > Please check if you have the same issue with the final Render Animation mode (now that it's fixed) with and without the "Lock Viewport" option enabled. We build the latest commit and tried it. It doesn't crash for us anymore. It also seems like it is very hard to reproduce the glitchyness in with the viewport render animation now. However it now glitches out for us everytime with "Render Animation" when using workbench. (Note that it still is not reliably reproducible in workbench as it happens on random frames still) However it seems fine with both EEVEE and EEVEE next. Locking the viewport doesn't seem to help as the glitches still happen with or without it on. Are you able to reproduce this more reliably with "Render Animation" as well? 🤔 > do you still need me to try out that experiment with a packaged build? We tried the latest build for linux from today with a clean config without any addons. It was still broken.
Member

Thank you for taking the time to test it.
It's weird that it happens only on Workbench Next, I would expect it to be related to the Draw Manager.

Are you able to reproduce this more reliably with "Render Animation" as well? 🤔

Not reliably. I was able to reproduce it only once for a single frame after MANY attempts.
It happened in "Render Animation" mode, but it could have been just coincidence.

I guess either @Jeroen-Bakker or @fclem may need to debug it on-site at some point then. 🙁
At least we have that option!

Thank you for taking the time to test it. It's weird that it happens only on Workbench Next, I would expect it to be related to the Draw Manager. > Are you able to reproduce this more reliably with "Render Animation" as well? 🤔 Not reliably. I was able to reproduce it only once for a single frame after MANY attempts. It happened in "Render Animation" mode, but it could have been just coincidence. I guess either @Jeroen-Bakker or @fclem may need to debug it on-site at some point then. 🙁 At least we have that option!
Jesse Yurkovich added
Module
EEVEE & Viewport
and removed
Interest
EEVEE & Viewport
labels 2023-09-04 03:10:31 +02:00
Member

For whatever reason I'm now able to reproduce it consistently.

The GPU debug shows this error on glitched meshes:

ERROR (gpu.debug): Workbench > Opaque.Gbuffer > MeshMaterial : GL_INVALID_OPERATION error generated. VAO names must be generated with glGenVertexArrays before they can be bound or used.

If I got this right, it's an issue with dangling pointers in the GL backed.
It's weird that it started showing up now and only with Workbench Next. 🤔

@Hjalti @ZedDB Could you check if this fixes the issue on your side?
I've triggered a package build for the fix, they'll be available here when ready:
https://builder.blender.org/download/patch/PR111929/

For whatever reason I'm now able to reproduce it consistently. The GPU debug shows this error on glitched meshes: > ERROR (gpu.debug): Workbench > Opaque.Gbuffer > MeshMaterial : GL_INVALID_OPERATION error generated. VAO names must be generated with glGenVertexArrays before they can be bound or used. If I got this right, it's an issue with dangling pointers in the GL backed. It's weird that it started showing up now and only with Workbench Next. :thinking: @Hjalti @ZedDB Could you check if this fixes the issue on your side? I've triggered a package build for the fix, they'll be available here when ready: https://builder.blender.org/download/patch/PR111929/

@pragma37 NICE!

It seems to fix the issue on our side. We don't seem to get any glitches in that build of the PR.

@pragma37 NICE! It seems to fix the issue on our side. We don't seem to get any glitches in that build of the PR.
Blender Bot added
Status
Resolved
and removed
Status
Confirmed
labels 2023-09-05 15:34:24 +02:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
7 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#111699
No description provided.