<![CDATA[Bug in mograph python effector default state R20]]>When you use a mograph python effector switched to "full control" mode by default it doesn't work because of the absence of a falloff field. It took me awhile to figure out why my custom effectors didn't work coming from R18 to R20.

I would suggested updating the boilerplate in the effector when switching to full control mode to check for a falloff if that's possible. If not maybe fall back to commented out version for with falloff and without?

]]>http://developers.maxon.net/forum/topic/11639/bug-in-mograph-python-effector-default-state-r20RSS for NodeTue, 09 Jun 2026 18:19:30 GMTMon, 24 Jun 2019 18:53:09 GMT60<![CDATA[Reply to Bug in mograph python effector default state R20 on Wed, 03 Jul 2019 15:08:22 GMT]]>Thanks for reporting I've created a bug report.

Cheers,
Maxime

]]>http://developers.maxon.net/forum/post/58746http://developers.maxon.net/forum/post/58746Wed, 03 Jul 2019 15:08:22 GMT<![CDATA[Reply to Bug in mograph python effector default state R20 on Tue, 02 Jul 2019 17:04:22 GMT]]>Hey @m_adam thanks for getting back to me. I'm on R20.059.

Here's the default python effector when switched to full control. I haven't touched anything. As you can see it does nothing even though it's supposed to be lifting each clone up 100cm.

If you set the last parameter in the md.SetArray() function to False. It will work.

python_effector_demo_01.c4d

]]>http://developers.maxon.net/forum/post/58731http://developers.maxon.net/forum/post/58731Tue, 02 Jul 2019 17:04:22 GMT<![CDATA[Reply to Bug in mograph python effector default state R20 on Mon, 01 Jul 2019 09:23:20 GMT]]>Hi @codysorgenfrey, thanks for writing to us.

Normally this issue was fixed in R20 SP1, so which version do you use?
If you are in greater than SP1 (R20.026) please attach an example file since I'm not able to reproduce it anymore.

Cheers,
Maxime.

]]>http://developers.maxon.net/forum/post/58703http://developers.maxon.net/forum/post/58703Mon, 01 Jul 2019 09:23:20 GMT