Hi, does new Evole allow for RIVE files to be embedded into pages?
Thank you.
Hi @Ciro_C at this time we don’t support using .riv files as assets - though that is something that has been talked about internally - so if that would be of interest, please let us know! Also if you have any more specifics around your requirement that would help.
In the meantime, you should be able to use Rive content within the iFrame element. In Rive, you can select Export > Generate Share Link. I think you should be able to use either the ‘Embed link’ or ‘Embed code’ version with our iFrame element.
Seconding that my organisation would be veeeerrry interested in Rive integration! We’ve tested it in legacy Evolve before but there was some limitations on the iFrame. Haven’t got around to testing it in new Evolve 
Editing just to say - have tested it in the new iFrame component and it’s working pretty well!
@Matt_Leathes Would be very interested in Rive file support, particularly if the files could be manipulated from the logic in Evolve to change their animation states, or vice versa; inputs in Evolve could communicate with the Rive file to make a change.
@LaurynS Out of interest, when you add it to an iframe, can you do this (have inputs in Evolve change a Rive animation state), or is it more of a hover-over or click to change the animation? (Hopefully that made sense!)
I don’t see how Evolve inputs could change the Rive state just yet, but I could see how you could potentially get creative with logic. Yes, it’s mostly just mouse-tracking and click to interact animations that are the benefit here.
I second (third?) adding Rive integration. Being able to use the State machine inside Rive and perhaps combine with Logic to be able to effect the SCORM a would be great.
The issue i run into with using Rive (or Lottie) with iFrames is due to the height not being auto calculated.
This means that at ‘full size’ the Rive element displays correctly (Figure A)
However if you have your browser window thinner than ‘full size’ the iFrame keeps the original specified height and you get excess spacing around elements (Figure B) that our Clients flag, and make the component unusable. (Does that make sense?)
Hopefully .Riv integration could fix that issue and open up many more opportunities! 
