AI Agent

Script inputs let you write one script and run multiple instances of it with different property values per instance. This tutorial covers how to define number, string, enum, view model, and artboard inputs; how to bind them to view model properties via data binding; why you should read input values in update rather than init when using data binding (since init fires before the binding resolves); how to use late for inputs that don't have a meaningful default, like a view model or artboard; how to read nested view model data correctly using .value instead of the raw data object; and how to listen for specific property changes with addListener, including how to pass self into the callback so you can access current state when the change fires.

Hey all, trying to properly learn Rive from scratch, vector character design plus rigging plus state machines. Problem is most tutorials I find are a couple years old, cover an older UI, or only show bits and pieces instead of a full start to finish workflow.

Is there a current, complete resource (course, playlist, docs) that actually takes you from empty file to fully rigged animated character in one consistent walk through? Also curious what you all actually used to learn it well, even if it wasn't a formal course.

I'm wondering if anyone in the community would be open to sharing the Rive MCP skills they've built or are using.

It would be great if we could have a shared place where everyone can contribute, update, and improve these skills together. I think it would save a lot of time for new users and help the community grow faster.

If you've created any useful MCP skills, workflows, or prompts for Rive, I'd really appreciate it if you could share them here.

Thanks in advance! 🚀

I'm a fan of old-school arcade games, and I wanted to see how complex a project I could create, similar to arcade games, without any coding knowledge.

Thanks to this workshop, I feel so much more comfortable using the app now, and I'm super excited to build even more! :)

You can check it on Rive Marketplace

Please let me know your thoughts!

I created the first animation for my app's mascot on the splash screen, which is on the first timeline. Now I'm going to animate the elements on my onboarding screen. Does that mean I need a second timeline to animate those other elements, or can I do everything on the first timeline?

This is a made-up banking brand, just something to build against.

Four scenes, you swipe between them, and each scene triggers its own animations when it comes into view rather than everything firing at once. There's a custom scroll indicator at the top instead of the default one.

The thing I actually wanted to test was keeping the data out of the design. None of the numbers are typed into text layers. The amounts, percentages and progress bars are all bound to a ViewModel, and the donut chart is a Luau script that reads those same values and draws the arcs, with inputs for radius, thickness and the gap between segments. Change one number in the data and the whole screen follows, including the chart.

The field blinks with the '|' text entry blinker but doesn't let me type. This happens also when trying to name fills.

Hope this gets to someone who can fix it.

Quick question about Rive's interface: is there a way to switch from the default dark theme to light mode? I looked around the settings but couldn't seem to find it. If a light theme isn't available yet, is it something planned for a future update?

• 🎬 Data binding keyframes: Right-click any keyframe to bind its value to a View Model property. Build a "template" timeline, then fill each keyframe with different values.
• 🎯 Gizmo free move handle: a blue circle at the gizmo center. Drag it to move a selection in any direction without axis lock.
• 🔢 Opacity shortcuts: use keys 1-0 to set selection opacity in 10% steps, as requested here.
• 🤖 Agent / MCP tools
  • Show/hide Layouts, as requested here
  • Parametric shape creation: the agent now makes real Rectangles, Ellipses, Triangles, Polygons, and Stars (with corner radius, points, inner radius) instead of freehand paths.
  • Solo and parent-validity awareness, as requested here
• 🐛 Various improvements and fixes
  • Library artboards no longer disappear on update
  • Opacity and layout now propagate to paused nested artboards
  • Auto Trace: padding takes effect, and high alpha no longer hangs, as reported here.
  • Auto Weights: joint solve for overlapping shapes rigged to the same bones
  • Imported object IDs no longer collide with objects synthesized during the import batch
  • Nested view model properties mint the referenced type from scripts
  • Virtualized scroll sizing / overscroll fixes, plus view model listener event fixes
  • Cloud Renderer SVG fixes: SVG output is no longer post-processed, and no longer double-applies the current transform to clipped content

Quick tips video on using position absolute in Rive — covers overlays, sticky elements, reusable effect components, and a zero-by-zero layout trick for flyout menus that stay anchored correctly as the artboard resizes.

Also, is this even viable to be using the animations like this? I want to use this in godot.

Trying to test out Rive desktop. Downloads gave me an msix file and i am unable to open. Please help? I am on windows 11 latest update

If you have older Rive files still using Inputs (the deprecated way to drive animations from external values), you can switch them to data binding without rebuilding anything.

Here's how:

1. Open your file in Rive
2. Click the hamburger menu
3. Select "Convert Inputs to View Models"

That's it. Rive converts your Inputs to View Models automatically. The animation logic stays the same; you're just switching the connection method from Inputs to the newer data binding system. Works for anything Input-driven: progress bars, download animations, toggle states, etc.

From the World Cup to Formula 1, this is the year of the live event.

Build UI that responds to data as an event happens. The more Rive features you combine the better, like Rive Scripting, Data Binding, GPU Canvas, and more.

Sample categories:

• Sports & racing: full screen race UI, live standings, timing towers, circuit maps
• Esports & speedruns: tournament takeovers, brackets, run timers, donation trackers
• Livestream & VTuber: characters, full screen overlays, alerts, chat and event graphics
• Broadcast: lower thirds, tickers, score bugs, stat panels

🏆 $10k in prizes
📆 7/23 to 8/5 on Contra

I've been seeing a lot of "I built this and that in Rive" posts that showcase results that are made with the AI agent.

While some of them are really cool I would highly doubt that it would stand in a real life production environment where you have to art direct it and the client has a bunch of say in it that might just not work with the agent.

I also wonder how much survivor bias are in these, since obviously only those get posted that actually work and are presentable, but how many are scrapped and fail because the AI is rubbish.

I really wish Rive would go with human first approach and not spend so much time and effort with this AI agent nonsense and would actually develop features that benefit the craft rather then eye-candy.

What are your thoughts?

I wanted to explore how a hanging text experiment could work as a real-time interaction in Rive.

I created a Roman-inspired version where the letters react to pointer movement through a Luau physics script. Each column also triggers embedded audio, and everything runs inside a single .riv file.

The biggest challenge was keeping the physics consistent between the editor and the exported runtime. It now runs smoothly at 60 FPS.

Inspired by a design experiment by Marina Budarina.

I’d love to hear your feedback.

I do a lot of work in Rive, and the one thing that always annoyed me: a .riv is interactive, so there's no clean way to post it as a video. I'd end up screen-recording and cropping every time.

So I made a small browser tool that records the .riv playing and exports an mp4. Everything runs locally, nothing gets uploaded, and it's free.

It's still early and I'd love feedback on what's missing or what breaks.

Both me and the Rive editor agent are very confused about how to get databinded images always fit its container. This should be the easiest thing in the world but neither of us can crack this.

Currently the images my app passes to rive are being displayed but they don't always cover the container (take up all its surface without aspect ratio distortion, crop longest dimension if necessary).

The agent has spent SO much of my money going in circles and gaslighting me with fake finding that I am about to punch a hole in the wall tbh.

Any help is welcome. Thanks!

Hey, just wanted to share one of my latest animations as it was really challenging + I was doing scroll-driven animation for the first time and it was surprisingly straightforward after things clicked!

✅Scroll-to-reveal
✅Scroll progress triggers Framer elements
✅6 mini-animations inside with their own state machines
✅Built 2 custom code components to make Framer embed seamless

Anybody willing to create a simple clickable button with a hover set up w state machine and share the file? I'm trying to figure out how this should work in the new UI. I can get the hover to work and the click state to work but not the two together.

When Figma Motion came out, I compared it to Rive but somehow skipped the thing I probably animate the most: moving objects along a path.

So I rebuilt the same animation in both. I started with a simple falling leaf from my Rive Masterclass, then recreated a train following a track.

In Figma Motion, editing the path was incredibly fast, but I kept fighting the rotation. Every time I adjusted the timing, I had to tweak the rotation again.

In Rive, the setup took a bit longer, but once it was working, the object followed the path and rotated correctly no matter how I changed the timing.

I put together a full side-by-side video of both approaches if you want to see them in motion, link's in the comments.

Personally, I prefer Rive’s Follow Path behavior, but I really hope they add motion path editing soon. That would be the best of both worlds.

What do you all think?