Cycles: Wrong Motion Blur With GPU Using Optix API #120256

Open
opened 2024-04-04 15:35:45 +02:00 by Roland-Vyens · 20 comments

System Information
Operating system: Windows-10-10.0.22621-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 551.86

Blender Version
Broken: version: 4.1.0, branch: blender-v4.1-release, commit date: 2024-03-25 20:42, hash: 40a5e739e270
Worked: (newest version of Blender that worked as expected)

Short description of error
Motion blur is wrong, things in front of the camera became translucent (notice locations just behind the wheel arch and the front door seam. But if you use CUDA or CPU, motion blur works correctly.

wrong motion blur with optix GPU right motion blur with CUDA GPU or CPU
屏幕截图 2024-04-04 211229.png 屏幕截图 2024-04-04 211258.png

Exact steps for others to reproduce the error
Use a Nvidia RTX card with Optix API to render this file.

**System Information** Operating system: Windows-10-10.0.22621-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 551.86 **Blender Version** Broken: version: 4.1.0, branch: blender-v4.1-release, commit date: 2024-03-25 20:42, hash: `40a5e739e270` Worked: (newest version of Blender that worked as expected) **Short description of error** Motion blur is wrong, things in front of the camera became translucent (notice locations just behind the wheel arch and the front door seam. But if you use CUDA or CPU, motion blur works correctly. | wrong motion blur with optix GPU | right motion blur with CUDA GPU or CPU | |---|---| | ![屏幕截图 2024-04-04 211229.png](/attachments/563ec9d6-6d84-4557-9acc-42338e48669c) | ![屏幕截图 2024-04-04 211258.png](/attachments/d07f2452-9950-4051-b0d8-d495867b26ec) | **Exact steps for others to reproduce the error** Use a Nvidia RTX card with Optix API to render this file.
Roland-Vyens added the
Status
Needs Triage
Priority
Normal
Type
Report
labels 2024-04-04 15:35:45 +02:00
Roland-Vyens changed title from Wrong Motion Blur With GPU Using Optix API to Cycles: Wrong Motion Blur With GPU Using Optix API 2024-04-04 19:42:01 +02:00
YimingWu added the
Interest
Render & Cycles
label 2024-04-05 06:30:15 +02:00
Member

I can confirm this issue with a RTX 4090 on Windows in Blender 4.1.

I'm pretty sure this issue has been present for a while, but I can't find the older bug report for this.

I can confirm this issue with a RTX 4090 on Windows in Blender 4.1. I'm pretty sure this issue has been present for a while, but I can't find the older bug report for this.
Alaska added
Status
Confirmed
Module
Render & Cycles
and removed
Status
Needs Triage
labels 2024-04-05 09:58:07 +02:00
Author

I can confirm this issue with a RTX 4090 on Windows in Blender 4.1.

I'm pretty sure this issue has been present for a while, but I can't find the older bug report for this.

I wouldn't notice it without those fancy ornate textures lmao

> I can confirm this issue with a RTX 4090 on Windows in Blender 4.1. > > I'm pretty sure this issue has been present for a while, but I can't find the older bug report for this. I wouldn't notice it without those fancy ornate textures lmao

I was just curious to see what would happen on Intel Arc.

Looks like its correct with oneAPI.
I tried your default settings and with GPU denoiser box checked.
ARC A750 + Blender 4.1 + Ubuntu 23 x64 + Intel's newest linux drivers as of today.

I was just curious to see what would happen on Intel Arc. Looks like its correct with oneAPI. I tried your default settings and with GPU denoiser box checked. ARC A750 + Blender 4.1 + Ubuntu 23 x64 + Intel's newest linux drivers as of today.

I am facing the same problem with different files of my own, really seems apparent with vehicles i guess lol

As OP said, when using CPU or CUDA, the issue doesn't appear. No troubleshooting helped.
Both Blender 4.0.2 and Blender 4.1 show this issue

Note to my screenshots, one is with Motion Blur on, other is off.

I am facing the same problem with different files of my own, really seems apparent with vehicles i guess lol As OP said, when using CPU or CUDA, the issue doesn't appear. No troubleshooting helped. Both Blender 4.0.2 and Blender 4.1 show this issue Note to my screenshots, one is with Motion Blur on, other is off.
Member

CC @pmoursnv do you have time to take a look at this?

CC @pmoursnv do you have time to take a look at this?
Author

I am facing the same problem with different files of my own, really seems apparent with vehicles i guess lol

As OP said, when using CPU or CUDA, the issue doesn't appear. No troubleshooting helped.
Both Blender 4.0.2 and Blender 4.1 show this issue

Note to my screenshots, one is with Motion Blur on, other is off.

Very strange lol. Are you using rigacar for car rig?

> I am facing the same problem with different files of my own, really seems apparent with vehicles i guess lol > > As OP said, when using CPU or CUDA, the issue doesn't appear. No troubleshooting helped. > Both Blender 4.0.2 and Blender 4.1 show this issue > > Note to my screenshots, one is with Motion Blur on, other is off. Very strange lol. Are you using rigacar for car rig?

Very strange lol. Are you using rigacar for car rig?

Yes! Did you?

I tried replicating the issue using Rigacar Addon with very simple geometry ( 1 big box and 4 small boxes as wheels) but i couldn't replicate it so far-

I thought might be some funky stuff happening due to the Objects being parented to Bones going through multiple levels of constraints?

> Very strange lol. Are you using rigacar for car rig? Yes! Did you? I tried replicating the issue using Rigacar Addon with very simple geometry ( 1 big box and 4 small boxes as wheels) but i couldn't replicate it so far- I thought might be some funky stuff happening due to the Objects being parented to Bones going through multiple levels of constraints?
Author

I thought might be some funky stuff happening due to the Objects being parented to Bones going through multiple levels of constraints?

I'm using rigacar for this paticular car, but I don't think it's because this addon or multiple levels of parenting. Beacuse I also tested with all objects anim baked in visual keying and clear parenting/constraints.

> I thought might be some funky stuff happening due to the Objects being parented to Bones going through multiple levels of constraints? I'm using rigacar for this paticular car, but I don't think it's because this addon or multiple levels of parenting. Beacuse I also tested with all objects anim baked in visual keying and clear parenting/constraints.

I'm using rigacar for this paticular car, but I don't think it's because this addon or multiple levels of parenting. Beacuse I also tested with all objects anim baked in visual keying and clear parenting/constraints.

Ok thank you for your effort!

unfortunately i fear slower rendering with Cuda is the only solution at the moment

> I'm using rigacar for this paticular car, but I don't think it's because this addon or multiple levels of parenting. Beacuse I also tested with all objects anim baked in visual keying and clear parenting/constraints. Ok thank you for your effort! unfortunately i fear slower rendering with Cuda is the only solution at the moment
Author

unfortunately i fear slower rendering with Cuda is the only solution at the moment

Yes the only method now is rendering with cuda. But for my scene, blender will crash after 10 - 30 frames rendered out using cuda. I have to constantly re-render manually, which is annoying

> unfortunately i fear slower rendering with Cuda is the only solution at the moment Yes the only method now is rendering with cuda. But for my scene, blender will crash after 10 - 30 frames rendered out using cuda. I have to constantly re-render manually, which is annoying
Member

But for my scene, blender will crash after 10 - 30 frames rendered out using cuda. I have to constantly re-render manually, which is annoying

Please create a seperate bug report for this issue.

> But for my scene, blender will crash after 10 - 30 frames rendered out using cuda. I have to constantly re-render manually, which is annoying Please create a seperate bug report for this issue.
Author

Please create a seperate bug report for this issue.

I have no idea whether it is a bug or gpu memory or something else, it's hard to recreate this issue, I need to do more test someday.

> Please create a seperate bug report for this issue. I have no idea whether it is a bug or gpu memory or something else, it's hard to recreate this issue, I need to do more test someday.
Member

This is a driver bug unfortunately, a fix is in the works. Will notify when an updated driver is released.

This is a driver bug unfortunately, a fix is in the works. Will notify when an updated driver is released.

This is a driver bug unfortunately, a fix is in the works. Will notify when an updated driver is released.

Thank you for the info Patrick!

Just for my understanding- is it coupled with the current Nvidia Studio/Game Driver?

Switching to an older version could fix this issue?

> This is a driver bug unfortunately, a fix is in the works. Will notify when an updated driver is released. Thank you for the info Patrick! Just for my understanding- is it coupled with the current Nvidia Studio/Game Driver? Switching to an older version could fix this issue?
Member

Drivers pre-r550 are likely unaffected, yes, I didn't verify this though.

Drivers pre-r550 are likely unaffected, yes, I didn't verify this though.

Drivers pre-r550 are likely unaffected, yes, I didn't verify this though.

I will try and report my results today!

> Drivers pre-r550 are likely unaffected, yes, I didn't verify this though. I will try and report my results today!

With my test scene visible in the first comment i made, i experience the glitch with every Studio Driver after (including) 551.23

546.33 rendering with Optix did not show the issue

I didn't do extensive testing though, only 2 frames per run.

With my test scene visible in the first comment i made, i experience the glitch with every Studio Driver after (including) 551.23 546.33 rendering with Optix did not show the issue I didn't do extensive testing though, only 2 frames per run.
Author

With my test scene visible in the first comment i made, i experience the glitch with every Studio Driver after (including) 551.23

546.33 rendering with Optix did not show the issue

I didn't do extensive testing though, only 2 frames per run.

So this is a brand new bug lol

> With my test scene visible in the first comment i made, i experience the glitch with every Studio Driver after (including) 551.23 > > 546.33 rendering with Optix did not show the issue > > > I didn't do extensive testing though, only 2 frames per run. So this is a brand new bug lol

With my test scene visible in the first comment i made, i experience the glitch with every Studio Driver after (including) 551.23

546.33 rendering with Optix did not show the issue

I didn't do extensive testing though, only 2 frames per run.

So this is a brand new bug lol

I will try working on a personal animation again with the old driver and report how it went.

I am actually surprised, because i rendered out 2 or 3 animations with the currently "faulty" drivers, but havent noticed continuous artefacts, except for a frame here and there maybe.

But all of the sudden, nut much after you made your Original Post, it became all the more apparent over different files of mine. Also it looks like only some Objects are affected by it, as i couldn't recreate the bug with simple primitives.

> > With my test scene visible in the first comment i made, i experience the glitch with every Studio Driver after (including) 551.23 > > > > 546.33 rendering with Optix did not show the issue > > > > > > I didn't do extensive testing though, only 2 frames per run. > > So this is a brand new bug lol I will try working on a personal animation again with the old driver and report how it went. I am actually surprised, because i rendered out 2 or 3 animations with the currently "faulty" drivers, but havent noticed continuous artefacts, except for a frame here and there maybe. But all of the sudden, nut much after you made your Original Post, it became all the more apparent over different files of mine. Also it looks like only some Objects are affected by it, as i couldn't recreate the bug with simple primitives.

Its been over a week since installing Studio Driver 546.33 and i havent encounterd this issue once.

Its been over a week since installing Studio Driver 546.33 and i havent encounterd this issue once.
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
5 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#120256
No description provided.