I think in that case this can be closed as "sort of Resolved" and you can open a new one for this new issue. Sounds like it shouldn't happen, unless the influence or Mute property is driven.

A colleague had this issue as well, it's on my radar, not sure when I will have time to investigate.

In T98494#1366562, @Hans Goudey (HooglyBoogly) wrote:

I mean that it wouldn't work when object evaluation has replaced the curve with an evaluated mesh

Ah okay, so deforming modifiers that can work on curve points will still work, that's good!
If you need to convert your curve to mesh while still letting it function as a curve, I think you can just separate the mesh generation part into a separate object using GeoNodes, and keep your curve as a real curve. 👍 Seems like a good workflow from user perspective in the first place.

"Path Animation" settings from the legacy curve object will have to be moved to the contraints that support them

Thank god! 🙏

While playing around with it a bit more, I also discovered something that looks more like a bug:

• Disable Path Animation
• Parent object
• Enable Path Animation
• Child object doesn't update in real-time (missing dependency I guess)

Tested, it just works! 10/10.

This report does not contain all the requested information, which is required for us to investigate the issue.

This report does not contain all the requested information, which is required for us to investigate the issue.

Setting no Needs Review since I'm waiting for clarification.

Done, my first time adding release notes, let me know if it needs to be tweaked.

Yes, it's worth mentioning that there also exist copy pasting issues when it comes to quitting Blender, but I was already aware that that's a known issue, so note that none of the inconsistent behaviours I listed here require quitting Blender.

Found this ridiculous workaround:
row.prop(constraint, 'mute', layout.icon(constraint)-constraint.mute+1, invert_checkbox=True)

In D13129#399694, @Campbell Barton (campbellbarton) wrote:

Also, an add-on may be enabled without being enabled in the preferences, so I'd like to double check that this will work properly.

If the addon is disabled in the user preferences, it cannot be enabled on a per workspace basis, because only addons that are enabled in the preferences show up at all in the workspace addon filter list. Maybe I misunderstand what you mean here.

Address feedback.

Address feedback.

arc missed a file...?

This is great! Especially for pre/early production, where we have a bunch of early layout meshes that we want to rig quickly using Surface Deform. I only wish it didn't spam the console in this case! =)

Can you check if this is happening with the version of CloudRig for Blender 3.0-3.1?

The patch is ready: D14757

Get in contact with me on blender.chat if you would like me to clarify what I find wrong with your communication, as it would be off-topic here.

I don't recommend condescension as your primary choice for a communication tool when asking strangers for favors. It highlights ignorance and gets in the way of building rapport.

Next release is June 8. Me reverting the patch today would have no effect on your studio's workflow, unless you want to use a random daily Alpha build for your production.
The patch comes with improvements to the UI and for most workflows, which the module maintainers have agreed on, as I'm sure you're aware, since there's a link to the review at the top: D11356

It might not be as trivial as I first thought, but I put it on my TODO list. Sadly though this is my last day at a PC this week, so I'll try to get around to it sometime next week.