Separating meshes by material makes render passes in cycles stuck in 1/64 #89884

New Issue

Lucas Skruzdeliauskas · 2021-07-16T01:39:09+02:00

2021-07-16 01:39:09 +02:00

System Information
AMD Ryzen 3600
AMD Radeon R9 390 8GB
SSD Adata SX8100NP
16 GB Kingston DDR4 2400MHz

Operating system: Windows 10
Graphics card: AMD Radeon R9 390 8GB

Blender Version
Broken: 2.92.0, 02948a2cab, master, 2021-02-04

Whenever you have a scene and decides to select every object in it, that was brought from Sketchup with the addon importer from gitHub, and in edit mode separates them all by material some places just don't have any material and the viewport render doens't get past 1/64 samples

The steps to reproduce this error are simply import any scene from sketchup with this addon https://github.com/RedHaloStudio/Sketchup_Importer/releases/tag/0.22.3 select all items and separate them by material and try to use viewport render in cycles

I will upload one of the scenes that have that problem with everything already broken Carros.blend

**System Information** AMD Ryzen 3600 AMD Radeon R9 390 8GB SSD Adata SX8100NP 16 GB Kingston DDR4 2400MHz Operating system: Windows 10 Graphics card: AMD Radeon R9 390 8GB **Blender Version** Broken: 2.92.0, 02948a2cab44, master, 2021-02-04 **Whenever you have a scene and decides to select every object in it, that was brought from Sketchup with the addon importer from gitHub, and in edit mode separates them all by material some places just don't have any material and the viewport render doens't get past 1/64 samples** The steps to reproduce this error are simply import any scene from sketchup with this addon https://github.com/RedHaloStudio/Sketchup_Importer/releases/tag/0.22.3 select all items and separate them by material and try to use viewport render in cycles I will upload one of the scenes that have that problem with everything already broken [Carros.blend](https://archive.blender.org/developer/F10225533/Carros.blend)

Lucas Skruzdeliauskas commented

2021-07-16 01:39:09 +02:00

Added subscriber: @lucasskruz

blender-admin commented

2021-07-16 01:39:09 +02:00

This issue was referenced by fdb811f030

This issue was referenced by fdb811f030577f10aca7af636f1a60a04332604f

Lucas Skruzdeliauskas commented

2021-07-16 03:40:29 +02:00

It does not break when you do one object at a time

Philipp Oeser commented

2021-07-23 12:28:17 +02:00

Added subscribers: @brecht, @lichtwerk

Philipp Oeser commented

2021-07-23 12:28:17 +02:00

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

Philipp Oeser commented

2021-07-23 12:28:17 +02:00

I can reproduce a problem (not totally sure yet if this is the only problem here).
In a Debug build, I first isolated this by removing stuff one by one ended up with a single object and culprit material called r light0.
Then I noticed this material had luxcore Custom properties (including an ID pointer to a Nodetree). If I removed the Custom property, everything was fine again.
Then I noticed luxcore properties on the scene as well. If I removed the Custom properties on the scene (as opposed to doing it on materials), everything was fine again as well.
So this is your scene with just that one property removed (and it now renders fine for me)

Carros_luxcore_scene_prop_removed.blend

note: with the Custom Property still there, I was getting this assert:

blender: intern/cycles/kernel/../kernel/kernel_accumulate.h:670: ccl::float3 ccl::path_radiance_clamp_and_sum(ccl::KernelGlobals*, ccl::PathRadiance*, float*): Assertion `!"Non-finite final sum in path_radiance_clamp_and_sum!"' failed.

@brecht: does this ring a bell in conjunction with luxcore custom props?

other note: this was the custom prop on the Material (with the ID pointer that looked unset in the UI)

>>> D.materials['r light0']['luxcore']['node_tree']

<bpy id prop: owner="MAr light0", name="node_tree", address=0x7f3206fe6a88>

But of course with luxcore now in play, we have to find out if/how the Sketchup importer has to do with it.
@lucasskruz : could you check with Factory Settings (File > Defaults > Load Factory Settings), so luxcore is out of play, then try the same thing (Import sketchup, separate by material and render)?

I can reproduce a problem (not totally sure yet if this is the **only** problem here). In a Debug build, I first isolated this by removing stuff one by one ended up with a single object and culprit material called `r light0`. Then I noticed this material had `luxcore` Custom properties (including an ID pointer to a Nodetree). If I removed the Custom property, everything was fine again. Then I noticed luxcore properties on the scene as well. If I removed the Custom properties on the scene (as opposed to doing it on materials), everything was fine again as well. So this is your scene with just that one property removed (and it now renders fine for me) ![image.png](https://archive.blender.org/developer/F10234788/image.png) [Carros_luxcore_scene_prop_removed.blend](https://archive.blender.org/developer/F10234791/Carros_luxcore_scene_prop_removed.blend) note: with the Custom Property still there, I was getting this assert: ``` blender: intern/cycles/kernel/../kernel/kernel_accumulate.h:670: ccl::float3 ccl::path_radiance_clamp_and_sum(ccl::KernelGlobals*, ccl::PathRadiance*, float*): Assertion `!"Non-finite final sum in path_radiance_clamp_and_sum!"' failed. ``` @brecht: does this ring a bell in conjunction with luxcore custom props? other note: this was the custom prop on the Material (with the ID pointer that looked unset in the UI) ``` >>> D.materials['r light0']['luxcore']['node_tree'] <bpy id prop: owner="MAr light0", name="node_tree", address=0x7f3206fe6a88> ``` But of course with luxcore now in play, we have to find out if/how the Sketchup importer has to do with it. @lucasskruz : could you check with Factory Settings (`File` > `Defaults` > `Load Factory Settings`), so luxcore is out of play, then try the same thing (Import sketchup, separate by material and render)?

Lucas Skruzdeliauskas commented

2021-07-24 03:15:07 +02:00

I checked, and it still doesn't work, a clue i spotted to when it's malfunctioning is that when separating by materials, some objects disapear or change their materials to none, like in this mercedez where the door seems to be with no materials, and it looks like it only happens on the objects that are related to tohers, like the ones that are mirrerored (mirrors, doors, parts of the chassi, etc.)

I checked, and it still doesn't work, a clue i spotted to when it's malfunctioning is that when separating by materials, some objects disapear or change their materials to none, like in this mercedez where the door seems to be with no materials, and it looks like it only happens on the objects that are related to tohers, like the ones that are mirrerored (mirrors, doors, parts of the chassi, etc.)![image.png](https://archive.blender.org/developer/F10235563/image.png)

Brecht Van Lommel commented

2021-07-26 18:34:34 +02:00

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

Brecht Van Lommel closed this issue

2021-07-26 18:34:34 +02:00

Brecht Van Lommel self-assigned this 2021-07-26 18:34:34 +02:00

Brecht Van Lommel commented

2021-07-26 18:34:38 +02:00

This is fixed in 3.0 and will be fixed in the next 2.93 LTS as well. Note that we no longer fix bugs in 2.92.

In #89884#1195233, @lichtwerk wrote:
@brecht Van Lommel (brecht): does this ring a bell in conjunction with luxcore custom props?

You can ignore this assert, it's for debugging. NaNs can happen in some rare samples in valid scenes, they are unrelated to this.

This is fixed in 3.0 and will be fixed in the next 2.93 LTS as well. Note that we no longer fix bugs in 2.92. > In #89884#1195233, @lichtwerk wrote: > @brecht Van Lommel (brecht): does this ring a bell in conjunction with luxcore custom props? You can ignore this assert, it's for debugging. NaNs can happen in some rare samples in valid scenes, they are unrelated to this.

Falk David referenced this issue

2023-02-10 13:03:23 +01:00

Blender LTS: Maintenance Task 2.93 #88449

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

Separating meshes by material makes render passes in cycles stuck in 1/64 #89884