MOPs Forums

Nope, you're not overlooking anything... looks like mesh interpolation isn't working in this mode. I'll patch this up, but in the meantime the best solution is to uncheck "Enable Template Interpolation".

Today's build adds drag-drop reordering to the Attribute Mapper. Let me know how it works for you!

Henry

If you notice this bug happening in a clean scene, please let me know. I'll keep working on the reordering thing.

Thanks for purchasing, and I'm happy you're enjoying MOPs!

Hi Nathan,

I'm not able to replicate this bug on my end. Can you tell me what version of Houdini you're using? Is the scene you're working on an upgrade from a much older build of MOPs Plus? I'm testing in both 18.0 and 18.5 and have no trouble modifying string attributes.

That bug's a new one! I'll check it out.

You mentioned the reordering in a past thread... I'm working on something, it's just taking a while to beat Qt into submission.

There's no guaranteed way to update a node to a more recent version. In general, if I make a change to a node that isn't backwards compatible, I'll version up the HDA so that older files will still work as they did. You can use the Asset Bar (you can enable this from the assets window) to switch bet...

Hi Lu, You don't need to unpack geometry for Redshift to be able to access it in materials. The RS Curvature node is scale-dependent, so at the default scale of the letters generated by MOPs+ Typography, you might want to try using a Radius of 0.02 as a starting point. You should be able to clearly ...

Looks like this was a bug or omission from a previous update... I've just added an Enable Falloff parameter to the Spring Modifier. The update is in the `henry_dev` branch on GitHub... if you switch to that branch and download the latest zip, it will have this new change. I'll fold this into the nex...

This is a bug caused by Houdini having multiple active network viewers. If you revert to one of the standard Houdini layouts, activation should work as normal. I'll patch this out eventually, it's just not always easy to tell which network viewer is the "right" one to create the activator in.

This is a tricky one, because the original mesh is deforming so there's going to sometimes be gaps no matter what because the exploded primitives are effectively "rigid" and can't be deformed, only transformed. Additionally, areas where the mesh nearly collides (elbows and other tight intersections)...