MOPs Forums

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)...

Hey Geoff, Part of the issue here is determining which way is the "right" orientation on a soccer ball. If you were to run Polyframe or MOPs Orient Mesh on the source geometry before you add those points, and you visualize the up vectors, you can see that it's hard to really know for sure what the u...

Hello, The reason your expression doesn't work is because you can't accumulate a value (+=1) in SOPs without there being some kind of solver involved. It looks to me like you want the tree sequences to "activate" upon the falloff value being greater than zero? I'm attaching a HIP file that shows how...

I responded to your email, but for anyone else watching this thread, the extrusion groups in MOPs Typography work fine, but the groups are packed along with the geometry. If you want to use the groups, you either need to unpack, or target the groups using Material Stylesheets.

Is there any chance you can send me a sample file with a scrubbed CSV that's using similar formatting to what you were using initially? It sounds like a parsing error, but it's hard to know exactly what to repair without being able to reproduce the error exactly. Regarding the errors you're seeing, ...

Hello! Sorry about the error reporting; this is a Houdini issue I've been trying to work through with SideFX for a while. It's pretty hard to properly show error reports on blackboxed nodes. Hopefully that can be fixed soon. Regarding the error you're seeing, I'm not able to reproduce it from here. ...

I'm not sure exactly what error you're running into, but if it's a VEX error, you just need to download a more recent build of MOPs. The latest Stable build, v1.3, should have the problem fixed. If you're still having trouble, please show me the exact error you're seeing.

Thanks!

I think I know what the issue was... assuming you're using MOPs+ Indie, the bug has been fixed. If you re-download version 2021-01-02, it should activate. Please let me know if you're still having any trouble.

Hmm, okay. It sounds like there's possibly something else going wrong with the installation process.

If you dive inside a SOP network and hit the Tab menu, do you see MOPs Plus nodes in there? They will throw license errors if you cook them, but you should still be able to see them.