1
$\begingroup$

I have this scene where I fracture the earth and assign a distance to each piece called heat

I then scale it to between 0-1 and pass that to a color ramp and color the pieces.

This works exactly as expected in the preview.

enter image description here

enter image description here

However, in cycles the attribute becomes 0 by default. And everything has the same value.

enter image description here

The geonode setup is this simple.

enter image description here

This feels like a bug. Can anyone think of why this wouldn't work in cycles?

Improve this question
$\endgroup$
4
  • $\begingroup$ Do you have a single object with islands, or one object per piece ? $\endgroup$
    – StefLAncien
    Commented May 19 at 6:48
  • $\begingroup$ One object per piece. $\endgroup$
    – TheJeran
    Commented May 19 at 7:15
  • $\begingroup$ It would be much easier if you could upload your file. Finding a solution by just recreating something similar to your setup might suffer from having different properties which do not apply in your scene - which is why none of the proposed solutions in the answer might not work for you eventually. $\endgroup$
    – Gordon Brinkmann
    Commented May 19 at 16:08
  • $\begingroup$ The interesting here would be, because you give no information about it in your question: How have you fractured the earth and how are the pieces moving? $\endgroup$
    – Gordon Brinkmann
    Commented May 19 at 16:19

1 Answer 1

Reset to default
0
$\begingroup$

(Using Blender 3.6.8)

Final (?) proposal

It seems that "heat" is an attribute of the Cycles render engine. Changing "heat" to "Heat" is solving the different behaviour compared to the Eevee render engine:

GN V3

Shader V3

Resources:

First proposal

Storing the attribute in Instance domain, instead of Point domain, yields the same behaviour with Eevee and Cycles render engines, using the following setup:

GN Graph

Shader Cycles

Shader Eevee

Resources:

Second proposal

Following is a proposal working in Point domain (dark green part of the GN graph) and in Instance domain (dark red part of the GN graph):

GN V2

V2 by point

V2 by instance

Resources:

Improve this answer
$\endgroup$
3
  • $\begingroup$ I will probably delete first and second proposal, if the third one is validated... $\endgroup$
    – StefLAncien
    Commented May 19 at 10:01
  • $\begingroup$ This will not work. Since I am using two materials on my objects. Instances do not support multiple material assignments. Also this doesn't explain why it won't show up in Cycles. I would be curious to see if you can assign a second material to the tops of all of those cubes and still get the correct result tho. Would narrow down the issue $\endgroup$
    – TheJeran
    Commented May 19 at 12:22
  • $\begingroup$ @TheJeran: Are you talking about what I labelled "Final (?) proposal" ? Or about the "First" and "Second" proposals, that might be removed ? Could you try and change "heat" into "Heat", and let us know the outcome ? $\endgroup$
    – StefLAncien
    Commented May 19 at 12:27

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .