When you drag and drop a Rive file (.riv) into the FUSE editor, FUSE automatically detects the exposed inputs from the Rive file and makes them available for data binding. Exposed inputs can include text fields, image slots, number values, and color inputs. These become the elements you can bind data to in FUSE.

​

For FUSE to detect an input, it must be explicitly exposed in the Rive editor. Unexposed inputs will not appear in FUSE and cannot be bound to data.

​

[SCREENSHOT: the FUSE editor with a .riv file being dragged in]

​

To bring a Rive file into FUSE, start by opening the FUSE graphics editor, then drag and drop your .riv file directly into the editor window. FUSE will automatically detect the Rive file's exposed inputs, and these detected inputs will then appear as bindable elements within FUSE.

​

The types of inputs FUSE can detect include the following:

​

• Text fields

• Image slots

• Number values

• Color inputs

​

Rive inputs must be explicitly exposed in the Rive editor for FUSE to see and bind them. If an input is not exposed in the Rive file, FUSE will not detect it and it will not be available for data binding.

​

Image slots in Rive must also be explicitly exposed for FUSE to populate them. Unexposed image slots will remain blank even if you attempt to bind data to them.

​

[SCREENSHOT: a Rive file's exposed inputs shown as bindable elements in the FUSE editor]

​

Once the Rive file is imported and FUSE has detected the exposed inputs, you can bind data to each element. For each exposed Rive input, you can either enter values manually (static text, fixed colors) or create FUSE expressions for dynamic data binding.

​

Manual entry is useful for fixed labels, while expressions connect to live data from the LIGR data hierarchy or external data sources.

​