Optix render errors with motion blur and unknown bone constraint relationship #71344

New Issue

stephen thomas · 2019-11-04T20:01:01+01:00

stephen thomas commented

2019-11-04 20:01:01 +01:00

System Information
Operating system: Linux-5.3.0-19-generic-x86_64-with-debian-buster-sid 64 Bits
Graphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21

Blender Version
Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-11-03 03:57, hash: 8ab6ef30ab
Worked: (optional)

Short description of error
For the past couple of hours I've been trying to figure out what exactly is causing this bug, so apologies for it being a bit vague.

Find attached part of a character from a project I'm currently working on. When rendering with Optix with motion blur switched on, the character shows errors on certain parts of the body, the eye being one of them. I've stripped the rig down as far as I can while keeping the bug active, but I can't narrow it down further to find the exact cause. I believe it's something to do with the stretch to constraint on the 'body' bone, which is also squashing the eye bone. The error doesn't occur when rendering with CUDA.

Currently, the eye is parented to the eye.l bone. If the the Armature modifier is used instead of parenting, the render error doesn't occur.

Exact steps for others to reproduce the error
Open 'rtx-optix-motion-blur-bug.blend'.
Change Cycles Render Device to OptiX and hit render
Turn off motion blur and hit render.
Compare results.

system-info.txt

rtx-optix-motion-blur-bug.blend

**System Information** Operating system: Linux-5.3.0-19-generic-x86_64-with-debian-buster-sid 64 Bits Graphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21 **Blender Version** Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-11-03 03:57, hash: `8ab6ef30ab` Worked: (optional) **Short description of error** For the past couple of hours I've been trying to figure out what exactly is causing this bug, so apologies for it being a bit vague. Find attached part of a character from a project I'm currently working on. When rendering with Optix with motion blur switched on, the character shows errors on certain parts of the body, the eye being one of them. I've stripped the rig down as far as I can while keeping the bug active, but I can't narrow it down further to find the exact cause. I believe it's something to do with the stretch to constraint on the 'body' bone, which is also squashing the eye bone. The error doesn't occur when rendering with CUDA. Currently, the eye is parented to the eye.l bone. If the the Armature modifier is used instead of parenting, the render error doesn't occur. **Exact steps for others to reproduce the error** Open 'rtx-optix-motion-blur-bug.blend'. Change Cycles Render Device to OptiX and hit render Turn off motion blur and hit render. Compare results. [system-info.txt](https://archive.blender.org/developer/F7935358/system-info.txt) ![parented-to-bone-vs-armature-modifier.png](https://archive.blender.org/developer/F7935359/parented-to-bone-vs-armature-modifier.png) ![with-motion-blur.png](https://archive.blender.org/developer/F7935360/with-motion-blur.png) ![without-motion-blur.png](https://archive.blender.org/developer/F7935361/without-motion-blur.png) [rtx-optix-motion-blur-bug.blend](https://archive.blender.org/developer/F7935362/rtx-optix-motion-blur-bug.blend)

stephen thomas commented

2019-11-04 20:01:01 +01:00

Added subscriber: @stephenthomas

Patrick Mours was assigned by Brecht Van Lommel

2019-11-05 16:15:54 +01:00

Patrick Mours commented

2019-11-07 20:08:33 +01:00

So, this is an interesting one. The problem here is that there is a mismatch between the motion SRT transform that OptiX uses for traversal and the one Cycles computes for shading. Which causes these artifacts.

OptiX essentially expects a SRT with a scaling/shear matrix of the form

/ sx a b px \
| 0 sy c py |
| -- |
\ 0 0 sz pz /

But the transform decomposition code in Cycles generates a scaling matrix of the form

/ sx d e \
| d sy f |
| -- |
\ e f sz /

Currently the OptiX implementation in Cycles mistakenly assumes that a = d, b = e and c = f, which is why things go wrong. I think the cleanest way to fix this is to modify the decomposition code to create factors more inline with what OptiX uses, but I'll need to do some testing to make sure this wouldn't break anything.

So, this is an interesting one. The problem here is that there is a mismatch between the motion SRT transform that OptiX uses for traversal and the one Cycles computes for shading. Which causes these artifacts. OptiX essentially expects a SRT with a scaling/shear matrix of the form ``` / sx a b px \ | 0 sy c py | | -- | \ 0 0 sz pz / ``` But the transform decomposition code in Cycles generates a scaling matrix of the form ``` / sx d e \ | d sy f | | -- | \ e f sz / ``` Currently the OptiX implementation in Cycles mistakenly assumes that `a = d`, `b = e` and `c = f`, which is why things go wrong. I think the cleanest way to fix this is to modify the decomposition code to create factors more inline with what OptiX uses, but I'll need to do some testing to make sure this wouldn't break anything.

Philipp Oeser commented

2020-01-15 20:17:17 +01:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2020-01-15 20:17:17 +01:00

Changed status from 'Needs Triage' to: 'Confirmed'

Philipp Oeser commented

2020-01-15 20:17:17 +01:00

I am getting the following [which is very likely caused by trying this in a hacked build on a non-RTX 970m...]

Failed to build OptiX acceleration structure
OptiX CUDA error CUDA_ERROR_INVALID_CONTEXT in cuMemAlloc(&motion_transform_gpu, motion_transform_size), line 1450

Leaving that aside, I would assume from the previous comments that this is actually confirmed, @pmoursnv?

I am getting the following [which is very likely caused by trying this in a hacked build on a non-RTX 970m...] ``` Failed to build OptiX acceleration structure OptiX CUDA error CUDA_ERROR_INVALID_CONTEXT in cuMemAlloc(&motion_transform_gpu, motion_transform_size), line 1450 ``` Leaving that aside, I would assume from the previous comments that this is actually confirmed, @pmoursnv?

Patrick Mours commented

2020-01-16 11:57:21 +01:00

The invalid context error has been fixed in ff430dea66, but that was just a simple oversight. But yes, this is confirmed.
It is also relevant for D6575, since Embree uses the same decomposition (see RTCQuaternionDecomposition documentation, they call the parameters "skew" and "shift") that OptiX uses.

The invalid context error has been fixed in ff430dea66, but that was just a simple oversight. But yes, this is confirmed. It is also relevant for [D6575](https://archive.blender.org/developer/D6575), since Embree uses the same decomposition (see `RTCQuaternionDecomposition` documentation, they call the parameters "skew" and "shift") that OptiX uses.

blender-admin commented

2020-01-16 18:08:52 +01:00

This issue was referenced by blender/cycles@82fdb33159

This issue was referenced by blender/cycles@82fdb33159eb0d29a75981f2085205a39fd054e6

blender-admin commented

2020-01-16 18:08:52 +01:00

This issue was referenced by 26687dda5a

This issue was referenced by 26687dda5ab7de1e2a00cb6252a6eb919c3f570c

Patrick Mours commented

2020-01-22 15:50:14 +01:00

Changed status from 'Confirmed' to: 'Resolved'

Patrick Mours closed this issue

2020-01-22 15:50:14 +01:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Optix render errors with motion blur and unknown bone constraint relationship #71344