Did something change on rive.get_go()?

Questions
#1

Hello everyone.

I recently updated to editor 1.4.3 and subsequently updated the rive extension to the appropriate version. Right after updating, a problem appeared with the rive.get_go() function.

The error is simply that the bone wasn’t found, which is odd given that it had worked for months until this point. So before reporting for a bug I just wanted to make sure that nothing was changed about this function.

I did try to download my .riv file again but it still doesn’t work. I also noticed that the appearance of my rive model was apparently bugged (with no outline and strange positions)

Should I file for a bug report, or is there something I am not aware of?

Thank you for reading!

#2

Ah, yes.
Just like the Spine extension, we now have a check box that enables the creation of bones (default false).

For most objects we figure that the bones aren’t actually used, hence no need to create them by default.

3 Likes
#3

Thank you for your quick response! I just tested, problem solved.

While we are at it I thought I might share this with you, it only happens on Windows. As you can see my model is in the middle of an animation and missing some outline.

image
image1067×541 54.1 KB

It doesn’t pose any problem for now but I prefer sharing just in case.

#4

Hmm, that seems a bit odd. You are using the release 1.0 of the extension?

Perhaps @jhonny.goransson may be able to look at it.
Could you create an issue in the github repo for the extension?
And if possible, attach a problematic model.

#5

Yes it’s the 1.0 release. I tried to create a new model from scratch and the problem also appears so I’m going to link this one in the github issue :

image
image1168×439 22.9 KB

Edit : the bug has already been issued so I will second it!

2 Likes
#6

What’s the link to the issue? And is there a repro available?

#7

Link to the Issue :

1 Like