Looking at the error, it seems that it might have been exported before, but perhaps failed, because it seems something has already been disconnected. I will add a check to avoid that error, but i think there might have been something else wrong with the rig prior to this export. Hard to say exactly what though.

Unreal Engine can handle the conversion from Y Up to Z Up, so you don't need to change that in Maya.

Can you provide more details? Are you loading the mesh group and the rig into the fields? Are you choosing "Export Skeleton and Mesh to FBX" or "Export Animation to FBX"? With "Show Stack Trace" enabled under the History menu in the script editor, are you getting any warnings or errors in the history section of the script editor?

How are you exporting the character from Maya? If you are exporting fbx, did you use the functionality in the"Export" tab in the RRM3 UI? This will strip out the rig and only output the joints.

Hello, RRM3 now has custom nodes so I can build more functionality while reducing the number of nodes. You can download and the RRM3 Node Plugin installer with the rig so your art director can open the rig. This blog post goes over the details: https://www.rapidrig.com/post/rrm3-simple-plug-in-now-available

Hello, If you can send me any error messages you are getting, that would help me debug the problem. If your proxies are broken at this stage and you have no backups or have not saved the proxies, you can try a couple options: 1. Save the proxy data file, then delete these proxies and load it back in. You may have to adjust some things back to the way they were if that method works. 2. Or, if you have a rig in your scene (which does not appear to be the case here, unfortunately) you can also load build proxies from the rig.

Good question, I saw the 5.5 video and it seems like there is some remapping happening with joint names. With RRM3, you can generate a Single Hierarchy skeleton using Unreal naming conventions and orientation, so in theory, that would just work. UE5.5 looks like it only supports bipeds for now so this likely wouldn't work on non-bipeds. Once I get the next big update pushed out, I will set aside some time to test UE5.5 with RRM3 and evaluate what work, if any would be required.

Squash and stretch in the head is a challenge due to the way joints by default handle scaling. It's possible to disable change the default setting of the joints, but scale does would not transfer to modules that are attached to the face, so it would give inconsistent behaviour. I'll do some testing and get back to you on this. For the ears, you can attach a module to the head. You could use an auxiliary module for a very basic setup, or go with an FK chain for long, floppy ears that require different directions, multiple joints, simulation, IK, etc. I intentionally did not include ears because the head module has a lot of complexity already.

Thanks for reporting this. I will need to add some checks for unit sizes and adjust the locators. I am doing a lot of code refactoring at the moment so it will be a bit of time before the next update. Would you be able to switch to centimeters when generating the proxies, and then switch back to meters after?

Hello Oseias, you may not have seen my reply buried below but you can download the RRM3 Nodes plugin here: https://www.rapidrig.com/download-rrm3 You can send the RRM3 Nodes plugin to your animator along with the rig so that they can open up the rig without needing a full license/installation. For more information, here is a blog post about this topic: https://www.rapidrig.com/post/rrm3-simple-plug-in-now-available

Hello, difficult to tell without seeing the before state, but is your mesh skinned to the Single Hierarchy Joints? If so, did you enable the "Connect Joint Scale" option when you generated the rig? You can check this by selecting any of the single hierarchy joints and seeing if there are connections to the scale channels.

There is a lot to unpack in these comments, and so rather than making a lengthy response, I have tried to address your concerns in what I hope is a fair solution. I have spent the past week writing a new plugin installer that is just the required nodes for opening scenes with RRM3 and requires no additional licensing. This plugin does not come with the UI or any other features. Simply the nodes I have written to construct the rigs so files can be opened without errors and have all the extended functionality I have written into RRM3. This can be shared within your team. You can read the blog post here: https://www.rapidrig.com/post/rrm3-simple-plug-in-now-available Dustin

I have uploaded BETA_2024_09_11 which has several fixes for control appearances and should resolve this issue when rebuilding the rig.

I believe you already have a node called "Pivot_Ctrl" that exists in your scene before you are generating your rig and you are hitting a name clash. Can you have a look at your scene and see if this is indeed the case? I am working on a major code refactor to handle this issue, but it's going to take some time.

Thanks for reporting this. I have a fix going in the next update that should address this. Through debugging this, I found a few more issues, especially with these fk controls that have a volume appearance. Fix will be in next week's update. Dustin

Good catch, I will have a fix for this in the next update, which should be available next week. The fix will require updating the proxies. Dustin

Thanks for finding this. I will get this fixed in the next update. Thank you!

This is usually due to the hierarchy not being consistent. The warning in unreal should tell you what specifically is the issue in the hierarchy. If not, you may have to manually inspect the hierarchies and see where there is an inconsistency. Either in a mismatched name or a joint having a different parent between the two skeletons.

I have released a new update that hopefully address this issue. For more info, check out the blog post: https://www.rapidrig.com/post/new-rrm3-version-info Apologies for the delay. This required doing some planning and work on the site which took some time to implement the best option I could come up with.

Hi Mariana, we spoke back and forth via email, but for others interested, the licensing is the same for all products, which can be found here: https://www.rapidrig.com/general-info On that page, click the "What can I use Rapid Rig for?" for more details.