Hi, I don't have a V-Ray license, so I am unable to test this myself. Do you know if the mesh batch renders properly in Maya Software or Arnold? Can you describe exactly what is happening? Is the model not moving? Are you only using Maya skinning? Or are you using other deformers like delta mush? Are you rendering locally or on a farm? I am trying to think what the issue could be, because I have not had issues with Maya Software or Arnold.

I have released BETA 3.0.1 which should resolve this. You can download it here: https://www.rapidrig.com/download-rrm3

In 3.0.1, I have added a new Maya Space control for the Trajectory. You can get the version here: https://www.rapidrig.com/download-rrm3

I have rolled out a fix for this in BETA_3_0_1. You can get it here:https://www.rapidrig.com/download-rrm3 The locators may end up really huge if you change the units while a scene is open, but the error should be gone now. I will add more fixes and support for more units in a future release.

I have rolled out a fix for this in BETA_3_0_1. You can get it here: https://www.rapidrig.com/download-rrm3 The locators may end up really huge if you change the units while a scene is open, but the error should be gone now. I will add more fixes and support for more units in a future release.

When exporting fbx files that you want to have custom animation channel data, the best method I know of is to have those channels on a joint in the skeleton. Joints are where all the animation should typically be. Anything on meshes or other nodes will likely be lost on export. My recommendation would be to have the same attributes you already created on the controls be added and driven 1:1 on the root joint. Either through a set driven key or maybe using proxy attributes. After exporting with those new joint attributes, it should get the animation data into engine, and then I think you’ll have to set up how to drive those morph channels using the animation data from the joint. I haven’t set this up myself but I know it’s possible. Dustin

This looks to be related to the f-string. Are you running Python 2 in Maya 2022?

In your script editor, do you have "Show Stack Trace" enabled? There isn't anything meaningful in this error so hopefully it was not enabled, and you can try again. I tested in Maya 2022 and I am not hitting any errors.

Thanks for reporting this, I will add a fix in the next update.

I'll add a "MayaSpace" control for the Trajectory in the next update, which I think should be a solution.

I am not sure what could cause your attributes to already be disconnected at time of export, but in the next update, I will add a check to not try to disconnect attributes. You could also try rebuilding the rig, which should remake the missing connections, and try exporting again.

It's strange that it is getting hung up on the f-string formatting. That is compatible with Python in Maya 2022. Can you run the following two lines of code in the script editor, and let me know what it prints? import sys print(sys.version)

Thanks for the detailed reply. That's really helpful to get context. Unfortunately I have not been able to reproduce most of what you have described. I did a test build of a rig from the 2024_05_22 release and another rig from the 2024_09_20 release. The control orientations are identical between both versions where Z is the twist axis across the majority of controls, as it has always been in RRM3. The "world" and "object" controls for the IK arms and legs has the same behaviour between both rigs as well. I did notice that the old proxies came in weird when first opening the file. I applied a slight scale change on the "RRM_MAIN" of the 2024_05_22 proxies, and that change jarred the proxies to go back to their normal location. Not sure why that is happening, but undoing the scale change kept the proxies in the correct locations. I also updated the proxies from the 2024_05_22 setup using the UI from 2024_09_20. No issues there. Then rebuilt a 2024_05_22 rig using the updated proxies which hit a snag on the "Keep Control Shapes", but after disabling that option, the rig rebuilt correctly. This was testing a biped build, so maybe there is more going on with other modules or settings that I didn't run into. Would you be able to send me one of your old rigs with proxies so I can take a look at it? I do not need any geometry. Just the rig. Then I can see exactly what you are describing. Dustin

The changes you are describing, is this the proxies or rig controls? RRM3 controls have had the same axes since its inception. There are some Maya space controls that were later added, as shown here: https://www.rapidrig.com/post/rapid-rig-modular-3-new-axes-controls but these did not remove any of the previous functionality. They are additive to the existing controls and do not need to be used. You mention proxy rigs, those also have not had any major intentional changes that change axes if that is what you are referring to. Maybe I am misunderstanding what old logic and new version you are referring to? There is an option to "Update Proxy Rig to Latest Version". That might help in your situation. Can you explain how the new version is destroying your proxies? I haven't run into this before, so I would like to know what exactly is going on. Dustin

You are correct, the updates have slowed down because I am doing a major code refactor. It's going to take a while longer, but once complete it will make the tool more stable and open opportunities for more features.

Thanks for the additional details. I will email you with directions on how to fix this.

It is warning that there are joints (or other influences if you are not skinning to joint hierarchy) that were not skinned to. It might be fine, I will make a note to print more information to the script editor in a future update.

There is a 30 day limit for the download link. This is a Wix "feature" that I cannot change. If you could hit the upvote on this, it might help get this changed. As a workaround, when logged in you can go to this link to access the latest version as well as the archives and see release descriptions: https://www.rapidrig.com/download-rrm3 

Are you getting any errors in the script editor?

Not currently, but I will add it to the list of future features. I will try to roll that out with all the major code updates currently ongoing.