Indigo Renderer Forum

I am using Indigo 3.0.10 and Skindigo 3.0.10 and I noticed that any textures I have with displacement enabled stop subdividing when I put them inside a component and enable instancing. Is this a bug or is there something else I need to do?

Aflac wrote:I am using Indigo 3.0.10 and Skindigo 3.0.10 and I noticed that any textures I have with displacement enabled stop subdividing when I put them inside a component and enable instancing. Is this a bug or is there something else I need to do?

Hi, this is a bug. I'm not sure if it is a new bug in SkIndigo 3.0.10 or if it's been around for awhile. I'll put it on my high priority fix list.

Whaat wrote:

Aflac wrote:I am using Indigo 3.0.10 and Skindigo 3.0.10 and I noticed that any textures I have with displacement enabled stop subdividing when I put them inside a component and enable instancing. Is this a bug or is there something else I need to do?

Hi, this is a bug. I'm not sure if it is a new bug in SkIndigo 3.0.10 or if it's been around for awhile. I'll put it on my high priority fix list.

I try "old" 2.4.13 (Indigo & SkIndigo)... same bug.

test: instanced objects on the right have constant displacement!

Do you happen to be using view-dependent displacement (ie the pixel threshold more than 0)? I have gotten errors related to that when using instances in Blendigo.

FakeShamus wrote:Do you happen to be using view-dependent displacement (ie the pixel threshold more than 0)? I have gotten errors related to that when using instances in Blendigo.

That's because view-dependent displacement means that the object is divided according to its visibility and distance from camera, so objects at different distances/angles will be subdivided differently. This creates a problem for instances because they are all using the same mesh data. View-dependent subdivision is incompatible with the basic principle behind instances. Not really a bug, just a limitation of instances as a whole.

StompinTom wrote:That's because view-dependent displacement means that the object is divided according to its visibility and distance from camera, so objects at different distances/angles will be subdivided differently. This creates a problem for instances because they are all using the same mesh data. View-dependent subdivision is incompatible with the basic principle behind instances. Not really a bug, just a limitation of instances as a whole.

yes... have sense
but
<view_dependent_subdivision>false</view_dependent_subdivision> on *-meshes.igs file don't works


...
i thinks view_dependent should not be a mesh's parameter (or material's) but a camera's parameter... like focus!