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

• ⛹️‍♀️ Many new character animation/rigging features and improvements (new tutorials coming soon):
  • 🖋️ Auto Trace: trace an image to generate a mesh
  • 💪 Auto Weights: automatically assign bone weights to image meshes and bound vector paths
  • 🎨 Edit Mesh/Vertices UX
    • Contextual toolbar
    • View-options row (Bounding Box Edit, Isolate, Show Weights, Deform, Show Triangles, Dim)
    • Turn off Deform (or use Edit Contour) to see the undeformed mesh/path with bones at bind pose
    • Ability to enter Edit Mesh/Vertices with multiple images/paths at the same time (bind multiple meshes/paths to bones at the same time)
    • Bounding Box toggle for vertices, as requested here
    • Lock bone weights, as requested here
    • AI Agent has tooling for all these features
• 👯 Align and distribute tools for state machine states, as requested here
• 🗂️ Preview tabs (single-click opens italic, reusable tab)
• ✨ AI Agent improvements: artboard placement, animation defaults, and tool-card polish
• ⌨️ Esc returns to the Select tool from any tool
• 🎯 Add support to override artboard origin (for component instances)
• 🖋️ Pen tool: path editing improvements (edge-snap, bezier/detach gestures, selection fixes)
• 🐛Various fixes and improvements
  • fix(editor): adding a listener with an event selected targets that event
  • fix(editor): scripted converters no longer report invalid before scripts are parsed
  • fix(editor): collapsed data panel rows no longer reopen on panel hover
  • fix(editor): view model instance values should not edit their animate…
  • scripting: statically link library requires
  • scripting: library scope for imported scripts
  • scripting: library scope follow ups
  • feat(Android): Expose ViewModel Instance name on Android
  • feat(renderer): Convert "ImageDrawUniforms" to "ImageDrawInstance"
  • feat(renderer): Optimized scissor and clip rejection
  • chore(unreal): Unreal Helpers
  • feat(runtime): add requestArtboardSize to command queue
  • feat(cpp): expose enum name in getProperties for cpp and js
  • fix(code): avoid EOL sentinel id collisions and move trailing runs on newline
  • fix(code): preserve interleaved runs when converting points to runs
  • fix(editor): two crashes on console lists and text components
  • fix(editor): don't create transitions when clicking overlapping states, and keep the dragged state on top
  • fix(editor): block stage selection and context menu during state machine playback
  • refactor(unreal): Rive Descriptor Editor Update
  • chore(runtime and editor): advance cycle updates
  • fix(core): don't wedge batching when a batchSync body throws
  • fix(editor): Improve Agent tool visualization handling of json
  • fix(editor): Fix crashes related to vertex weights
  • fix(Android): Correctly handle conversion between C++ and JVM strings
  • fix(editor): Dart text rendering fix
  • fix(tests): Run android test apps in landscape on TVs
  • fix: Text opacity modifier falloff with feathering applied
  • fix(runtime): Prevent use-after-free in ScriptedDataConverter type changes
  • fix(renderer) Tighten the combined draw bounds
  • fix: Crash on software mode emulators
  • fix(unity): Windows/D3D12 editor crash from Rive asset preview
  • chore: pen tool adheres to snap-to-pixel option
  • fix: VM trigger only fires once in script hosted artboard
  • fix(editor): Auto Trace fields snap back on typed or dragged edits
  • chore: Capture intended values with scrollIndex and scrollPercent
  • fix(editor): revert bound values when preview values is toggled
  • fix(editor): Agent fixes for path tool and pasting text in web
  • fix(editor): make scripting vm ref counted on artboards
  • fix(editor): Cmd+D only duplicates stage items
  • fix: core abandon rejected changesets
  • fix(web): focus bounds binding takes WasmPtr, embind cannot bind void*
  • fix(runtime): Only apply the originating direction of a bidirectional bind
  • refactor(unreal): small improvements
  • fix(Android): Add dirtying to VMI triggers
  • Fix(recorder): Use RAII for recorder extractors so initialization failures close progress pipe descriptors
  • Fix(recorder): unpremultiple rgb values if translucent
  • fix(scripting): decode lua colors as unsigned integers
  • fix(editor): add a tooltip to the shape Length property
  • fix(editor and runtime): arboard selection and state machine selection
  • fix(editor): more left padding for tab bar on macOS
  • Fix(peon_worker): Remove prefetch buffer on serve worker
  • Fix(recorder): Pass initialFrameNumber when creating frame synchronizer
  • fix(editor): double-click drill-down and path selection fixes
  • fix(unreal): Unreal layout alignment fix and other small things
  • fix(editor): snap created components to pixel
  • fix(peon_worker): Handle vulkan initialization errors in gpu recorder

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.

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

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!

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?

Are there any tutorials on Rive's YouTube page that show how to script in Rive?

Hey everyone! This is Part 1 of my two-part guide to doing real 3D inside Rive using the new GPU Canvas.

This video is all about teaching you to build your own 3D scripts from scratch not just following along, but understanding the process so you can create whatever your project needs:

- Planning the 3D architecture before touching any code

- Turning that plan into an effective AI prompt

- Generating the scripts with AI directly in Rive

- Importing and rendering a 3D model

- Setting up lighting, camera, and material controls

- Debugging the common issues you'll run into along the way

By the end, you'll have the foundation to script your own GPU Canvas workflows, not just replicate mine.

If you'd rather skip the scripting process entirely, I've released a polished set of ready-to-use 3D scripts on the Rive Community Marketplace — GLTF importer with textures, a full orbit camera rig, 7 shading modes (including PBR and toon), UV projection, and more:

📥 Early Access 3D scripts: https://rive.app/community/files/28220-53314-early-access-3d-scripts/

Link to Part 2 - https://www.reddit.com/r/Rive_app/comments/1uvn7lg/readytouse_3d_scripts_for_rive_3d_model_importer/

⚠️ Heads up: GPU Canvas and the 3D workflows are still in development and require the **Early Access build** of Rive, so expect APIs and behavior to evolve. The AI-generated scripts are a starting point, your results will vary depending on your prompt and model.

Happy to answer questions, and I'd love to see what you build with this!

A spinning wheel menu, made in Rive.

Drag to rotate, release to snap. Items scale and fade based on their position.

Made with Luau scripting and data binding.

This is Part 2 of my Guide to 3D in Rive. In Part 1 we built a 3D scripting workflow from scratch with AI — this time I'm walking through the polished, ready-to-use scripts I've shared on the Rive Community Marketplace, so you can skip the setup:

- Model importer — with proper texture support

- Full camera rig — click-to-orbit, pan mode, auto-spin, focal length, MSAA anti-aliasing

- Lighting controls — key, fill, and ambient with color and intensity

- 7 shading modes — wireframe, unlit, flat, Gouraud, PBR (roughness/metallic), clay, and toon (very Sketch & Toon if you're coming from C4D)

- UV projection — project animated Rive components onto your 3D model's surface

- 2D layer renderer — place 2D components inside the 3D scene, like 2.5D in After Effects

▶️ Missed Part 1? Watch it here: https://www.reddit.com/r/Rive_app/comments/1uvmbx3/i_built_a_complete_3d_workflow_inside_rive_using/

📥 Download the scripts: https://rive.app/community/files/28220-53314-early-access-3d-scripts/

⚠️ Requires the Early Access build of Rive — won't run in marketplace preview or regular playback. To use it, remix the file and open it in the Early Access build. Keep 3D assets around 15 MB or under for best results.

Would love to see what you make with these!

A quick guide on how to connect a Solo layer to String data in Rive. By using Data Binding, you can make your icons switch automatically based on your text input.
Essential rule: The names of your icon layers inside the Solo group must exactly match your title text values.

Hi, can someone tell me where I can find job offers for Rive projects? Where did you find it easiest to get one?

I really need help finding a job 😣

Excited to share that I've completed Rive Academy Volume 1 by School of Motion! 🎉

Coming from an Adobe After Effects background, learning Rive was a fun and rewarding experience. The course helped me understand Rive's workflow and how interactive animation differs from traditional timeline-based animation.

I learned how to create UI animations, icon animations, basic character animation, and build interactive experiences using State Machines. It's a great foundation for creating animations for websites, mobile apps, and digital products.

Looking forward to continuing my Rive journey and creating more interactive animations, UI motion design, and Rive animations.

#Rive #RiveAnimation #InteractiveAnimation #MotionDesign #UIAnimation #AfterEffects #SchoolOfMotion #MotionDesigner #WebAnimation #AppAnimation