Vertex map not working with Vertex Displacement node? Tweet

[SundancePioneer]

Hey people,

I am currently trying to get a working setup that mixes displacement using a fields-driven vertex map. However it seems that whenever i use the vertex map to blend the displacement nodes, it looses all height information.

This is the basic vertex map on a simple sphere:


This is the setup in the shader:


This is the result (no height data...):


However, when i use internal Octane nodes (such as Float, Falloff, or Noise) the height data is maintained (using 90deg falloff in this case):


Is this some sort of internal limitation, or is there just a flaw in my setup?

Any help is greatly appreciated - thanks!

Best regards

Sundance

[Jengo_1]

Joining the question, been trying to use vertexmap for displacements all day to no avail.
Here's what I've tried so far:

Tried both vertex and texture displacement
tried to use the vertexmap in the blend node in the dislacepment mix node
tried disabling enable c4d shader baking, and use OSL for c4d
tried to use the baking-texture node
tried to up vertexmap resolution and priority in the common tab
I think I tried a few other things but nothing works. This issue been asked about for a few years now so I kind assumed it was addressed in the new versions, but if it's not I'll let it go.

[SundancePioneer]

Joining the question, been trying to use vertexmap for displacements all day to no avail.

Thanks for sharing the stuff you tried @Jengo_1 - i have been trying most of that stuff as well, but from what i could find online, it seems to me that the vertex map node is still not really accessible by Octane for some reason? But as you mentioned, it has been asked for quite some time now. Maybe the devs could shed some light on whether this is on the roadmap or not? It would in fact be a really good feature...

[aoktar]

Vertexmap technology(vertex attributes) are not still supported by Octane renderer. You may try to use C4d's effect to do it.

[SundancePioneer]

Vertexmap technology(vertex attributes) are not still supported by Octane renderer. You may try to use C4d's effect to do it.

Thanks for following up @aoktar - by "C4d's effect" you are talking about the displace deformer? Or something else?

[aoktar]

Vertexmap technology(vertex attributes) are not still supported by Octane renderer. You may try to use C4d's effect to do it.

Thanks for following up @aoktar - by "C4d's effect" you are talking about the displace deformer? Or something else?

Yes displace deformer, I know it's not exact same but similar because both are deforming the vertexes at end.

[Jengo_1]

Thanks for the clear up aoktar! Yeah I've ended up trying a displacement deformer but it requires too many subdivisions for the effect to be practical.
Hopefully we'll get access to the vertexmap soon!
Aoktar, I'm just curious - is this issue (and similar issues that involve C4D restrictions) are a thing where you guys have to figure how to work around the C4D infrastructure half blindly? Or does Maxon allow you full access to the code of the program? Just wonder why Redshift for example has a easier time integrating with c4d, even before they were bought by Maxon. I'm so ignorant to these kind of things, it's actually fascinating to know how it works.

[aoktar]

First this is not C4D related issue, our CORE is not supporting that. Also I don't wish to suppose RS is having more than us for integration. At least they should use same SDK but they may have a tighter communication to ask every issues.

[Jengo_1]

I see what you're saying, well I definitely appreciate the fact that you guys are out here making this engine happen. It changed my life!