Cycles render broken on Nvidia p106-100 rig, but renders fine on other machine. #77287

New Issue

Zach Hixson · 2020-06-03T00:24:48+02:00

Zach Hixson commented

2020-06-03 00:24:48 +02:00

System Information
Operating system: Ubuntu 18.04.4 LTS
Graphics card: 2x Nvidia P106-100

Blender Version
Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-03-12 05:06, hash: 375c7dc4ca
Worked: (optional)

Short description of error
I have a scene that renders fine on my Windows 10 machine with a gtx1070/970 combo, but when I render it on my headless render server with 2x P106-100 cards, half of the scene renders incorrectly. It seems to be fixed if I turn off motion blur, but I need it on for this shot so turning it off isn't really an option. I've been using these cards for the past 2 years and haven't had a single problem, so it's strange that this one scene causes such issues.

Exact steps for others to reproduce the error
I can't seem to find a reliable way to reproduce this bug. It seems to have something to do with having other render layers, as the main render layer renders fine, but all others in that one scene appear to be suffering from various motion blur related bugs. No other scenes are affected though.

I've simplified the scene to exclude all proprietary assets and attached it to this post. On the left is what it should look like, on the right is what I get when I render it on my headless machine.

animation_testing.blend

**System Information** Operating system: Ubuntu 18.04.4 LTS Graphics card: 2x Nvidia [P106](https://archive.blender.org/developer/P106.txt)-100 **Blender Version** Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-03-12 05:06, hash: `375c7dc4ca` Worked: (optional) **Short description of error** I have a scene that renders fine on my Windows 10 machine with a gtx1070/970 combo, but when I render it on my headless render server with 2x [P106](https://archive.blender.org/developer/P106.txt)-100 cards, half of the scene renders incorrectly. It seems to be fixed if I turn off motion blur, but I need it on for this shot so turning it off isn't really an option. I've been using these cards for the past 2 years and haven't had a single problem, so it's strange that this one scene causes such issues. **Exact steps for others to reproduce the error** I can't seem to find a reliable way to reproduce this bug. It seems to have something to do with having other render layers, as the main render layer renders fine, but all others in that one scene appear to be suffering from various motion blur related bugs. No other scenes are affected though. I've simplified the scene to exclude all proprietary assets and attached it to this post. On the left is what it should look like, on the right is what I get when I render it on my headless machine. ![example.png](https://archive.blender.org/developer/F8573053/example.png) [animation_testing.blend](https://archive.blender.org/developer/F8573055/animation_testing.blend)

Zach Hixson commented

2020-06-03 00:24:48 +02:00

Added subscriber: @ZachHixson

Alaska commented

2020-06-03 07:00:55 +02:00

Added subscriber: @Alaska

Alaska commented

2020-06-03 07:00:55 +02:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Alaska commented

2020-06-03 07:00:55 +02:00

Running a test render with a GTX 1050Ti driver 440.82 on Linux with Blender 2.82a from the command line for headless rendering, I am unable to reproduce the issue.

The most likely cause is outdated graphics drivers or failing hardware. Could you try updating your graphics drivers?

Are you also able do this for me:

Test a new version of Blender like 2.83 and/or 2.90: https://builder.blender.org/download/
Open Blender on the machine which is experiencing the issue and select from the top of Blender "Help>Save System Info" and upload it here? There may be a way to generate this file by the command line, not sure.

Running a test render with a GTX 1050Ti driver 440.82 on Linux with Blender 2.82a from the command line for headless rendering, I am unable to reproduce the issue. The most likely cause is outdated graphics drivers or failing hardware. Could you try updating your graphics drivers? Are you also able do this for me: 1. Test a new version of Blender like 2.83 and/or 2.90: https://builder.blender.org/download/ 2. Open Blender on the machine which is experiencing the issue and select from the top of Blender "Help>Save System Info" and upload it here? There may be a way to generate this file by the command line, not sure.

Alaska commented

2020-06-03 07:25:50 +02:00

Correction: Upon further investigation, I can confirm the issue on my system in headless and non-headless mode.

This issue persist when testing with 2.90.

Upon further investigation, it seems the issue occurs during the part of the animation where the plane is scaled to 0. I've seen reports for this kind of issue before. I will merge these reports.

Note: The report is not the exact same, but the sane sort of thing happens. There's rendering artifacts when a object is scaled to 0 while motion blur is enabled.

Correction: Upon further investigation, I can confirm the issue on my system in headless and non-headless mode. This issue persist when testing with 2.90. Upon further investigation, it seems the issue occurs during the part of the animation where the plane is scaled to 0. I've seen reports for this kind of issue before. I will merge these reports. Note: The report is not the exact same, but the sane sort of thing happens. There's rendering artifacts when a object is scaled to 0 while motion blur is enabled.

Alaska commented

2020-06-03 07:25:58 +02:00

Removed subscriber: @Alaska

Alaska commented

2020-06-03 07:26:11 +02:00

Closed as duplicate of #75441

Alaska closed this issue

2020-06-03 07:26:11 +02:00

Zach Hixson commented

2020-06-03 20:47:08 +02:00

The plane scaled to 0 bit would explain a lot, and why it only affects those two render layers. I'll try moving it out of the way instead and see if that fixes it for the time being. The holdout plane was there to save on render time, so that way time wasn't wasted on render layers when they weren't going to be used anyways.

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

Cycles render broken on Nvidia p106-100 rig, but renders fine on other machine. #77287