Blender rig exporter/animation importer

See Blender rig exporter/animation importer - #568 by Den_S.

can confirm this plugin conflict’s with @Maximum_ADHD 's ToolGripEditor
If either one of you could fix it, that’d be greatly appreciated.

Anyone seeing this error when importing and rebuilding rigs? What I put in was just the standard R15 Rig using the updated plugin. I’m using the newest Blender version, so does that have something to do with it?

2 Likes

It looks like an issue with the environment.
It seems you are using a new version of Blender, but its possible that the addon “RobloxtoBlenderAnimator.py” has not been updated. This could also mean deprecated features that are no longer supported. The error given is that it encoded your rig and stuff in the background, and its unable to find where it is when decoding it. JSON files are often encoded to compress it so that it takes less space. The JSONDecodeError is because its expecting something there, but a null value was given back. Try re-importing and rigging and see if that works. If not, you might have to wait for the libraries to be updated.

Make sure no warnings appear when selecting your rig in the Roblox plugin and that you use the correct addon version for your blender version.

Very cool plugin that I’ve used for a while.

But with this new update (or something, it might not be this!), after I select my rig model, the game starts running, and once I close out of the plugin Studio crashes… :thinking:

The tool seems completely broken for me.

exporting a fully welded rig:
image

turns into a mess without any weldConstraints and breaks the magazine motor6d constraint:
https://gyazo.com/85c81f57870299696ac0b0c18ee9835a

That is, if i can export at all due to multiple errors (blender ones i can’t catch, and roblox claiming it can’t find constraint linking x to x, which is most likely my own rigging)

This is a Studio bug.

Fix all issues with your rig first (check if the default Roblox animation editor handles it correctly) and make sure that the exporter plugin does not show any warnings, that most likely solves your issue.

I have an issue with this plugin.
When I close it, the studio crashed.

3 Likes

how do i use the 2.8 version i dont understand it its weird for me and idk how to select the rig and yeah

1 Like

pls can i have the link for the rig idk how to get one its not-understandable for me. thx if you want.

I am trying to import an animation to blender to the rig doesn’t seem to be working? Something with keying.

EDIT: It is saying it cannot map rig. If that helps

Screen Shot 2020-01-05 at 16.01.17.png

how i’m i able to fix this?

This is a Studio bug.

The rig you’re trying to import has different bone (names) than the auto-generated one. Import the FBX with the regular importer and check bone names inside of the armatures. Alternatively use some other more advanced bone mapping tool in Blender.

It looks like something is corrupted/majorly incorrect there, it might be an incorrect script or a script for an incorrect version. Would recommend starting over if you fail to solve it.

2 Likes

you got the 2.8 version in the discription i use 2.8? or is that 2.81? if not then thx i’ll try it anyway :slight_smile:

It’s compatible with 2.80, maybe works without changes in 2.81 (untested).

nvm thx allot for me some reason only works on 2.81 weird but thats fine i geuss.

Hmm, I don’t suppose you could fix the crashing issue since it’s a studio bug. I also noticed that if a rig has bones that have the same name it results in the rig becoming corrupt as in the bones don’t move the correct part or not moving anything at all. Might want to add that into the “Warnings”.

1 Like

Does the default animation editor support such rigs? If it does, I’ll be sure to add a warning for it (things the default editor already detects are not checked in this plugin).

Anyone else having this plugin crash studio when you close it? This has been a bug for me across multiple PCs for months

3 Likes